CIS Critical Security Controls v8.1, released June 2024, is the Center for Internet Security's prioritized cyber-defense checklist: 18 Controls, broken into 153 Safeguards, prioritized through 3 cumulative Implementation Groups sized to an organization's resources — IG1 (56 foundational Safeguards), IG2 (+74, 130 total) and IG3 (+23, all 153). It is an iterative refresh of Version 8 (May 2021) that deliberately kept the same 18 Controls and 153 Safeguards rather than renumbering or re-scoping them. CIS describes the Controls as "a prescriptive, prioritized, and simplified set of best practices" for defending against common attacks.
Key takeaways
- None of this touched the count or numbering of Safeguards — an organization already working from v8 does not need to re-map its program to adopt v8.1.
- Each Control is an objective; the work itself lives in its individually numbered Safeguards (e.g., Safeguard 1.1, 1.2, …), 153 of which exist across all 18 Controls, per CIS's Implementation Groups page.
- The most operationally important part of the Controls is not the 18-item list but the Implementation Groups (IGs) — a cumulative way to decide which Safeguards to adopt first.
- Yes, in two ways.
What actually changed in v8.1?
CIS frames the v8.1 update around three design principles, quoted directly from its own page: "Context" ("enhances the scope and practical applicability of Safeguards by incorporating specific examples and additional explanations"), "Coexistence" ("aligns with other major security frameworks to the extent practical while preserving the unique features of the CIS Controls"), and "Consistency" ("maintains continuity for existing CIS Controls users, ensuring little to no change due to this update"). In concrete terms, CIS's own change list for v8.1 is:
- Added "the 'Govern' security function introduced in the National Institute of Standards and Technology (NIST) Cybersecurity Framework (CSF) 2.0"
- "Realigned NIST CSF security function mappings to match NIST CSF 2.0"
- "Included new and expanded glossary definitions for reserved words"
- "Revised Asset Classes, alongside new mappings to Safeguards"
- Fixed "minor typos in Safeguard descriptions"
- Added "clarification to a few anemic Safeguard descriptions"
None of this touched the count or numbering of Safeguards — an organization already working from v8 does not need to re-map its program to adopt v8.1. CIS's download for v8.1 comes as a PDF, an Excel workbook, a change log and the Implementation Groups; the per-Safeguard measurement method is published separately, as described below.
What are the 18 Controls?
Per CIS's own published list, the 18 Controls are:
| # | Control |
|---|---|
| 1 | Inventory and Control of Enterprise Assets |
| 2 | Inventory and Control of Software Assets |
| 3 | Data Protection |
| 4 | Secure Configuration of Enterprise Assets and Software |
| 5 | Account Management |
| 6 | Access Control Management |
| 7 | Continuous Vulnerability Management |
| 8 | Audit Log Management |
| 9 | Email and Web Browser Protections |
| 10 | Malware Defenses |
| 11 | Data Recovery |
| 12 | Network Infrastructure Management |
| 13 | Network Monitoring and Defense |
| 14 | Security Awareness and Skills Training |
| 15 | Service Provider Management |
| 16 | Application Software Security |
| 17 | Incident Response Management |
| 18 | Penetration Testing |
Each Control is an objective; the work itself lives in its individually numbered Safeguards (e.g., Safeguard 1.1, 1.2, …), 153 of which exist across all 18 Controls, per CIS's Implementation Groups page.
How do the Implementation Groups work?
The most operationally important part of the Controls is not the 18-item list but the Implementation Groups (IGs) — a cumulative way to decide which Safeguards to adopt first. CIS's own IG pages state the structure directly:
| Group | Safeguards | CIS's description |
|---|---|---|
| IG1 | 56 | "The on-ramp to the CIS Controls," a "foundational set of 56 cyber defense Safeguards," aimed at an enterprise "typically small to medium-sized with limited IT and cybersecurity expertise" |
| IG2 | +74 → 130 total | "Comprised [of] 74 additional Safeguards" that "builds upon the 56 Safeguards identified in IG1," for an enterprise with staff "responsible for managing and protecting IT infrastructure" across multiple departments |
| IG3 | +23 → 153 total | "Comprised of an additional 23 Safeguards," building on IG1 and IG2 "totaling the 153 Safeguards in CIS Controls v8 and v8.1," for an enterprise with dedicated security specialists facing "targeted attacks from a sophisticated adversary" |
Because the groups are cumulative, every IG1 Safeguard is also in IG2 and IG3 — there is no scenario where an organization implements IG2 without having also implemented IG1's 56 Safeguards. An auditor or customer asking "are you IG1?" is asking whether all 56 IG1-tagged Safeguards, spread across all 18 Controls, are in place — not just the first few Controls on the list. CIS's IG1 page calls IG1 "essential cyber hygiene" and "an emerging minimum standard of information security for all enterprises."
Do CIS Controls apply to a device maker?
Yes, in two ways. First, a device maker is itself an enterprise: its build servers, code repositories and signing keys are enterprise assets, and the firmware it ships is "in-house developed" software. CIS describes Control 16 as managing "the security life cycle of in-house developed, hosted, or acquired software to prevent, detect, and remediate security weaknesses before they can impact the enterprise" (Control 16 page). Most of Control 16 sits in IG2 and IG3, so a firmware team that claims IG2 is making claims about its development process, not only its office IT.
Second, your customers run the Controls on your product. CIS's Control 1 explicitly includes "non-computing/Internet of Things (IoT) devices" among the enterprise assets to inventory, and Safeguard 4.1 names them in the secure-configuration process. A gateway, PLC or camera you ship becomes an asset in someone else's IG1 program, and what your product makes easy or hard shows up in their audit.
CIS has published IoT-specific guidance before — the CIS Controls v7.1 Internet of Things Companion Guide, dated June 2019 — but that guide targets v7.1 numbering. For v8.1, work from the Safeguard text itself.
Which Safeguards cover firmware development and vulnerability handling?
The Safeguard text and IG assignments below come from CIS's public Controls Assessment Specification, written for v8; v8.1 kept the same numbering and IG counts. Wording is shortened here; read the full text on the Control 16 and Control 7 pages before using it in an audit.
| Safeguard | Short title | IG | What it asks of a firmware team |
|---|---|---|---|
| 2.1 | Establish and Maintain a Software Inventory | 1, 2, 3 | Know what software runs on your own build and signing systems |
| 7.1 | Vulnerability Management Process | 1, 2, 3 | A documented process, reviewed annually |
| 7.2 | Remediation Process | 1, 2, 3 | "Risk-based remediation strategy," reviewed monthly or more often |
| 7.7 | Remediate Detected Vulnerabilities | 2, 3 | Remediation "on a monthly, or more frequent, basis" |
| 16.1 | Secure Application Development Process | 2, 3 | Covers secure design, coding, training, "security of third-party code" and testing |
| 16.2 | Process to Accept and Address Software Vulnerabilities | 2, 3 | "A means for external entities to report," with intake, assignment, remediation and tracking |
| 16.4 | Inventory of Third-Party Software Components | 2, 3 | A "bill of materials," including the risks of each component, evaluated "at least monthly" |
| 16.5 | Up-to-Date and Trusted Third-Party Components | 2, 3 | Trusted sources, or evaluate components "for vulnerabilities before use" |
| 16.6 | Severity Rating System for Application Vulnerabilities | 2, 3 | A rating system and a "minimum level of security acceptability for releasing code" |
| 16.12 | Code-Level Security Checks | 3 | Static and dynamic analysis in the life cycle |
| 16.13 | Application Penetration Testing | 3 | Authenticated and unauthenticated testing of the application |
| 16.14 | Threat Modeling | 3 | Identify design flaws "before code is created" |
Two observations for device teams. 16.4 is CIS's SBOM Safeguard in all but name; our firmware SBOM guide covers how to build one for a binary image. And 16.2 is the vulnerability-disclosure intake a product security team runs anyway; our vulnerability disclosure policy template is a starting point. For 16.14 and 16.13, catalogues such as MITRE CAPEC and MITRE D3FEND give the shared vocabulary.
What will customers running CIS Controls ask of your device?
Read from the customer side, several IG1 Safeguards turn into product requirements. The Safeguard text is from the Assessment Specification pages for Control 1, Control 2, Control 4 and Control 8.
| Customer Safeguard (IG1) | What the customer must do | What your product should make possible |
|---|---|---|
| 1.1 Detailed Enterprise Asset Inventory | Record hardware address, machine name and owner for every asset, IoT included | Discoverable model, serial and MAC; stable identifiers |
| 2.1 Software Inventory | Record title, publisher, version for software on assets | Readable firmware version; an SBOM on request |
| 2.2 Authorized Software is Currently Supported | Allow only supported software, or document an exception | A published support period per firmware line |
| 4.7 Manage Default Accounts | Disable default accounts "such as root, administrator, and other pre-configured vendor accounts" | No shared default password; documented way to disable vendor accounts |
| 7.3 / 7.4 Automated Patch Management | Apply OS and application updates monthly or more often, through automated patch management | Signed updates that can be rolled out at fleet scale |
| 8.2 Collect Audit Logs | Enable logging across enterprise assets | Exportable logs (syslog or similar) |
A product that cannot meet these forces each customer to write an exception under 2.2 or 4.7. That cost tends to come back to you in procurement and security questionnaires.
What does an IG2 plan look like for a device team?
Worked example — synthetic, for illustration only. A 40-person company makes Linux-based building-automation controllers. It already meets IG1 for its office IT and wants to claim IG2 for its engineering organisation within two quarters.
Inventory first (2.1 → 16.4)Generate an SBOM for each shipping firmware line and store it with the release. Review the component list monthly, as 16.4 asks, and record which components are past upstream support. Vulnerability intake (16.2)Publish a security contact and policy, route reports to a tracker with severity fields, and record time to triage and time to fix. Severity and release gate (16.6)Adopt CVSS plus exploit data (CISA KEV, FIRST EPSS) as the rating, and set a release rule: no known-exploited vulnerability ships unfixed without a recorded exception. See our KEV and EPSS guide. Remediation rhythm (7.2, 7.7)Monthly review of open findings against the component inventory, with fixes tied to the next firmware release. Development process (16.1, 16.5)Write down the secure-development process, including how third-party code is chosen and updated. Our IEC 62443-4-1 guide covers a fuller version of the same practices. Evidence packFor each Safeguard, keep the document, the date of last review and one record that shows it running — the same inputs the Assessment Specification lists.
IG3 items (16.12–16.14) come next: code-level checks, application penetration testing and threat modelling.
Where does this sit next to NIST CSF and IEC 62443?
v8.1's main structural change was aligning its internal "security functions" to the six Functions of NIST CSF 2.0 (see our NIST CSF 2.0 guide) — adding a Govern function and realigning the others — which CIS calls "Coexistence": aligning "with other major security frameworks to the extent practical while preserving the unique features of the CIS Controls." That is a mapping exercise, not a merger: CIS Controls remain a flat list of 18 prescriptive Controls and 153 Safeguards, not CSF's six Functions/22 Categories/Subcategories taxonomy. Organizations already building toward CSF 2.0, ISO/IEC 27001, or sector rules like IEC 62443 (see our IEC 62443-2-1 guide) can use CIS Controls as the concrete "what to actually configure" layer underneath those higher-level outcome or requirement statements — but each framework's own text, not a third-party crosswalk, should be the final word on whether a specific Safeguard satisfies a specific regulatory requirement. For product requirements specifically, the CIS Controls are an enterprise framework; component-level requirements live in standards such as IEC 62443-4-2.
What are the common pitfalls?
- Claiming an IG by Control count. IG1 is 56 specific Safeguards across the Controls, not "Controls 1 to 6."
- Reading 16.4 as a one-off SBOM. It asks for an inventory that is evaluated "at least monthly" and records risks per component.
- Treating Control 16 as web-app only. Firmware is in-house developed software; the Safeguards apply.
- Quoting v7.1 IoT guidance against v8.1 numbering. The companion guide predates the v8 renumbering.
- Relying on summaries for audit text. Use the CIS download or the Assessment Specification, not a table like the ones above.
Where should a team start?
Start at IG1, regardless of sizeCIS positions IG1's 56 Safeguards as what every enterprise should have, not just small ones — confirm the full 56 across all 18 Controls before claiming IG1 status, since they are spread unevenly (some Controls have several IG1 Safeguards, others none). Treat IGs as a progression path, not a scorecard choiceMoving from IG1 to IG2 means implementing 74 additional Safeguards on top of the 56 already in place, not picking a different 130. Add the product viewCheck your device against the customer-side table above; each gap is a future exception in a customer's audit. Use the v8.1 Govern-function and CSF realignment as a bridge, not a substitute, if your organization is also tracking NIST CSF 2.0 — the Safeguard-level detail in CIS Controls is what turns a CSF outcome statement into something an engineer can actually implement and audit. Re-verify Safeguard-to-IG mappings against CIS's own Controls Navigatorbefore building compliance tooling, since third-party summaries (including this guide's own tables) can drift from the authoritative source as CIS issues future minor updates. Our firmware security testing pillar covers the testing side of 16.12 and 16.13.
Where does firmware SBOM and CVE matching fit?
SoftWSP doesn't score an organization's IG1/IG2/IG3 maturity or map findings to CIS Safeguards — that's a broader program assessment outside what a firmware scan can confirm. What the platform does is narrower: it extracts a CycloneDX 1.6 SBOM from a firmware image, matches the components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report that an engineer reviews. That output is evidence an engineering team can file under 16.4 (component inventory) and the Control 7 remediation work; deciding which Safeguard it satisfies, and whether, stays with your team and your assessor.
SoftWSP's device and firmware security work can help an engineering team work out which CIS Safeguards are realistic to implement first for a connected product or OT environment, rather than treating all 153 as equally urgent: see device & firmware security services.
This guide summarises public CIS publications; it does not constitute legal or compliance advice. Confirm current Safeguard text and IG assignments against CIS's own Controls Navigator and downloadable workbook before using them in an audit or contract.
Put this guide to work
Frequently asked questions
What is CIS Critical Security Controls v8.1?
A prioritized set of cyber-defense best practices published by the Center for Internet Security (CIS). CIS's own text describes the Controls as "a prescriptive, prioritized, and simplified set of best practices" organizations can use to defend against common attacks. Version 8.1 is, per CIS's blog, an iterative update released in June 2024, three years after Version 8 (May 2021), rather than a ground-up rewrite — CIS states it kept the same 18 Controls and 153 Safeguards and designed the update around three principles: "Context," "Coexistence," and "Consistency," the last of which CIS defines as "maintain[ing] continuity for existing CIS Controls users, ensuring little to no change due to this update."
What changed between CIS Controls v8 and v8.1?
CIS's own v8.1 page lists the changes as: the addition of "the 'Govern' security function introduced in the National Institute of Standards and Technology (NIST) Cybersecurity Framework (CSF) 2.0"; having "realigned NIST CSF security function mappings to match NIST CSF 2.0"; "included new and expanded glossary definitions for reserved words"; "revised Asset Classes, alongside new mappings to Safeguards"; fixed "minor typos in Safeguard descriptions"; and added "clarification to a few anemic Safeguard descriptions." None of this changed which 153 Safeguards exist or which Implementation Group each belongs to.
What are the 18 CIS Controls?
Per CIS's own published list: 1) Inventory and Control of Enterprise Assets, 2) Inventory and Control of Software Assets, 3) Data Protection, 4) Secure Configuration of Enterprise Assets and Software, 5) Account Management, 6) Access Control Management, 7) Continuous Vulnerability Management, 8) Audit Log Management, 9) Email and Web Browser Protections, 10) Malware Defenses, 11) Data Recovery, 12) Network Infrastructure Management, 13) Network Monitoring and Defense, 14) Security Awareness and Skills Training, 15) Service Provider Management, 16) Application Software Security, 17) Incident Response Management, and 18) Penetration Testing. Each Control breaks down into individually numbered Safeguards (for example, Safeguard 1.1).
What are Implementation Groups (IG1, IG2, IG3) and how many Safeguards does each contain?
A cumulative, three-tier way to decide which of the 153 Safeguards to implement first, based on an organization's size and risk profile. CIS's own IG1 page states IG1 "is the on-ramp to the CIS Controls and consists of a foundational set of 56 cyber defense Safeguards," aimed at an enterprise that is "typically small to medium-sized with limited IT and cybersecurity expertise." CIS's IG2 page states IG2 "is comprised [of] 74 additional Safeguards and builds upon the 56 Safeguards identified in IG1" (56 + 74 = 130 total), for an enterprise that "employs individuals who are responsible for managing and protecting IT infrastructure" across multiple departments. CIS's IG3 page states IG3 "is comprised of an additional 23 Safeguards. It builds upon the Safeguards identified in IG1 (56) and IG2 (74) totaling the 153 Safeguards in CIS Controls v8 and v8.1," aimed at an enterprise with dedicated security specialists facing "targeted attacks from a sophisticated adversary."
Is CIS Controls v8.1 mandatory, and how does it relate to NIST CSF?
No single global mandate requires CIS Controls; CIS positions them as voluntary best-practice guidance, though some contracts, insurers, or state/sector rules reference them. v8.1's main structural change was aligning its "security functions" to the six Functions of NIST CSF 2.0 (see our [NIST CSF 2.0 guide](/guides/nist-csf-2-0/)) by adding a Govern function and realigning the others — CIS itself frames this as "Coexistence," aligning "with other major security frameworks to the extent practical while preserving the unique features of the CIS Controls," not as adopting CSF's Categories or Subcategories wholesale. Treat CIS Controls as a prioritized, prescriptive Safeguard checklist that maps onto CSF's broader outcome taxonomy, rather than a competing or identical framework.
Sources
- CIS: Critical Security Controls Version 8.1 (overview, design principles, changes from v8)
- CIS: The 18 CIS Critical Security Controls (list)
- CIS: Implementation Groups overview (153 Safeguards total, cumulative IG1/IG2/IG3)
- CIS: Implementation Group 1 (IG1) — 56 Safeguards
- CIS: Implementation Group 2 (IG2) — +74 Safeguards (130 total)
- CIS: Implementation Group 3 (IG3) — +23 Safeguards (153 total)
- CIS: The Ongoing Evolution of the CIS Critical Security Controls (blog, v8.1 release timing)
- NIST: Cybersecurity Framework (CSF) 2.0 — official overview page
- CIS: Control 16, Application Software Security (overview)
- CIS: CIS Controls v7.1 Internet of Things Companion Guide (2019)
- CIS: Controls Assessment Specification for Controls v8 (home)
- CIS: Controls Assessment Specification, Control 1 (Safeguard 1.1)
- CIS: Controls Assessment Specification, Control 2 (Safeguards 2.1, 2.2)
- CIS: Controls Assessment Specification, Control 4 (Safeguards 4.1, 4.7)
- CIS: Controls Assessment Specification, Control 7 (Safeguards 7.1-7.7)
- CIS: Controls Assessment Specification, Control 8 (Safeguard 8.2)
- CIS: Controls Assessment Specification, Control 16 (Safeguards 16.1-16.14)
- CIS: Controls Assessment Specification, Control 18 (Safeguards 18.1, 18.2)
About this guide
SoftWSP Firmware Security Desk
Covers the Firmware vulnerabilities & fixes cluster: 129 guides.

In this cluster
Questions about this page?
