Skip to content

P2 - High Severity Incident (Triage Matrix)

Density:

Compromise of a critical business service, isolated lateral movement within production VLANs, credential harvesting targeting privileged operators, or unmitigated exploited Zero-Day vulnerability.

  • โœ… C2 beaconing detected from a core database server or financial application gateway.
  • โœ… Successful Pass-the-Hash or Kerberoasting attack on service accounts with localized admin rights.
  • โœ… Web shell persistence identified on public-facing reverse proxy or API gateway.
  • โœ… Indirect prompt injection altering decision parameters of an operational AI inference pipeline without system crash.
  • Incident Lead Role: CSIRT Lead Investigator
  • Standby Obligation: Working-hours + on-call emergency paging within 15 minutes
  • Crisis Cell Required: YES (Mandatory War Room Activation)

Senior Threat Hunter

Assigned to primary response team for escalation, containment sign-off, and stakeholder synchronization.

Network Operations Lead

Assigned to primary response team for escalation, containment sign-off, and stakeholder synchronization.

DevSecOps / AppSec Lead

Assigned to primary response team for escalation, containment sign-off, and stakeholder synchronization.

Regional DPO

Assigned to primary response team for escalation, containment sign-off, and stakeholder synchronization.

Regulatory FrameworkMandatory DeadlineNotification AuthorityTrigger Threshold
GDPR (Article 33)72 hours (conditional on PII risk assessment)Lead Supervisory AuthorityPotential unauthorized access to customer records pending forensic log verification.
PCI DSS 4.0 Incident Handling24 hoursPayment Card Brands & AcquirersSuspected breach of Cardholder Data Environment (CDE).