-
Notifications
You must be signed in to change notification settings - Fork 441
0xC0FFEEEE - O365 Suspicious Mailbox Rule Created #3336
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
Merged
Merged
Changes from 7 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
e23ed50
O365 Suspicious Mailbox Rule Created
0xC0FFEEEE a8a5ac8
Merge branch 'develop' into susmailrule
patel-bhavin b4783e0
remove enabled_by_default
0xC0FFEEEE be4fcbe
Merge branch 'develop' into susmailrule
0xC0FFEEEE f9c28cc
minor changes to ensure CI testing works
patel-bhavin f738531
Merge branch 'develop' into susmailrule
patel-bhavin 6dd60e8
Merge branch 'develop' into susmailrule
pyth0n1c 7e9f150
add url toolbox requirement
0xC0FFEEEE 10d1435
Update detection name
0xC0FFEEEE ff747d4
Merge branch 'develop' into susmailrule
0xC0FFEEEE aedca32
Merge branch 'develop' into susmailrule
patel-bhavin 9d23cc4
simplify SPL & add threat object
0xC0FFEEEE ff7729e
Merge branch 'develop' into susmailrule
0xC0FFEEEE 6ff8fe0
Merge branch 'develop' into susmailrule
patel-bhavin e1b41cc
Merge branch 'develop' into susmailrule
patel-bhavin d5feba1
drilldown update- minor
patel-bhavin 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
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,57 @@ | ||
| name: O365 Suspicious Mailbox Rule Created | ||
| id: 603ebac2-f157-4df7-a6ac-34e8d0350f86 | ||
| version: 1 | ||
| date: '2025-02-14' | ||
| author: '0xC0FFEEEE, Github Community' | ||
| type: TTP | ||
| status: production | ||
| description: This analytic detects suspicious mailbox rule creation, a common technique used in Business Email Compromise. It uses a scoring mechanism to identify a combination of attributes often featured in mailbox rules created by attackers. | ||
| This may indicate that an attacker has gained access to the account. | ||
| search: '`o365_management_activity` Workload=Exchange Operation="New-InboxRule" | rename Parameters{}.* | ||
| as * | eval temp=mvzip(Name,Value, "<JOIN>") | fields - Name Value | mvexpand temp | ||
| | eval temp_name=mvindex(split(temp,"<JOIN>"),0), temp_value=mvindex(split(temp,"<JOIN>"),1) | ||
| | eval {temp_name}=temp_value | stats values(Name) as Name, values(MarkAsRead) as | ||
| MarkAsRead, values(MoveToFolder) as MoveToFolder by _time Id user | lookup ut_shannon_lookup word as Name | ||
| | eval entropy_score=if(ut_shannon<=2, 1, 0) | eval len_score=if(len(Name)<=3, 1, | ||
| 0) | eval read_score=if(MarkAsRead="True", 1, 0) | eval folder_score=if(match(MoveToFolder, | ||
| "^(RSS|Conversation History|Archive)"), 1, 0) | eval suspicious_score=entropy_score+len_score+read_score+folder_score | ||
| | where suspicious_score>2 | `o365_suspicious_mailbox_rule_created_filter`' | ||
| how_to_implement: You must install the Splunk Microsoft Office 365 Add-on and ingest | ||
| Office 365 management activity events. | ||
0xC0FFEEEE marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| known_false_positives: Short rule names may trigger false positives. Adjust | ||
| the entropy and length thresholds as needed. | ||
| references: | ||
| - https://attack.mitre.org/techniques/T1564/008/ | ||
| drilldown_searches: | ||
| - name: View the detection results | ||
| search: '%original_detection_search%' | ||
| earliest_offset: $info_min_time$ | ||
| latest_offset: $info_max_time$ | ||
| - name: View risk events for the last 7 days for $user$ | ||
| search: '| from datamodel Risk.All_Risk | search normalized_risk_object="$user$" starthoursago=168 endhoursago=1 | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`' | ||
| earliest_offset: $info_min_time$ | ||
| latest_offset: $info_max_time$ | ||
| rba: | ||
| message: A suspicious mailbox rule was created by $user$ | ||
| risk_objects: | ||
| - field: user | ||
| type: user | ||
| score: 25 | ||
| threat_objects: [] | ||
| tags: | ||
| analytic_story: | ||
| - Office 365 Account Takeover | ||
| asset_type: O365 Tenant | ||
| mitre_attack_id: | ||
| - T1564.008 | ||
| product: | ||
| - Splunk Enterprise | ||
| - Splunk Enterprise Security | ||
| - Splunk Cloud | ||
| security_domain: audit | ||
| tests: | ||
| - name: True Positive Test | ||
| attack_data: | ||
| - data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1564.008/o365/o365_suspicious_mailbox_rule.log | ||
| sourcetype: o365:management:activity | ||
| source: o365 | ||
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.
Uh oh!
There was an error while loading. Please reload this page.