नोट
इस पेज तक पहुँच के लिए प्रमाणन की आवश्यकता होती है. आप साइन इन करने या निर्देशिकाओं को बदलने का प्रयास कर सकते हैं.
इस पेज तक पहुँच के लिए प्रमाणन की आवश्यकता होती है. आप निर्देशिकाओं को बदलने का प्रयास कर सकते हैं.
This article provides an overview of Microsoft Zero Trust security solutions.
Security adoption
The Microsoft Security Adoption Framework (SAF) connects security strategy to execution through four connected components:
- Business scenarios help business leaders define critical security outcomes across the organization. They focus on why the organization is improving security.
- Security disciplines organize the strategy, architecture, processes, and operating practices required to support those outcomes. They focus on what security work and capabilities are needed.
- Technologies identify what must be protected across identity, endpoints, applications, data, infrastructure, network, and AI. They focus on where security capabilities are applied.
- Technical solutions translate security requirements into implementation and sustainable operations across products and platforms. They focus on how security is implemented and operated.
Together, these four components connect desired outcomes to execution. Technical solutions combine business context, discipline strategies, architecture, and relevant technology guidance into step-by-step product-level implementation guidance.
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
Use current SAF guidance to define the business outcome, organize the required security work, and then select technical solutions and product guidance for implementation.
| Business scenario | Start with |
|---|---|
| Rapidly and securely adopt AI | Protect Microsoft Copilot |
| Enable people to do their job securely | Enable secure remote work |
| Identify and protect critical business assets | Secure and govern privileged access |
| Continuously improve security posture and compliance | Strengthen security posture and compliance and Security standards and frameworks |
| Minimize business damage from security incidents | 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 | Endpoints - 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 | Applications - 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 | Network - 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 AI with Zero Trust | AI - Secure AI applications, agents, models, prompts, context, tools, and connectors. Apply strong identity controls, least privilege permissions, data protection, runtime monitoring, and policy governance across AI workflows. |
The Zero Trust Workshop also includes DevSecOps and SecOps as workshop pillars. In SAF, these pillars map to the Development Security discipline and SecOps discipline, rather than to technologies.
Next steps
- Review technology pillars.
- Learn about the Security Adoption Framework (SAF).
- Review critical security business scenarios.