nerdexam
GIAC

GSEC · Question #67

You have an automated system for patching the operating systems of all your computers. All patches are supposedly current. Yet your automated vulnerability scanner has just reported vulnerabilities…

The correct answer is A. Check some systems manually. When automated patching and vulnerability scan results conflict, manually verifying a sample of systems is the correct first step to establish ground truth before taking further action.

Incident Handling, Risk, and Governance

Question

You have an automated system for patching the operating systems of all your computers. All patches are supposedly current. Yet your automated vulnerability scanner has just reported vulnerabilities that you believe have been patched. Which of the actions below should you take next?

Options

  • ACheck some systems manually.
  • BRerun the system patching routines.
  • CContact the incident response team.
  • DIgnore the findings as false positives.

How the community answered

(24 responses)
  • A
    75% (18)
  • B
    8% (2)
  • C
    13% (3)
  • D
    4% (1)

Why each option

When automated patching and vulnerability scan results conflict, manually verifying a sample of systems is the correct first step to establish ground truth before taking further action.

ACheck some systems manually.Correct

Automated patch deployment can fail silently due to errors, incomplete reboots, or misconfigured deployment targets, so manually inspecting a representative sample of systems confirms whether patches were actually applied. This provides the factual basis needed before deciding to rerun patching, escalate to incident response, or accept the findings.

BRerun the system patching routines.

Rerunning patching routines before verifying the actual system state is premature and may not address the root cause of why deployment failed in the first place.

CContact the incident response team.

Escalating to incident response is premature without first confirming whether the scanner findings reflect a real, unpatched vulnerability rather than a patch deployment failure.

DIgnore the findings as false positives.

Dismissing findings as false positives without investigation is irresponsible and could leave genuinely unpatched vulnerabilities exposed to exploitation.

Concept tested: Patch verification workflow and vulnerability scanner result validation

Source: https://learn.microsoft.com/en-us/windows/security/threat-protection/windows-security-configuration-framework/windows-security-baselines

Topics

#vulnerability scanning#patch management#false positives#security verification

Community Discussion

No community discussion yet for this question.

Full GSEC Practice