A vulnerability scanner identifies a high-severity vulnerability in a web server that is exposed to the internet. According to common remediation SLAs, what is the typical timeframe to remediate a critical vulnerability?
Correct: Critical vulnerabilities typically have a 24-72 hour SLA.
Why this answer
Critical vulnerabilities in internet-exposed systems typically require remediation within 24–72 hours under common SLAs (e.g., PCI DSS, NIST, or organizational security policies). This timeframe reflects the high risk of remote exploitation, where an attacker can compromise the server before a longer window expires.
Exam trap
The exam often tests the distinction between critical (24–72 hours), high (7 days), and medium (30 days) SLAs, and the trap here is that candidates confuse 'high' with 'critical' and select 7 days instead of the shorter window.
How to eliminate wrong answers
Option A is wrong because 90 days is far too long for a critical vulnerability on an internet-facing web server; such a window is more typical for low-severity or non-exploitable issues. Option C is wrong because 7 days is a common SLA for high-severity vulnerabilities, not critical ones, which demand faster action due to immediate exploitation risk. Option D is wrong because 30 days is a typical remediation timeframe for medium-severity vulnerabilities, not critical ones, and would leave the server exposed to active attacks.