References

Browse the catalog#

Detection Rule Catalog: Catalog-relevant rules from Sigma, Elastic, Splunk, Kusto, and Chronicle, grouped by MITRE ATT&CK tactic and technique
ATT&CK Coverage Graph: Lays out the MITRE ATT&CK matrix as tactic columns with technique cells, each showing event and rule coverage; per-technique pages list contributing events and rules with a cross-vendor event coverage matrix

Lookup tables#

Logon Type: Values in Security events 4624, 4625, 4648
Access Mask: Bitmask values for file, registry, AD, and SAM objects in Security events 4656, 4657, 4661, 4662, 4663
Process Access Rights: Bitmasks in Sysmon event 10 and Security event 4663
Privilege Constants: Values in Security events 4672, 4673, 4674
UAC Flags: Bitmask flags in Security events 4738, 4720
NTSTATUS Codes: Complete table from Windows 11 25H2

Platform coverage matrices#

Non-Windows rules organized by each platform's native action vocabulary, across all vendors:

AWS Coverage: CloudTrail rules grouped by event source and event name
Azure AD Coverage: Entra ID rules grouped by audit category and sign-in result
Entra ID Sign-In Telemetry: Sign-in log tables, ResultType error codes, and key detection fields for interactive, non-interactive, service principal, and managed identity sign-ins
GCP Coverage: Google Cloud Audit Log rules grouped by service and method
M365 Coverage: Microsoft 365 audit rules grouped by workload and operation
Okta Coverage: Okta System Log rules grouped by event type

Vendor coverage reports#

Per-vendor mappings to Windows catalog events; each also links its non-Windows rules out to the platform matrices above.

Sigma Rule Coverage: Sigma rule mappings to catalog events, by event and provider
Elastic Rule Coverage: Elastic rule mappings to catalog events, by event and provider
Elastic Inferred Detection Coverage: Inferred Elastic rule-to-event mappings at medium and low confidence
Splunk Rule Coverage: Splunk rule mappings to catalog events, by event and provider
Kusto Rule Coverage: Microsoft Sentinel and Defender XDR rule mappings to catalog events, by event and provider
Chronicle Rule Coverage: Chronicle/YARA-L rule mappings to catalog events, by event and provider

Field guides#

Collection Priority: Which events to collect first, ranked from authoritative sources (Microsoft, Australian Signals Directorate, Yamato Security, and more)

Using this site#

Search and Filter Syntax: Search operators, filter syntax, and keyboard shortcuts

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)