1. Resources
  2. Detection rules
Sigma · Splunk · Sentinel · QRadar

Detection rules for identity attacks

408 identity attacks across 13 platforms, each mapped to MITRE ATT&CK and the threat groups that use it, with Sigma rules and ready-to-use Splunk, Sentinel and QRadar queries.

Platforms
13
Techniques covered
101
Tactics
14
Attacks
408
Sigma rules
1083

408 attacks across 13 platforms

Download the full pack

The whole library in one archive: 408 attacks and 1083 rules as Sigma files, plus 1067 Splunk, 995 Sentinel and 700 QRadar queries. A rule has a SIEM query only where a faithful conversion exists. The README covers macros, tables and tuning. We email the download link to your work address.

Frequently asked questions

How are the Splunk, Sentinel and QRadar queries produced?

Every rule is written once in Sigma, the open detection format, and converted at build time with pySigma: the official Splunk and Kusto backends for SPL and KQL, and Forestall’s own AQL backend for QRadar. Sentinel queries are checked against the Log Analytics table schemas. When a rule cannot be expressed faithfully for a SIEM, the page says why instead of showing a guessed query. Two approximations are published, each with a note beside the query: some QRadar queries search the raw event payload for a value or leave out the condition on whether the operation succeeded, because QRadar has no property for it, and Splunk matches on values inside JSON objects are substring searches on the raw event.

Can I use the rules commercially?

Yes. The rules are released under the Detection Rule License (DRL) 1.1: use, modify and share them, including in commercial products and services, as long as you credit Forestall.

Which log sources do I need?

Active Directory rules use the Security event log of domain controllers (with the relevant advanced audit policies); the forged-ticket rules use the System log of domain controllers, where the Key Distribution Center writes its events. Cloud rules use Microsoft Entra ID sign-in and audit logs, the Azure Activity log, AWS CloudTrail, Google Cloud Audit Logs and the GitHub audit log. A few rules need a log that is off until you turn it on, such as Microsoft Graph activity logs, Key Vault resource logs or AD FS auditing, and each of those rules says so. Rules for Microsoft 365, Exchange, Intune, Oracle Cloud, GitLab, CyberArk and Ping Identity use each product’s own audit log. Each rule lists its log source and the fields it relies on, and each query says which connector or add-on it assumes.

How does this relate to Forestall?

Detection tells you an attack is happening. Forestall finds the exposures that make each attack possible (over-privileged accounts, risky permissions and misconfigurations) so you can remove them before anyone tries. That applies to the platforms Forestall scans: Active Directory, Entra ID, Azure, Microsoft 365, AWS, Google Cloud and GitHub. Rules for the other platforms are vendor-neutral, and each page says so.

Where do the techniques, tactics and threat groups come from?

From MITRE ATT&CK® Enterprise v20.1. Each attack is mapped to its ATT&CK techniques and tactics, and the threat groups listed are the ones ATT&CK records as using those techniques. © The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.

Detect it, then make it impossible.

Forestall maps the identity exposures and attack paths behind these techniques across AD, Entra ID and cloud. Read-only and agentless.

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.