Which of the following is the most proactive and practical way to prevent new secret scanning alerts?

Question

Options

• AScan for non-provider patterns
• BUse feature branches
• CConfigure a secret scanning Actions workflow.
• DEnable push protection.

• A
  13% (4)
• B
  3% (1)
• C
  10% (3)
• D
  73% (22)

Explanation

To prevent new secret scanning alerts, enable push protection to block secrets from being committed in the first place, and manage push protection patterns to disable blocking for specific, low-risk secret types or false positives. Enable Push Protection Prevent new commits: Push protection proactively scans code for secrets before they are pushed to a repository. If a secret is detected, the push is blocked, providing immediate feedback to developers and preventing secrets from entering the codebase. Configure patterns: You can configure which secret patterns are blocked at the organization or enterprise level. By disabling patterns that frequently generate false positives, you can reduce the number of new alerts.

No community discussion yet for this question.