Which patterns are secret scanning validity checks available to?

Question

Options

• Ahigh entropy strings
• Bcustom patterns
• Cpush protection patterns
• Dpartner patterns

• A
  2% (1)
• B
  90% (44)
• C
  6% (3)
• D
  2% (1)

Explanation

Supported secrets This table lists the secrets supported by secret scanning. You can see the types of alert that get generated for each token, as well as whether a validity check is performed on the token. Provider: Name of the token provider. Partner: Token for which leaks are reported to the relevant token partner. Applies to public repositories only. *-> User: Token for which leaks are reported to users on GitHub. Applies to public repositories, and to private repositories where GitHub Secret Protection and secret scanning are enabled. -> Includes default tokens, which relate to supported patterns and specified custom patterns, as well as non-provider tokens such as private keys, which usually have a higher ratio of false For secret scanning to scan for non-provider patterns, the detection of non-provider patterns must be enabled for the repository or the organization.

No community discussion yet for this question.