Question 50
At fictional Riverstone Travel, an endpoint security engineer responsible for booking service endpoints is reviewing endpoint provisioning, security modules and profile delivery during a test environment commissioning (FCT-7.4-2.3-013). The observed endpoint management issue is: A security engineer publishes a vulnerability report then assumes it automatically installs every missing operating system patch. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to track vulnerability-to-remediation closure using repeated scans and change evidence. It mitigates the actual failure: A security engineer publishes a vulnerability report then assumes it automatically installs every missing operating system patch. A suitable correction is to use vulnerability findings to drive an appropriate documented remediation and update workflow; its proof is that subsequent assessment confirms that the targeted exposure is no longer present after authorized patching.
Incorrect Answers
“Monitor event ingestion freshness alongside alert volume instead of counting alerts alone” checks a different ongoing risk rather than the reported failure: a security engineer publishes a vulnerability report then assumes it automatically installs every missing operating system patch. The relevant mechanism is endpoint vulnerability assessment and actual software patch deployment are different security activities. The directly matched preventive control is “Track vulnerability-to-remediation closure using repeated scans and change evidence”.
“Check effective real-time protection and tamper restrictions during fleet compliance audits” checks a different ongoing risk rather than the reported failure: a security engineer publishes a vulnerability report then assumes it automatically installs every missing operating system patch. The relevant mechanism is endpoint vulnerability assessment and actual software patch deployment are different security activities. The directly matched preventive control is “Track vulnerability-to-remediation closure using repeated scans and change evidence”.
“Include before-and-after agent version, registration and module checks in upgrade gates” checks a different ongoing risk rather than the reported failure: a security engineer publishes a vulnerability report then assumes it automatically installs every missing operating system patch. The relevant mechanism is endpoint vulnerability assessment and actual software patch deployment are different security activities. The directly matched preventive control is “Track vulnerability-to-remediation closure using repeated scans and change evidence”.