azureblog.co.uk
← SC-200 study plan
SC-200 · Manage a security operations environment

Configure the Microsoft Sentinel SIEM and platform

Sentinel roles, retention across the analytics tier, data lake tier and XDR tables, workbooks, and SOC optimization.

  • 16 min
  • 4 concepts
  • Try it yourself
  • 4-question check

Learn

Microsoft Sentinel runs in the Microsoft Defender portal on top of a Log Analytics workspace and the Sentinel data lake. Setting it up well means the right people have the right access, data is kept for the right time at the right cost, and coverage keeps improving.

  1. 1

    Specify Microsoft Sentinel roles

    Microsoft Sentinel Reader: view data, incidents and workbooks. Microsoft Sentinel Responder: also manage incidents (assign, change status). Microsoft Sentinel Contributor: also create and edit analytics rules, workbooks and other content. Microsoft Sentinel Playbook Operator: run playbooks manually. Automation Contributor: lets Sentinel add playbooks to automation rules. Assign at resource group or workspace scope; Logic App Contributor is needed to create playbooks.

    Remember: Reader → Responder → Contributor.

  2. 2

    Manage data retention for XDR and Microsoft Sentinel tables, including Analytics, Data lake, and XDR tiers

    XDR tier: Defender XDR advanced hunting tables are kept for 30 days by default. Analytics tier: Sentinel workspace tables for detections and hunting, with 90 days included and longer interactive retention configurable. Data lake tier: low-cost long-term storage (up to 12 years) queried with KQL jobs and notebooks; analytics data is mirrored there, and some tables can go to the lake only. Set retention per table in Table management.

    Remember: Hot detections: analytics. Years of cheap history: data lake.

  3. 3

    Create and configure Microsoft Sentinel workbooks

    Workbooks are interactive dashboards built on Azure Monitor Workbooks: KQL queries, parameters, charts and grids. Install templates from the content hub solutions (for example Microsoft Entra ID sign-ins), save and customise them, or create your own.

    Remember: Workbooks come with content hub solutions.

  4. 4

    Optimize the Microsoft Sentinel platform, including SOC optimization recommendations

    SOC optimization gives recommendations on data value (tables ingested but not used by detections, suggestions to move them to cheaper tiers), threat-based coverage (gaps against attack scenarios such as human-operated ransomware or AiTM, with rules to add), and similar-organisation recommendations. Track and mark recommendations as completed.

    Remember: Paying for data no rule uses? SOC optimization will say so.

Data tiers

TierUsed forRetention
XDR (advanced hunting)Defender tables, hunting, custom detections30 days default
Analytics (Sentinel)Detections, hunting, incidents90 days included, extendable
Data lakeLong-term, low-cost analysis with KQL jobs and notebooksUp to 12 years

Try it

Decide where a data source should live.

This interactive part needs JavaScript.

In the portal

  • Table managementMicrosoft Defender portal: Microsoft Sentinel > Configuration > Tables
  • WorkbooksMicrosoft Defender portal: Microsoft Sentinel > Threat management > Workbooks
  • SOC optimizationMicrosoft Defender portal: Exposure management > SOC optimization
  • Content hubMicrosoft Defender portal: Microsoft Sentinel > Content management > Content hub

Key terms

Click a card to see the definition.

Check your understanding

4 questions. Score 80% or more and these skills are marked as confident in your SC-200 study plan.

  1. Which role can manage incidents but not create analytics rules?

  2. How long can the Sentinel data lake keep data?

  3. Default retention for Defender XDR advanced hunting data?

  4. Which feature flags ingested tables no detection uses?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.