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 best practices apply at many levels. They help organizations make informed decisions about managing security risk and improving resilience. Best practices can address people, processes, and technology across strategy, governance, architecture, implementation, and operations.
Microsoft security guidance includes many forms of best practices. These range from strategic principles and organizational practices to security standards and frameworks, secure configuration baselines and benchmarks, architecture, assessments, technology guidance, and implementation practices. These forms of guidance provide different perspectives and levels of detail and are designed to work together rather than as a single checklist or prescribed approach.
Standards and frameworks provide established security practices. They organize security objectives, practices, controls, or requirements into structures that organizations can use to guide security programs, assess progress, and communicate alignment. Microsoft guidance helps organizations connect these frameworks to practical security work and technology implementation.
Best practices must be adapted to organizational context. Business priorities, risk, regulatory and policy requirements, threat environment, technology estate, existing capabilities, resources, and organizational structure can affect which practices are most important and how they should be implemented.
Use the following resources based on what you are trying to accomplish.
Establish a security foundation with Zero Trust
Use Zero Trust as a security foundation for designing, implementing, and operating security controls across your organization.
Zero Trust applies three principles across business, security, and technology decisions: verify explicitly, use least privilege access, and assume breach.
Organize and improve your security program with SAF
Use the Microsoft Security Adoption Framework (SAF) to connect business priorities and risk to coordinated security work and technology implementation.
SAF helps business, technology, and security roles collaborate across business scenarios, security disciplines, technologies, and technical solutions.
Use established security baselines and benchmarks
Security baselines provide tested starting points. They help organizations apply established security recommendations consistently rather than developing every security configuration from the beginning.
Microsoft provides security baselines and benchmarks for different technologies and environments, including:
- Microsoft Cloud Security Benchmark (MCSB): Provides security recommendations for improving the security of cloud workloads, data, and services. See Overview of the Microsoft cloud security benchmark.
- Windows and Windows Server security baselines: Provide Microsoft-recommended configuration settings for securing Windows devices and servers. See Windows security baselines and configure security baselines for Windows Server 2025.
- Microsoft 365 Apps for enterprise security baseline: Provides recommended configuration settings for Microsoft 365 Apps and guidance for balancing security with productivity requirements. See Security baseline for Microsoft 365 Apps for enterprise.
- Microsoft Edge security baseline: Provides recommended security configuration settings for Microsoft Edge. See Microsoft Edge security baseline settings reference for Microsoft Intune.
- Microsoft Intune security baselines: Provide deployable groups of recommended security settings for Windows devices and supported security technologies managed with Intune. See Use security baselines to help secure Windows devices you manage with Microsoft Intune.
A security baseline is a starting point, not a universal configuration. Evaluate and adapt baselines based on organizational risk, regulatory and policy requirements, technology dependencies, operational needs, and productivity requirements.
Assess your Zero Trust implementation
Use the Zero Trust assessment to evaluate your current implementation, identify security gaps, and prioritize improvements across Zero Trust technology controls.
Assessment results can provide a practical starting point for prioritizing improvements and measuring progress over time.
Secure specific technologies
Use technology security guidance when you need to secure a particular part of your technology environment.
The guidance applies Zero Trust principles across identities, endpoints, applications, data, infrastructure, networks, and AI and connects to more detailed implementation guidance.
Apply security standards and frameworks
Use Security standards and frameworks when your organization uses an established security standard or framework to structure security objectives, practices, controls, or requirements.
Standards and frameworks capture and organize security practices from different authorities, communities, and areas of expertise. Organizations can use them to structure security programs, establish common expectations, assess progress, and communicate alignment.
Microsoft mappings connect framework objectives to SAF guidance, security capabilities, technology implementation, and relevant Microsoft product guidance. Organizations can use these mappings to help align security work with framework objectives and requirements without treating framework alignment or compliance as the complete measure of security success.
Learn from Microsoft's security engineering practices
Use the Microsoft Secure Future Initiative (SFI) to learn from security engineering practices, patterns, and lessons from Microsoft's efforts to strengthen the security of its products and services.
SFI complements SAF and other Microsoft security guidance with engineering practices and lessons that organizations can consider as they improve their own security programs.
Next steps
Choose the guidance that best matches your current goals and organizational context. These resources are designed to work together, so you can start with the guidance most familiar or relevant to you and connect to other guidance as your security priorities evolve.