Skip to content
Skillpedia
Misc35k · #5548

building-soc-escalation-matrix

Lets your agent create a plan for handling security incidents. It defines how issues are classified, who is notified, and what the response times are.

What it does

This tool helps create a detailed plan for handling security incidents. It defines how serious a problem is, who needs to be notified, and how quickly things must be resolved.

When to use it

  • ✓When setting up a new security system.
  • ✓When reviewing how your team handles security issues.
  • ✓To ensure you follow security and privacy rules.

Example of what to ask your AI

“Create an escalation matrix for security incidents, defining severity levels, response times, and who to contact.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/main/skills/building-soc-escalation-matrix/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/main/skills/building-soc-escalation-matrix/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool uses information about business risk, system importance, and data sensitivity to determine incident severity. Based on this, it outlines the next steps and who should be informed.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill building-soc-escalation-matrix

Or download just the file:

curl -L https://raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/main/skills/building-soc-escalation-matrix/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Building SOC Escalation Matrix

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

                    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

…

FAQ

What is a 'SOC'?

SOC stands for 'Security Operations Center'. It's the team responsible for monitoring and responding to security threats in an organization.

What are 'SLAs'?

SLAs are Service Level Agreements. They define the maximum time allowed to respond to or resolve an incident.

Why use 'context-driven criteria'?

Because not all incidents are the same. An issue on a small system might be less serious than the same issue on a business-critical system, even if the threat looks identical.

Details

Original description by the author

Build a structured SOC escalation matrix defining severity tiers, response SLAs, tiered escalation paths, and notification procedures for security incidents, using context-driven criteria that combine business risk, asset criticality, and data sensitivity. Use when designing or revising how a SOC triages and escalates incidents across analyst tiers.

repo: mukul975/Anthropic-Cybersecurity-Skills

Popularity

GitHub stars
35k
Ranking position
#5548
License
Apache-2.0
Updated
8/31/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills