หมายเหตุ
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลอง ลงชื่อเข้าใช้หรือเปลี่ยนไดเรกทอรีได้
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลองเปลี่ยนไดเรกทอรีได้
Microsoft's Secure Future Initiative provides lessons that organizations can use to strengthen their own security programs. Many of the security practices implemented through SFI are established security practices already covered by Microsoft Zero Trust, architecture, operational, and product guidance.
SFI adds value by showing which practices Microsoft prioritized, why they became priorities, what Microsoft changed, and what organizations can learn from Microsoft's experience. Use the existing Microsoft security guidance linked from this section to plan and implement these practices in your environment.
How to use this guidance
Use SFI to inform prioritization and program sequencing, not as a separate implementation framework.
- Start with the SFI overview for context and boundaries.
- Use SAF to organize your modernization journey.
- Use Zero Trust guidance to align principles and architecture.
- Use product and architecture documentation for implementation details.
Pillar 1: Protect identities and secrets
Security outcome Microsoft prioritized: Reduce unauthorized access risk from weak authentication, overprivilege, exposed secrets, and long-lived credentials.
SFI priorities: phishing-resistant authentication, managed identities, centralized secrets protection, automated rotation, supported identity SDKs, and exposed-secret detection.
Implementation insights from SFI: credential misuse and token abuse create high-impact attack paths; reducing standing credential risk and standardizing identity controls improves resilience.
Zero Trust alignment: Verify explicitly, Use least privilege, Assume breach.
Canonical implementation guidance:
- Secure identity with Zero Trust
- Microsoft Entra architecture
- Workload identities
- Privileged access strategy
- Azure Key Vault security baseline
SFI pattern pages retained for SFI-specific context:
- Phishing-resistant MFA
- Adopt standard SDKs for identity
- Safe Secrets Standard
- Secure identity to get ready for AI
Pillar 2: Protect tenants and isolate systems
Security outcome Microsoft prioritized: Limit blast radius and identity-based lateral movement across tenants, environments, and administrative boundaries.
SFI priorities: tenant isolation, hardened cross-tenant access controls, safer administrative workstations, and stronger controls for app identities and tenant configurations.
Implementation insights from SFI: explicit boundary design and consistent governance reduce systemic risk from complex multi-tenant operations.
Zero Trust alignment: Verify explicitly, Use least privilege, Assume breach.
Canonical implementation guidance:
- Deploy tenant restrictions
- Cross-tenant access settings
- Privileged access strategy
- Security baselines and governance
SFI pattern pages retained for SFI-specific context:
- Eliminate identity lateral movement
- Remove legacy systems that risk security
- Higher security for Microsoft Entra ID apps
- Secure all tenants and their resources
- Secure Admin Workstations (SAW) devices and how they are used
Pillar 3: Protect networks
Security outcome Microsoft prioritized: Reduce lateral movement and unauthorized connectivity across internal and production networks.
SFI priorities: stronger segmentation, identity-aware controls, isolation boundaries, and tighter controls for privileged network paths.
Implementation insights from SFI: practical segmentation sequencing and boundary hardening are essential for reducing high-consequence network pivot paths.
Zero Trust alignment: Verify explicitly, Use least privilege, Assume breach.
Canonical implementation guidance:
- Secure networks with Zero Trust
- Azure network security architecture
- Azure landing zone network topology and connectivity
SFI pattern pages retained for SFI-specific context:
Pillar 4: Protect engineering systems
Security outcome Microsoft prioritized: Improve trust in software supply chains, source code systems, build pipelines, and engineering operations.
SFI priorities: secure build pipelines, stronger source code access controls, software supply chain governance, and engineering security standards.
Implementation insights from SFI: reducing systemic engineering risk requires combined controls across identity, workflow governance, and pipeline integrity.
Zero Trust alignment: Verify explicitly, Use least privilege, Assume breach.
Canonical implementation guidance:
- Secure development imperatives in SAF
- GitHub security hardening
- Defender for DevOps
- NIST SSDF (SP 800-218)
SFI pattern pages retained for SFI-specific context:
- Standardize secure development pipelines
- Zero Trust for source code access
- Protect the software supply chain
- Governed pipeline templates
- Securing source code with GitHub Advanced Security
Pillar 5: Monitor and detect cyberthreats
Security outcome Microsoft prioritized: Improve detection speed and quality by increasing telemetry coverage, correlation, and operational visibility.
SFI priorities: infrastructure inventory, log retention standards, centralized access to security telemetry, and faster anomaly detection.
Implementation insights from SFI: durable detection improvements require consistent data quality, shared telemetry standards, and governance across teams.
Zero Trust alignment: Verify explicitly, Assume breach.
Canonical implementation guidance:
- SIEM and XDR overview
- Microsoft Sentinel architecture and best practices
- Defender XDR operations
- Cloud security posture and inventory guidance
SFI pattern pages retained for SFI-specific context:
- Complete production infrastructure inventory
- Security log retention standards
- Rapid anomaly detection and response
- Centralize access to security logs
Pillar 6: Accelerate response and remediation
Security outcome Microsoft prioritized: Reduce incident impact and duration through coordinated response, automation, and feedback loops into engineering.
SFI priorities: faster vulnerability mitigation, stronger response orchestration, and improved communication and recovery discipline.
Implementation insights from SFI: response maturity improves when remediation workflows, ownership models, and post-incident learning are integrated into engineering and operations.
Zero Trust alignment: Verify explicitly, Use least privilege, Assume breach.
Canonical implementation guidance:
- Plan incident response with SAF
- Prepare for incident response with SAF
- Microsoft incident response playbooks
- Defender XDR incident response
SFI pattern pages retained for SFI-specific context:
- Accelerate vulnerability mitigation
- Accelerating vulnerability response
- Respond to incidents in AI systems
Relationship to SAF
The Microsoft Secure Future Initiative is Microsoft's multiyear security transformation program. The Security Adoption Framework incorporates relevant lessons and practices from SFI while connecting organizations to established Microsoft architecture, operational, and technology guidance for implementation.
Next steps
- Review what's new in SFI
- Review Integrate NIST CSF 2.0 governance
- Return to Secure Future Initiative overview