IntermediateMicrosoft Security Operations Analyst project · about 12 hours

Microsoft Sentinel workspace with detections

Connect data sources, write KQL detections and triage incidents.

The real-world brief

A SOC needs its first detections in Microsoft Sentinel.

What you will build

  • Connected data sources
  • Three analytics rules
  • Test incidents
  • Triage notes

Skills you will practise

Data connectorsKQLAnalytics rulesTriage

Tools

Microsoft SentinelKQLMicrosoft Entra ID logsDefender XDR connector

Project tasks

The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.

1Connect Steps in portal
2Detect Steps in portal
3Test Steps in portal
4Triage Steps in portal

How companies use Microsoft Security Operations Analyst

Banking: Stopping account takeover. Attackers used stolen passwords to sign in. MFA, Conditional Access and alerts on risky sign-ins. Takeovers stopped.

Hospital: Catching ransomware early. Ransomware spread before anyone noticed. Endpoint detection, SIEM rules and isolation playbooks. A drill showed attacks contained early.

Retail: Protecting customer data. Card and personal data sat in unknown places. Data discovery, labels, encryption and loss prevention. Sensitive data is known and protected.

Questions

Can I add the Microsoft Sentinel workspace with detections project to my resume?

Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.

How long does this project take?

About 12 hours of hands-on work, and it fits best after week 4 of the Microsoft Security Operations Analyst (SC-200) course.

Where do I get the step-by-step tasks?

Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.