Enhance the AMSI Request Body Scanning analysis #2490
Draft
+71
−10
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
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Description:
Enhances the AMSI Request Body Scanning analysis to provide more detailed and actionable information about the configuration state.
When AMSI Request Body Scanning is enabled for specific protocols (rather than globally via
EnabledAll), the output now lists which protocols are configured:I've also added yellow warning indicator when AMSI Request Body Scanning is not enabled.
I fixed a bug where AMSI body scanning showed as enabled even if it was turned on for a specific protocol (like
EnabledOwa) but later disabled by another setting override usingEnableAll=False.Validation:
Lab