cso-incident-investigation

Guides learners through investigating a Defender XDR incident and writing a one-page IR report.

2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/jay-steenbergen/MSSAMentorAgent --skill cso-incident-investigation-jay-steenbergen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cso-incident-investigation
Source: https://github.com/jay-steenbergen/MSSAMentorAgent/tree/main/.github/skills/tracks/cybersecurity-ops/cso-incident-investigation
Command: npx skills add https://github.com/jay-steenbergen/MSSAMentorAgent --skill cso-incident-investigation-jay-steenbergen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New SOC analysts often lack a repeatable method for triaging incidents and producing reports that a SOC lead would accept. This Skill walks a learner through one real or simulated Microsoft Defender XDR incident end-to-end, building the muscle memory of alert triage, entity scoping, timeline construction, and incident report writing within a realistic time-box. ## Core Features & Use Cases - Structured five-phase investigation: Walks alerts, entities, evidence, timeline, and impact assessment in Defender XDR, then classifies and closes the incident with proper tags and summary. - IR report template: Produces a one-page markdown incident report with Summary, Scope, Alerts, Timeline, Root cause, and Recommended actions sections. - KQL timeline hunting: Includes an Advanced Hunting query to bracket the attack window and find the earliest known compromise (patient zero). - Use Case: A cybersecurity student who just onboarded a VM to Defender for Endpoint runs an evaluation attack, then uses this Skill to triage the resulting incident, classify it as a true positive (penetration test), and deliver a SOC-ready IR report in about 75 minutes. ## Quick Start Ask the mentor to start the cso-incident-investigation project and walk you through triaging an active incident in the Defender XDR portal into a one-page IR report.

Frequently Asked Questions about cso-incident-investigation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate an incident in Microsoft Defender XDR?

Open the incident in security.microsoft.com, walk the Alerts tab to note MITRE techniques and entities, map compromised versus touched assets, build a UTC timeline from device and user timelines, then classify and close with tags and a summary.

How do I write an incident response report for a SOC?

Use a one-page markdown template with five sections: Summary, Scope, Alerts, Timeline, and Root cause plus Recommended actions. Keep the executive summary to one or two plain-English sentences and record all timestamps in UTC.

What is the difference between true positive, benign positive, and false positive?

A true positive is real attacker behavior, a benign positive is legitimate activity that looked malicious, and a false positive means the detection itself was wrong. Correct classification drives MTTR and detection effectiveness metrics.

Does this project require a real security incident to work?

No. If no real incident exists, you can run a Defender evaluation lab simulation, a Microsoft test script, or an EICAR test file scan to generate an alert, then investigate that as a sanctioned penetration test classification.

What are the prerequisites for this incident investigation project?

You need a completed Defender for Endpoint onboarding with at least one incident in the portal, Security Reader or higher role in Defender XDR, and a markdown editor such as VS Code for the IR report.

When should I escalate to DFIR instead of handling triage myself?

SOC analysts triage and escalate; deep forensics like disk imaging and memory analysis belong to DFIR specialists. This project deliberately excludes memory forensics and custom analytics rules, focusing on end-to-end triage and reporting.