Reading width
Wide uses the full column for everything, text, diagrams, code, and exercises. Narrow keeps the standard reading width.
Text size
Scales the body text. Headings and code blocks keep their size.
In this section
Microsoft SOC Detection and Response: Course Orientation
Introduction
A security operations center detects attacks on an organization and responds to them, and in a company that runs on Microsoft 365 it does that work in Microsoft Defender and Microsoft Sentinel. This course teaches that work from both seats in the SOC: the analyst who investigates incidents and the engineer who keeps the detections, automation and data behind them working. It's taught against one month of records from Northgate Engineering, an 810-person company whose month holds ordinary activity and several real attacks, and every figure in the course comes from a query you can run.
It's built for anyone who works in a Microsoft SOC or expects to. No prior experience is assumed; every concept is explained where it's first used, and every table is introduced where it's first read. Readers who already work in a SOC will find the methods and records useful from the first module, and the later modules go well past the basics.
Module 0 orients you. It shows what a Microsoft SOC does and where SOCs fail, how to judge a SOC's maturity from its own records, the pipeline every alert follows, what the course builds, and how to use the lab. It carries no knowledge check, because it orients rather than tests.
How to get the most from this module
Read 0.1 first; the others refer back to its queue. Run every query in the practice console, and write down what you expect before you run it, as 0.7 explains. Most of the numbers in the orientation reappear in later modules, and the ones you predicted are the ones you'll remember.
What you will be able to do
Work a Microsoft SOC's incident queue and record verdicts that teach. Build detections for identity, mail, endpoints, cloud and network, specified, tested and tuned. Investigate past the edge of an incident, and document what you find so someone else can follow it. Harden the estate and automate response, and check what automation did. Measure the operation without misleading anyone, judge threat intelligence by what it matched, and run AI agents as workers whose output is checked. The course ends with a Project: an incident, a detection and an operation review from your own environment.
Do I already know this material?
Six scenarios across the whole course, from the first calls in the queue to the hardest judgments about measures and AI. Answer them to see where you sit.
An automation rule assigned an incident to an analyst three days ago. It is still New, with no comments. What does the owner field tell you?
A rule that watches for a remote-administration tool fires when an IT administrator uses it, as their job requires. How should the incident be classified?
A query for sign-ins from an attacker's relay address, over the last seven days in SigninLogs, returns one user. What do you check before reporting it?
An incident groups eight on-premises alerts from a domain compromise. The summary says no cloud activity was observed. What is your next step?
Your report says the SOC's median time to close is 1.2 hours. Eighty-three incidents are still open, waiting a median of 377 hours. What should the report say?
A triage agent closed 54 reported messages as benign this month; analysts reversed three. A draft report says the agent is 94% accurate. What is wrong?
Start here
Begin with 0.1, which reads a month of Northgate's incident queue and shows who closes what, and what nobody picks up. If you came for a particular module, go straight to it: later modules build on earlier ones rather than repeat them, and each says what it uses from before.