Detections

Explore public detection logic contributed by the community across SIEM and rule languages.

3,865 detections

Identifies when an organization doesn't have the proper license for PIM and is out of compliance.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Identifies when a privilege role assignment has taken place outside of PIM and may indicate an attack.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Identifies when the same privilege role has multiple activations by the same user.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Identifies when a privilege role can be activated without performing mfa.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Identifies when a user has been assigned a privilege role and are not using that role.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Monitor and alert for device registration or join events where MFA was not performed.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Detects risky authentication from a non AD registered device without MFA being required.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Monitor and alert for sign-ins where the device was non-compliant.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Monitor and alert for Sign-ins by unknown devices from non-Trusted locations.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Device code flow is an OAuth 2.0 protocol flow specifically for input constrained devices and is not used in all environments.
If this type of flow is seen in the environment and not being used in an input constrained device scenario, further investigation is warranted.
This can be a misconfigured application or potentially something malicious.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Detects when an account is disabled or blocked for sign in but tried to log in
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Alert on when legacy authentication has been used on an account
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
User has indicated they haven't instigated the MFA prompt and could indicate an attacker has the password for the account.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Detects when there is a interruption in the authentication process.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
Detects a successful login to the Microsoft Intune Company Portal which could allow bypassing Conditional Access Policies and InTune device trust using a tool like TokenSmith.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
6 months ago
000
KQL Query from file: Admin consent for M365 Connector for Claude
avatar
Steven Lim@KQLWizard
avatar
SlimKQL 2026
7 months ago
650919
This rule detects the presence of newly exposed risky web components, such as administrative panels or development tools, that have been discovered by Microsoft Defender External Attack Surface Management (EASM). The rule identifies components from a predefined list of 'risky_components' that have been seen for the first time within the last 7 days, indicating a recent exposure that could increase the attack surface.
avatar
Tech Creaatives@Techcreaatives
avatar
Detections.ai Community
7 months ago
151332
KQL Query from file: M365 Connector for Claude Detection
avatar
Steven Lim@KQLWizard
avatar
SlimKQL 2026
7 months ago
571860
Detects multiple multi-factor authentication (MFA) attempts that are denied or ignored by a user beyond a defined threshold within a specific lookback window. This behavior is indicative of an MFA fatigue attack, where an adversary repeatedly sends MFA requests to a user in hopes they will eventually approve one to stop the annoyance.
avatar
A’Keem Gurley@MFA_meex
avatar
Detections.ai Community
7 months ago
301440
This rule detects two related scenarios: 1. Device Code Phishing: Correlates successful device code authentications with subsequent device registrations for the same user within a short time frame. This can indicate an attacker using a phished device code to register a new device. 2. Primary Refresh Token (PRT) Device Registration: Identifies device registrations that occur after an authentication to the Device Registration Service using a Primary Refresh Token. This pattern is indicative of an attacker minting a PRT and then using it to register or join a device, potentially bypassing conditional access policies.
avatar
F S@Fsdr
avatar
Detections.ai Community
7 months ago
621666
KQL Query from file: KQL Detection for MDI Password Protection Insight
avatar
Steven Lim@KQLWizard
avatar
SlimKQL 2026
7 months ago
451570
Page 137 of 185