NIST SP 800-172
SI

NIST SP 800-172 3.14.1e: Verify Integrity of Security Critical Software and Firmware

Verify the integrity of security critical and essential software using root of trust mechanisms or cryptographic signatures.

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

What else in your programme already covers this

This control maps to 32 controls across 17 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 Cybersecurity Framework 2.0 · 5 controls

  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
  • NIST-CSF-PR.PS-05 Installation and execution of unauthorized software are prevented
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
  • NIST-CSF-RC.RP-05 The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed

NIST SP 800-53 Rev 5 · 3 controls

PCI DSS 4.0 · 3 controls

  • 11.5.2 11.5.2 Change detection on critical files
  • 11.6.1 11.6.1 Payment page tamper detection
  • 6.4.3 6.4.3 Payment page script management

CIS Controls v8 · 2 controls

  • CIS-16.5 Use Up-to-Date and Trusted Third-Party Software Components
  • CIS-2.7 Allowlist Authorized Scripts

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

FedRAMP High · 2 controls

  • SI-7 Software, Firmware, and Information Integrity
  • SI-7(1) Integrity Checks

FedRAMP Moderate · 2 controls

  • SI-7 Software, Firmware, and Information Integrity
  • SI-7(1) Integrity Checks

HIPAA Security Rule · 2 controls

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

Azure Security Benchmark · 1 control

  • ASBv3-AM-5 Use only approved applications in virtual machine

C5 (Germany) · 1 control

  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 8.24 Use of cryptography

ISO 27002:2022 · 1 control

  • 8.24 Use of cryptography

NIST SP 800-218 · 1 control

SOC 2 · 1 control

  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software

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 SI

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

NIST SP 800-172 3.14.1e is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-172 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 24 of 35 NIST SP 800-172 controls already carry evidence.

If you hold NIST SP 800-53 Rev 568.6% covered · 11 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.165.7% covered · 12 gapsIf you hold NIST SP 800-161 Rev 162.9% covered · 13 gapsIf you hold FedRAMP Moderate60% covered · 14 gapsIf you hold NIST Cybersecurity Framework 2.048.6% covered · 18 gapsIf you hold C5 (Germany)45.7% covered · 19 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. 5 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 32 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll NIST SP 800-172 controls