Custom patterns can include patterns internal to your organization.

Custom patterns can include patterns internal to your organization.

• A. True
• B. False
• C. Only for public patterns
• D. Requires external service

Answer: (A)

Custom patterns in secret scanning can include patterns internal to your organization. You can define these patterns using the same pattern syntax (regex-like) used for generic secrets, which lets you detect internal API keys, tokens, or credentials that are specific to your environment. This is important because internal assets often follow unique naming conventions that wouldn’t match generic patterns, so adding internal patterns helps catch secrets that would otherwise slip through. By configuring these at the organization level, scans can run across all repositories you control, aiding early detection and remediation. Unlike options that imply internal patterns aren’t possible or require external services, this capability is supported within the platform and does not require external tooling.

Custom patterns in secret scanning can include patterns internal to your organization. You can define these patterns using the same pattern syntax (regex-like) used for generic secrets, which lets you detect internal API keys, tokens, or credentials that are specific to your environment. This is important because internal assets often follow unique naming conventions that wouldn’t match generic patterns, so adding internal patterns helps catch secrets that would otherwise slip through. By configuring these at the organization level, scans can run across all repositories you control, aiding early detection and remediation.

Unlike options that imply internal patterns aren’t possible or require external services, this capability is supported within the platform and does not require external tooling.