CIS Controls v8.1 control library
Every control CMDash tracks for CIS Controls v8.1, in the order the standard itself uses. Each one is a row in the product with an owner, a status, evidence and its own history — this page is the public index of what those rows are.
CIS publishes the Controls at no cost under a Creative Commons licence whose NoDerivatives and NonCommercial terms rule out embedding the safeguard text in this product.
CMDash publishes the identifiers, titles and cross-framework mappings so you can see the shape of what is tracked, and links you to Center for Internet Security for the document itself. A tenant that holds its own licence can load the real text through the framework import.
Download free from CIS →Families
Enterprise Asset Inventory · 5
| 1.1 | Establish and maintain detailed enterprise asset inventory Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 1.2 | Address unauthorized assets |
| 1.3 | Utilize DHCP logging to update enterprise asset inventory |
| 1.4 | Use dynamic host configuration protocol to update asset inventory |
| 1.5 | Use a passive asset discovery tool |
Software Asset Inventory · 7
| 2.1 | Establish and maintain a software inventory Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 2.2 | Ensure authorized software is currently supported |
| 2.3 | Address unauthorized software |
| 2.4 | Utilize automated software inventory tools |
| 2.5 | Allowlist authorized software |
| 2.6 | Allowlist authorized libraries |
| 2.7 | Allowlist authorized scripts |
Data Protection · 14
| 3.1 | Establish and maintain a data management process Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 3.2 | Establish and maintain a data inventory |
| 3.3 | Configure data access control lists |
| 3.4 | Enforce data retention |
| 3.5 | Securely dispose of data |
| 3.6 | Encrypt data on end-user devices |
| 3.7 | Establish and maintain a data classification scheme |
| 3.8 | Document data flows |
| 3.9 | Encrypt data on removable media |
| 3.10 | Encrypt sensitive data in transit |
| 3.11 | Encrypt sensitive data at rest Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 3.12 | Segment data processing and storage |
| 3.13 | Deploy a data loss prevention solution Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 3.14 | Log sensitive data access |
Secure Configuration · 12
Account Management · 6
| 5.1 | Establish and maintain an inventory of accounts Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 5.2 | Use unique passwords |
| 5.3 | Disable dormant accounts |
| 5.4 | Restrict administrator privileges |
| 5.5 | Establish and maintain an inventory of service accounts |
| 5.6 | Centralize account management |
Access Control Management · 8
| 6.1 | Establish an access granting process |
| 6.2 | Establish an access revoking process |
| 6.3 | Require MFA for externally-exposed applications Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 6.4 | Require MFA for remote network access |
| 6.5 | Require MFA for administrative access Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 6.6 | Establish and maintain an inventory of auth and authorization systems |
| 6.7 | Centralize access control |
| 6.8 | Define and maintain role-based access control |
Vulnerability Management · 7
| 7.1 | Establish and maintain a vulnerability management process Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 7.2 | Establish and maintain a remediation process |
| 7.3 | Perform automated operating system patch management |
| 7.4 | Perform automated application patch management |
| 7.5 | Perform automated vulnerability scans of internal assets Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 7.6 | Perform automated vulnerability scans of external assets |
| 7.7 | Remediate detected vulnerabilities |
Audit Log Management · 12
| 8.1 | Establish and maintain an audit log management process |
| 8.2 | Collect audit logs Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 8.3 | Ensure adequate audit log storage |
| 8.4 | Standardize time synchronization |
| 8.5 | Collect detailed audit logs |
| 8.6 | Collect DNS query audit logs |
| 8.7 | Collect URL request audit logs |
| 8.8 | Collect command-line audit logs |
| 8.9 | Centralize audit logs Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 8.10 | Retain audit logs |
| 8.11 | Conduct audit log reviews |
| 8.12 | Collect service provider logs |
Email & Browser Protection · 7
Malware Defenses · 7
| 10.1 | Deploy and maintain anti-malware software Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 10.2 | Configure automatic anti-malware signature updates |
| 10.3 | Disable autorun and autoplay |
| 10.4 | Configure automatic anti-malware scanning of removable media |
| 10.5 | Enable anti-exploitation features |
| 10.6 | Centrally manage anti-malware software |
| 10.7 | Use behavior-based anti-malware software |
Data Recovery · 5
| 11.1 | Establish and maintain a data recovery process Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 11.2 | Perform automated backups |
| 11.3 | Protect recovery data |
| 11.4 | Establish and maintain an isolated instance of recovery data |
| 11.5 | Test data recovery |
Network Infrastructure · 8
Network Monitoring · 11
Security Awareness · 9
Service Provider Management · 7
Application Security · 14
Incident Response · 9
Penetration Testing · 5
| 18.1 | Establish and maintain a penetration testing program Maps to NIST Cybersecurity Framework (1.1, legacy) |
| 18.2 | Perform periodic external penetration tests |
| 18.3 | Remediate penetration test findings |
| 18.4 | Validate security measures after each penetration test |
| 18.5 | Perform periodic internal penetration tests |
Where this comes from
Control identifiers, families and titles are the rows CMDash’s own seed data writes for CIS Controls v8.1 8.1, published from a build-time export rather than read from any customer’s workspace. Cross-framework mappings are CMDash’s own, and each one is shown on both frameworks it connects.
Every control on this page becomes a row with an owner, a status, evidence and an audit trail — with the crosswalks already wired, so evidence mapped once counts in more than one framework.