CIS Controls v8
CIS Control 2: Inventory and Control of Software Assets

CIS Controls v8 CIS-2.1: Establish and Maintain a Software Inventory

Keep a detailed register of all licensed software installed across enterprise assets. Each entry has to capture the title, the publisher, the date of first installation or use, and the business reason for it; where it makes sense, also capture the URL, the app store or stores, the version or versions, how it is deployed, and the date it was retired. Revisit and refresh the register at least twice a year.

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

What else in your programme already covers this

This control maps to 48 controls across 24 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 · 5 controls

ISO 27701:2019 · 4 controls

  • 6.5 Asset management
  • 6.5.1 Responsibility for assets
  • 6.5.2 Information classification
  • 6.9.5 Control of operational software

SOC 2 · 4 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

HIPAA Security Rule · 3 controls

ISO/IEC 42001:2023 · 3 controls

  • 7.1 Resources
  • A.4.2 Resource documentation
  • A.4.5 System and computing resources

NIST SP 800-66 Rev 2 · 3 controls

PCI DSS 4.0 · 3 controls

  • 12.3.3 12.3.3 Cryptographic cipher suite and protocol inventory reviewed annually
  • 12.5.1 12.5.1 Inventory of in-scope system components
  • 6.3.2 6.3.2 Inventory of bespoke software and components

Australian Information Security Manual · 2 controls

  • ISM-1493 Maintaining software registers
  • ISM-1643 Versions and patch histories in software registers

Azure Security Benchmark · 2 controls

  • ASBv3-AM-5 Use only approved applications in virtual machine
  • DS-2 Ensure software supply chain security

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

ISO 27001:2022 · 2 controls

  • 5.32 Intellectual property rights
  • 5.9 Inventory of information and other associated assets

ISO 27002:2022 · 2 controls

  • 5.32 Intellectual property rights
  • 5.9 Inventory of information and other associated assets

NIST SP 800-171 Rev 3 · 2 controls

  • 03.04.08 Authorized Software - Allow by Exception
  • 03.04.10 System Component Inventory

C5 (Germany) · 1 control

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CIS Controls v8.1 · 1 control

  • 2.1 Establish and Maintain a Software Inventory

CMMC 2.0 · 1 control

DORA · 1 control

FedRAMP High · 1 control

  • CM-8 System Component Inventory

FedRAMP Moderate · 1 control

  • CM-8 System Component Inventory

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-172 · 1 control

  • 3.4.1e Authoritative Source for Software and Firmware

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.

Other controls in CIS Control 2: Inventory and Control of Software Assets

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

CIS Controls v8 CIS-2.1 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 48 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll CIS Controls v8 controls