Question 680
A server operations team encounters the following situation: A file-integrity monitor reports unauthorized changes to payroll exports, but the response team never verifies trusted hashes or identifies affected files. Which sustained operational control best reduces the likelihood of this same issue recurring?
Explanation
Correct Answer
This control targets the underlying recurrence risk: An integrity alert alone lacks validated scope and root cause. It builds validation into the affected workflow and supports the expected recovery result: The altered files and activity source are identified without changing unaffected data.
Incorrect Answers
This control addresses a different scenario: A payroll database's audit logs are overwritten after only two days, despite a legal requirement to retain access evidence much longer. That event's root mechanism was short log rotation removes evidence before the required retention period. The described incident instead arises from: An integrity alert alone lacks validated scope and root cause.
This control addresses a different scenario: A sales database logs 10,000 failed sign-ins overnight, but no SIEM correlation exists and the failures remain unnoticed in isolated host logs. That event's root mechanism was isolated logs without correlation or alerting can hide attempted intrusion. The described incident instead arises from: An integrity alert alone lacks validated scope and root cause.
This control addresses a different scenario: A vendor requests remote access to a security vault, and a single local administrator can approve and execute an unrestricted key export. That event's root mechanism was a single identity can authorize and execute an exceptionally sensitive operation. The described incident instead arises from: An integrity alert alone lacks validated scope and root cause.