“The worst time to learn Incident Response is during the incident itself.”
If you’re an SOC analyst, cybersecurity student, or anyone preparing for incident response, you know that nothing beats hands-on practice.
That’s why I created IR Sim 101, a realistic cybersecurity incident simulation that walks you through the entire incident response workflow, from initial detection to final report writing.
This project is more than just a cybersecurity lab. It’s a story-driven breach investigation where logs, artifacts, and documentation are structured exactly like in a real Security Operations Center (SOC).
The repository mimics real-world IR documentation and evidence handling:
IR-Sim-101/
│
├── detection_notes/
│ ├── MITRE_TTPs.txt
│ ├── analyst_walkthrough.md
│ ├── ioc_list.txt
│ ├── network_analysis.txt
│ └── recommendations.txt
│
├── docs/
│ ├── Incident_Scenario.md
│ ├── incident_logs.md
│ ├── incident_summary.txt
│ └── incident_timeline.md
│
├── simulation/
│ └── artifacts/
│ ├── O365_login_events.csv
│ ├── internal_portal_logs.csv
│ ├── powershell_activity.csv
│ └── credentials/
│ └── harvested_creds.csv
│
└── README.md
In the detection_notes/
folder, I documented every finding as if I were responding live:
MITRE_TTPs.txt
→ Map attacker behavior to MITRE ATT&CKioc_list.txt
→ Indicators of Compromise (IOCs)network_analysis.txt
→ Network anomalies & suspicious patternsrecommendations.txt
→ Security improvementsanalyst_walkthrough.md
→ Step-by-step reasoningSEO Tip for Readers: Always maintain a centralized IR notebook during investigation, it’s the difference between confusion and clarity.
The docs/
folder is where the full breach narrative lives:
Incident_Scenario.md
→ Background and detection contextincident_logs.md
→ Raw logs for huntingincident_timeline.md
→ Chronology of attacker actionsincident_summary.txt
→ Executive-ready summaryPro Insight: If your SOC team doesn’t have an incident storyline, you’re just reacting, not responding.
Inside simulation/artifacts/
, I uncovered the real attack flow:
O365_login_events.csv
→ Suspicious geo-diverse loginsinternal_portal_logs.csv
→ Sensitive file accesspowershell_activity.csv
→ Obfuscated persistence scriptscredentials/harvested_creds.csv
→ Evidence of credential theftKey Skill for SOC Analysts: Learn to spot anomalies across different log types, attackers rarely leave all their traces in one place.
Jumping between detection notes and artifacts confirmed suspicions.
For example:
ioc_list.txt
with O365_login_events.csv
confirmed malicious access.Why This Matters: In incident response exercises, correlation turns scattered alerts into a cohesive attack narrative.
A well-built incident timeline transforms chaos into clarity:
The recommendations.txt
file became the blueprint for prevention:
Incident Response Mindset: Your job isn’t over when the breach ends — it’s over when you’ve reduced the chance it happens again.
By running this simulation, you’ll practice:
This isn’t just reading about IR, it’s doing IR.
incident_scenario.md
firstsimulation/artifacts/
detection_notes/
“The only way to stay calm in chaos is to practice chaos.”
IR Sim 101 is controlled chaos, the perfect training ground for SOC analysts, cybersecurity students, and blue-teamers preparing for the real thing.
Watch the guided walkthrough video → Where logs become stories, and every alert is a clue.
GitHub: IR Sim 101 Repository
LinkedIn: Yug Shah
Press enter or click to view image in full size