Deterministic Consent Gate: analytics remain disabled until explicit opt-in. No third-party trackers are loaded.

Specification de capacite

Playbook-based containment workflows

Threat Response Automation

Playbook-based containment workflows defines a core capability outcome delivered by Threat Response Automation, including implementation intent and execution coverage.

NIS2DORA

Objectif

Translate Threat Response Automation intent into a concrete capability stream that can be executed, measured, and accepted by the delivery team.

Contexte de perimetre

Detection and response loop with automated triage and controlled containment.

Entrees

- Current-state architecture and operating model

- Approved bundle scope and target compliance obligations

- Delivery constraints, timeline, and responsible owners

Sorties

- Implemented capability increment with ownership mapping

- Execution notes and evidence pointers for review

- Operational handover requirements for production use

Criteres d acceptation

- Capability can be demonstrated in a controlled walkthrough

- Owner, scope, and change boundaries are explicit

- Linked controls and evidence references are complete

Notes de preuve de conformite

- [NIS2] Capability execution mapped in Threat Response Automation control evidence

- [DORA] Capability execution mapped in Threat Response Automation control evidence

Schema de specification

Role responsable

Capability Stream Owner

Validation finale

Product owner and platform lead

Politique de versioning

Revisioned per release with backward-compatibility notes

Cadence de revue

Sprint review and monthly capability maturity checkpoint

Retention des preuves

Operational evidence retained for at least 12 months

Sections obligatoires

- Capability objective and intended business outcome

- Technical scope and dependency matrix

- Implementation steps and ownership mapping

- Validation checklist and acceptance evidence

- Operational handover and support model