National Institute of Standards and Technology
Secure Software Development, Security, and Operations (DevSecOps) Practices
Go to Project Page
Example Implementation 1 & 2
DevSecOps Practices
Executive Summary
1. Introduction
1.1. Background
1.1.1. Development, Security, and Operations (DevSecOps)
1.1.2. The Role of AI in Software Development
1.1.3. The Role of Zero Trust in Software Development
1.2. Audience
1.3. Scope
1.4. Challenges
1.5. How to Use This Guide
2. Notional Reference Model for DevSecOps for Demonstration of NIST SSDF
Updated
2.1. Organizational Preparation
2.2. Phases of the Software Development Lifecycle
2.2.1. Plan
2.2.2. Develop
2.2.3. Build
2.2.4. Test
2.2.5. Release
2.2.6. Deploy
2.2.7. Operate
2.3. Continuous Improvements, Security, and Monitoring
2.4. Continuous Feedback
2.5. Continuous Integration/Continuous Delivery (CI/CD) Pipeline
2.6. Zero Trust Security
2.7. Artificial Intelligence
New
3. Mapping SSDF to DevSecOps Notional Reference Model
New
3.1. Prepare the Organization (PO)
3.2. Protect the Software (PS)
3.3. Produce Well-Secured Software (PW)
3.4. Respond to Vulnerabilities (RV)
4. Example Implementations
Updated
4.1. Example Implementation 1 (E1)
4.1.1. Plan
4.1.2. Develop
4.1.3. Build
4.1.4. Test
4.1.5. Release
4.1.6. Deploy
4.1.7. Operate
4.1.8. Continuous Improvements, Security, and Monitoring
4.2. Example Implementation 2 (E2)
New
4.2.1. Plan
4.2.2. Develop
4.2.3. Build
4.2.4. Test
4.2.5. Release
4.2.6. Deploy
4.2.7. Operate
4.2.8. Continuous Improvements, Security, and Monitoring
5. Functional Demonstrations
New
5.1. Functional Demonstration Scenarios
5.1.1. Phase A - Plan
5.1.2. Phase B – Develop
5.1.3. Phase C - Build
5.1.4. Phase D - Test
5.1.5. Phase E – Release
5.1.6. Phase F - Deploy
5.1.7. Phase G - Operate
5.1.8. Phase H – Continuous Improvements, Security, and Monitoring
5.2. Functional Demonstration Results
5.2.1. Example Implementation 1 (E1)
5.2.2. Example Implementation 2 (E2)
6. Next Steps
Appendix A List of Acronyms
Appendix B Component Description
Appendix C SSDF Analysis
New
C.1. Prepare the Organization (PO)
C.1.1. PRACTICE (PO.1) - Define Security Requirements for Software Development:
C.1.2. PRACTICE (PO.2) - Implement Roles and Responsibilities:
C.1.3. PRACTICE (PO.3) - Implement Supporting Toolchains:
C.1.4. PRACTICE (PO.4) - Define and Use Criteria for Software Security Checks:
C.1.5. PRACTICE (PO.5) - Implement and Maintain Secure Environments for Software Development:
C.2. Protect Software (PS)
C.2.1. PRACTICE (PS.1) - Protect All Forms of Code from Unauthorized Access and Tampering:
C.2.2. PRACTICE (PS.2) - Provide a Mechanism for Verifying Software Release Integrity:
C.2.3. PRACTICE (PS.3) - Archive and Protect Each Software Release:
C.3. Produce Well-Secured Software (PW)
C.3.1. PRACTICE (PW.1) - Design Software to Meet Security Requirements and Mitigate Security Risks:
C.3.2. PRACTICE (PW.2) - Review the Software Design to Verify Compliance with Security Requirements and Risk Information:
C.3.4. PRACTICE (PW.4) - Reuse Existing, Well-Secured Software When Feasible Instead of Duplicating Functionality:
C.3.5. PRACTICE (PW.5) - Create Source Code by Adhering to Secure Coding Practices:
C.3.6. PRACTICE (PW.6) - Configure the Compilation, Interpreter, and Build Processes to Improve Executable Security:
C.3.7. PRACTICE (PW.7) - Review and/or Analyze Human-Readable Code to Identify Vulnerabilities and Verify Compliance with Security Requirements:
C.3.8. PRACTICE (PW.8) - Test Executable Code to Identify Vulnerabilities and Verify Compliance with Security Requirements:
C.3.9. PRACTICE (PW.9) - Configure Software to Have Secure Settings by Default:
C.4. Respond to Vulnerabilities (RV)
C.4.1. PRACTICE (RV.1) - Identify and Confirm Vulnerabilities on an Ongoing Basis:
C.4.2. PRACTICE (RV.2) - Assess, Prioritize, and Remediate Vulnerabilities:
C.4.3. PRACTICE (RV.3) - Analyze Vulnerabilities to Identify Their Root Causes:
Appendix D Collaborators and their Contribution
D.1. AMI
D.1.1. Meridian Firmware Management Service
D.1.2. Meridian Security Services: VMS and SBOM
D.2. Black Duck
D.2.1. Polaris Platform
D.2.2. Black Duck SCA
D.2.3. Black Duck Coverity
D.2.4. Continuous Dynamic
D.2.5. Software Risk Manager (SRM)
D.3. CyberArk Software
D.3.1. CyberArk Privilege Cloud
D.3.2. CyberArk Endpoint Privilege Manager
D.3.3. CyberArk Code Sign Manager
D.3.4. CyberArk Secrets Hub
D.3.5. CyberArk Conjur Cloud
D.3.6. CyberArk Workload Identity
D.3.7. CyberArk Certificate Manager SaaS
D.3.8. CyberArk Certificate Manager (Self-Hosted)
D.3.9. CyberArk Certificate Manager for Kubernetes
D.4. Dell Technologies
D.5. DigiCert
D.5.1. DigiCert Software Trust Manager
D.6. Endor Labs
D.6.1. Reachability-Based SCA
D.6.2. Endor Code (SAST + Secret Scanning)
D.6.3. Container Scanning
D.6.4. Endor Patches
D.6.5. AI Code Security Review
D.7. GitLab
D.7.1. The GitLab Platform
D.7.2. GitLab Duo (AI)
D.8. Google
D.8.1. Cloud Workstations
D.8.2. Google Cloud Build
D.8.3. Artifact Registry and Artifact Analysis
D.8.4. Binary Authorization
D.8.5. Cloud Deploy
D.8.6. Google Kubernetes Engine
D.8.7. Cloud Run
D.8.8. Security Command Center
D.8.9. deps.dev
D.9. IBM
D.9.1 IBM Cloud and DevSecOps
D.9.2 IBM Cloud Continuous Delivery
D.9.3 IBM Cloud Container Registry and Vulnerability Advisor
D.9.4 IBM Cloud Kubernetes Service and Red Hat OpenShift Services
D.9.5 IBM Cloud Secrets Manager
D.9.6 IBM Cloud Key Protect
D.9.7 IBM Cloud Object Storage (S3‑Compatible)
D.10. Microsoft and GitHub Advanced Security (GHAzDO)
D.10.1. Azure Container Registry (ACR)
D.10.2. Azure DevOps (AzDO)
D.10.3. Azure Entra ID
D.10.4. Azure Key Vault (AKV)
D.10.5. Azure Managed DevOps Pool (MDP)
D.10.6. Azure Privileged Identity Management (PIM)
D.10.7. Azure Sentinel
D.10.8. Bicep and Azure Resource Manager (ARM)
D.10.9. GitHub Advanced Security (GHAS)
D.10.10. GitHub Copilot
D.10.11. IDEs – Visual Studio and Visual Studio Code (VS Code)
D.10.12. Microsoft Defender for Cloud (MDC)
D.10.13. Microsoft SBOM Tool
D.10.14. Notary Project
D.11. NextLabs
D.11.1. NextLabs CloudAz Zero Trust Policy Platform
D.11.2. NextLabs Policy Enforcer
D.12. Palo Alto Networks
D.12.1. Cortex Cloud Security Platform
D.13. Resilience Cyber Security
D.13.1. Attestation Store
D.13.2. Policy As Code Engine
D.13.3. AI Workflows
D.14. Sagittal AI
D.14.1. Neo
Appendix E Change Log
Updated
Example Implementation 3
Scope
Readahead for October 28 Webinar: NCCoE DevSecOps and the Impact of Agentic Super Intelligence (SI)
Secure Software Development, Security, and Operations (DevSecOps) Practices
Search
Please activate JavaScript to enable the search functionality.