security: Add advanced security policy (Github Policy Service)#239
Merged
christinalau0 merged 2 commits intoAzure:masterfrom Apr 19, 2024
Merged
Conversation
jadarsie
approved these changes
Apr 19, 2024
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
2 participants
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.
Reason for Change:
This PR adds advanced security policies for this repo. With Github's built in mechanism, secret scanning and secret scanning push protection is already enabled. The new yaml matches the current policy.
Additionally, the new yaml enables pull request validation of dependencies. When this feature is enabled, a PR check is automatically run on every PR to determine whether the PR has added or modified any dependencies. If it has, those dependencies are checked for vulnerabilities. If vulnerabilities are found, then the severity of the dependency is compared against the failOnSeverity setting to determine if the check should fail.
Issue Fixed:
Credit Where Due:
Does this change contain code from or inspired by another project?
If "Yes," did you notify that project's maintainers and provide attribution?
Requirements:
Notes: