Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article provides an overview of Microsoft Zero Trust security solutions.
Security adoption
Microsoft's structured adoption model for Zero Trust security focuses on three components:
- Business scenarios help business leaders to define critical security outcomes across the organization. They focus on why we're adopting Zero Trust security.
- Security disciplines define the strategy, architecture, and processes required to support the security outcomes. They focus on what capabilities are needed.
- Technology pillars focus on implementing security for specific areas such as identity, data, and devices. They focus on where security capabilities are applied.
Technical solutions are the final step in the security adoption and deployment journey and focus on how. They connect the business scenarios, discipline strategies, and architectures, together with relevant technology pillars into step-by-step product-level implementation guides.
Technical solutions
Technical solutions do the following:
- Align to business scenarios.
- Translate and break down business scenarios into actionable steps.
- Implement security architectures and controls from across security disciplines.
- Base implementation guidance on Microsoft security best practices.
- Enforce security controls across technology pillars.
How solutions use technology pillars
Technology pillars define where security controls are applied, but they aren't implemented on their own.
Technical solutions use technology pillars in two ways:
- Organize implementation around a primary pillar. Each solution focuses on securing a specific area, such as identity, endpoints, or data.
- Apply controls across multiple pillars Implementing a solution requires integrating capabilities from other pillars. For example, securing identity also depends on device compliance, application access, and security operations.
To summarize:
- Technology pillars provide the structure and scope.
- Solutions provide the end-to-end implementation.
Choose your starting point
You can implement Zero Trust solutions from a couple of starting points:
- You can start with a business scenario that's important for your business. For example Improve security posture and compliance across the organization.
- Alternatively you might want to focus on improving security for a specific domain, and start with a specific technology pillar. For example Secure endpoints across the organization.
Both approaches use the same set of Microsoft security technologies.
Scenario-based adoption ensures alignment to business priorities, while technology-focused adoption helps address immediate risks in specific areas of security.
Start with business scenarios
The table summarizes technical solutions based on business scenarios. Follow any of the solutions for end-to-end implementation guidance.
| Solution | Business scenario |
|---|---|
| Protect Microsoft Copilot | Rapidly and securely adopt AI |
| Secure hybrid work | Enable people to do their job securely |
| Protect privileged access | identify and protect critical business assets |
| Improve security posture | Continuously improve security posture and compliance. |
| Meet compliance requirements | Continuously improve security posture and compliance. |
| Minimize attack impact | Minimize business damage from security incidents |
Start with technology pillars
The table summarizes technical solutions based on specific technology pillars. Follow any of the solutions for end-to-end implementation guidance.
Each solution is organized by a primary technology pillar but integrates controls from multiple pillars.
| Solution | Technology pillar |
|---|---|
| Secure identity with Zero Trust | Identity - Define the Zero Trust control plane across people, services, and devices. Verify every access request using strong authentication, enforce conditional access, and apply least privilege based on risk, compliance, and typical behavior. |
| Secure endpoints with Zero Trust | Devices - Protect all devices accessing your environment—from IoT and mobile to partner-managed and cloud-hosted systems. Enforce device health and compliance, and continuously monitor endpoint risk before granting or maintaining access. |
| Secure data with Zero Trust | Data - Protect data at all times, regardless of location. Classify and label sensitive information, encrypt it, and enforce access controls and usage restrictions based on data sensitivity. |
| Secure apps with Zero Trust | Apps - Secure applications and APIs as the interface to data. Discover and govern shadow IT, enforce in-app permissions, apply real-time access controls, monitor for abnormal behavior, and validate secure configuration. |
| Secure infrastructure with Zero Trust | Infrastructure - Protect compute resources including servers, VMs, containers, and microservices. Assess configurations, enforce just-in-time (JIT) access, and use telemetry to detect and automatically respond to threats and anomalies. |
| Secure networks with Zero Trust | Networks - Secure the transport layer for all access. Use segmentation and micro-segmentation to limit lateral movement, and apply encryption, monitoring, analytics, and real-time threat protection across network traffic. |
| Secure SecOps | SecOps - Integrate signals across all pillars to detect, investigate, and respond to threats. Correlate alerts, automate responses, and use centralized visibility to continuously validate trust and improve security posture. |
Next steps
- Review technology pillars.
- Learn about our Zero Trust adoption model.
- Review critical security business scenarios.