Question 580
A review board considers proposals for this EPM issue: A background service identity initiates a privileged application launch not seen in its baseline profile. Which approach should be REJECTED because it most directly defeats the intended control?
Explanation
Correct Answer
Unexpected privileged activity should be validated against service purpose and authorization. “Ignore the anomaly because the account is not a human user.” would not meet the stated operational condition. Investigate legitimate scheduled tasks, account permissions, and process lineage. Correlate the service's expected schedule with actual elevation and endpoint logs.
Incorrect Answers
“Implement the reviewed response: Investigate legitimate scheduled tasks, account permissions, and process lineage.” requires checking Correlate the service's expected schedule with actual elevation and endpoint logs. Investigate legitimate scheduled tasks, account permissions, and process lineage.
“Require outcome evidence: Correlate the service's expected schedule with actual elevation and endpoint logs.” requires checking Correlate the service's expected schedule with actual elevation and endpoint logs. Investigate legitimate scheduled tasks, account permissions, and process lineage.
“For unusual elevation by service account, record the responsible owner, exact target scope, and a review date before closure.” records a controlled change and supports accountable evaluation. Unexpected privileged activity should be validated against service purpose and authorization. Correlate the service's expected schedule with actual elevation and endpoint logs.