Update to the Secret Auditing page #954
Open
Conversation
This file contains 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
…hnologists meeting. GitHub secret scanning upgraded to a must. Team must also review alerts and record outcomes.
willp-bl
approved these changes
Nov 7, 2024
huwd
approved these changes
Nov 27, 2024
timblair
requested changes
Nov 27, 2024
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.
As per discussion in GDS Lead Tech meeting - action was to review the guidance on GitHub secret scanning with security colleagues.
Proposal is to upgrade the use of GitHub secret scanning to a must from should.
This change also recommends that teams must review alerts on a regular basis, timing of this suggested to be aligned to existing team processes.
Teams also must record outcomes, even for false positives.