Rename MSSentinel integration to MSDefenderGraphSecurityAPI - #4
Open
3lina wants to merge 1 commit into
Open
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
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.
Summary
This feeder was initially named and scoped around Microsoft Sentinel, but it now polls the
Microsoft Graph Security API (/security/alerts_v2), which aggregates alerts
from any product in the Microsoft Defender suite, not just Sentinel. This PR
renames the vendor and function so their name and description reflect that
actual scope.
Changes
Breaking change to note
The alert sourceRef prefix changed from sentinel-incident- to
msdefender-incident-. Incidents already ingested under the old prefix will
not be matched as duplicates after this change deploys.