CIS Controls v8
CIS Control 16: Application Software Security

CIS Controls v8 CIS-16.4: Establish and Manage an Inventory of Third-Party Software Components

Set up and manage a current inventory of the third-party components that development relies on, commonly called a bill of materials, together with components planned for later use. Record the risks each third-party component might carry. Check the list at least monthly for changes or updates to the components and to confirm each one is still supported.

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

What else in your programme already covers this

This control maps to 60 controls across 21 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 · 8 controls

NIST Cybersecurity Framework 2.0 · 6 controls

  • NIST-CSF-GV.SC-04 Suppliers are known and prioritized by criticality
  • 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-GV.SC-09 Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle
  • NIST-CSF-ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-ID.RA-10 Critical suppliers are assessed prior to acquisition

ISO 27001:2022 · 5 controls

  • 5.21 Managing information security in the information and communication technology (ICT) supply chain
  • 5.22 Monitoring, review and change management of supplier services
  • 5.9 Inventory of information and other associated assets
  • 8.25 Secure development life cycle
  • 8.8 Management of technical vulnerabilities

HIPAA Security Rule · 4 controls

ISO 27701:2019 · 4 controls

  • 6.11 Systems acquisition, development and maintenance
  • 6.11.2 Security in development and support processes
  • 6.12.1 Information security in supplier relationships
  • 6.5.1 Responsibility for assets

NIST SP 800-66 Rev 2 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC9.2 CC9.2 Assessing and managing vendor and business partner risk

ISO 27002:2022 · 3 controls

  • 5.21 Managing information security in the ICT supply chain
  • 5.9 Inventory of information and other associated assets
  • 8.28 Secure coding

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-218 · 3 controls

AWS Well-Architected Security Pillar · 2 controls

  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • SEC11-BP05 Centralize services for packages and dependencies

Australian Information Security Manual · 2 controls

  • ISM-1730 Producing a software bill of materials
  • ISM-2054 Using third-party software bills of materials

FedRAMP High · 2 controls

  • CM-8 System Component Inventory
  • SR-2 Supply Chain Risk Management Plan (SR-2)

FedRAMP Moderate · 2 controls

  • CM-8 System Component Inventory
  • SR-2 Supply Chain Risk Management Plan (SR-2)

NIST SP 800-172 · 2 controls

  • 3.11.6e Supply Chain Risk Assessment, Response, and Monitoring
  • 3.14.3e Include Systems in Scope of Enhanced Requirements or Segregate into Purpose-Specific Networks

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-35 Anticipate the End of Maintenance of Software and Systems

Azure Security Benchmark · 1 control

  • DS-2 Ensure software supply chain security

CMMC 2.0 · 1 control

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

NIS2 Directive · 1 control

  • Art.21.3 Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessments

PCI DSS 4.0 · 1 control

  • 6.3.2 6.3.2 Inventory of bespoke software and components

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 CIS Control 16: Application Software Security

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-16.4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

If you hold ISO 27001:202266.7% covered · 51 gapsIf you hold FedRAMP Moderate62.7% covered · 57 gapsIf you hold NIST SP 800-53 Rev 557.5% covered · 65 gapsIf you hold NIST Cybersecurity Framework 2.050.3% covered · 76 gapsIf you hold ISO 27002:202249.7% covered · 77 gapsIf you hold Azure Security Benchmark49% covered · 78 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. 240 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll CIS Controls v8 controls