Detections

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

4,916 detections

This query visualises total emails with Phish (BEC) - Impersonation detections over time.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0027
This query visualises total emails with Spoof - Composite Authentication fails summarizing the data daily.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0026
This query visualises top sender email addresses of inbound emails submitted as false negatives by users.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1026
This query visualises user submissions where admin also performed 'mark and notify' action on the submission
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0026
Visualises the top 10 users with click attempts on URLs in emails detected as malware, phishing, or spam, helping analysts identify risky user behaviour and potential targets.
Based on Defender for Office 365 workbook: https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/part-2-build-custom-email-security-reports-and-dashboards-with-workbooks-in-micr/4411303
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
3061
Visualises where URLs have been identified in emails, summarizing by location (for example: Attachment, header, body) to help analysts understand distribution and risk.
Based on Defender for Office 365 workbook: https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/part-2-build-custom-email-security-reports-and-dashboards-with-workbooks-in-micr/4411303
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0035
This query visualises top 10 subjects of intra-org emails submitted as false negatives by users.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1023
This query visualises the total ammount of user false negative submissions from the junk folder
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0023
Identifies the top 10 sender domains delivering inbound emails classified as malware, phishing, or spam.
Based on Defender for Office 365 workbook: https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/part-2-build-custom-email-security-reports-and-dashboards-with-workbooks-in-micr/4411303
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1053
Identifies the top 10 users receiving inbound emails classified as malware, phishing, or spam.
Based on concepts from the Defender for Office 365 solution in Sentinel: https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/part-2-build-custom-email-security-reports-and-dashboards-with-workbooks-in-micr/4411303
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
4153
This query visualises the total ammount of user false negative or false positive submissions by the verdict of the submission grading.
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0022
Identifies the top 10 external sender addresses delivering inbound emails classified as phishing.
If you want to exclude your own organization's domains (including subdomains), add a filter after the phishing filter, e.g.:
| where SenderFromAddress !contains ".yourdomain.com"
(Replace "yourdomain.com" with your actual domain.)
Based on Defender for Office 365 workbook: https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/part-2-build-custom-email-security-reports-and-dashboards-with-workbooks-in-micr/4411303
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1144
Detects suspicious use of an .exe extension after a non-executable file extension like .pdf.exe, a set of spaces or underlines to cloak the executable file in spear phishing campaigns
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
4059
This analytic detects when classic branch protection rules are disabled in GitHub Organizations. It monitors GitHub Organizations audit logs for `protected_branch.destroy` events, tracking actor details, repository information, and associated metadata. Identifying disabled branch protection is critical as it could indicate attempts to bypass code review requirements and security controls. Branch protection rules are essential security controls that enforce code review, prevent force pushes, and maintain code quality. Disabling these protections could allow malicious actors to directly push unauthorized code changes or backdoors to protected branches. The impact of disabled branch protection includes potential code tampering, bypass of security reviews, introduction of vulnerabilities or malicious code, and compromise of software supply chain integrity. This activity could be part of a larger attack chain where an adversary first disables security controls before attempting to inject malicious code.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0039
Identifies the top 10 external sender addresses delivering inbound emails classified as spam.
To exclude your own organization's domains (including subdomains), add a filter after the spam filter, e.g.:
| where SenderFromAddress !contains ".yourdomain.com"
(Replace "yourdomain.com" with your actual domain.)
Based on Defender for Office 365 workbook: https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/part-2-build-custom-email-security-reports-and-dashboards-with-workbooks-in-micr/4411303
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0034
This analytic detects the execution of PowerView PowerShell cmdlets `Get-ObjectAcl` or `Get-DomainObjectAcl`, which are used to enumerate Access Control List (ACL) permissions for Active Directory objects. It leverages Event ID 4104 from PowerShell Script Block Logging to identify this activity. This behavior is significant as it may indicate an attempt to discover weak permissions in Active Directory, potentially leading to privilege escalation. If confirmed malicious, attackers could exploit these permissions to gain unauthorized access or escalate their privileges within the network.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0036
The analytic detects when branch rulesets are deleted in GitHub Organizations. The detection monitors GitHub Organizations audit logs for branch ruleset deletion events by tracking actor details, repository information, and associated metadata. For a SOC, identifying deleted branch rulesets is critical as it could indicate attempts to bypass code review requirements and security controls. Branch rulesets are essential security controls that enforce code review, prevent force pushes, and maintain code quality. Disabling these protections could allow malicious actors to directly push unauthorized code changes or backdoors to protected branches. The impact of disabled branch protection includes potential code tampering, bypass of security reviews, introduction of vulnerabilities or malicious code, and compromise of software supply chain integrity. This activity could be part of a larger attack chain where an adversary first disables security controls before attempting to inject malicious code.
Splunk Security@SplunkSecurity
avatar
Splunk Security Content
1 year ago
0034
This query visualises the amount of total Malware detections of files located on SharePoint, OneDrive and Teams, summarizing by the locations they are stored
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
3030
This query helps reviewing quarantine release trend in Defender for Office 365
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
0030
Detects suspicious remote procedure call (RPC) service anomalies based on the spawned sub processes (long shot to detect the exploitation of vulnerabilities like CVE-2022-26809)
Yamato Security Hayabusa@YamatoSecurityHayabusa
avatar
Yamato Security Hayabusa Rules
1 year ago
1041
This query visualises the total amount of spam emails that are quarantined, summarized by the detection method
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1029
Page 184 of 235