Update Detecting Misconfigured EXO Transport Rules.kql #5
Conversation
This file contains 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
ThreatClassification is only populated if the MDO LLM scanning finds any threats on the emails, this was only introduced recently and the field is not always populated. ThreatTypes will always be populated when there are any kind of detections on the email (Spam/Phish/Malware).
|
I'm not Raviv but you are very welcome 😄 |
|
Oops wrong person. Thanks 🙏 |
|
Did this merge successfully? 😅 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ThreatClassification is only populated if the MDO LLM scanning finds any threats on the emails, this was only introduced recently and the field is not always populated. ThreatTypes will always be populated when there are any kind of detections on the email (Spam/Phish/Malware).