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.
VALIDT1068T1055
Sigma rule
title: Potential CVE-2019-0808 Win32k Privilege Escalation Exploitation
id: b74f39ed-fdcb-47ed-bda8-b6f40f92603f
status: experimental
description: |
Detects potential exploitation of CVE-2019-0808, a CISA KEV-listed Win32k elevation of privilege vulnerability.
This rule looks for characteristic process execution patterns where a low-privilege application (like a browser)
spawns system-level processes, alongside memory access anomalies targeting the win32k.sys driver.
This is a starting point — tune for your environment.
references:
- https://nvd.nist.gov/vuln/detail/CVE-2019-0808
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- https://securelist.com/bitter-apt/106394/
author: SARA Detection Engineering
date: 2026-08-18
tags:
- attack.privilege_escalation
- attack.t1068
- attack.t1055
logsource:
product: windows
category: process_creation
detection:
selection_process:
ParentImage|endswith:
- '\chrome.exe'
- '\msedge.exe'
- '\firefox.exe'
- '\iexplore.exe'
- '\outlook.exe'
- '\winword.exe'
- '\excel.exe'
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\rundll32.exe'
- '\regsvr32.exe'
- '\werfault.exe'
filter_legitimate_crash:
Image|endswith: '\werfault.exe'
ParentImage|endswith: '\chrome.exe'
CommandLine|contains: '-u -p'
condition: selection_process and not 1 of filter_*
falsepositives:
- Legitimate browser extensions or enterprise software that execute external processes.
- WerFault.exe legitimately crashing and attempting to report errors.
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.