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.
Security standards and frameworks help organizations define security objectives, practices, and requirements. The Microsoft Security Adoption Framework (SAF) helps translate these standards and frameworks into coordinated security work across business, technology, and security roles and connects that work to technology implementation. You don't need to adopt SAF instead of an existing standard or framework. SAF can help translate the objectives and requirements you already use into coordinated security work and technology implementation.
This guidance helps organizations understand how established security standards and frameworks relate to SAF and Microsoft security technologies. The framework mappings provide more detailed alignment where available.
Organizations can use this guidance and the mappings to:
- Translate standards and framework objectives into actionable security work. Connect objectives, practices, and requirements to SAF security disciplines, roles, and responsibilities.
- Plan and implement security improvements. Identify relevant security capabilities, technologies, implementation guidance, and Microsoft products that can help address framework objectives and organizational priorities.
- Coordinate work across business, technology, and security teams. Provide shared context for planning, architecture, implementation, operations, and security oversight.
- Assess progress and communicate alignment. Relate security improvements and implemented capabilities back to the objectives and requirements of the standard or framework.
These mappings help organizations apply standards and frameworks using SAF and Microsoft security technologies. They don't replace authoritative standards, frameworks, or requirements, and they don't by themselves demonstrate compliance.
Security and compliance have different purposes, but they reinforce each other. Effective, risk-driven security establishes repeatable controls, clear ownership, operational processes, and measurable evidence. Organizations can map applicable regulatory, contractual, and industry requirements to those security practices and controls. Good security makes compliance easier to achieve, demonstrate, and sustain, but it doesn't automatically satisfy every compliance obligation.
Zero Trust
Zero Trust provides the security principles that underpin SAF. SAF helps organizations apply these principles across business decisions, security practices, technology design, implementation, and operations.
Use these resources to understand Zero Trust and connect it to SAF:
- Zero Trust overview explains the Zero Trust principles and how organizations can apply them across their security strategy.
- Zero Trust frameworks and standards connects Zero Trust guidance to established frameworks, standards, and related implementation guidance.
Framework mappings
Use these mappings to connect objectives from established security frameworks and strategies to SAF security disciplines and technologies. From there, use technical solutions and Microsoft product guidance to support implementation. This connects each framework to SAF while preserving its original structure, terminology, and intent.
NIST Cybersecurity Framework 2.0
Use the NIST Cybersecurity Framework 2.0 mapping to connect the CSF Core, Organizational Profiles, and Tiers to SAF disciplines, current role actions, technologies, technical solutions, and relevant Microsoft implementation guidance.
CIS Controls and CIS Benchmarks
Use the CIS Controls and CIS Benchmarks mapping to distinguish organization-level CIS Controls and Implementation Groups from technology-specific CIS Benchmarks, assign role actions, and connect the work to SAF and implementation guidance.
The Open Group Zero Trust model
Use The Open Group Zero Trust model mapping to connect current Zero Trust capabilities, security roles, and Architecture Building Blocks (ABBs) to SAF and selected Microsoft technology examples. The page distinguishes published Open Group material from evolving draft and Snapshot material.
CISA Zero Trust Maturity Model
Use the CISA Zero Trust Maturity Model mapping and implementation guidance to connect CISA's five pillars and three cross-cutting capabilities to relevant SAF security disciplines and technologies, then continue to Microsoft implementation guidance.
DoD Zero Trust Strategy
Use the DoD Zero Trust Strategy mapping and implementation guidance to navigate from DoD Zero Trust pillars and capability areas to relevant SAF security disciplines and technologies, then continue to Microsoft implementation guidance.
Use a standard or framework as a SAF starting point
Build security around business and security risk, then map applicable compliance requirements to the resulting practices and controls. You can also use a standard or framework as a practical starting point when your organization already uses it, must meet specific requirements, or wants established structure for security improvements.
To use a standard or framework as a SAF starting point:
- Identify business and security risks and the outcomes that matter.
- Identify relevant objectives, practices, or requirements from the applicable standard or framework.
- Connect them to SAF security disciplines to understand the work, ownership, and operational processes needed.
- Identify the technologies that must be protected and the roles involved.
- Use technical solutions and Microsoft product guidance to select implementation options.
- Map applicable compliance requirements to the resulting practices and controls, and collect measurable evidence through normal operations.
- Assess progress and alignment against organizational outcomes and applicable framework or standard objectives.
Security does not equal compliance. Alignment or compliance alone doesn't define security success, and effective security doesn't automatically establish compliance. SAF helps organizations connect framework-driven work to broader security outcomes, strategy, architecture, implementation, and operations while reusing consistent controls, ownership, processes, and evidence across applicable requirements.
Choose your path
Security leaders and governance teams
- Organize the security improvement program with SAF.
- Use SAF effectively across the adoption journey.
- Continue to the framework mappings to connect requirements and objectives to security work, roles, and technologies.
Architects and practitioners
- Plan integrated capabilities with MCRA.
- Modernize end-to-end security architecture.
- Connect Microsoft security products and platforms to outcomes.
- Continue from framework objectives to technical solutions.