-
Notifications
You must be signed in to change notification settings - Fork 841
Enable binskim to extract packages #6989
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR enhances security scanning capabilities in the Azure DevOps pipeline by configuring Guardian (GDN) extraction tools and enabling comprehensive BinSkim scanning.
Key changes:
- Adds GDN extraction configuration for security analysis tools (BinSkim, Bandit, Roslyn Analyzers)
- Configures file type filters for extracting artifacts from build outputs
- Enables BinSkim scanning for all file extensions through feature flags
Previously I set the pipeline to publish all artifacts, which was way too much, since that contained referenced binaries, tests, etc. Instead we need to publish only what we build and ship from this repo. That way we only run validation on those shipping packages.
|
Thanks a lot @ericstj! |
|
Not quite ready, I think I mistook the path
|
|
Should be better now - https://dev.azure.com/dnceng/internal/_build/results?buildId=2830669&view=results |
Official build test -- https://dev.azure.com/dnceng/internal/_build/results?buildId=2828070&view=results
Note the build will fail due to #6988 but should run enough for us to see binskim results.
Microsoft Reviewers: Open in CodeFlow