หมายเหตุ
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลอง ลงชื่อเข้าใช้หรือเปลี่ยนไดเรกทอรีได้
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลองเปลี่ยนไดเรกทอรีได้
This pillar focuses on improving trust across software development, build, release, and supply chain systems.
Security outcome Microsoft prioritized
Microsoft prioritized reducing systemic engineering risk by hardening source control, build pipelines, dependency governance, and software delivery integrity controls.
What Microsoft prioritized
- Better inventory and governance of engineering assets
- Stronger controls for source code access
- Secure-by-default pipeline standards
- Tighter supply chain risk controls for dependencies and artifacts
- Better security signal quality in engineering workflows
Lessons from SFI implementation
- High-impact engineering risk reductions require coordinated identity, policy, and pipeline controls.
- Standardized engineering patterns reduce control drift and improve response speed.
- Secure supply chain outcomes depend on both technical controls and governance rigor.
Zero Trust and NIST CSF alignment
This pillar primarily applies Verify explicitly, Use least privilege access, and Assume breach.
Representative NIST CSF mappings:
- Identify (ID) for engineering inventory and dependency visibility
- Protect (PR) for pipeline, artifact, and access controls
- Govern (GV) for supply chain and engineering policy outcomes
Use canonical implementation guidance
Use these resources for implementation details:
- Secure development imperatives in SAF
- Defender for DevOps
- GitHub Advanced Security
- NIST SSDF (SP 800-218)
Related SFI pattern pages
- Standardize secure development pipelines
- Zero Trust for source code access
- Protect the software supply chain
- Improving compliance monitoring
- Developer security stories for Secure by Design
- Governed pipeline templates
- Securing source code with GitHub Advanced Security