Update Suspicious SharePoint document name#3965
Merged
Conversation
Adding newly observed pattern
github-actions
Bot
added
the
in-test-rules
Remove check for internal SharePoint shares in detection rule.
Member
Author
|
hunt showing latest exclusive matches on the ms exchange removal... there are some FPs but I'm tolerant of them for the # of FNs we resolve. https://platform.sublime.security/messages/hunt?huntId=019c42a1-be6f-7423-a59e-127b1bc0d9bd |
MSAdministrator
approved these changes
Feb 9, 2026
zoomequipd
approved these changes
Feb 10, 2026
zoomequipd
approved these changes
Feb 13, 2026
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
3 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.
Description
Adding newly observed pattern
Associated samples
Associated hunts
Why am I removing
.name == "X-MS-Exchange-CrossTenant-AuthAs"check?In instances where the sender does not have an MS Exchange account, msft will send the message on the users behalf with a noreply address from Microsoft. This header will be included. This is going to create a fair amount of telemetry so I want to let this sit for a little bit.
hunt
My intention would be to later remove the solicited sender check as well as these are often coming from popped user accounts. But that will be a different PR