Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
mukul975/building-soc-escalation-matrixDFIR and threat hunting

building-soc-escalation-matrix

⁨Build a structured SOC escalation matrix defining severity tiers, response⁩

v1.03 installs+3 in 7 days36.3K StarsApache-2.0synced 12 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/building-soc-escalation-matrix

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
z6KtBPNXKj…ER4XeHBg==The CLI checks the SHA-256 and the signature before it writes a file.
Packagee3dcc96c…dd95b695
e3dcc96c8fd5…6497dd95b6958 files · ⁦12.1 KB⁩
ScanMedium3 findings
  • Executable script shipped with the skillscripts/agent.py
  • Executable script shipped with the skillscripts/process.py
  • Links to outside domains
See the full scan
Sourcegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/building-soc-escalation-matrix@54a7988

Overview

A SOC escalation matrix defines how security incidents move through the organization based on severity, impact, and response requirements. Modern SOCs use context-driven escalation combining business risk, asset criticality, and data sensitivity rather than purely severity-based models. Organizations using AI and automation in their SOC cut detection-and-containment lifecycle to approximately 161 days, an 80-day improvement over the 241-day industry average.

When to Use

  • When deploying or configuring building soc escalation matrix capabilities in your environment
  • When establishing security controls aligned to compliance requirements
  • When building or improving security architecture for this domain
  • When conducting security assessments that require this implementation

Prerequisites

  • Familiarity with soc operations concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

SOC Tier Structure

Tier 1 - Alert Triage Analyst

  • Monitors SIEM dashboards and alert queues
  • Performs initial alert classification (true/false positive)
  • Handles P3 and P4 incidents to resolution
  • Escalates P1 and P2 incidents to Tier 2 within SLA
  • Documents initial findings in ticketing system

Tier 2 - Incident Analyst

  • Performs deep-dive investigation on escalated incidents
  • Conducts root cause analysis and scoping
  • Executes containment procedures
  • Handles P2 incidents to resolution
  • Escalates P1 incidents to Tier 3 or management

Tier 3 - Senior Analyst / Threat Hunter

  • Handles P1 critical incidents and APT investigations
  • Performs proactive threat hunting
  • Develops detection rules and playbooks
  • Conducts malware reverse engineering
  • Leads incident response for major breaches

Management Escalation

  • SOC Manager: Operational decisions, resource allocation
  • CISO: Business impact decisions, executive communication
  • Legal/PR: Data breach notification, media response
  • External IR: Third-party incident response engagement

Severity Classification

P1 - Critical

Attribute Value
Impact Active data breach, ransomware spreading, critical systems compromised
Business Impact Revenue loss, regulatory exposure, customer data at risk
Initial Response 15 minutes
Escalation to Tier 2 Immediate
Escalation to Management 30 minutes
Resolution Target 4 hours
Communication Every 30 minutes to stakeholders
Examples Active ransomware, confirmed data exfiltration, domain admin compromise

P2 - High

Attribute Value
Impact Confirmed compromise, limited scope, no active exfiltration
Business Impact Potential revenue impact, contained risk
Initial Response 30 minutes
Escalation to Tier 2 30 minutes if unresolved
Escalation to Management 2 hours
Resolution Target 8 hours
Communication Every 2 hours to SOC management
Examples Compromised user account, malware on single endpoint, insider threat indicator

P3 - Medium

Attribute Value
Impact Suspicious activity requiring investigation
Business Impact Low immediate risk
Initial Response 4 hours
Escalation to Tier 2 8 hours if unresolved
Resolution Target 24 hours
Communication Daily status update
Examples Policy violation, failed brute force, suspicious email report

P4 - Low

Attribute Value
Impact Informational alerts, routine security events
Business Impact Minimal
Initial Response 8 hours
Escalation Only if pattern emerges
Resolution Target 72 hours
Communication Weekly summary
Examples Vulnerability scan findings, expired certificates, policy exceptions

Escalation Decision Matrix

text
                    Asset Criticality
                    Low        Medium      High        Critical
Severity  Low      P4         P4          P3          P3
          Medium   P4         P3          P2          P2
          High     P3         P2          P2          P1
          Critical P2         P1          P1          P1

Context-Driven Escalation Triggers

Automatic Escalation (no analyst decision needed)

Trigger Action
Ransomware detected on any endpoint P1 - Immediate Tier 3 + Management
Domain admin account compromise P1 - Immediate Tier 3 + Management
Active data exfiltration to external IP P1 - Immediate Tier 3 + Management
Critical infrastructure (DC, SCADA) alert P1 - Immediate Tier 2 minimum
Executive account anomaly P2 - Immediate Tier 2
Multiple hosts with same malware P1 - Immediate Tier 2

Time-Based Escalation

Condition Action
P2 unresolved after 4 hours Escalate to Tier 3
P3 unresolved after 12 hours Escalate to Tier 2
Any incident unresolved past SLA Escalate to SOC Manager
P1 unresolved after 2 hours Escalate to CISO

Communication Templates

P1 Initial Notification

text
SUBJECT: [P1 CRITICAL] Security Incident - {Incident_ID}

Incident Summary:
- Type: {incident_type}
- Affected Systems: {systems}
- Affected Users: {users}
- Current Status: {status}
- Assigned To: {analyst}

Impact Assessment:
- Business Impact: {impact}
- Data at Risk: {data_risk}
- Containment Status: {containment}

Next Actions:
- {action_1}
- {action_2}

Next Update: {time} (30-minute intervals)
Bridge Line: {conference_details}

Escalation Matrix Implementation

SOAR Integration

yaml
# XSOAR escalation playbook trigger
trigger:
  condition: incident.severity == "critical" AND incident.asset_criticality == "high"
  action:
    - assign_tier: 3
    - notify: [soc_manager, ciso]
    - create_war_room: true
    - start_bridge: true
    - set_sla: 4h

auto_escalation_rules:
  - name: P2 Time-Based Escalation
    condition: incident.severity == "high" AND incident.age > 4h AND incident.status != "resolved"
    action:
      - escalate_tier: 3
      - notify: soc_manager
      - add_comment: "Auto-escalated due to SLA breach"

References

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/agent.py
  2. MediumFile · Executable script shipped with the skillscripts/process.py
  3. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0Nov 13, 202654a7988e3dcc96cSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login