[Security][Detection Engine][9.2 & Serverless] IM rule has DOES NOT MATCH condition #2672
Conversation
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
nastasha-solomon
added
the
Team:Experience
🔍 Preview links for changed docs |
…/elastic/docs-content into issue-2295-im-not-match-9.2-serv
bmorelli25
reviewed
Aug 22, 2025
Co-authored-by: Brandon Morelli <[email protected]>
bmorelli25
approved these changes
Aug 22, 2025
approksiu
approved these changes
Aug 25, 2025
vitaliidm
approved these changes
Aug 26, 2025
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.
Contributes to #2295 by documenting the new
DOES NOT MATCHcondition that's available for indicator match rules. Also makes minor improvements to the steps for creating the indicator match rule and fixes a typo in thesecuritySolution:defaultThreatIndexadvanced setting description.Preview