Question

Your organization uses an internally developed authentication service that issues tokens in a proprietary format (prefix 'intauth_' followed by 40 hex characters). A security engineer wants Secret Protection to detect these tokens across every repository in the organization, both existing and newly created, without configuring each repository individually. Which approach correctly achieves this?

Accepted Answer

Create the custom secret pattern at the organization level in the security settings, which makes it available for scanning across all repositories in the org.

Answer

Add the pattern to a .github/secret_scanning.yml file in a single repository so it automatically propagates to the rest of the organization.

Answer

Submit the pattern to GitHub support so it can be added to the built-in partner pattern list used for all customers.

Answer

Create the custom pattern separately in each repository, since custom secret patterns can only be defined at the repository scope.