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.
VALIDT1059.003T1059.001T1218.011
Sigma rule
title: Potential CVE-2015-0310 Exploitation Adobe Flash Child Process Execution
id: 966ac5f9-e026-469d-84f6-fc5cb2b50bb1
date: 2026-08-18
status: experimental
description: >
Detects potential exploitation of CVE-2015-0310, a use-after-free vulnerability in Adobe Flash Player.
CVE-2015-0310 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
This rule identifies Adobe Flash Player spawning suspicious child processes (system shells, LOLBins),
which is characteristic of successful Flash exploitation via drive-by downloads or malicious Office documents.
Starting point — tune for your environment.
references:
- https://nvd.nist.gov/vuln/detail/CVE-2015-0310
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
author: SARA Detection Engineering
tags:
- attack.execution
- attack.t1059.003
- attack.t1059.001
- attack.t1218.011
logsource:
category: process_creation
product: windows
detection:
selection_flash_parent:
ParentImage|endswith:
- '\flashplayerplugin.exe'
- '\flashplayerapp.exe'
- '\flash.ocx' # Surrogate process for embedded ActiveX in Office/IE
selection_susp_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\rundll32.exe'
- '\regsvr32.exe'
- '\mshta.exe'
condition: selection_flash_parent and selection_susp_child
falsepositives:
- Legitimate interactive Flash content invoking local helper scripts (extremely rare in modern environments)
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.