Incident Documentation
What is Incident Documentation?
The recording of all aspects of a security incident including timeline, actions taken, evidence collected, and lessons learned.
Frameworks that govern incident documentation
What the standards actually require on incident documentation
Requirements naming incident documentation across this standard, quoted from the control text.
NIST SP 800-611 control
Operate detection and analysis per NIST SP 800-61 Rev 2 Section 3.2 (Detection and Analysis). Tasks include (a) Attack vectors as taxonomy (External/Removable Media + Attrition + Web + Email + Improper Usage + Loss or Theft of Equipment + Other) for categorisa...
NISTSP61-4 · Detection and Analysis: Sources, Triage, Categorisation, Prioritisation →Questions people ask about incident documentation
What is Incident Documentation?
The recording of all aspects of a security incident including timeline, actions taken, evidence collected, and lessons learned.
Why is Incident Documentation important for compliance?
Incident Documentation is a key concept in Information Security. Understanding incident documentation helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 686 frameworks with 311K cross-framework control mappings.
Which compliance frameworks address Incident Documentation?
Incident Documentation appears in the requirement text of NIST SP 800-61. Across these standards we have identified 1 control that names it directly, each linked to the control text on the compliance platform.
Where can I learn more about Incident Documentation?
Explore our compliance framework pages to see how incident documentation applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 686 frameworks.
See how Incident Documentation applies across compliance frameworks
Our platform maps 686 frameworks with 311K cross-framework control mappings. Explore how this concept is addressed across standards.
Written and maintained by Gerard Blokdyk, The Art of Service.