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.
The Microsoft Secure Future Initiative (SFI) and Security Adoption Framework (SAF) serve different but complementary purposes:
- SFI is Microsoft's internal, multiyear security transformation program. It provides lessons from Microsoft's experience improving security across engineering, operations, governance, architecture, and organizational practices.
- SAF is customer-facing guidance for structuring and sustaining security modernization based on an organization's business priorities and risks.
SAF incorporates relevant lessons and practices from Microsoft's SFI experience without reproducing SFI's internal organizational model. Organizations can use these lessons within their own security programs while adapting them to their risks, technology estate, capabilities, regulatory requirements, and organizational structure.
How SFI informs SAF
SFI provides several types of experience that inform SAF guidance:
- Culture and governance: Microsoft's transformation reinforces the importance of executive accountability, security culture, governance, risk management, organizational roles, and security architecture.
- Security principles: Secure by Design, Secure by Default, and Secure Operations inform how security is planned, designed, implemented, and operated.
- Engineering priorities: SFI's six engineering pillars show where Microsoft prioritized improvements across identity, tenants, networks, engineering systems, detection, and response.
- Implementation experience: Practices developed and refined through SFI provide examples of how organizations can make security improvements repeatable, measurable, and sustainable.
These SFI concepts inform SAF, but they do not become a separate SAF taxonomy. SAF organizes customer security modernization around business priorities and risk, security disciplines, technologies that must be protected, and technical implementation.
Culture, governance, and architecture
Microsoft's SFI transformation extends beyond technical controls. It also includes changes to culture, governance, accountability, risk management, and architecture.
These elements connect primarily to the following SAF security disciplines:
| SFI area | Relevant SAF security discipline |
|---|---|
| Security culture, training, and organizational accountability | Strategy, Integration, and Governance |
| Cybersecurity governance and policy | Strategy, Integration, and Governance |
| Managing and mitigating security risk at scale | Strategy, Integration, and Governance; Security Posture |
| End-to-end security architecture | Security Architecture |
These mappings illustrate relationships between Microsoft's SFI experience and customer-facing SAF guidance. Organizations should adapt these practices to their own governance structures, decision rights, risk management processes, and operating models.
SFI security principles
SFI is guided by three security principles:
- Secure by Design: Integrate security requirements into architectures and engineering decisions from the beginning.
- Secure by Default: Design and operate technologies with strong baseline protections and safer default configurations.
- Secure Operations: Continuously detect, respond, recover, and improve based on threat intelligence, operational evidence, and lessons learned.
These principles apply broadly across SAF rather than mapping to a single discipline or technology. They influence security strategy, architecture, development, implementation, and operations.
SFI also applies Zero Trust principles throughout Microsoft's security transformation. SAF provides customer-facing guidance for applying Zero Trust across business and security decisions, architecture, technologies, implementation, and operations.
Map SFI engineering priorities to SAF
SFI execution is organized around six engineering pillars. These pillars identify areas where Microsoft prioritized change within its own environment.
The following mapping provides a navigation bridge from SFI priorities to relevant SAF guidance. It does not imply structural equivalence between SFI and SAF and is not an objective-by-objective or activity-by-activity crosswalk.
| SFI engineering priority | Relevant SAF security disciplines | Relevant SAF technologies |
|---|---|---|
| Protect identities and secrets | Access and Identity; Security Architecture | Identity; Applications |
| Protect tenants and isolate systems | Access and Identity; Security Architecture; Infrastructure Security | Identity; Infrastructure; Network |
| Protect networks | Infrastructure Security; Access and Identity; Security Architecture | Network; Infrastructure |
| Protect engineering systems | Development Security; Security Architecture | Applications; Infrastructure |
| Monitor and detect cyberthreats | SecOps/SOC; Security Posture | Cross-technology telemetry and security signals |
| Accelerate response and remediation | SecOps/SOC; Security Posture; Strategy, Integration, and Governance | Cross-technology response and remediation |
Many SFI priorities span multiple SAF disciplines and technologies. This reflects the cross-functional nature of security work rather than a one-to-one relationship between the two models.
Learn from SFI implementation experience
SFI also provides implementation lessons that can help organizations translate security priorities into repeatable practices.
For example, SFI uses paved paths to make secure practices easier to adopt consistently. Paved paths provide approved patterns, tools, and approaches that help teams perform common work in a secure and repeatable way.
Paved paths are an SFI implementation approach, not a SAF taxonomy. SAF can incorporate lessons from approaches such as paved paths while allowing organizations to select implementation models appropriate to their own technologies, teams, risks, and operating environments.
How to use this mapping
Use SFI, this mapping, and SAF for different purposes:
- Use SFI to understand Microsoft's security priorities, transformation experience, and lessons learned.
- Use this mapping to identify SAF security disciplines and technologies related to those lessons.
- Use SAF to organize security modernization around your organization's business priorities, risks, roles, technology estate, and implementation needs.
- Use Microsoft architecture, technology, and product guidance to design, implement, and sustainably operate the resulting security capabilities.
This approach lets organizations learn from Microsoft's experience without assuming that Microsoft's internal organizational structure or implementation model should be reproduced directly.