Code scanning adds mitigated alert dismissal reason
Code scanning alerts can now be dismissed with a "Mitigated" reason when vulnerabilities are controlled by external measures like web application firewalls or network policies. This allows developers to document when risks are managed outside the application itself.
You can now dismiss a code scanning alert with the reason Mitigated when a vulnerability remains in the code but external controls, such as a web application firewall or network policy, mitigate its risk.
The new dismissal reason helps you distinguish mitigated vulnerabilities from alerts marked Won’t fix, align dismissals with formal exception and risk-acceptance processes, and reduce the need to track these decisions outside GitHub.
For more information, see resolving code scanning alerts.
The post Code scanning adds a mitigated alert dismissal reason appeared first on The GitHub Blog.
Source: original entry ↗
More from GitHub
Follow GitHub to get its new changes in your feed and email digest.
GitHub App improvements for least privilege and management
GitHub has released improvements to GitHub Apps that enable developers to migrate away from classic personal access tokens, enhance app management capabilities, and request fewer sensitive permissions for better security.
Gemini 4 Argon now available in GitHub Copilot
Google's Gemini 4 Argon frontier model is now generally available in GitHub Copilot, designed for complex coding, agentic, and reasoning tasks to enhance developer productivity.
Audit GitHub Code Quality finding dismissals and reopenings
Users can now review manual dismissals and reopenings of GitHub Code Quality findings in their organization or enterprise audit log, enabling better tracking and governance of code quality decisions.