NIST SP 800-218
NIST SP 800-218: Information Security Policies

NIST SP 800-218 SP800-218-PO.5.2: Harden Development Endpoints

Secure and harden development endpoints (the systems used to perform development) to perform development-related tasks with a reduced attack surface.

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

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 4 controls

Azure Security Benchmark · 3 controls

  • ASBv3-DS-3 Secure DevOps infrastructure
  • ASBv3-PA-6 Use privileged access workstations
  • ES-1 Use Endpoint Detection and Response (EDR)

C5 (Germany) · 2 controls

  • C5-AM-02 Acceptable Use and Safe Handling of Assets Policy
  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

CIS Controls v8 · 2 controls

  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • CIS-4.1 Establish and Maintain a Secure Configuration Process

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

ISO 27001:2022 · 2 controls

  • 8.1 User end point devices
  • 8.9 Configuration management

ISO 27002:2022 · 2 controls

  • 8.1 User endpoint devices
  • 8.9 Configuration management

NIST SP 800-161 Rev 1 · 2 controls

AWS Well-Architected Security Pillar · 1 control

BSIMM · 1 control

  • SE1.2 Ensure host and network security basics are in place

CMMC 2.0 · 1 control

FedRAMP High · 1 control

  • CM-6 Configuration Settings

FedRAMP Moderate · 1 control

  • CM-6 Configuration Settings

NIST Cybersecurity Framework 2.0 · 1 control

SOC 2 · 1 control

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

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: Information Security Policies

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

NIST SP 800-218 SP800-218-PO.5.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 26 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll NIST SP 800-218 controls