Domain 3 · 30–35% — heaviest domain

Manage security and threats using Microsoft Defender XDR

The integrated extended detection & response suite. Know which Defender product covers which attack surface, how incidents correlate alerts, and the day-to-day policies for email, endpoint and cloud-app protection.

Defender XDR is the umbrella over four workload products:
flowchart TD XDR[Microsoft Defender XDR
security.microsoft.com] --> O[Defender for Office 365
email & collaboration] XDR --> E[Defender for Endpoint
devices] XDR --> I[Defender for Identity
on-prem AD signals] XDR --> CA[Defender for Cloud Apps
SaaS / shadow IT] O --> INC[Unified Incidents] E --> INC I --> INC CA --> INC
Defender productProtectsKey signals / sensors
Defender for Office 365Email, Teams, SharePoint, OneDriveMail flow, URLs, attachments, impersonation
Defender for EndpointWorkstations & servers (EDR)Process/file/network events, vulnerabilities
Defender for IdentityOn-prem AD DS / AD FSDomain-controller sensors, lateral movement, recon
Defender for Cloud AppsSaaS & cloud apps (CASB)App activity, shadow IT, OAuth apps

One portal, one correlated incident queue

All four products surface in security.microsoft.com and feed a single incident queue — Defender XDR automatically correlates alerts across email, endpoint, identity and cloud apps into one attack story. Permissions can be managed by Defender XDR Unified RBAC (custom roles built from granular data sources & permission levels) which can supersede the individual product role models.

Caveat — Defender XDR vs Defender for Cloud

Microsoft Defender XDR (security.microsoft.com) protects M365 workloads / endpoints / identities. Microsoft Defender for Cloud (Azure portal) is a separate CSPM/CWPP product for Azure/AWS/GCP resources. The exam offers both as options — choose XDR for Microsoft 365 scenarios.

3.1 Review & respond to security reports and alerts

Exposure Management & Microsoft Secure Score

Microsoft Secure Score measures security posture as a percentage = points achieved ÷ points achievable. Improvement actions are grouped by product: Identity (Entra), Devices (Defender for Endpoint), Apps (O365 / Cloud Apps), and Data. A higher score means stronger posture.

Action statusPoints awarded?Meaning
To address❌ NoNot yet actioned (default state)
Planned❌ NoOn the roadmap but not yet done
Risk accepted❌ NoYou knowingly accept the risk — sacrifices the points
Resolved through third partyYesMitigated by a non-Microsoft product
Resolved through alternate mitigationYesMitigated by another internal control

Caveat — Secure Score ≠ Compliance / Identity Secure Score

Microsoft Secure Score (security posture) is different from Compliance Manager / Compliance score (Purview) and from the legacy "Identity Secure Score". Remember: Risk accepted = no points, but Resolved through third party / alternate mitigation = full points.

Incidents & alerts

An alert is a single detection; an incident is the aggregation of all related alerts + affected assets (devices, users, mailboxes, apps) into one attack story. Defender XDR correlates automatically across products, so one click shows the full kill chain. Manage in security.microsoft.com → Incidents & alerts.

flowchart LR A1[Alert: phishing email
Defender for O365] --> INC((Incident)) A2[Alert: malicious file run
Defender for Endpoint] --> INC A3[Alert: suspicious sign-in
Entra / Identity] --> INC A4[Alert: mass download
Defender for Cloud Apps] --> INC INC --> ASSETS[Assets: user · device · mailbox] INC --> STORY[Attack story & graph] INC --> RESP[Respond: assign · classify · remediate]
Correlation: alerts from multiple products roll up into one incident with a shared attack story.

Incident management workflow:

Automated Investigation & Response (AIR) & the Action center

Advanced hunting (KQL)

Advanced hunting proactively queries up to 30 days of raw event data using KQL (Kusto Query Language). Two modes: Guided (visual query builder, no KQL needed) and Advanced (write KQL directly).

Schema tableContains
DeviceEvents, DeviceProcessEvents, DeviceNetworkEventsEndpoint process, file & network telemetry
EmailEvents, EmailAttachmentInfo, EmailUrlInfoDefender for Office 365 mail flow & payloads
IdentityLogonEvents, IdentityInfoSign-ins & identity (Entra + Defender for Identity)
CloudAppEventsDefender for Cloud Apps activity
AlertInfo, AlertEvidenceAlerts & their linked entities
// KQL: emails that delivered a malicious attachment in last 7 days
EmailAttachmentInfo
| where Timestamp > ago(7d)
| where MalwareFilterVerdict == "Malware"
| join EmailEvents on NetworkMessageId
| project Timestamp, SenderFromAddress, RecipientEmailAddress, FileName, Subject
// KQL: devices that ran a specific suspicious process
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName in~ ("powershell.exe", "cmd.exe")
| where ProcessCommandLine has "-enc"
| project Timestamp, DeviceName, AccountName, ProcessCommandLine
| order by Timestamp desc

Custom detection rules

Save a hunting query as a custom detection rule to generate alerts automatically. You set the frequency (every 24h / 12h / 6h / 3h / continuous (NRT)), the impacted entities columns, severity, and response actions (isolate device, run AV scan, block file, etc.). The query must return Timestamp and a device/user/mailbox ID column.

Defender XDR reports

Know which report answers which question:

ReportShows
Threat protection statusMalware/phish detections, ZAP actions, detection technology trends
Mailflow status / Top senders & recipientsMail volume, blocked vs delivered, spoof
URL protectionSafe Links click verdicts (allowed / blocked)
Device health / Vulnerable devicesSensor health, OS & AV status, exposure
Compromised usersAccounts flagged suspicious or restricted

Threat analytics & Defender Threat Intelligence

Threat analytics is the in-product threat-intelligence dashboard written by Microsoft security researchers. Each threat analytics report covers an active campaign, technique or actor and ties it to your tenant:

Microsoft Defender Threat Intelligence (MDTI) goes deeper: searchable threat-actor profiles, IOCs (indicators of compromise — IPs, domains, hashes), and intelligence articles you can pivot from into hunting.

Caveat — Threat analytics vs Secure Score

Both surface "recommendations," but Threat analytics mitigations are threat-specific (close gaps for an active campaign), whereas Secure Score actions improve overall posture. For "respond to a specific named threat," choose Threat analytics.

3.2 Email & collaboration protection — Defender for Office 365

Builds on Exchange Online Protection (EOP) — the always-on anti-malware/anti-spam baseline for all Exchange Online mailboxes. Defender for Office 365 adds advanced protection in two plans:

LayerProvides
EOP (all EXO)Anti-malware, anti-spam, anti-phishing (spoof), connection & mail-flow filtering
Defender for O365 Plan 1Safe Attachments, Safe Links, advanced anti-phishing (impersonation), real-time detections
Defender for O365 Plan 2Plan 1 + Threat Explorer, Attack Simulation Training, Automated Investigation & Response (AIR), proactive threat hunting
flowchart LR M[Inbound email] --> C[Connection filter
IP allow/block] C --> MAL[Anti-malware
+ Safe Attachments] MAL --> SPF[Anti-spoof /
anti-phishing] SPF --> SPAM[Anti-spam
content filter] SPAM --> RULE[Mail flow rules
transport rules] RULE --> D{Verdict} D --> INBOX[Inbox] D --> JUNK[Junk] D --> QUAR[Quarantine]
Simplified EOP / Defender for Office 365 inbound filtering order. Safe Links rewrites URLs at time-of-click after delivery.

Threat policies & rules

PolicyWhat it doesCaveat
Safe AttachmentsDetonates attachments in a sandbox before deliveryActions: Off / Monitor / Block / Replace / Dynamic Delivery (body delivered, attachment scanned)
Safe LinksTime-of-click URL rewriting & scanning in mail, Teams, Office appsProtects against URLs that go bad after delivery
Anti-phishingImpersonation & spoof intelligence, mailbox intelligenceP1+ adds user/domain impersonation protection
Anti-malwareMalware filter + Common Attachments FilterZero-hour Auto Purge (ZAP) removes mail post-delivery
Anti-spamInbound/outbound spam & bulk thresholdsOutbound spam policy can restrict compromised senders

Preset security policies & Configuration Analyzer

Standard and Strict preset policies apply Microsoft's recommended settings automatically. The Configuration Analyzer compares your custom policies to Standard/Strict and recommends improvements. Policy precedence: Strict > Standard > custom (by priority) > Built-in protection.

Caveat — Tenant Allow/Block List vs transport rules

Use the Tenant Allow/Block List (Defender portal) to allow/block specific senders, domains, URLs, files. Overrides hierarchy matters: explicit block in the allow/block list, then policies. Don't confuse with Exchange mail flow (transport) rules, which are broader mail routing logic.

Safe Attachments — actions

ActionBehaviour
OffNo scanning
MonitorDeliver, but track detonation verdict
BlockBlock the message + attachment (current/future) recommended
Dynamic DeliveryDeliver the body immediately, attach the file once scanning clears (no delay to the email)

Safe Links — key settings

Anti-phishing detail

Anti-spam & anti-malware internals

ConceptMeaning
SCL (Spam Confidence Level)−1 (allow) to 9; higher = more likely spam
BCL (Bulk Complaint Level)1–9 rating of bulk/grey mail; threshold configurable
ASF (Advanced Spam Filter)Optional aggressive content rules (mostly legacy)
Common Attachments FilterAnti-malware blocks risky file types by extension (e.g. .exe, .js)
ZAPZero-hour Auto Purge retro-removes delivered spam/phish/malware when verdicts change
Outbound spam policyLimits/automatically restricts senders that exceed sending thresholds (compromise signal)

Alert policies

Alert policies (Defender/Purview portal) trigger alerts on activities — e.g. malware campaign detected, unusual external file sharing, a user exceeding sending limits. Many default alert policies ship enabled. Each has a severity and can email recipients.

Investigate & respond to email/collab threats

Quarantine & quarantine policies

Quarantine holds blocked messages. Quarantine policies control what end-users can do with their own quarantined items and whether they get notified:

End-user capabilityTypical use
No accessHigh-risk verdicts (malware, high-confidence phish) — admin only
Limited access (request release)User can preview & request release; admin approves
Full access (release)User can release themselves (e.g. bulk/spam)

Caveat — what users can release

By default, malware and high-confidence phishing are quarantined with admin-only release — end-users cannot release them even with a permissive policy. Quarantine notifications (formerly end-user spam notifications) are enabled per quarantine policy.

Attack simulation training

Attack Simulation Training (Defender for O365 Plan 2) runs benign phishing campaigns to train users. Technique types: Credential Harvest, Malware Attachment, Link in Attachment, Link to Malware, Drive-by URL, OAuth Consent Grant.

Restricted entities & blocked users

When a user is detected sending too much spam (likely compromised), they are added to Restricted entities and blocked from sending email. The admin investigates, secures the account (reset password, revoke sessions), then removes them from the restricted list to restore sending.

3.3 Endpoint protection — Defender for Endpoint

Onboarding devices

Microsoft Defender for Endpoint (MDE) is the EDR for devices. Onboarding methods depend on OS/management:

ScenarioOnboarding method
Intune-managed devicesIntune connector (Endpoint security) — recommended for cloud
Windows (manual / small scale)Local onboarding script from the portal
On-prem / domain-joined at scaleGroup Policy or Configuration Manager (SCCM/MECM)
ServersMDE plan / Defender for Servers (Azure Arc / Defender for Cloud)
macOS / Linux / mobilePlatform-specific packages / MDM

Onboarding & offboarding details

Devices appear in the Device inventory. Use Run a detection test to confirm onboarding. Set data retention, RBAC / device groups and device tags in Settings → Endpoints. Offboarding uses a separate script whose package expires after ~30 days — don't reuse old packages, and never deploy the offboarding script as your onboarding policy.

Caveat — onboarding method by management state

Cloud/Intune-managed → Intune EDR connector (Endpoint security → EDR). Domain-joined at scale → Group Policy or Configuration Manager. Standalone/small → local script. Down-level servers may need the MMA/unified agent or Defender for Cloud (Azure Arc).

Configure endpoint settings & reduce attack surface

Respond to threats on a device

From a device entity page (or via Live Response / custom detection), available response actions:

ActionEffect
Isolate deviceCut network connectivity (Defender still reports in); full or selective isolation
Restrict app executionOnly Microsoft-signed apps may run
Run antivirus scanTrigger quick/full Defender AV scan remotely
Collect investigation packageGather forensic artefacts for analysis
Live ResponseRemote shell to investigate/remediate (run scripts, pull files)
IndicatorsAdd file hash / IP / URL / certificate as allow, audit, or block across the org

Defender Vulnerability Management (MDVM)

Microsoft Defender Vulnerability Management surfaces a device Exposure score and prioritised security recommendations, mapping software weaknesses (CVEs) to your devices in real time.

Caveat — Exposure score vs Secure Score for Devices

In MDVM, a lower Exposure score is better (less exposed to vulnerabilities). The Secure Score for Devices (configuration posture) is the opposite — higher is better. Don't mix the directions up.

3.4 Microsoft Defender for Cloud Apps

The CASB (Cloud Access Security Broker) — visibility & control over SaaS apps, shadow IT, and data in the cloud. It works across four stages:

flowchart LR D[1 · Discover
find shadow IT] --> S[2 · Sanction / Govern
tag & connect apps] S --> P[3 · Protect
file policies · DLP · session control] P --> C[4 · Control & respond
alerts · governance actions]
Defender for Cloud Apps lifecycle: discover → sanction → protect → control.
Connection methodGives you
App connector (vendor API)Deep visibility + governance over sanctioned apps (activities, files, OAuth) — acts after the event
Cloud Discovery (traffic logs / MDE)Find shadow IT & risk-score discovered apps
Conditional Access App Control (reverse proxy)Real-time, in-session enforcement during access

App connector for Microsoft 365

App connectors use vendor APIs to connect sanctioned apps for deep visibility & governance. Connect the Microsoft 365 connector (one click, uses the same identity platform) to scan activity, files and apply governance to M365 data. App connectors give richer, ongoing control than Cloud Discovery — but they act after activity occurs (not in real time).

Conditional Access App Control (session & access policies)

Integrates with Entra Conditional Access to route sessions through Defender for Cloud Apps as a reverse proxy, enabling real-time controls:

Caveat — real-time control needs CAAC

To block a download on an unmanaged device in real time, you need a session policy via Conditional Access App Control — an app connector alone can only act after the fact, and Cloud Discovery only gives visibility.

Policies & triggering alerts

Policy typeDetects / does
Activity policySingle-activity rules (e.g. admin from risky IP) → alert/suspend
Anomaly detectionImpossible travel, unusual activity, mass download (UEBA-based)
File policyScan stored files for sensitive data / sharing; quarantine
Cloud Discovery policyAlert on new/risky discovered apps or data volumes
App discovery / OAuth app policyFlag risky third-party OAuth apps with broad permissions
Session policyReal-time controls via Conditional Access App Control (block download, etc.)

Interpret the activity log

The activity log records every action (sign-ins, file ops, admin changes) ingested from connected apps. Filter by user, app, IP, location; pivot to investigate; promote a recurring pattern into an activity policy.

Cloud App Discovery & responding to findings

Caveat — Discovery vs Connector vs Session control

Cloud Discovery = find shadow IT from logs (visibility). App connector = API-level governance of sanctioned apps (after-the-fact). Conditional Access App Control / session policies = real-time, in-session enforcement (e.g. block download on unmanaged device). Match the requirement to the right mechanism.