Describe the behaviour you want to detect. SARA writes a starting Sigma rule with MITRE tags, false-positive guidance, and detection-engineering context. Anonymous, no account, best-effort generic detection.
VALIDT1190
Sigma rule
title: Potential CVE-2024-21762 FortiOS SSL VPN Exploitation Attempt
id: bb8a7128-ace7-488b-851e-bb9460e2c7b9
date: 2026-08-18
status: experimental
description: >
Detects potential exploitation of CVE-2024-21762, an out-of-bounds write vulnerability
in Fortinet FortiOS SSL VPN. This rule looks for suspicious HTTP requests targeting
the /remote/error endpoint with specific query parameters or anomalous HTTP methods
that match known exploit patterns. This rule is a starting point — tune for your environment.
references:
- https://nvd.nist.gov/vuln/detail/CVE-2024-21762
- https://www.fortiguard.com/psirt/FG-IR-24-015
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
author: SARA Detection Engineering
tags:
- attack.initial_access
- attack.t1190
logsource:
category: proxy
product: null
detection:
selection_target:
cs-uri-stem|contains|all:
- '/remote/error'
selection_param:
- cs-uri-query|contains: 'errcode='
- cs-method:
- 'PUT'
- 'DELETE'
- 'PATCH'
filter_legit:
cs-user-agent|contains:
- 'FortiClient'
- 'Fortinet'
condition: selection_target and selection_param and not filter_legit
fields:
- c-ip
- cs-method
- cs-uri-stem
- cs-uri-query
- cs-user-agent
- sc-status
falsepositives:
- Legitimate FortiClient or Fortinet management traffic interacting with the error page
- Custom network monitoring or vulnerability scanners checking SSL VPN availability
level: high
Sigma is the open, vendor-neutral format for log-based detections. One rule, written once, converts to Splunk SPL, Elastic ES|QL, KQL for Microsoft Sentinel, Sumo, Chronicle, QRadar, and more. Detection engineers love it for the same reason ATT&CK is the lingua franca for tactics — Sigma is the lingua franca for the queries that detect them.
GuideHow to use this tool
Describe the behaviour you want to detect in plain English. Be specific — "PowerShell encoded command spawned by an Office process" wins over "PowerShell abuse".
SARA writes a starting Sigma rule with the right logsource, fields, MITRE ATT&CK tags, and false-positive guidance.
Copy the YAML or convert to your target backend. Then tune the rule for your environment — the output is a starting point, not a tested artifact.
When to useWhen is the Sigma generator the right move?
Closing a coverage gap fast
You've got a fresh write-up of a TTP and need a starting detection in your stack today. Generate, tune, ship.
Onboarding a junior detection engineer
Pair-program with SARA: the generator produces the skeleton, the engineer learns by tuning, the team commits the result.
Translating between backends
You have a rule in one query language; describe it in English and get the Sigma version + conversions to every other backend.
Sanity-checking a hypothesis
Sketch a detection idea in 30 seconds before investing in a full DE sprint.
API
Want this in your SOAR or SIEM?
SARA Open ships an OpenAI-compatible API. Call POST /api/v1/sigma — Plain English in, valid Sigma YAML out, with MITRE tags and false-positive guidance.