Study guide

8.6 Vulnerability Management and Threat Intelligence

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.6 Vulnerability Management and Threat Intelligence

Key Takeaways Explain This Topic AI

Microsoft Defender Vulnerability Management (MDVM) provides continuous asset discovery, risk-based vulnerability assessment, and built-in remediation across Windows, macOS, Linux, Android, iOS, and network devices.

MDVM is available as an add-on to Defender for Endpoint Plan 2 and as a standalone offering; it prioritizes vulnerabilities by breach likelihood and business context.

Microsoft Threat Intelligence (listed as Microsoft Defender Threat Intelligence before the October 21, 2026 outline) provides threat actor, indicator, and infrastructure context to enrich investigations.

Vulnerability Management = your weaknesses/exposure; Threat Intelligence = the adversary/threat context.

Both feed the Microsoft Defender portal; do not confuse vulnerability management with Purview compliance score.

Last updated: October 2026

Defender Vulnerability Management (MDVM)

Microsoft Defender Vulnerability Management (MDVM) continuously discovers assets and assesses their vulnerabilities and misconfigurations , then helps remediate them — all prioritized by real-world risk rather than raw CVSS scores. It uses Microsoft threat intelligence, breach-likelihood predictions , and business context so the highest-risk exposures rise to the top. Coverage spans Windows, macOS, Linux, Android, iOS, and network devices .

Core MDVM capabilities:

Capability What it provides

Asset discovery & inventory Continuous, real-time view of devices, software, certificates, browser extensions, and firmware

Risk-based vulnerability assessment Prioritizes vulnerabilities by exploitability and breach likelihood, not just severity

  • Security baselines assessment Checks devices against benchmarks (e.g., CIS)
  • Built-in remediation Creates remediation requests that flow to IT (integrates with Intune)
  • Blocking vulnerable apps / mitigations Reduce exposure while patches are pending

MDVM grew out of the threat & vulnerability management engine in Defender for Endpoint. It is available as core capabilities in Defender for Endpoint Plan 2 , as an add-on , and as a standalone offering. The exam cue is simple: anything about finding, prioritizing, and reducing your own weaknesses and exposure is Defender Vulnerability Management .

Microsoft Threat Intelligence

Microsoft Threat Intelligence (listed as Microsoft Defender Threat Intelligence, or Defender TI, before the October 21, 2026 outline) is the other side of the coin: instead of your weaknesses, it provides context about the adversary — threat actors, their tools, indicators of compromise (IOCs), and malicious infrastructure (domains, IPs, host pairs). It maps the global threat landscape so analysts can enrich an investigation: "who is behind this, what infrastructure do they use, what else is connected to this indicator?" This intelligence is surfaced through threat analytics in the Microsoft Defender portal and enriches incidents across Defender XDR and Microsoft Sentinel.

Telling the Two Apart (and from Look-alikes)

The two names describe their jobs; let that guide you:

Question is about... Choose One-line cue

Your weaknesses / exposure to fix Defender Vulnerability Management "What are we exposed to and how do we fix it?"

The adversary / threat landscape Microsoft Threat Intelligence "Who is attacking and what infrastructure do they use?"

  • Cross-service incident investigation in one portal Microsoft Defender XDR Correlated incidents
  • SIEM/SOAR , hunt across all data, playbooks Microsoft Sentinel Tenant-wide analytics
  • Compliance score / improvement actions Microsoft Purview Compliance Manager Regulatory posture

Two traps to avoid:

Vulnerability management is NOT compliance score. Defender Vulnerability Management (security domain) measures technical exposure ; Compliance Manager / compliance score (Purview, compliance domain) measures regulatory posture . Both "reduce risk," but they are different exam answers.

Threat Intelligence is NOT Sentinel. If the prompt is broad SIEM/SOAR — ingest any log, hunt across everything, run playbooks — that is Microsoft Sentinel . Microsoft Threat Intelligence specifically means threat actor/indicator/infrastructure context .

Quick cues

"Discover and prioritize vulnerable software on our devices" → Defender Vulnerability Management .

"Research a threat actor's tools and malicious infrastructure" → Microsoft Threat Intelligence .

"Improve our regulatory compliance score" → Purview Compliance Manager (not vulnerability management).

Risk-Based Prioritization — Why It Matters

The defining idea of Defender Vulnerability Management is that not all vulnerabilities are equal. A typical enterprise has thousands of open vulnerabilities and cannot patch them all at once. MDVM ranks them by real-world risk — combining the vulnerability's exploitability and active-exploitation signals (Microsoft threat intelligence and breach-likelihood predictions) with business context (how exposed and how critical the affected asset is).

The result is a prioritized, finite list of the exposures that actually matter most, with built-in remediation that hands work to IT (integrating with Microsoft Intune) and the option to block vulnerable applications as an interim mitigation while patches are scheduled. It also continuously inventories not just software but certificates, browser extensions, firmware, and hardware , broadening the picture of what could be exploited.

Its packaging is worth a one-line memory note: MDVM's core capabilities are included in Defender for Endpoint Plan 2 , and a fuller premium feature set is available as an add-on or as a standalone product — so an organization can get vulnerability management without buying the full endpoint suite.

Threat Intelligence — Knowing the Adversary

Where MDVM looks inward at your exposure, Microsoft Threat Intelligence looks outward at the adversary . It maps the global threat landscape — profiles of threat actors , their tools and techniques , indicators of compromise , and the malicious infrastructure (domains, IP addresses, host pairs, certificates) they operate. Analysts use it to enrich an investigation: pivot from a suspicious domain to everything connected to it, or read an actor profile to understand intent.

Microsoft surfaces this intelligence through threat analytics in the Defender portal, and it enriches incidents across both Defender XDR and Microsoft Sentinel .

Two Clean Distinctions for Exam Day

Keep these straight: Vulnerability Management = inward, my weaknesses, technical exposure (security domain). Threat Intelligence = outward, the adversary, threat context (security domain). Neither is Microsoft Sentinel — Sentinel is the SIEM/SOAR that consumes this intelligence at scale. And vulnerability management is not the same as Purview's compliance score , which measures regulatory posture in the compliance domain. When a question pairs "risk" with technical weaknesses on devices, answer Defender Vulnerability Management ; when it pairs "risk" with regulations and controls, answer Compliance Manager .