{“lastseen”:”2025-10-07T17:37:56″,”description”:”Building on the momentum of our initial launch of the Microsoft Secure Future Initiative (SFI) patterns and practices, this second installment continues our commitment to making security implementation practical and scalable. The first release introduced a foundational library of actionable guidance rooted in proven architectures like Zero Trust. Now, we\u2019re expanding that guidance with new examples that reflect our ongoing learnings\u2014helping customers and partners understand our strategic approach more deeply and apply it effectively in their own environments.\\n\\nDiscover more about the Microsoft Secure Future Initiative\\n\\nThis next set of SFI patterns and practices articles include practical, actionable guidance built by practitioners, for practitioners, in the areas of network, engineering systems, and security response. Each of the six articles includes details on how Microsoft has improved our security posture in each area so customers, partners, and the broader security community can do the same.\\n\\n**Pattern name** | **SFI Pillar** | **What it helps you do** \\n—|—|— \\n**Network isolation****** | Protect networks | Contain breaches by default. Strongly segment and isolate your network (through per-service ACLs, isolated virtual networks, and more) to prevent lateral movement and limit cyberattackers if they get in. \\n**Secure all tenants and their resources****** | Protect tenants and isolate systems | Help eliminate \u201cshadow\u201d tenants. Apply baseline security policies, such as multifactor authentication (MFA), Conditional Access, and more, to every cloud tenant and retire unused ones, so cyberattackers can\u2019t exploit forgotten, weakly-secured environments. \\n**Higher security for Entra ID apps****** | Protect tenants and isolate systems | Close identity backdoors. Enforce high security standards for all Microsoft Entra ID (Azure AD) applications\u2014removing unused apps, tightening permissions, and requiring strong authorization\u2014to block common misconfigurations cyberattackers abuse for cross-tenant attacks. \\n**Zero Trust for source code access****** | Protecting engineering systems | Secure the dev pipeline. Require proof-of-presence MFA for critical code commits and merges to help ensure only verified developers can push code and stop cyberattackers from surreptitiously injecting changes. \\n**Protect the software supply chain****** | Protecting engineering systems | Lock down builds and dependencies. Govern your continuous integration and continuous delivery (CI\/CD) pipelines and package management\u2014use standardized build templates, internal package feeds, and automated scanning to block supply chain cyberattacks before they reach production. \\n**Centralize access to security logs****** | Monitoring and detecting threats | Speed up investigations. Standardize and centralize your log collection (with longer retention) so that security teams have unified visibility and can detect and investigate incidents faster\u2014even across complex, multi-cloud environments. \\n \\n## **More about SFI patterns and practices**\\n\\nJust as software design patterns provide reusable solutions to common engineering problems, SFI patterns and practices offer repeatable, proven approaches to solving complex cybersecurity challenges. Each pattern is crafted to address a specific security risk\u2014legacy infrastructure or inconsistent CI\/CD pipelines\u2014and is grounded in Microsoft\u2019s own experience. Like design patterns in software architecture, these security patterns are modular, extensible, and built for reuse across diverse environments.\\n\\nAdditionally, each pattern in the SFI patterns and practices library follows a consistent and purposeful structure. Every article begins with a **pattern name** \u2014a concise handle that captures the essence of the cybersecurity challenge. The **problem** section outlines the security risk and its real-world context, helping readers understand why it matters. The **solution** describes how Microsoft addressed the issue internally. The **guidance** section provides practical recommendations that customers can consider applying in their own environments. Finally, the **implications** section outlines the outcomes and trade-offs of implementing the pattern, helping organizations anticipate both the benefits and the operational considerations.\\n\\nThis structure offers a framework for understanding, applying, and evolving security practices. \\n\\n## Next steps with SFI\\n\\n## April 2025 progress Report \\n\\nRead the report \u2197\\n\\nSecurity is a journey, and Microsoft is committed to sharing our insights from SFI. Watch for more actionable advice in coming months. SFI patterns and practices provide a roadmap for putting secure architecture into practice. Embracing these approaches enables organizations to advance their security posture, minimize deployment hurdles, and establish environments that are secure by design, by default, and in operations. \\n\\nTo get access to the full library, visit our new SFI patterns and practices webpage. And check out the new SFI video on our redesigned website to hear directly from Microsoft leadership about how we are putting **security above all else**.\\n\\n## **Let\u2019s build a secure future, together**\\n\\nTalk to your Microsoft account team to integrate these practices into your roadmap. \\n\\nKeep up to date with all the SFI updates\\n\\nTo learn more about Microsoft Security solutions, visit our website. Bookmark the Security blog to keep up with our expert coverage on security matters. Also, follow us on LinkedIn (Microsoft Security) and X (@MSFTSecurity) for the latest news and updates on cybersecurity. \\n\\nThe post New Microsoft Secure Future Initiative (SFI) patterns and practices: Practical guides to strengthen security appeared first on Microsoft Security Blog.”,”published”:”2025-10-07T16:00:00″,”modified”:”2025-10-07T16:00:00″,”type”:”mssecure”,”title”:”New Microsoft Secure Future Initiative (SFI) patterns and practices: Practical guides to strengthen security”,”source”:””,”references”:””,”id”:”MSSECURE:04C6709EA9021327853A583D017079FE”,”bulletinFamily”:”blog”,”cwe”:null,”cvelist”:[],”sourceData”:””,”sourceHref”:””,”cvss”:{“score”:0,”severity”:”NONE”,”vector”:”NONE”,”version”:”NONE”},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:”https:\/\/www.microsoft.com\/en-us\/security\/blog\/2025\/10\/07\/new-microsoft-secure-future-initiative-sfi-patterns-and-practices-practical-guides-to-strengthen-security\/”,”category_name”:”News”,”post_link”:””,”product”:””,”version”:””,”vendor”:””,”ai_description”:””,”ai_severity”:””,”ai_vendor”:””,”ai_product”:””,”ai_version”:””,”ai_score”:0}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:”2025-10-07T17:37:56″,”description”:”Building on the momentum of our initial launch of the Microsoft Secure Future Initiative (SFI) patterns and practices, this second installment continues our commitment to…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[6,8,12,110,13,33,7,11,5],"class_list":["post-20537","post","type-post","status-publish","format-standard","hentry","category-category_news","tag-cve","tag-cvss","tag-exploit","tag-mssecure","tag-news","tag-none","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n