After addressing a high-severity Code Scanning alert, what is the recommended final step?

Prepare for the GitHub Advanced Security Certification Test. Practice with multiple choice questions, detailed explanations, and hints. Achieve success on your first attempt!

Multiple Choice

After addressing a high-severity Code Scanning alert, what is the recommended final step?

Explanation:
After addressing a high-severity Code Scanning alert, the final step is to fix the underlying issue and then close the alert once the fix is verified. This keeps the alert status accurate, signals to the team that the risk has been mitigated, and provides a traceable record of what was changed and why. It’s important to re-run the scan or review the changes in a pull request to confirm the remediation actually resolves the vulnerability before closing. Dismissing the alert and keeping it open, removing the file, or disabling Code Scanning all undermine security visibility and protection, whereas remediating and then closing ensures proper triage and accountability.

After addressing a high-severity Code Scanning alert, the final step is to fix the underlying issue and then close the alert once the fix is verified. This keeps the alert status accurate, signals to the team that the risk has been mitigated, and provides a traceable record of what was changed and why. It’s important to re-run the scan or review the changes in a pull request to confirm the remediation actually resolves the vulnerability before closing. Dismissing the alert and keeping it open, removing the file, or disabling Code Scanning all undermine security visibility and protection, whereas remediating and then closing ensures proper triage and accountability.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy