NIST SP 800-172
CM

NIST SP 800-172 3.4.1e: Authoritative Source for Software and Firmware

Establish and maintain an authoritative source and repository to provide a trusted source and accountability for approved and vetted software components.

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

What else in your programme already covers this

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

CIS Controls v8 · 5 controls

  • CIS-16.11 Leverage Vetted Modules or Services for Application Security Components
  • CIS-2.1 Establish and Maintain a Software Inventory
  • CIS-2.2 Ensure Authorized Software is Currently Supported
  • CIS-2.5 Allowlist Authorized Software
  • CIS-2.6 Allowlist Authorized Libraries
  • NIST-CSF-GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties
  • NIST-CSF-ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained
  • NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk
  • NIST-CSF-PR.PS-05 Installation and execution of unauthorized software are prevented

NIST SP 800-53 Rev 5 · 4 controls

  • AM-2 Use only approved services
  • ASBv3-AM-5 Use only approved applications in virtual machine
  • ASBv3-DS-3 Secure DevOps infrastructure

FedRAMP High · 3 controls

  • CM-10 Software Usage Restrictions
  • CM-7(2) Prevent Program Execution
  • CM-7(5) Authorized Software Allow-by-Exception

FedRAMP Moderate · 3 controls

  • CM-10 Software Usage Restrictions
  • CM-7(2) Prevent Program Execution
  • CM-7(5) Authorized Software Allow-by-Exception

ISO 27001:2022 · 3 controls

  • 5.21 Managing information security in the information and communication technology (ICT) supply chain
  • 8.19 Installation of software on operational systems
  • 8.4 Access to source code

ISO 27002:2022 · 3 controls

  • 5.21 Managing information security in the ICT supply chain
  • 8.19 Installation of software on operational systems
  • 8.4 Access to source code

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-218 · 3 controls

C5 (Germany) · 2 controls

CMMC 2.0 · 2 controls

PCI DSS 4.0 · 2 controls

  • 12.5.1 12.5.1 Inventory of in-scope system components
  • 6.3.2 6.3.2 Inventory of bespoke software and components
  • 03.04.08 Authorized Software - Allow by Exception

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 CM

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

NIST SP 800-172 3.4.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.

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.

Query this from an agent

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