Search / openssf/osps-baseline-to-ssdf
mapping
OSPS Baseline to NIST SSDF Mapping Mapping Document
openssf/osps-baseline-to-ssdf
Cross-walk from the Open Source Project Security (OSPS) Baseline controls to NIST SSDF. Each mapping asserts a "relates-to" relationship; strength, confidence-level, and rationale are left unset and should be added as the mappings are individually reviewed.
Published by OSPS Baseline Authors
License No license declared
Pull latest (v0.0.0-dev-671f23f)
$grcli unpack --repository openssf/osps-baseline-to-ssdf --version v0.0.0-dev-671f23f Releases
1 live| Version | Manifest digest | Published | License | Status | |
|---|---|---|---|---|---|
| v0.0.0-dev-671f23f | 6a047812544311… | 1mo ago | No license declared | Live unsigned | Details → |
Mapping references
external standards this artifact maps to (v0.0.0-dev-671f23f)-
The Open Source Project Security (OSPS) Baseline is a set of security criteria that projects should meet to demonstrate a strong security posture.
-
The Secure Software Development Framework (SSDF) is a set of fundamental, sound, and secure software development practices based on established secure software development practice documents from organizations such as BSA, OWASP, and SAFECode. Few software development life cycle (SDLC) models explicitly address software security in detail, so practices like those in the SSDF need to be added to and integrated with each SDLC implementation. Following the SSDF practices should help software producers reduce the number of vulnerabilities in released software, reduce the potential impact of the exploitation of undetected or unaddressed vulnerabilities, and address the root causes of vulnerabilities to prevent recurrences. Also, because the SSDF provides a common language for describing secure software development practices, software producers and acquirers can use it to foster their communications for procurement processes and other management activities.
Builds upon
artifacts this one extends, imports, or shares a lexicon withNo upstream references yet
This artifact doesn't extend, import, or share a lexicon with anything else in the registry.
Extended or imported by
other artifacts that build upon this oneNo dependents yet
Published artifacts that extend or import this one will appear here.