CIS Controls v8 CIS-16.5: Use Up-to-Date and Trusted Third-Party Software Components

What else in your programme already covers this

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

FedRAMP High · 5 controls

CM-7 Least Functionality
RA-5 Vulnerability Monitoring and Scanning
SA-22 Unsupported System Components (SA-22)
SI-2 Flaw Remediation
SR-11 Component Authenticity (SR-11)

FedRAMP Moderate · 5 controls

CM-7 Least Functionality
RA-5 Vulnerability Monitoring and Scanning
SA-22 Unsupported System Components (SA-22)
SI-2 Flaw Remediation
SR-11 Component Authenticity (SR-11)

PCI DSS 4.0 · 5 controls

12.3.4 12.3.4 Annual review of hardware and software technologies
5.2.1 5.2.1 Anti-malware deployed on all system components
6.3.1 6.3.1 Vulnerability identification and risk ranking
6.3.2 6.3.2 Inventory of bespoke software and components
6.4.3 6.4.3 Payment page script management

CMMC 2.0 · 4 controls

CA.L2-3.12.3 Security Control Monitoring
CM.L2-3.4.9 User-Installed Software
RA.L2-3.11.2 Vulnerability Scan
SI.L2-3.14.1 Flaw Remediation

ISO 27002:2022 · 4 controls

5.21 Managing information security in the ICT supply chain
8.25 Secure development life cycle
8.28 Secure coding
8.8 Management of technical vulnerabilities

NIST Cybersecurity Framework 2.0 · 4 controls

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-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk

NIST SP 800-161 Rev 1 · 4 controls

161R1-CM-10 Software Usage Restrictions
161R1-CM-14 Signed Components
161R1-SA-22 Unsupported System Components
161R1-SR-4 Provenance

NIST SP 800-53 Rev 5 · 4 controls

NIST800-SI-2 SI-2 Flaw Remediation
NIST800-SR-11 SR-11 Component Authenticity
NIST800-SR-3 SR-3 Supply Chain Controls and Processes
NIST800-SR-5 SR-5 Acquisition Strategies, Tools, and Methods

AWS Well-Architected Security Pillar · 3 controls

SEC06-BP02 Provision compute from hardened images
SEC06-BP05 Automate compute protection
SEC11-BP05 Centralize services for packages and dependencies

Australian Information Security Manual · 3 controls

ISM-2027 Verifying software artefacts before import
ISM-2029 Restricting third-party libraries to trustworthy sources
ISM-2055 Using third-party build provenance

ISO 27001:2022 · 3 controls

5.21 Managing information security in the information and communication technology (ICT) supply chain
8.25 Secure development life cycle
8.8 Management of technical vulnerabilities

ISO 27701:2019 · 3 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

NIST SP 800-218 · 3 controls

SP800-218-PO.1.3 Communicate Requirements to Third-Party Providers
SP800-218-PW.4.1 Reuse Trusted Software Components
SP800-218-PW.4.4 Verify Acquired Components Meet Security Requirements

HIPAA Security Rule · 2 controls

164.308(a)(1)(ii)(A) Risk Analysis (Required)
164.308(a)(1)(ii)(B) Risk Management (Required)

NIST SP 800-172 · 2 controls

3.14.1e Verify Integrity of Security Critical Software and Firmware
3.14.3e Include Systems in Scope of Enhanced Requirements or Segregate into Purpose-Specific Networks

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(1)(ii)(A) Risk Analysis (Required)
164.308(a)(1)(ii)(B) Risk Management (Required)

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

C5 (Germany) · 1 control

C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept

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

CCM-TVM-05 External Library Vulnerabilities

ISO/IEC 42001:2023 · 1 control

8.3 AI risk treatment

NIS2 Directive · 1 control

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

NIST SP 800-171 Rev 3 · 1 control

03.17.03 Supply Chain Requirements and Processes

SOC 2 · 1 control

SOC2-CC9.2 CC9.2 Assessing and managing vendor and business partner risk

UK Cyber Essentials · 1 control

CE-SU.1 Software Licensed and Supported

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.

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

CIS Controls v8 CIS-16.5 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 gaps If you hold FedRAMP Moderate62.7% covered · 57 gaps If you hold NIST SP 800-53 Rev 557.5% covered · 65 gaps If you hold NIST Cybersecurity Framework 2.050.3% covered · 76 gaps If you hold ISO 27002:202249.7% covered · 77 gaps If 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 each Browse the graph free