NIST SP 800-218
NIST SP 800-218: Asset Management

NIST SP 800-218 SP800-218-PW.4.2: Maintain Well-Secured In-House Components

What does SP800-218-PW.4.2 require?

Create and maintain well-secured software components in-house following SSDF practices to meet common internal needs.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 16 controls across 13 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

  • CCM-AIS-02 Application Security Baseline Requirements
  • CCM-AIS-04 Secure Application Design and Development

NIST SP 800-161 Rev 1 · 2 controls

  • 161R1-SA-15 Development Process, Standards, and Tools
  • 161R1-SA-20 Customized Development of Critical Components

NIST SP 800-53 Rev 5 · 2 controls

Azure Security Benchmark · 1 control

  • ASBv3-GS-10 Define and implement DevOps security strategy

C5 (Germany) · 1 control

  • C5-DEV-01 Policies for the development/procurement of information systems

CIS Controls v8 · 1 control

  • CIS-16.1 Establish and Maintain a Secure Application Development Process

FedRAMP High · 1 control

  • SA-15 Development Process, Standards, and Tools (SA-15)

FedRAMP Moderate · 1 control

  • SA-15 Development Process, Standards, and Tools (SA-15)

ISO 27001:2022 · 1 control

  • 8.25 Secure development life cycle

ISO 27002:2022 · 1 control

ISO/IEC 42001:2023 · 1 control

  • 8.3 AI risk treatment

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-172 · 1 control

  • 3.4.1e Authoritative Source for Software and Firmware

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in NIST SP 800-218: Asset Management

You are reading one control. How much of NIST SP 800-218 have you already done?

NIST SP 800-218 SP800-218-PW.4.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-218 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 30 of 42 NIST SP 800-218 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.4% covered · 12 gapsIf you hold C5 (Germany)61.9% covered · 16 gapsIf you hold NIST SP 800-161 Rev 161.9% covered · 16 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.152.4% covered · 20 gapsIf you hold ISO 27002:202252.4% covered · 20 gapsIf you hold Azure Security Benchmark50% covered · 21 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 16 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll NIST SP 800-218 controls