GH-500 · Question #88
Which of the following is NOT an action a user can take when they receive an alert from GitHub Advanced Security (GHAS)?
The correct answer is C. Report the alert to GitHub. GHAS alerts support dismissal, investigation, and remediation actions, but formally reporting an alert to GitHub is not a built-in action available to users.
Question
Which of the following is NOT an action a user can take when they receive an alert from GitHub Advanced Security (GHAS)?
Options
- AIgnore the alert.
- BDismiss the alert.
- CReport the alert to GitHub.
- DInvestigate the alert and take appropriate action.
How the community answered
(32 responses)- A6% (2)
- C91% (29)
- D3% (1)
Why each option
GHAS alerts support dismissal, investigation, and remediation actions, but formally reporting an alert to GitHub is not a built-in action available to users.
Ignoring an alert is a valid user behavior within GHAS; while not recommended, users can choose to take no action on an alert.
Dismissing an alert is a standard, built-in action in GHAS that requires selecting a dismissal reason such as 'false positive,' 'used in tests,' or 'won't fix.'
GHAS does not provide a 'report to GitHub' action for security alerts; the available actions are limited to dismissing with a reason (e.g., false positive or accepted risk), investigating the issue, and remediating the vulnerability - escalating alerts to GitHub itself is not part of the alert management workflow.
Investigating an alert and taking appropriate remediation action - such as patching code or rotating a secret - is the primary intended response to any GHAS security alert.
Concept tested: Available user actions for managing GHAS security alerts
Source: https://docs.github.com/en/code-security/code-scanning/managing-code-scanning-alerts/managing-code-scanning-alerts-for-your-repository
Topics
Community Discussion
No community discussion yet for this question.