How to approach it
Record the time, affected asset, alert source and current evidence. Compare the event against expected activity, such as a scheduled change or a known service account pattern. Collect independent signals where available.
If harm may be ongoing, follow the incident playbook and escalate promptly. Containment can limit the spread of an incident, while preserving relevant logs helps the response team determine scope and cause.
Worked example
A login alert flags an employee’s account from an unfamiliar country. A mailbox audit shows a new forwarding rule. The second signal makes the case more urgent. The response team can preserve the audit trail and follow its account containment procedure while determining whether mail was forwarded.
Practice questions
A scheduled vulnerability scanner caused an endpoint alert at its usual weekly time. What evidence would support closing it as expected activity?
Show answer and explanation
Match the scanner identity, source, approved schedule, affected assets and observed behavior. Record the corroboration in the alert.
Multiple endpoints report a suspicious file change and a shared drive is still being altered. What should you prioritize?
Show answer and explanation
Escalate through the incident plan and take authorized containment steps to stop continuing changes. Preserve available logs and related evidence.
An employee says a suspicious email was opened, but no link was clicked. What should you record before classifying the incident?
Show answer and explanation
Record the message details, recipient, reported actions and relevant mail or endpoint telemetry. Use that evidence to assess whether anything executed or credentials were exposed.
Official reference
CompTIA Security+ certification and objectives
What to study next
- Security+ practice: Least privilege
Grant the minimum access needed for a task, scoped to the right resource and for only as long as required.