O365 message trace detections: support o365:graph:messagetrace (Office 365 add-on 6.x) - #4286
Open
sbaker-gre wants to merge 2 commits into
Open
sbaker-gre wants to merge 2 commits into
sbaker-gre wants to merge 2 commits into
Conversation
sbaker-gre
requested review from
P4T12ICK,
RavenTait,
ljstella,
nasbench,
onurmerdogan,
patel-bhavin,
pyth0n1c,
rosplk and
tccontre
as code owners
September 23, 2026 19:26
Splunk Add-on for Microsoft Office 365 6.x collects message trace through Microsoft Graph and emits sourcetype o365:graph:messagetrace with camelCase fields (senderAddress, recipientAddress, messageId, status) instead of the PascalCase fields of the retired Reporting web service sourcetypes. - Add o365:graph:messagetrace to the o365_messagetrace macro. - Switch the four dependent detections from raw field names to the CIM fields the add-on aliases for both sourcetypes: status_code, recipient, src_user, message_id. Behaviour is unchanged on the legacy sourcetypes. - Replace the Organization field, which the Graph sourcetype does not carry, with a sender-domain vs recipient-domain comparison. - Update drilldowns to use recipient. Affected: O365 Email Password and Payroll Compromise Behavior, O365 Email Receive and Hard Delete Takeover Behavior, O365 Email Send and Hard Delete Exfiltration Behavior, O365 Email Send Attachments Excessive Volume. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Second test per detection replays the same four suspect messages in the o365:graph:messagetrace shape (companion attack_data change adds o365_graph_messagetrace_suspect_events.log). The legacy test is kept to prove backward compatibility with o365:reporting:messagetrace. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
sbaker-gre
force-pushed
the
fix/o365-messagetrace-graph-sourcetype
branch
from
September 23, 2026 19:32
c9e65bd to
1f742a2
Compare
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #4285.
Splunk Add-on for Microsoft Office 365 6.x emits message trace as
o365:graph:messagetracewith camelCase fields. The four message trace detections and their macro only handled the
retired Reporting web service sourcetypes and PascalCase raw fields, so they return nothing
on a current add-on.
Changes
macros/o365_messagetrace.yml: addo365:graph:messagetrace.sourcetypes:
Status→status_code,RecipientAddress→recipient,SenderAddress→src_user,MessageId→message_id. Drilldowns updated to match.Organization(absent on the Graph sourcetype) replaced with a sender-domain vsrecipient-domain comparison in the two exfiltration-style detections.
Legacy test retained to prove backward compatibility with
o365:reporting:messagetrace.Detections
Verification
contentctl-ng buildpasses.o365:graph:messagetracedata (add-on 6.0.2), all five CIM fields are populatedon 2,000 of 2,000 sampled events. Graph
statusvalues are lowercase (delivered);the
status_code=Deliveredfilter is in the base search where value matching iscase-insensitive, so it matches both.
🤖 Generated with Claude Code