-
Notifications
You must be signed in to change notification settings - Fork 594
[New Rule] Threat Intelligence Signal - Microsoft Defender for Office 365 #4994
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
terrancedejesus
wants to merge
6
commits into
main
Choose a base branch
from
4993-new-rule-threat-intelligence-signal---microsoft-defender-for-office-365
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+62
−0
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
967f02a
adding new rule 'Threat Intelligence Signal - Microsoft Defender for …
terrancedejesus 7fe23ba
added mitre mapping
terrancedejesus b8d3a8c
Update rules/integrations/o365/initial_access_defender_for_m365_threa…
terrancedejesus dcc3c68
Merge branch 'main' into 4993-new-rule-threat-intelligence-signal---m…
terrancedejesus 08346ca
added note for max signals
terrancedejesus 77d46d9
linted
terrancedejesus File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
62 changes: 62 additions & 0 deletions
62
rules/integrations/o365/initial_access_defender_for_m365_threat_intelligence_signal.toml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
[metadata] | ||
creation_date = "2025/08/19" | ||
integration = ["o365"] | ||
maturity = "production" | ||
promotion = true | ||
updated_date = "2025/08/19" | ||
|
||
[rule] | ||
author = ["Elastic"] | ||
description = """ | ||
Identifies a Microsoft 365 audit log generated for Threat Intelligence signals by Microsoft Defender for Office 365. | ||
Signals generated may relate to services such as Exchange Online, SharePoint Online, OneDrive for Business and others. | ||
""" | ||
false_positives = [ | ||
""" | ||
Signals are generated by Microsoft Defender for Office 365. False-positives may occur if legitimate user activity is | ||
misclassified as a threat. | ||
""", | ||
] | ||
from = "now-9m" | ||
index = ["filebeat-*", "logs-o365.audit-*"] | ||
language = "kuery" | ||
license = "Elastic License v2" | ||
max_signals = 1000 | ||
name = "Threat Intelligence Signal - Microsoft Defender for Office 365" | ||
note = "For information on troubleshooting the maximum alerts warning please refer to this [guide](https://www.elastic.co/guide/en/security/current/alerts-ui-monitor.html#troubleshoot-max-alerts).\n" | ||
references = [ | ||
"https://learn.microsoft.com/en-us/purview/audit-supported-services", | ||
"https://www.octiga.io/en-gb/insights/nist-csf-for-office-365", | ||
"https://learn.microsoft.com/en-us/office/office-365-management-api/office-365-management-activity-api-schema", | ||
] | ||
risk_score = 47 | ||
rule_id = "60c814fc-7d06-11f0-b326-f661ea17fbcd" | ||
severity = "medium" | ||
tags = [ | ||
"Domain: Cloud", | ||
"Domain: SaaS", | ||
"Data Source: Microsoft 365", | ||
"Data Source: Microsoft 365 Audit Logs", | ||
"Use Case: Threat Detection", | ||
] | ||
timestamp_override = "event.ingested" | ||
type = "query" | ||
|
||
query = ''' | ||
event.dataset: "o365.audit" and event.code: "ThreatIntelligence" | ||
''' | ||
|
||
|
||
[[rule.threat]] | ||
framework = "MITRE ATT&CK" | ||
[[rule.threat.technique]] | ||
id = "T1566" | ||
name = "Phishing" | ||
reference = "https://attack.mitre.org/techniques/T1566/" | ||
Comment on lines
+50
to
+55
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this true for all generated signals? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
|
||
|
||
[rule.threat.tactic] | ||
id = "TA0001" | ||
name = "Initial Access" | ||
reference = "https://attack.mitre.org/tactics/TA0001/" | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to adjust this event in the integrations to gave
event.kind
set toalert
, so we automatically push an alert for it using the default promotion rule?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great question. Honestly I do not see why not other than keeping them separate for our visibility. Checking telemetry, I see we have several promotions for compliance related alerts. Based on docs from MSFT, this seems to be a good fit for adjusting
event.kind
toalert
. The only other consideration is max signals for external alerts and potentially missing these if the threshold is hit because of compliance related alerts that are noisy. I'd rather keep separate as a rule.