IR-4 Detection and analysis - investigate an incident
Ensure the security operations team can query and use diverse data sources when investigating potential incidents, collecting logs broadly enough to track activity across the attack chain without blind spots.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Log source inventory mapped to attack chain stages · SIEM / log platform
periodic reviewEvidence produced at each review
- Investigation records demonstrating cross-source correlation · Document repository
governing documentDocuments that govern the control
- Analyst query access to those sources · Document repository
- Documented gap analysis identifying blind spots · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- only alert data retained, not the underlying telemetry
- analysts must request log access per investigation, costing hours
- identity, network and endpoint logs held in separate systems that cannot be joined
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetIR-3 Detection and analysis - create incidents based on high-quality alerts · IR-5 Detection and analysis - prioritize incidents