Performing Soc Tabletop Exercise
Overview
Cybersecurity skill for performing soc tabletop exercise. Follows industry best practices and security standards.
When to Use
Trigger phrases:
- "performing soc tabletop exercise"
- "Annual or semi-annual incident response testing is required (NIST, ISO 27001, PC"
- "New SOC analysts need exposure to major incident scenarios in a controlled envir"
- "Updated playbooks need validation before next real incident"
Use this skill when:
- Annual or semi-annual incident response testing is required (NIST, ISO 27001, PCI DSS compliance)
- New SOC analysts need exposure to major incident scenarios in a controlled environment
- Updated playbooks need validation before next real incident
- Cross-functional coordination (SOC, IT, Legal, PR, Executive) needs rehearsal
- Post-incident reviews reveal gaps requiring scenario-based training
Do not use as a replacement for technical purple team exercises — tabletop exercises test processes and decision-making, not technical detection capabilities.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Exercise facilitator with incident response experience
- Participant list: SOC analysts (Tier 1-3), SOC manager, IT operations, Legal, HR, Communications
- Conference room or video call with screen sharing capability
- Printed or digital scenario injects with timed release schedule
- Evaluation scorecard for assessing participant responses
- Existing incident response plan and playbooks for reference during exercise
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for soc tabletop exercise operations.
- Prepare Environment — Set up tools, access, and data sources required for soc tabletop exercise.
- Execute Core Workflow — Perform the soc tabletop exercise operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Design — Define interface, identify patterns, plan implementation
- Implement — Write code following existing conventions, add tests
- Verify — Run tests, check integration, validate behavior
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-soc-tabletop-exercise3description: Use when performs tabletop exercises for SOC teams simulating security incidents through discussion-based scenarios to test incident response procedures, communication workflows, and decision-making under pressure without impacting production systems. Use when organizations need to validate IR playbooks, train analysts, or meet compliance requirements for incident response testing.4license: Apache-2.05---67# Performing Soc Tabletop Exercise89## Overview1011Cybersecurity skill for performing soc tabletop exercise. Follows industry best practices and security standards.1213## When to Use1415**Trigger phrases:**16- "performing soc tabletop exercise"17- "Annual or semi-annual incident response testing is required (NIST, ISO 27001, PC"18- "New SOC analysts need exposure to major incident scenarios in a controlled envir"19- "Updated playbooks need validation before next real incident"202122Use this skill when:23- Annual or semi-annual incident response testing is required (NIST, ISO 27001, PCI DSS compliance)24- New SOC analysts need exposure to major incident scenarios in a controlled environment25- Updated playbooks need validation before next real incident26- Cross-functional coordination (SOC, IT, Legal, PR, Executive) needs rehearsal27- Post-incident reviews reveal gaps requiring scenario-based training2829**Do not use** as a replacement for technical purple team exercises — tabletop exercises test processes and decision-making, not technical detection capabilities.303132## When NOT to Use3334- When you lack proper authorization for testing35- For production systems without change management36- When the task requires legal or compliance expertise beyond technical scope373839## Prerequisites4041- Exercise facilitator with incident response experience42- Participant list: SOC analysts (Tier 1-3), SOC manager, IT operations, Legal, HR, Communications43- Conference room or video call with screen sharing capability44- Printed or digital scenario injects with timed release schedule45- Evaluation scorecard for assessing participant responses46- Existing incident response plan and playbooks for reference during exercise4748## Workflow4950```python51# Example: IOC detection52import re5354IOC_PATTERNS = {55 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",56 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",57 "hash_md5": r"\b[a-f0-9]{32}\b",58 "hash_sha256": r"\b[a-f0-9]{64}\b",59}6061def extract_iocs(text: str) -> dict:62 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}63```64651. **Plan Operations** — Define objectives, scope, and success criteria for soc tabletop exercise operations.662. **Prepare Environment** — Set up tools, access, and data sources required for soc tabletop exercise.673. **Execute Core Workflow** — Perform the soc tabletop exercise operations following established procedures.684. **Validate Results** — Verify that results meet quality standards and objectives.695. **Report Findings** — Document results, observations, and recommendations.706. **Follow Up** — Track remediation actions and verify fixes where applicable.7172## Tools7374- **Analysis Platform** — Data processing and visualization75- **Collaboration Tools** — Team coordination and knowledge sharing767778## Process79801. **Design** — Define interface, identify patterns, plan implementation811. **Implement** — Write code following existing conventions, add tests821. **Verify** — Run tests, check integration, validate behavior8384## Verification8586- [ ] All soc tabletop exercise procedures executed completely and documented87- [ ] Findings validated against multiple data sources88- [ ] False positives identified and filtered89- [ ] Results documented with evidence and timestamps90- [ ] Recommendations provided with risk-based prioritization9192## Anti-Rationalization Table9394| Rationalization | Reality |95|---|---|96| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |97| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |98| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |