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 Ivanti CSA Path Traversal Exploitation CVE-2024-8963
id: 3f2a7fc0-c822-40c2-a414-51a23114a475
status: experimental
description: |
Detects potential exploitation of CVE-2024-8963, a path traversal vulnerability in Ivanti Cloud Services Application (CSA).
Attackers use encoded "../" sequences in HTTP requests to escape the web root and read arbitrary files.
This rule looks for characteristic path traversal patterns in HTTP URIs targeting Ivanti CSA endpoints.
Note: This rule is a starting point — tune for your environment.
references:
- https://www.cisa.gov/news-events/alerts/2024/10/03/cisa-adds-one-known-exploited-vulnerability-catalog
- https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Cloud-Services-Application-CSA-Path-Traversal-CVE-2024-8963
- https://www.rapid7.com/blog/post/2024/10/04/etr-cve-2024-8963-ivanti-cloud-services-application-csa-path-traversal/
author: SARA Detection Engineering
date: 2026-08-15
tags:
- attack.t1190
- attack.initial_access
logsource:
category: webserver
product: ""
detection:
selection_traversal:
cs-uri-query|contains:
- "%2f..%2f"
- "%2F..%2F"
- "/..%2f"
- "%2f../"
- "..%2f..%2f"
- "..%5c..%5c"
- "/..%5c"
filter_legitimate_scanners:
cs-user-agent|contains:
- "Qualys"
- "Nessus"
- "Tenable"
- "Rapid7"
condition: selection_traversal and not filter_legitimate_scanners
fields:
- c-ip
- cs-method
- cs-uri-query
- cs-user-agent
- sc-status
falsepositives:
- Legitimate vulnerability scanners running authorized assessments against the CSA management interface.
- Misconfigured load balancers or reverse proxies appending unexpected path segments.
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.