Detections

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

414 detections

'An account could be blocked if there are too many failed authentication attempts in a row. This hunting query identifies if a MFA user account that is set to blocked tries to login to Microsoft Entra ID.
This query has also been updated to include UEBA logs IdentityInfo and BehaviorAnalytics for contextual information around the results.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2099
'This detection identifies high-severity alerts across various Microsoft security products, including Microsoft Defender XDR and Microsoft Entra ID, and correlates them with instances of Google Cloud VM creation. It focuses on instances where VMs were created within a short timeframe of high-severity alerts, potentially indicating suspicious activity.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2093
Looks for a new MFA method added to an account that was preceded by medium or high risk sign-in session for the same user within maximum 6h timeframe
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
4071
'This hunting query identifies updates to the RequiredResourceAccess property of an OAuth application.
This property specifies resources that an application requires access to and the set of OAuth permission scopes and application roles that it needs under each of those resources.
This pre-configuration of required resource access drives the consent experience. The resourceAccess property of the requiredResourceAccess type is a collection of ResourceAccess.
A threat actor might update this property before granting permissions to an application.
'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2067
'Detects successful signins using single factor authentication where the device, location, and ASN are abnormal.
Single factor authentications pose an opportunity to access compromised accounts, investigate these for anomalous occurrencess.
Ref: https://docs.microsoft.com/azure/active-directory/fundamentals/security-operations-devices#non-compliant-device-sign-in'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
3066
'Looks for new device registrations following a risky user account sign-in. By default the
query will use a 6 hour lookback period, this can be configured within the query.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2061
This query shows authentication methods being added and devices registered around the time of a high risk sign in which could indicate an attempt to establish persistence on a compromised account. The threshold can be changed to a wider timeframe if needed.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
8062
'Highlights accounts associated with multiple authentications from different geographical locations in a short period of time.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2056
'Identifies when the Azure Run Command operation is executed by a UserPrincipalName and IP Address that has resulted in a recent user entity behaviour alert.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
5156
'Summarize all the failures and success events for all users in the last 24 hours,
only identify users with more than 100 failures in the set period'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2052
'This query examines Microsoft Entra ID sign-ins and identifies anomalous changes in a user's location profile. A variation joins results back onto the original sign-in data to review the location set with each identified user in tabular form.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2049
'Detects a Service Principal being assigned an app role that has sensitive access such as Mail.Read.
A threat actor who compromises a Service Principal may assign it an app role to allow it to access sensitive data, or to perform other actions.
Ensure that any assignment to a Service Principal is valid and appropriate.
Ref: https://docs.microsoft.com/azure/active-directory/fundamentals/security-operations-applications#application-granted-highly-privileged-permissions'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0049
' Identifies failed MFA attempts from Privileged accounts. Privileged accounts list can be based on IdentityInfo UEBA table or built-in watchlist.
Ref : https://docs.microsoft.com/azure/active-directory/fundamentals/security-operations-privileged-accounts#things-to-monitor'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1048
'Query for new sign-ins from stale/inactive accounts. UEBA filters based on ActivityInsights. Results for accounts created in the last 7 days are filtered out.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
8048
'Identifies a match across various data feeds for domains, hashes and IP IOC related to Mercury
Reference: https://www.microsoft.com/security/blog/2022/08/25/mercury-leveraging-log4j-2-vulnerabilities-in-unpatched-systems-to-target-israeli-organizations/'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0048
'Identifies accounts that have been added to a PIM managed privileged group'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2045
'Identifies IPs with failed attempts to sign in to one or more disabled accounts signed in successfully to another account.
This analytic will additionally identify the successful signed in accounts as the mapped account entities for investigation.
References: https://docs.microsoft.com/azure/active-directory/reports-monitoring/reference-sign-ins-error-codes
50057 - User account is disabled. The account has been disabled by an administrator.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
9045
'This query looks for unfamiliar Sign-in's thats not seen recently for the given user
with azure portal login attempts and audit logs to help detect and reduce the analysis timeline for defenders'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1044
'Compares the current day to last 14 days of audits to identify new audit activities. Useful for tracking malicious activity related to user/group additions/removals by Azure Apps and automated approvals.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2042
'Compares current day to last 14 days of audits to identify new audit activities. Useful for tracking malicious activity related to user/group additions/removals by specific users.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0039
'Identifies a match across various data feeds for domains related to an actor tracked by Microsoft as Star Blizzard.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1039
Page 16 of 20