-
Notifications
You must be signed in to change notification settings - Fork 841
Add eng/sdl-tsa-vars.config for TSA integration #6980
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
Merged
Merged
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
Co-authored-by: SamMonoRT <46026722+SamMonoRT@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add eng/sdl-tsa-vars.config to repository
Add eng/sdl-tsa-vars.config for TSA integration
Oct 29, 2025
Copilot finished work on behalf of
SamMonoRT
October 29, 2025 15:23
Contributor
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 adds a new SDL (Security Development Lifecycle) TSA (Trust Services Automation) configuration file that configures security scanning tools and their integration with Azure DevOps for the dotnetextensions repository.
Key changes:
- Configures security scanning tools (PoliCheck, CredScan, BinSkim) with TSA integration
- Sets up DevDiv project integration with proper notification channels
- Defines exclusion/suppression file paths for security scan results
Comments suppressed due to low confidence (1)
eng/sdl-tsa-vars.config:1
- The configuration references exclusion/suppression files (
.config/PoliCheckExclusions.xmland.config/CredScanSuppressions.json) that may not exist in the repository. Consider either creating these files as part of this PR or documenting that they should be created if security scan results need to be suppressed.
-SourceToolsList @("policheck","credscan")
wtgodbe
reviewed
Oct 29, 2025
wtgodbe
reviewed
Oct 29, 2025
SamMonoRT
approved these changes
Oct 29, 2025
wtgodbe
approved these changes
Oct 29, 2025
This was referenced Nov 11, 2025
Merged
Merged
This was referenced Nov 13, 2025
Open
Open
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.
Adds TSA (Team Security Advisor) configuration file for Azure DevOps security scanning integration.
Changes
Created
eng/sdl-tsa-vars.configwith configuration values from.config/tsaoptions.json:https://devdiv.visualstudio.com/DevDiv\ASP.NET Core\Policy Violationsdotnetextensionsaspnetcore-build@microsoft.comConfigured source scanning tools (PoliCheck, CredScan) and artifact scanning (BinSkim)
Added suppression file paths for PoliCheck and CredScan
Set standard values for TsaOnboard, TsaPublish, and TsaCodebaseAdmin
File format follows dotnet/efcore, dotnet/aspnetcore, and dotnet/runtime conventions for Azure Pipelines SDL task integration.
Original prompt
This pull request was created as a result of the following prompt from Copilot chat.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Microsoft Reviewers: Open in CodeFlow