← Frameworks / NIST SSDF 1.1 / Coverage Analysis

NIST Secure Software Development Framework (SSDF) Version 1.1, NIST SP 800-218 — SP 800-53 Coverage

How well do NIST SP 800-53 Rev 5 controls address each NIST SSDF 1.1 requirement? This analysis maps from framework clauses back to SP 800-53, with expert coverage weightings and gap identification.

Clauses: 42
Avg Coverage: 53.9%
Publisher: NIST
Coverage Distribution
Full (85-100%): 6 Substantial (65-84%): 18 Partial (40-64%): 6 Weak (1-39%): 5 None (0%): 7

Clause-by-Clause Analysis

Sorted by clause
PO.1.1 Identify and document all security requirements for the organization’s software development infrastructures and processes, and maintain the requirements over time.

Rationale

SA-15 has the developer follow a documented development process that addresses security requirements and names its standards and tools. The organisation reviews that process on a set cycle. SA-01 sets acquisition policy and procedures and keeps them current. SA-08 applies security engineering principles to development, and SR-03 sets controls against supply chain risk.

Gaps

The task also covers requirements for the development infrastructure, such as build systems and developer endpoints. These controls reach it through the tools SA-15 names. NIST pairs the environments themselves with SA-03(01), under PO.5.1.

PO.1.2 Identify and document all security requirements for organization-developed software to meet, and maintain the requirements over time.

Rationale

SA-08 applies security engineering principles to the software's specification and design. NIST also names SA-08(03), modularity and layering, which matches the task's example of modular code with its security components kept apart. SA-15 has the development process address security requirements explicitly, and SR-03 adds the organisation's controls against supply chain risk.

Gaps

The task asks the producer to identify and document the software's own security requirements and keep them current. These controls take those requirements as given and apply them in design and development.

Mapped Controls

PO.1.3 Communicate requirements to all third parties who will provide commercial software components to the organization for reuse by the organization’s own software.

Rationale

SA-04 puts security requirements, assurance requirements and acceptance criteria into acquisition contracts, which matches the task directly. SA-09 has external service providers meet the organisation's requirements. SA-10, with SA-10(01), has the developer manage configuration and enable integrity checks of its software. SA-15 has it follow a documented development process. SR-03, SR-04 and SR-05 add supply chain controls, provenance and acquisition strategies.

Gaps

The task's examples add attestation by the supplier and a process for approved exceptions. SA-04's acceptance criteria and SR-05's contract tools cover them in part.

PO.2.1 Create new roles and alter responsibilities for existing roles as needed to encompass all parts of the SDLC. Periodically review and maintain the defined roles and responsibilities, updating them as needed.

Rationale

SA-03 has the organisation define and document security and privacy roles and responsibilities throughout the system development life cycle, and identify the people who hold them.

Gaps

The task also asks for the roles to be reviewed and updated over time. Set a review cycle for them alongside SA-03.

Mapped Controls

PO.2.2 Provide role-based training for all personnel with responsibilities that contribute to secure development. Periodically review personnel proficiency and role-based training, and update the training as needed.

Rationale

NIST names SA-08. Its discussion lists training developers to build secure software among the security engineering principles.

Gaps

Role-based training, with regular review of proficiency and of the training itself, is the subject of AT-03 (role-based training). NIST's table leaves AT-03 out for this task.

Mapped Controls

PO.2.3 Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development-related roles and responsibilities.
0%

Rationale

NIST's SSDF table names no SP 800-53 control for this task.

Gaps

The task asks for upper management's commitment to secure development, conveyed to everyone with a development role. SA-01's acquisition policy addresses management commitment, and NIST's table names SA-01 for PO.1.1.

PO.3.1 Specify which tools or tool types must or should be included in each toolchain to mitigate identified risks, as well as how the toolchain components are to be integrated with each other.

Rationale

SA-15 has the developer name the standards and tools used in development and document their options and configurations. The organisation reviews them against its security requirements.

Gaps

The task also asks how the tools in each toolchain work together, and for tools chosen to mitigate identified risks. Plan the toolchain as a whole on top of SA-15's list of tools.

Mapped Controls

PO.3.2 Follow recommended security practices to deploy, operate, and maintain tools and toolchains.

Rationale

SA-15 has the developer manage changes to its development tools and protect their integrity. The organisation reviews the tools and their configurations on a set cycle.

Gaps

Running the toolchain securely, for example hardening and patching the tools, draws on SP 800-53's configuration management (CM) and system and information integrity (SI) families. NIST's table leaves those out for this task.

Mapped Controls

PO.3.3 Configure tools to generate artifacts of their support of secure software development practices as defined by the organization.

Rationale

SA-15 has the developer document the specific tool options and configurations used in development.

Gaps

The task asks for tools set up to produce artifacts, such as logs and reports, that show each secure development practice took place. SA-15 records the tools' settings. Collect and keep that evidence as well.

Mapped Controls

PO.4.1 Define criteria for software security checks and track throughout the SDLC.

Rationale

NIST names SA-15(01), which has the developer define quality metrics at the start of development and give evidence of meeting them at set points. It counts for SA-15. SA-15 itself has the organisation review the development process against its security requirements.

Gaps

Quality metrics reach wider than security. Define security criteria as well, such as the checks a release must pass, and track them in the team's workflow.

Mapped Controls

PO.4.2 Implement processes, mechanisms, etc. to gather and safeguard the necessary information in support of the criteria.

Rationale

SA-15(01) has the developer give evidence of meeting the agreed metrics, and SA-15(11) archives each release with the evidence from its final security review. Both count for SA-15. SA-15 itself has the developer protect the integrity of changes to its process and tools.

Gaps

The task also asks to safeguard the gathered information. Protect it from tampering and unauthorised access with the organisation's own access and integrity controls.

Mapped Controls

PO.5.1 Separate and protect each environment involved in software development.

Rationale

NIST names SA-03(01), which has the organisation protect preproduction environments, such as development and test environments, in line with risk. It counts for SA-03. SA-08's principles include clear security boundaries, and SA-15 sets the documented development process those environments serve.

Gaps

The task asks to separate each environment, with measures such as network segmentation and multi-factor authentication. Those come from SP 800-53's system and communications protection (SC) and identification and authentication (IA) families, which NIST's table leaves out for this task.

Mapped Controls

PO.5.2 Secure and harden development endpoints (i.e., endpoints for software designers, developers, testers, builders, etc.) to perform development-related tasks using a risk-based approach.

Rationale

SA-15 covers the development process and its tools, including how the tools are configured.

Gaps

Hardening the endpoints developers work on is configuration management work, such as CM-06 (configuration settings) and CM-07 (least functionality). NIST's table leaves those out for this task.

Mapped Controls

PS.1.1 Store all forms of code – including source code, executable code, and configuration-as-code – based on the principle of least privilege so that only authorized personnel, tools, services, etc. have access.

Rationale

SA-10 has the developer manage configuration, control the integrity of changes to code and other configuration items, and make only approved changes.

Gaps

The task's main ask is least-privilege access to stored code. That is the subject of AC-03 (access enforcement) and AC-06 (least privilege), which NIST's table leaves out for this task.

Mapped Controls

PS.2.1 Make software integrity verification information available to software acquirers.

Rationale

NIST names SA-08, which applies security engineering principles to the design and development of the software.

Gaps

Publishing integrity information that acquirers can check, such as hashes or signatures, matches SA-10(01), which has the developer enable integrity verification. NIST's table names SA-10(01) for PO.1.3, and SA-08 alone here.

Mapped Controls

PS.3.1 Securely archive the necessary files and supporting data (e.g., integrity verification information, provenance data) to be retained for each software release.

Rationale

NIST names SA-15(11), which has the developer archive each release together with the evidence from its final security review. SA-10 keeps the release's configuration items under change control, and SR-04 keeps valid provenance for the release and its components.

Gaps

These controls say what to keep. Protect the archive itself from change and loss.

Mapped Controls

PS.3.2 Collect, safeguard, maintain, and share provenance data for all components of each software release (e.g., in a software bill of materials [SBOM]).

Rationale

SR-04 has the organisation document and maintain valid provenance for its systems, components and their data. SR-03 sets the supply chain processes that provenance supports, and SA-08 applies security engineering principles.

Gaps

The task also asks to share provenance data with acquirers, for example as a software bill of materials (SBOM). SR-04 keeps provenance for the organisation's own use.

Mapped Controls

PW.1.1 Use forms of risk modeling – such as threat modeling, attack modeling, or attack surface mapping – to help assess the security risk for the software.

Rationale

NIST names SA-11(02), threat modeling and vulnerability analyses during development, and SA-11(06), attack surface reviews, which count for SA-11. It also names SA-15(05), attack surface reduction, which counts for SA-15. SA-08's principles include threat modeling to find the controls needed to mitigate risk.

Gaps

A close match. Set the inputs, tools and depth of the modeling, which SA-11(02) leaves to the organisation.

Mapped Controls

PW.1.2 Track and maintain the software’s security requirements, risks, and design decisions.

Rationale

SA-17 has the developer produce a design specification and security architecture that describe the security functions and how they work together. SA-10 has it document approved changes with their security impacts and track security flaws. SA-08 applies security engineering principles to the design.

Gaps

The task also asks to track the risks, and to keep requirements, risks and design decisions linked as the software changes.

Mapped Controls

PW.1.3 Where appropriate, build in support for using standardized security features and services (e.g., enabling software to integrate with existing log management, identity management, access control, and vulnerability management systems) instead of creating proprietary implementations of security features and services.
0%

Rationale

NIST's SSDF table names no SP 800-53 control for this task.

Gaps

The task asks the producer to build in support for standard security services, such as the organisation's existing log and identity management systems, in place of its own implementations.

PW.2.1 Have 1) a qualified person (or people) who were not involved with the design and/or 2) automated processes instantiated in the toolchain review the software design to confirm and enforce that it meets all of the security requirements and satisfactorily addresses the identified risk information.
0%

Rationale

NIST's SSDF table names no SP 800-53 control for this task.

Gaps

The task asks for the design to be reviewed against the security requirements and risks, by qualified people who did not design it or by automated checks in the toolchain. SA-17, which NIST names for PW.1.2, gives the design specification such a review checks.

PW.4.1 Acquire and maintain well-secured software components (e.g., software libraries, modules, middleware, frameworks) from commercial, open-source, and other third-party developers for use by the organization’s software.

Rationale

SA-04 puts security requirements into acquisition contracts for components, and SA-05 obtains the documentation on configuring and using them securely. NIST names SA-08(03), modularity and layering, which counts for SA-08, and SA-10(06), trusted distribution of updates, which counts for SA-10. SR-03 and SR-04 add supply chain controls and provenance.

Gaps

Open-source components come without a contract, so SA-04 reaches commercial components only. For open-source ones, vet the project and keep the components current through SR-03's supply chain processes.

PW.4.2 Create and maintain well-secured software components in-house following SDLC processes to meet common internal software development needs that cannot be better met by third-party software components.

Rationale

NIST names SA-08(03), which has the organisation build modularity and layering into its systems. It counts for SA-08. Modular design makes shared in-house components possible.

Gaps

The task asks for shared components built and maintained in-house through the organisation's development life cycle. SA-03 and SA-15 set that life cycle and process, and NIST's table names them for other tasks.

Mapped Controls

PW.4.4 Verify that acquired commercial, open-source, and all other third-party software components comply with the requirements, as defined by the organization, throughout their life cycles.

Rationale

NIST names SR-04(03), which validates that a component received is genuine and unaltered, and SR-04(04), which validates its internal composition and provenance. Both count for SR-04. SR-03 addresses weaknesses in the supply chain, and SA-09 monitors external providers' compliance on an ongoing basis.

Gaps

The task asks to verify components against the organisation's requirements throughout their life. Check them for newly published vulnerabilities as well, for example with software composition analysis.

Mapped Controls

PW.5.1 Follow all secure coding practices that are appropriate to the development languages and environment to meet the organization’s requirements.
0%

Rationale

NIST's SSDF table names no SP 800-53 control for this task.

Gaps

The task asks developers to follow secure coding practices suited to their languages and environment. SA-15, which NIST names for other tasks, has the development process name its standards.

PW.6.1 Use compiler, interpreter, and build tools that offer features to improve executable security.

Rationale

SA-15 has the developer name the tools used in development and document their options and configurations. The organisation reviews them against its security requirements.

Gaps

The task asks for tools that offer features to improve executable security, such as compiler hardening options. Add those features to the requirements SA-15's review checks against.

Mapped Controls

PW.6.2 Determine which compiler, interpreter, and build tool features should be used and how each should be configured, then implement and use the approved configurations.

Rationale

SA-15 has the developer document the specific tool options and configurations used, and the organisation review them on a set cycle. SR-09 adds a tamper protection programme, which can include build features that resist tampering.

Gaps

The task also asks that builds use the approved configurations every time. Enforce them in the build pipeline.

Mapped Controls

PW.7.1 Determine whether code review (a person looks directly at the code to find issues) and/or code analysis (tools are used to find issues in code, either in a fully automated way or in conjunction with a person) should be used, as defined by the organization.

Rationale

SA-11 has the developer plan ongoing security assessments and run testing and evaluation at a depth and coverage the organisation defines. The choice between code review and code analysis belongs in that plan.

Gaps

SA-11 frames the choice for testing in general. Decide for each part of the code whether people review it, tools analyse it, or both.

Mapped Controls

PW.7.2 Perform the code review and/or code analysis based on the organization’s secure coding standards, and record and triage all discovered issues and recommended remediations in the development team’s workflow or issue tracking system.

Rationale

NIST names SA-11(01), static code analysis, and SA-11(04), manual code reviews, with SA-11 itself, which has flaws remediated and corrected. It also names SA-15(07), automated vulnerability analysis, which counts for SA-15 and has the results delivered to named people.

Gaps

A close match. Review against the organisation's own secure coding standards, and triage the findings in the team's issue tracker.

Mapped Controls

PW.8.1 Determine whether executable code testing should be performed to find vulnerabilities not identified by previous reviews, analysis, or testing and, if so, which types of testing should be used.

Rationale

SA-11 has the developer plan ongoing security assessments and choose the kinds of testing, from unit to regression testing, at a depth and coverage the organisation defines.

Gaps

Testing aimed at finding vulnerabilities, such as penetration testing and dynamic analysis, sits in SA-11's enhancements. NIST names those for PW.8.2.

Mapped Controls

PW.8.2 Scope the testing, design the tests, perform the testing, and document the results, including recording and triaging all discovered issues and recommended remediations in the development team’s workflow or issue tracking system.

Rationale

SA-11 has the developer test at a defined depth and coverage, produce evidence of the results and correct the flaws found. NIST also names SA-11(05), penetration testing, and SA-11(08), dynamic code analysis, with SA-15(07), automated vulnerability analysis, which counts for SA-15.

Gaps

A close match. Record and triage each finding in the team's issue tracker.

Mapped Controls

PW.9.1 Define a secure baseline by determining how to configure each setting that has an effect on security or a security-related setting so that the default settings are secure and do not weaken the security functions provided by the platform, network infrastructure, or services.
0%

Rationale

NIST's SSDF table names no SP 800-53 control for this task.

Gaps

The task asks the producer to define a secure baseline, so that the software's default settings are secure. SA-08(23), secure defaults, which NIST names for PW.9.2, comes closest.

PW.9.2 Implement the default settings (or groups of default settings, if applicable), and document each setting for software administrators.

Rationale

NIST names SA-08(23), which has the organisation build the principle of secure defaults into its systems. It counts for SA-08. SA-05 has administrator documentation describe how to configure and run the software securely.

Gaps

Document each security-related setting for administrators, as the task asks.

Mapped Controls

RV.1.1 Gather information from software acquirers, users, and public sources on potential vulnerabilities in the software and third-party components that the software uses, and investigate all credible reports.

Rationale

SA-10 has the developer track security flaws and their resolution and report them. SR-03 finds and addresses weaknesses in supply chain elements, and SR-04's provenance records show which components the software uses.

Gaps

The task asks to gather vulnerability reports from users and public sources. Run a public reporting channel, as in RA-05(11), and watch advisories, as in SI-05. NIST's table leaves both out for this task.

Mapped Controls

RV.1.2 Review, analyze, and/or test the software’s code to identify or confirm the presence of previously undetected vulnerabilities.

Rationale

SA-11 has the developer test and evaluate the software at all stages after design, then remediate and correct the flaws found.

Gaps

Keep reviewing and testing released code for vulnerabilities, as the task asks.

Mapped Controls

RV.1.3 Have a policy that addresses vulnerability disclosure and remediation, and implement the roles, responsibilities, and processes needed to support that policy.

Rationale

NIST names SA-15(10), which has the developer provide, implement and test an incident response plan. It counts for SA-15. Its discussion notes the plan's value when organisations respond to vulnerabilities in commercial products.

Gaps

The task asks for a vulnerability disclosure policy, with the roles and processes to take reports and remediate. A public reporting channel, as in RA-05(11), comes closer, and NIST's table leaves it out for this task.

Mapped Controls

RV.2.1 Analyze each vulnerability to gather sufficient information about risk to plan its remediation or other risk response.

Rationale

NIST names SA-15(07), which counts for SA-15 and has the developer judge the exploitation potential of each vulnerability found and the mitigations open to it. SA-10 tracks security flaws and their resolution.

Gaps

SA-15(07) covers vulnerabilities found by automated analysis. Analyse reports from other sources the same way.

Mapped Controls

RV.2.2 Plan and implement risk responses for vulnerabilities.

Rationale

SA-11 has the developer run a verifiable flaw remediation process and correct flaws, and SA-10 makes only approved changes and tracks flaw resolution. SA-15(07), which counts for SA-15, works out potential mitigations for delivered vulnerabilities. SA-05's documentation covers known vulnerabilities in configuration and use.

Gaps

The task also asks to tell users about fixes and workarounds, for example in security advisories.

RV.3.1 Analyze identified vulnerabilities to determine their root causes.
0%

Rationale

NIST's SSDF table names no SP 800-53 control for this task.

Gaps

The task asks for the root cause of each vulnerability to be found.

RV.3.2 Analyze the root causes over time to identify patterns, such as a particular secure coding practice not being followed consistently.
0%

Rationale

NIST's SSDF table names no SP 800-53 control for this task.

Gaps

The task asks for root causes to be analysed over time to find patterns, such as a secure coding practice applied unevenly.

RV.3.3 Review the software for similar vulnerabilities to eradicate a class of vulnerabilities, and proactively fix them rather than waiting for external reports.

Rationale

SA-11 has the developer test at a defined depth and coverage and correct the flaws it finds.

Gaps

The task asks to search the software for a whole class of vulnerability once one instance is found, and to fix them before outsiders report them.

Mapped Controls

RV.3.4 Review the SDLC process, and update it if appropriate to prevent (or reduce the likelihood of) the root cause recurring in updates to the software or in new software that is created.

Rationale

SA-15 has the organisation review the development process, standards and tools on a set cycle against its security requirements, and has the developer manage changes to the process.

Gaps

The task reviews the process in response to the root causes of vulnerabilities. SA-15(06), continuous improvement of the development process, fits it best.

Mapped Controls

Methodology and Disclaimer

This coverage analysis maps from NIST SSDF 1.1 clauses/requirements back to NIST SP 800-53 Rev 5 controls, assessing how well the SP 800-53 control set addresses each framework requirement.

Coverage weighting represents an informed estimate based on control-objective alignment, not a definitive compliance determination. Weightings consider whether SP 800-53 controls address the intent of each framework requirement, even where terminology and structure differ.

This analysis should be validated by qualified assessors for use in compliance or audit activities. The authoritative source for any compliance determination is always the framework itself.