GH-500 - Configure and use Secret Protection - Section 2.2
Explain how push protection prevents secrets at the source, and describe validity checks and prioritized alerting for high-confidence secrets.
Explain how push protection blocks a commit containing a high-confidence secret before it reaches the remote, and describe how validity checks confirm whether a detected secret is still active. Distinguish the bypass push protection options available to developers and when each is appropriate.
push protectionvalidity checkshigh-confidence secretsbypass push protection
More in this domain
Back to all Configure and use Secret Protection objectives, or the GH-500 cert hub.
Examworthy is not affiliated with or endorsed by GitHub. Original, blueprint-aligned practice material only.