Incident Management

Respond with precision. Recover with confidence.

Detect, triage, and resolve security and operational incidents with playbooks, clear ownership, and audit-ready timelines. Tie everything back to assets, risks, and controls.

Create an incident Explore features
MTTAmean time to acknowledge
MTTRmean time to resolve
P1/P2active major incidents
Closed 30dtrend vs. target
Incident timeline / dashboard placeholder

End-to-end incident response — fast, coordinated, auditable

From alert to lessons learned, everything stays linked to assets, risks, and controls.

Detect

Signal intake

Ingest alerts from SIEM/EDR, email, or forms. Auto-dedupe & correlate by asset, user, or indicator.

Triage

Severity & priority

Apply impact/urgency matrix, set SLAs, and route to on-call with clear ownership and responders.

Orchestrate

Playbooks

Step-by-step tasks for malware, phishing, outage, data loss, access abuse, and more—customisable.

Contain

Coordinated actions

Quarantine hosts, revoke tokens, reset creds, block indicators—recorded with actor & timestamp.

Recover

Service restoration

Track dependencies and validate recovery steps with checklists and change approvals.

Learn

Root cause & PIR

Capture RCA, lessons learned, and CAPA; link back to risks, controls, and policies for prevention.

Tip: Auto-open a risk item when P1/P2 incidents breach appetite, and push controls to treatment plans.

Key features

Built for major incident management and security response.

On-call & paging

Escalation policies with SMS/email/chat. Acknowledge to stop paging; auto-escalate on SLA breach.

Bridges & comms

Spin up Slack/Teams bridges, stakeholder updates, and customer-safe status notes from one place.

Forensic timeline

Immutable timeline of actions, artifacts, and decisions—perfect for audits and regulators.

Links to estate

Tie incidents to assets, users, vendors, services, risks, and policies for true blast-radius insight.

Templates & SLAs

Severity matrix, playbook templates, responder roles, and per-severity SLA targets.

Metrics

MTTA, MTTD, MTTR, reopen rate, SLA compliance, incidents by service/severity, and trend reporting.

Workflow: detect → triage → contain → eradicate → recover → review

Opinionated defaults; tuned to your incident categories and SLAs.

1

Detect

Alerts from SIEM/EDR/SOAR or manual reports become incidents with correlation and enrichment.

2

Triage & classify

Impact × urgency sets severity; assign incident commander, responders, and SLA clocks.

3

Contain & eradicate

Execute playbook tasks (isolate, revoke, patch, block), recording artifacts and evidence.

4

Recover service

Coordinate with change management; validate business and security recovery criteria.

5

PIR & CAPA

Run a post-incident review, document RCA, assign corrective/preventive actions, and link to risks.

Incident flow / swimlane diagram placeholder
Stakeholder comms: scheduled updates for execs, legal, PR, and customers with redaction controls.

Integrations

Bring signals in, push tasks out, keep everyone aligned.

  SIEM (Splunk/Sentinel)
  EDR/XDR
  SOAR / Webhooks
  Ticketing (Jira/ServiceNow)
  Chat (Slack/Teams)
  Email Intake
Two-way sync for tasks/notes; evidence remains centralized in PurpleWASP.

Security & compliance

Hardened, multi-tenant architecture with defensible evidence.

RBAC & SSO

Least-privilege roles, SSO/SAML/SCIM, optional MFA, and session hardening.

Encryption

TLS in transit; encryption at rest; optional field-level protection for sensitive artifacts.

Immutable logs

Full actor/timestamp audit trail of decisions and actions; exportable for regulators.

Evidence retention

Configurable retention, legal hold, and defensible deletion windows.

Standards

Supports ISO 27001 incident requirements; easy mapping to policies and risks.

Notifications

Document regulator/customer notifications with templates and approval flow.

Why PurpleWASP vs. ad-hoc incident handling

Reduce chaos, shorten outages, and produce defensible evidence.

Capability Manual / Ad-hoc PurpleWASP Incident Management
Ownership Unclear commander/responders Assigned roles, on-call, paging, escalation
Process Tribal knowledge Standardised playbooks per category/severity
Evidence Scattered notes Immutable timeline with artifacts & approvals
Metrics Hard to compute MTTA/MTTD/MTTR, SLA compliance, trends
Traceability Decoupled from estate Linked to assets, risks, policies, and controls

FAQs

Answers for incident commanders, SOC, and Ops.

Do you support major incident comms?
Yes—bridge channels, stakeholder updates, comms templates, and customer-safe notes.
Can we customise playbooks?
Absolutely—clone and edit per category/service; versioned with approvals.
How do metrics work?
We track MTTA/MTTD/MTTR and SLA timers automatically from acknowledgments and status changes.
Can incidents create risks or tasks?
Yes—open risks/CAPA automatically when thresholds are breached; sync tasks to ticketing.

Create your first incident

Open an incident, pick a category, assign an incident commander, and start the playbook.

New Incident Import Alerts

Configure playbooks

Set severity matrix, SLAs, and runbooks for common scenarios like phishing, ransomware, or outages.

Incident Settings Playbook Library

All actions are time-stamped and attributed. Perfect for audits and regulators.