Revise follow-up instructions for security reports#3206
Merged
Conversation
Updated the follow-up process for security vulnerability reports.
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates the security vulnerability reporting instructions in the SECURITY.md file to provide more specific guidance on follow-up communication with the Microsoft Security Response Center (MSRC).
Key Changes:
- Updated follow-up instructions to direct users to the MSRC Researcher Portal's Message functionality instead of email
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]>
akoeplinger
approved these changes
Nov 5, 2025
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.
Updated the follow-up process for security vulnerability reports.