Domain: Security and Access Control |
Level: MUST | Type: Preventive /
Corrective
Statement of Requirement:
Node Operators MUST maintain
documentation of the Security incident response procedures they
follow.
Purpose
Demonstrate the Node Operator's ability to anticipate and respond to
threats and adverse circumstances.
Audit Procedures
Verify that
documented security incident response procedures address the
identification, reporting, assessment, containment, eradication,
recovery, and post-incident review of security incidents, and
post-incident review and update of the procedures
security incident response procedures are maintained and available
to personnel with security or operational responsibilities.
responsible personnel and management are aware of the documented
security incident response procedures, understand their respective
responsibilities for responding to security incidents, and understand
the process for reviewing and updating the procedures as necessary.
Communication templates and escalation procedures;
roles/responsibilities matrix
Incident response exercise records and after-action reports
Version control history of the incident response document
Success Criteria
Interviews with personnel
Formal, versioned incident response plan exists covering both
generic and blockchain-specific security incidents
Plan includes all minimum elements: classification, detection,
containment, eradication, recovery, post-incident review, communication,
roles, escalation
Plan reviewed/updated within last 12 months
At least one exercise/tabletop conducted during audit period
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
No documented incident response plan exists
The plan does not address blockchain-specific scenarios (key
compromise, slashing)
Plan materially incomplete (e.g. missing containment, communication,
post-mortem, or roles)
Plan has stale information (e.g. outdated contacts, departed
personnel, or has not been updated to reflect an organisational
change)
No exercises conducted and the plan is never tested
Common Failure Patterns
Incident Response Plan is a generic template from non-blockchain
context without key compromise/slashing scenarios;
contact information is outdated, e.g. listing departed
personnel;
plan is created at initial certification and not updated, especially
if infrastructure or organisation changes have occurred;
exercises listed as required are not conducted;
the Incident Response Plan addresses detection and containment but
not post-incident review;
there are multiple conflicting versions claiming to be current.