Study guide
8.3 Defender for Endpoint
Azure SC-900 Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map
1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map
2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC
2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation
3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication
3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities
4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection
4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk
5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault
5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets
6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score
6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans
7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks
7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks
8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence
8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence
9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score
9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager
10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit
10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management
11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps
11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop
12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path
12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900
8.3 Defender for Endpoint
Key Takeaways Explain This Topic AI
Defender for Endpoint (formerly Microsoft Defender ATP) is Microsoft's endpoint security platform for Windows, macOS, Linux, iOS, and Android.
Its pillars include next-generation antimalware protection, endpoint detection and response (EDR), attack surface reduction (ASR), and threat and vulnerability management.
ASR rules block risky behaviors (like Office apps spawning child processes) to shrink the attack surface before exploitation.
EDR provides near-real-time behavioral detection, automated investigation and remediation, and advanced hunting on devices.
It ships in Plan 1 (preventive/ASR/next-gen AV) and Plan 2 (full EDR, automated investigation, threat & vulnerability management).
Last updated: June 2026
Endpoint Detection and Response Platform
Microsoft Defender for Endpoint (formerly Microsoft Defender ATP / Advanced Threat Protection ) is Microsoft's enterprise endpoint security platform. "Endpoint" means the devices users work on — and Defender for Endpoint is cross-platform, covering Windows, macOS, Linux, iOS, and Android . When an SC-900 scenario describes protecting, detecting threats on, or investigating devices , this is the product.
Defender for Endpoint is more than antivirus. It combines several capability pillars into one platform:
Pillar What it does
Next-generation protection Behavior-based, heuristic, real-time antimalware/antivirus (the evolution of Microsoft Defender Antivirus)
Attack surface reduction (ASR) Reduces the ways attackers can get in: ASR rules, application control, network protection, exploit protection, controlled folder access
Endpoint detection and response (EDR) Near-real-time behavioral detection of advanced attacks, with alerts surfaced as incidents
Automated investigation and remediation (AIR) Automatically investigates alerts and remediates threats, reducing analyst load
Threat & vulnerability management (TVM) Discovers, prioritizes, and helps remediate device vulnerabilities and misconfigurations
- Microsoft Threat Experts Managed threat hunting / expert assistance
- Attack Surface Reduction (ASR)
Attack surface reduction is about closing off the avenues an attacker can exploit before an attack succeeds. ASR rules block or audit risky behaviors that legitimate software rarely needs — for example, blocking Office applications from creating child processes, blocking executable content from email, or blocking credential theft from LSASS. Other ASR-family controls include network protection (blocks connections to malicious domains/IPs), controlled folder access (anti-ransomware folder guarding), and exploit protection . The theme: shrink the attack surface so there is less to defend.
EDR and Automated Response
Endpoint detection and response (EDR) continuously monitors device behavior and detects advanced, post-breach activity in near real time. Detections become alerts that roll into Defender XDR incidents. Automated investigation and remediation can then triage and fix many threats without an analyst, and advanced hunting lets analysts query raw device telemetry with KQL. 6).
Plan 1 vs. Plan 2
Defender for Endpoint comes in two plans:
Plan 1 Plan 2 (adds)
Next-generation antimalware protection Everything in Plan 1, plus:
- Attack surface reduction rules Endpoint detection and response (EDR)
- Device-based Conditional Access controls Automated investigation and remediation
- Manual response actions Threat & vulnerability management
- Centralized management Advanced hunting, Threat Experts, sandbox/deep analysis
Memory hook: Plan 1 = prevent (next-gen AV + ASR); Plan 2 = full EDR + automation + vulnerability management.
Where Endpoint Fits — and Common Traps
Defender for Endpoint is one of the four Defender XDR workloads; its alerts correlate with Office 365, Identity, and Cloud Apps signals into unified incidents. Keep these distinctions straight:
Endpoint device protection → Defender for Endpoint. Do not pick Defender for Office 365 (email) or Defender for Identity (on-prem AD).
Network controls like NSGs, Azure Firewall, WAF, Bastion, DDoS Protection are Azure infrastructure security from another chapter — not Defender for Endpoint.
Identifying/prioritizing device weaknesses → threat & vulnerability management within Defender for Endpoint, the engine behind Defender Vulnerability Management.
Quick cues
"Protect/detect threats on laptops, servers, mobile devices" → Defender for Endpoint .
"Block Office apps from spawning child processes" → ASR rule .
"Near-real-time behavioral detection and automated remediation on devices" → EDR (Plan 2) .
How Onboarding and Detection Flow
Defender for Endpoint protects a device once that device is onboarded — typically via Microsoft Intune, Group Policy, Configuration Manager, or a local script. Onboarded devices stream behavioral telemetry to the Defender for Endpoint cloud service, which scores risk, raises alerts, and exposes the device in the inventory. Each device gets a risk level and an exposure level so security teams can prioritize. Alerts then roll into Microsoft Defender XDR incidents, correlating with email, identity, and SaaS signals.
A worked scenario shows the pillars in action: a user opens a malicious macro-enabled document. Next-generation protection may block the known-bad payload outright. An attack surface reduction rule that blocks Office applications from creating child processes stops the macro from launching a script even if the file itself is unknown. If something still executes, EDR detects the anomalous process chain in near real time and raises an alert, and automated investigation and remediation can quarantine the file and isolate the device without waiting for a human.
Meanwhile threat & vulnerability management had already flagged that the device was running an outdated, exploitable application — context that helps the analyst understand how the attack was possible and what to patch.
Endpoint vs. Network vs. Identity — Keep Lanes Clear
A frequent SC-900 mistake is sending network or identity scenarios to Defender for Endpoint. Defender for Endpoint secures the device itself — the operating system, processes, files, and local configuration. It does not replace Azure network security (NSGs, Azure Firewall, Web Application Firewall, Azure Bastion, DDoS Protection), and it is not Defender for Identity (which watches on-prem Active Directory). When the protected object is a laptop, server, or phone , choose Defender for Endpoint; when it is a network boundary or an AD identity , choose the product for that surface. 6.