← Frameworks / CIS Controls v8.1.2 / Coverage Analysis

CIS Critical Security Controls Version 8.1.2 โ€” SP 800-53 Coverage

How well do NIST SP 800-53 Rev 5 controls address each CIS Controls v8.1.2 requirement? This analysis maps from framework clauses back to SP 800-53, with expert coverage weightings and gap identification.

Clauses: 153
Avg Coverage: 83.6%
Publisher: Center for Internet Security
Coverage Distribution
Full (85-100%): 102 Substantial (65-84%): 43 Partial (40-64%): 8 Weak (1-39%): 0

Clause-by-Clause Analysis

Sorted by clause
CIS 1.1 Detailed inventory of enterprise assets

Rationale

CM-08 asks for an accurate, complete inventory of system components, at the level of detail the organisation chooses, reviewed on a set cycle. CM-08(04) records who is accountable for each component.

Gaps

CIS lists what to record for each asset, such as its addresses and owner, and asks for a review at least every six months. Choose those details and that cycle in CM-08. Include devices that connect regularly but sit outside the organisation's control.

Mapped Controls

CIS 1.2 Handling of unauthorised assets on the network

Rationale

CM-07(09) keeps a list of approved hardware and stops anything else from being used or connected. CM-08(03) acts on an unauthorised component once it is found, for example by cutting its network access or isolating it.

Gaps

CIS asks the organisation to deal with unauthorised assets every week. Run CM-08(03)'s detection and response on that weekly cycle.

Mapped Controls

CIS 1.3 Active network scanning to find assets

Rationale

CM-08(03) runs automated checks on a set schedule to find components on the network that lack authorisation. CM-08(02) keeps the inventory current by automated means, and an active scanner is one such means.

Gaps

CIS asks for active scanning of the network at least once a day. Make an active scanner one of CM-08's automated tools and run it daily.

Mapped Controls

CIS 1.4 DHCP lease logs as a source for the asset inventory

Rationale

IA-03(03) standardises dynamic address leases and records each lease given to a device, which is what DHCP logging does. CM-08(02) keeps the inventory current from automated sources, and those lease records can feed it.

Gaps

CIS asks for the lease records to feed the asset inventory, with a check at least once a week. Link IA-03(03)'s records to CM-08's inventory on that cycle.

Mapped Controls

CIS 1.5 Passive discovery of assets from network traffic

Rationale

CM-08(03) detects components on the network automatically and on a set cycle, which a passive listening tool can do. CM-08(02) uses those results to keep the inventory current.

Gaps

CIS asks for a passive tool that finds assets by listening to network traffic. Add its findings to the inventory at least once a week, and count it among CM-08's automated means.

Mapped Controls

CIS 2.1 Inventory of installed software and licences

Rationale

CM-08 counts installed software as a system component, so its inventory covers software at the detail the organisation chooses, reviewed on a set cycle. CM-10 tracks software held under quantity licences, which gives the licence count.

Gaps

CIS lists the details to record for each piece of software, such as its business purpose, its publisher and the date it was first installed. Choose those details in CM-08.

Mapped Controls

CIS 2.2 Vendor support for authorised software

Rationale

CM-07(05) keeps a reviewed list of the software allowed to run, which is where the organisation marks supported software as authorised. SA-22 replaces components once vendor support ends, or arranges other support for any that have to stay.

Gaps

CIS asks for a check of support status at least monthly. Treat software that has lost support as unauthorised, unless a recorded exception names its compensating measures and the risk accepted.

Mapped Controls

CIS 2.3 Removal or recorded exception for unauthorised software

Rationale

CM-07 restricts software to what the organisation approves, and CM-07(01) reviews systems on a cycle and removes software found unnecessary or unsafe. CM-08(03) detects unauthorised software and sets off a defined response. CM-11 sets and enforces rules on what users may install, and monitors compliance.

Gaps

CIS lets unauthorised software stay under a recorded exception, and asks for a review at least monthly. Record those exceptions, and set CM-07(01)'s review to that monthly cycle.

Mapped Controls

CIS 2.4 Automated discovery of installed software

Rationale

CM-08(02) maintains the inventory, software included, with automated tools, so it stays current as installations change. CM-08(03) detects software components automatically and flags any that lack approval.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 2.5 Application allowlisting

Rationale

CM-07(05) applies a deny-all, permit-by-exception rule, so only software on the approved list runs, and the organisation reviews that list on a set cycle. CM-07(02) stops programs running outside the organisation's rules.

Gaps

CIS asks for a review of the allowlist at least every six months. Set that cycle in CM-07(05).

Mapped Controls

CIS 2.6 Control of which libraries load into processes

Rationale

CM-07(05) uses a deny-all, permit-by-exception rule, so only listed software runs. Applied to libraries and modules, the same rule decides which code a running process may load.

Gaps

CM-07(05) is written for programs. CIS applies allowlisting to the libraries a process loads as well. Extend the approved list to cover them.

Mapped Controls

CIS 2.7 Script allowlisting with signing and version control

Rationale

CM-07(05) lets only approved code run, and applied to scripts it blocks any that are unlisted. SI-07(15) authenticates code by its signature before it is installed, so the organisation can reject scripts that are unsigned or altered.

Gaps

CIS takes allowlisting down to scripts and names version control as one way to enforce it. Extend CM-07(05)'s list to scripts, and keep the approved ones under version control.

Mapped Controls

CIS 3.1 Documented process for handling data throughout its life

Rationale

RA-02 categorises the organisation's information by impact, which gives the process its sensitivity levels. SI-12 manages and retains information under legal and business requirements, which sets handling and retention limits. SI-12(03) sets how information is destroyed once its retention period ends.

Gaps

CIS asks for one documented process that names an owner for each set of data, reviewed every year. Gather the rules from RA-02 and SI-12 into that document.

Mapped Controls

CIS 3.2 Inventory of sensitive data

Rationale

CM-12 records where chosen information is processed and stored, who can reach it and how its location changes. PM-05(01) keeps a current inventory of the systems that process personal data, one kind of sensitive data.

Gaps

CIS asks for an inventory that covers all sensitive data, with a review at least once a year that gives that data priority. Name the sensitive information types in CM-12 and set that cycle.

Mapped Controls

CIS 3.3 Need-to-know access permissions on data

Rationale

AC-03 enforces approved authorisations for logical access to information, which is the job access control lists do. AC-06 limits each user to the access their duties need, which puts need to know into practice.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 3.4 Minimum and maximum retention periods for data

Rationale

SI-12 manages and retains information in line with the legal and operational requirements that apply to it. Those requirements set how long the organisation keeps each kind of data.

Gaps

CIS asks for both a minimum and a maximum retention period for each kind of data. Record both limits in SI-12's retention rules.

Mapped Controls

CIS 3.5 Disposal of data matched to its sensitivity

Rationale

MP-06 sanitises media before disposal or reuse, with methods whose strength matches the security category of the information. SI-12(03) names the techniques for destroying or erasing information when its retention period is over.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 3.6 Encryption of end-user devices holding sensitive data

Rationale

AC-19(05) requires full-device or container encryption on mobile devices such as phones and tablets. SC-28(01) applies cryptography to information at rest on the components the organisation names, such as laptop and desktop disks.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 3.7 Classification labels for the organisation's data

Rationale

AC-16 defines the security attributes and values the organisation allows and binds them to information, which provides the labels. RA-02 categorises systems and the information they hold by impact and records the result, which gives the scheme its basis.

Gaps

SP 800-53 categorises by impact level. CIS asks for an organisation-wide set of labels, such as public and confidential, reviewed every year. Define those labels in AC-16 and set the yearly review.

Mapped Controls

CIS 3.8 Map of data flows, service providers included

Rationale

CA-03 documents each information exchange with other systems, service providers included, with its interface details and the impact level of the information. CA-09 does the same for internal connections and the information they carry. CM-13 maps how the system processes personal data and which components take part.

Gaps

CIS asks for a record of all the organisation's data flows, provider flows included, reviewed every year. Bring these documents together and widen CM-13's map to data of every kind.

Mapped Controls

CIS 3.9 Encryption of removable media

Rationale

SC-28(01) uses cryptography to protect stored information on the components and media the organisation names. Naming removable media in that list brings it into scope.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 3.10 Encrypted transmission of sensitive data

Rationale

SC-08 protects the confidentiality and integrity of information in transmission. SC-08(01) does it with cryptography, such as TLS or SSH, which prevents disclosure and detects any change along the way.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 3.11 Encryption of sensitive data stored on servers

Rationale

SC-28(01) applies cryptography to stored information on the components the organisation names, such as database and file servers. Listing the systems that hold sensitive data brings them into scope.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 3.12 Segmentation of systems by data sensitivity

Rationale

SC-07(21) and (29) isolate components and functions in separate subnetworks behind boundary protection. SC-32 partitions the system into separate physical or logical domains on criteria the organisation sets, such as data sensitivity.

Gaps

CIS asks for segments drawn by data sensitivity. Set sensitivity as SC-32's partitioning criterion, and keep sensitive data on the assets approved for it.

Mapped Controls

CIS 3.13 Data loss prevention tools that locate sensitive data

Rationale

CM-12(01) uses automated tools to find chosen types of information on system components and keep its location records current. SC-07(10) prevents the unauthorised transfer of information out of the system, the protective side of a data loss prevention tool.

Gaps

SP 800-53 scopes discovery to the organisation's own components. CIS extends it to data held at service providers. Feed what the tool finds into the data inventory.

Mapped Controls

CIS 3.14 Audit logging of access to sensitive data

Rationale

AU-02 lets the organisation choose reading, changing and deleting sensitive data as event types to log. AU-12 generates audit records for those events on the components that hold the data.

Gaps

CIS asks for a log of each access to sensitive data, changes and disposal included. Name those events in AU-02's list of event types to log.

Mapped Controls

CIS 4.1 Documented process for configuring assets and software securely

Rationale

CM-01 sets out the process in documented configuration management policy and procedures, and reviews them on a set cycle and after set events. CM-02 keeps a documented baseline configuration under configuration control. CM-06 applies the most restrictive workable settings from common secure configurations and records approved deviations.

Gaps

CIS asks for a review of the process at least once a year. Set that cycle in CM-01.

Mapped Controls

CIS 4.2 Documented process for configuring network devices securely

Rationale

CM-01 documents configuration management procedures that cover network devices as parts of the system, and reviews them on a set cycle. CM-02 keeps baseline configurations for network devices under configuration control. CM-06 sets hardened settings for those devices from common secure configurations.

Gaps

CIS asks for a review of the network device process at least once a year. Set that cycle in CM-01.

Mapped Controls

CIS 4.3 Screen lock after a period of inactivity

Rationale

AC-11 locks the device after a period of inactivity that the organisation sets. The lock holds until the user authenticates again, which protects a session left unattended.

Gaps

CIS caps the idle time at 15 minutes on general-purpose operating systems and 2 minutes on mobile devices. Set those limits in AC-11.

Mapped Controls

CIS 4.4 Host-based firewalls on servers

Rationale

SC-07(12) puts host-based boundary protection, such as a host firewall, on the system components the organisation names. Naming servers there gives each one its own firewall.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 4.5 Default-deny host firewalls for end-user devices

Rationale

SC-07(12) adds host-based firewalls to the components the organisation names, such as workstations and laptops. SC-07(05) denies network traffic by default and allows it by exception, which gives those firewalls their default-deny rule.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 4.6 Secure administration of assets and software

Rationale

CM-02 holds configurations under configuration control, for example as code kept in version control. CM-07 prohibits or restricts insecure protocols, such as Telnet and plain HTTP for administration. SC-08 protects management sessions in transit, and SC-08(01) does so with cryptography, as SSH and HTTPS do.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 4.7 Default accounts shipped with systems and software

Rationale

AC-02 sets which account types are allowed and disables or removes the others, vendor default accounts among them. IA-05 requires default passwords and other authenticators to be changed before first use, which leaves any default account still in place unusable as shipped.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 4.8 Removal of unneeded services and functions

Rationale

CM-07 configures each system to provide only the capabilities it needs. CM-07(01) reviews systems on a set cycle, finds unneeded services and functions, and disables or removes them.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 4.9 Trusted DNS resolvers for assets and network devices

Rationale

CM-06 makes the DNS resolver that each asset and network device uses a configuration setting, which the organisation chooses and enforces. SC-21 has resolvers check the origin and integrity of the DNS answers they receive, which is the protection a trusted DNS server gives.

Gaps

CIS asks the organisation to choose the DNS servers its assets and network devices use: its own or reputable public ones. Set that choice in CM-06.

Mapped Controls

CIS 4.10 Lockout after repeated failed sign-ins on portable devices

Rationale

AC-07 limits consecutive failed logon attempts and locks the account or device automatically once a user goes past the limit, which the organisation sets.

Gaps

CIS caps failed attempts at 20 on laptops and 10 on tablets and smartphones. Set those limits in AC-07.

Mapped Controls

CIS 4.11 Remote wipe of organisation data on portable devices

Rationale

MP-06(08) gives the organisation the means to purge or wipe information remotely from devices it chooses. Choosing the portable end-user devices the organisation owns brings them within reach of a remote wipe.

Gaps

CIS names the events that call for a wipe, such as a lost or stolen device or a person leaving the organisation. Set those events in MP-06(08).

Mapped Controls

CIS 4.12 Work and personal separation on mobile devices

Rationale

AC-19 sets configuration requirements for mobile devices, and AC-19(05) protects organisation data inside a container on them. SC-50 enforces separation and policy in software between security domains, here the work and personal profiles.

Gaps

CIS asks for a separate work profile on each mobile device that supports one, holding the organisation's apps and data apart from personal ones. Make that profile a configuration requirement under AC-19.

Mapped Controls

CIS 5.1 Register of every account in the organisation

Rationale

AC-02 defines the account types in use and specifies the authorised users, roles and privileges for each account. It assigns account managers and reviews accounts against requirements on a set cycle.

Gaps

CIS lists details to record, such as each holder's name, username, start and end dates and department. It also asks the organisation to confirm at least once a quarter that each active account is authorised. Record those details and set that cycle in AC-02.

Mapped Controls

CIS 5.2 Unique password for each asset, with minimum lengths

Rationale

IA-05 requires authenticators strong enough for their use. IA-05(01) sets password rules, such as a minimum length and screening against weak passwords. IA-05(18) supports password managers, which make a different password for every asset practical.

Gaps

CIS asks for a different password on every asset. It sets a minimum of 8 characters for accounts with multi-factor authentication and 14 for accounts that rely on a password alone. Add both rules to IA-05(01).

Mapped Controls

CIS 5.3 Deactivation of accounts after 45 days of inactivity

Rationale

AC-02(03) disables accounts that stay inactive for longer than a period the organisation sets, which takes dormant accounts out of use.

Gaps

CIS fixes the inactivity period at 45 days. Set that value in AC-02(03).

Mapped Controls

CIS 5.4 Separate accounts for administration and everyday work

Rationale

AC-06(05) restricts privileged accounts to the named roles that need them. AC-06(02) has privileged users sign in with a non-privileged account for everyday work, such as web browsing and email.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 5.5 Service account register with owner and purpose

Rationale

AC-02 treats service accounts as one of the account types it manages. Each one has an assigned account manager and comes up for review on a set cycle.

Gaps

CIS asks for a record of each service account's owning department, purpose and review date, and a review at least once a quarter. Record those details and set that cycle in AC-02.

Mapped Controls

CIS 5.6 Central directory for all accounts

Rationale

AC-02(01) manages accounts with automated mechanisms, such as a directory service. IA-13 uses identity providers to manage identities, their attributes and access rights in one place.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 6.1 Process for granting access when people join or change role

Rationale

AC-02 requires approval before an account is created and grants access only on a valid authorisation. PS-05 reviews a person's access when they move to a new role and adjusts it to fit.

Gaps

CIS prefers the granting process to be automated. Use AC-02(01) to automate account management where you can.

Mapped Controls

CIS 6.2 Process for revoking access when people leave or change role

Rationale

AC-02 disables or removes accounts and alerts account managers when users leave or move, in step with personnel processes. PS-04 disables system access and revokes credentials within a set time of termination. PS-05 adjusts access to match the new role when a person transfers.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 6.3 Multi-factor authentication for internet-facing applications

Rationale

IA-02(01) and (02) ask for multi-factor authentication on privileged and non-privileged accounts, which covers signing in to applications reachable from the internet. IA-02(10) provides single sign-on, which lets the organisation enforce it in one place.

Gaps

SP 800-53 sets multi-factor authentication by type of account. CIS sets it by exposure: every internet-facing application that supports it, a third party's included.

Mapped Controls

CIS 6.4 Multi-factor authentication for remote access to the network

Rationale

AC-17 sets connection requirements for each type of remote access and authorises each one before use. IA-02(01) and (02) ask for multi-factor authentication on privileged and non-privileged accounts, which covers remote connections. IA-02(06) adds the case where one factor comes from a separate device.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 6.5 Multi-factor authentication for administrator accounts

Rationale

IA-02(01) requires multi-factor authentication for all access to privileged accounts. Administrator accounts are privileged accounts, so it applies to every one of them.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 6.6 Register of authentication and authorisation systems

Rationale

CM-08 keeps an inventory of system components with their details and reviews it on a set cycle. Authentication and authorisation servers are system components, so they appear in it.

Gaps

CIS asks for a separate list of the systems that authenticate and authorise users, including those a service provider hosts. Keep that list yourself, starting from the CM-08 inventory.

Mapped Controls

CIS 6.7 Central access control through single sign-on

Rationale

IA-02(10) provides single sign-on for the accounts and services the organisation chooses. IA-13 uses identity providers and authorisation servers to manage access rights and make access decisions in one place.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 6.8 Role-based access rights with a yearly review

Rationale

AC-02 sets the conditions for role membership and the privileges each account holds. AC-03(07) enforces a role-based access control policy. AC-06(07) reviews privileges on a set cycle, confirms each is still needed and removes the rest.

Gaps

CIS asks for a review of privileges at least once a year. Set that cycle in AC-06(07).

Mapped Controls

CIS 7.1 Documented process for managing vulnerabilities

Rationale

RA-01 documents the risk assessment policy and procedures, which cover vulnerability scanning, and reviews them on a set cycle. RA-05 sets out how the organisation scans for vulnerabilities and fixes them within the response times it chooses. SI-02 finds and corrects flaws as part of configuration management.

Gaps

CIS asks for a review of the process at least once a year. Set that cycle in RA-01.

Mapped Controls

CIS 7.2 Risk-based plan for fixing vulnerabilities

Rationale

RA-05 sets response times for fixing confirmed vulnerabilities, based on the organisation's assessment of risk. SI-02 sets time frames for installing security updates. SI-02(03) measures how long fixes take against set benchmarks.

Gaps

CIS asks for a review of the remediation plan at least once a month. Set that cycle alongside the response times in RA-05.

Mapped Controls

CIS 7.3 Automated patching of operating systems

Rationale

SI-02 sets a time limit for installing security updates. SI-02(04) brings in automated patch management tools, and SI-02(05) installs updates automatically on the components the organisation names, operating systems included.

Gaps

CIS asks for operating systems to be patched at least once a month. Set that time limit in SI-02.

Mapped Controls

CIS 7.4 Automated patching of applications

Rationale

SI-02 sets a time limit for installing security updates, application updates among them. SI-02(04) brings in automated patch management tools, and SI-02(05) installs updates automatically on the applications the organisation names.

Gaps

CIS asks for applications to be patched at least once a month. Set that time limit in SI-02.

Mapped Controls

CIS 7.5 Vulnerability scanning of internal assets

Rationale

RA-05 runs vulnerability scans across the organisation's systems at a frequency it sets. RA-05(05) grants the scanning tools privileged access, so they can also run authenticated scans.

Gaps

CIS asks for scans of internal assets at least once a quarter. Set that frequency in RA-05.

Mapped Controls

CIS 7.6 Vulnerability scanning of internet-facing assets

Rationale

RA-05 scans systems and hosted applications for vulnerabilities at a frequency the organisation sets. Its scope includes the systems and applications that are reachable from the internet.

Gaps

CIS asks for scans of internet-facing assets at least once a month. Give those assets their own frequency in RA-05.

Mapped Controls

CIS 7.7 Fixes for detected software vulnerabilities

Rationale

RA-05 sets the response times within which the organisation fixes confirmed vulnerabilities, based on risk. SI-02 corrects software flaws and installs security updates within a period the organisation sets.

Gaps

CIS asks the organisation to fix detected vulnerabilities at least once a month. Match the response times in RA-05 and SI-02 to that cycle.

Mapped Controls

CIS 8.1 Documented process for managing audit logs

Rationale

AU-01 documents the audit and accountability policy and procedures and reviews them on a set cycle. AU-02 chooses which events to log and why, and reviews that choice. AU-06 decides how often audit records are reviewed and analysed. AU-11 sets how long they are retained.

Gaps

CIS asks for a review of the process at least once a year. Set that cycle in AU-01.

CIS 8.2 Audit logging turned on for every enterprise asset

Rationale

AU-02 specifies which types of event each system must log. AU-12 turns on the generation of audit records for those events, across the system components the organisation names.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 8.3 Enough storage capacity for audit logs

Rationale

AU-04 allocates storage capacity for audit logs, sized to the organisation's retention requirements. Each logging destination then has room to keep its records for the full period the organisation sets.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 8.4 Clock synchronisation with at least two time sources

Rationale

SC-45 keeps the clocks of system components in step. SC-45(01) sets them by an authoritative time source, and SC-45(02) adds a secondary source in another region as a fallback.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 8.5 Detailed audit records for assets holding sensitive data

Rationale

AU-03 sets what each audit record shows. That includes the type of event, when and where it happened, its source, its outcome and the identities involved. AU-03(01) adds further detail, such as network addresses. AU-12 generates records with that content on the components the organisation chooses, such as those holding sensitive data.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 8.6 Logging of DNS queries

Rationale

AU-02 lets the organisation choose DNS queries as a type of event to log. AU-12 then generates audit records for those queries on DNS resolvers and the other components the organisation chooses.

Gaps

CIS names DNS queries as an event to log, where an asset supports it. Add them to the event types you select in AU-02.

Mapped Controls

CIS 8.7 Logging of URL requests

Rationale

AU-02 lets the organisation choose URL requests as a type of event to log. AU-12 then generates audit records for those requests on web proxies and similar components.

Gaps

CIS names URL requests as an event to log, where an asset supports it. Add them to the event types you select in AU-02.

Mapped Controls

CIS 8.8 Logging of command-line activity

Rationale

AU-02 lets the organisation choose command-line activity, such as shell commands, as a type of event to log. AU-12 then generates audit records for it on hosts and on terminals used for remote administration.

Gaps

CIS names command-line activity as an event to log. Add it to the event types you select in AU-02, covering shells and remote administration sessions.

Mapped Controls

CIS 8.9 Central collection and storage of audit logs

Rationale

AU-04(01) moves audit logs off the systems that produce them into separate storage. AU-06(04) reviews and analyses records from many components in one central place, as a security information and event management (SIEM) tool does. AU-12(01) compiles those records into a single audit trail, correlated by time.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 8.10 Audit log retention for at least 90 days

Rationale

AU-11 keeps audit records for a period the organisation sets, in line with its records retention policy. The organisation can choose a period of 90 days or more.

Gaps

CIS asks the organisation to hold audit logs for at least 90 days. Set that period in AU-11.

Mapped Controls

CIS 8.11 Review of audit logs for unusual activity

Rationale

AU-06 reviews and analyses audit records at a frequency the organisation sets, looking for signs of unusual activity. It then reports the findings.

Gaps

CIS asks for a review at least once a week. Set that frequency in AU-06.

Mapped Controls

CIS 8.12 Audit logs from service providers

Rationale

AU-16 coordinates audit information with outside organisations when it crosses organisational boundaries. SA-09 requires providers to apply the organisation's security controls and lets it monitor their compliance, for example through the logs they supply.

Gaps

CIS gives examples of provider events to collect, such as sign-ins, user management and the creation or deletion of data. Name the event types you need in each provider agreement.

Mapped Controls

CIS 9.1 Latest supported versions of email clients and web browsers

Rationale

CM-07(05) lets only approved software run, which limits users to the browsers and email clients the organisation allows. SA-22 replaces software once its vendor stops supporting it. SI-02 installs security updates within a set time, which keeps browsers and email clients on current versions.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 9.2 DNS filtering on every end-user device

Rationale

SC-07 controls outbound traffic at managed interfaces, where a filter can refuse lookups of known malicious domains. SC-07(12) adds protection on each host, which carries that filtering to the device itself.

Gaps

CIS asks for DNS filtering on every end-user device, in the office or remote, to block domains known to be malicious. Enforce it on each device, so it keeps working away from the corporate network.

Mapped Controls

CIS 9.3 Network URL filtering for all enterprise assets

Rationale

AC-04 enforces policy on where information may flow, so filters can block websites by category or reputation. SC-07 controls web traffic at managed interfaces, and SC-07(08) sends it through authenticated proxies where the filters apply.

Gaps

CIS asks for regular updates to the filters. Refresh the block lists and categories on a set schedule.

Mapped Controls

CIS 9.4 Limits on add-ons for web browsers and email clients

Rationale

CM-07 limits software to the functions the organisation needs, which means removing or disabling unneeded add-ons. CM-11 sets rules on what users may install, extensions included, and enforces them.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 9.5 Email sender authentication with DMARC

Rationale

SC-08(01) uses cryptography to detect changes to messages in transit, which is what a DKIM signature does. SI-08 filters unwanted mail at its entry points, where receiving servers check a sender's SPF, DKIM and DMARC records.

Gaps

CIS asks the organisation to publish SPF, DKIM and a DMARC policy for its own domains, so that receivers can reject forged mail in its name. Publish them, and check them on inbound mail too.

Mapped Controls

CIS 9.6 File-type blocking at the email gateway

Rationale

AC-04 enforces policy on information flows by type of content, so the email gateway can refuse unneeded attachment types. SI-03 places malicious code protection at entry points such as mail servers, where risky files are stopped.

Gaps

CIS asks for unneeded file types to be blocked at the email gateway. Decide which types the organisation needs, and block the rest there.

Mapped Controls

CIS 9.7 Attachment scanning and sandboxing on mail servers

Rationale

SI-03 places malicious code protection at entry points such as mail servers, where it scans attachments as they arrive. SC-44 opens suspicious attachments in a detonation chamber, an isolated sandbox, to check them for malicious code.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 10.1 Malware protection on every enterprise asset

Rationale

SI-03 puts malicious code protection at system entry and exit points and on endpoints, where it detects and removes malware. It also keeps that protection running and up to date.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 10.2 Automatic updates to malware signatures

Rationale

SI-03 asks for malicious code protection that updates itself automatically as new releases appear. That keeps the signature files current on every asset the protection covers.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 10.3 Autorun and autoplay blocked on removable media

Rationale

CM-07 limits each system to the functions it needs and switches off the rest, such as running code automatically from inserted media. CM-07(02) prevents program execution under the organisation's rules, which can prohibit auto-execute features. MP-07 restricts how removable media are used on systems, through controls the organisation sets.

Gaps

CIS names autorun and autoplay as the features to switch off. Add both to the functions CM-07 prohibits, for all removable media.

Mapped Controls

CIS 10.4 Automatic malware scans of removable media

Rationale

SI-03 scans files from external sources in real time, as users open or run them on an endpoint. Removable media count among those external sources.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 10.5 Exploit mitigations turned on in systems and software

Rationale

SI-16 protects memory from unauthorised code execution, which is the job of data execution prevention and address space layout randomisation. SI-07 protects the integrity of system software, as operating system integrity protection does. SI-07(15) authenticates code before installation, as signed-app checks do.

Gaps

CIS treats exploit mitigations as one group, to switch on wherever an asset or application supports them. SP 800-53 splits them between SI-16 and SI-07. Choose which to use on each platform.

Mapped Controls

CIS 10.6 Central administration of anti-malware tools

Rationale

SI-03 provides the malicious code protection to be managed. PL-09 manages chosen controls from a central point. It took in central management of malicious code protection from SI-03(01), which NIST withdrew.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 10.7 Behaviour-based malware detection

Rationale

SI-03 lets the organisation choose non-signature-based mechanisms. SP 800-53 describes these as heuristics that detect malicious code by how it behaves, which is what behaviour-based anti-malware does.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 11.1 Documented backup and recovery process

Rationale

CP-01 asks for documented contingency planning policy and procedures, reviewed on a set cycle. CP-02 sets recovery objectives and restoration priorities in a contingency plan. CP-09 sets which user and system data to back up and how often, and protects the backups. CP-10 brings systems back to a known state within set times.

Gaps

CIS asks for a review of the documented process at least once a year. Set that cycle in CP-01 and CP-02.

CIS 11.2 Automatic backups at least once a week

Rationale

CP-09 backs up user-level and system-level information at regular intervals. The organisation chooses the interval to meet its recovery objectives.

Gaps

CIS asks for backups to run automatically, at least once a week, and more often for sensitive data. Automate them and set that frequency in CP-09.

Mapped Controls

CIS 11.3 Backups protected to the same standard as live data

Rationale

CP-09 protects the confidentiality, integrity and availability of backups, and CP-09(08) encrypts them. CP-06 asks for an alternate storage site with controls equal to the primary site's. Backups held there get the same protection as the original data.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 11.4 Isolated, versioned copy of backups

Rationale

CP-06 keeps backups at an alternate storage site, and CP-06(01) places that site apart from the primary site. CP-09(03) stores backups of critical information in a separate facility or fire-rated container, away from the live system.

Gaps

CIS's examples of an isolated copy use versioned backup destinations. Keep versioned copies in that isolated store, whether offline, in a cloud service or at another site.

Mapped Controls

CIS 11.5 Quarterly test restores from a sample of backups

Rationale

CP-04 tests the contingency plan on a set cycle, recovery included, and acts on the results. CP-09(01) tests backups for reliability and integrity. CP-09(02) uses a sample of backup information to restore chosen functions during plan testing.

Gaps

CIS asks for test restores at least once a quarter. Set that frequency in CP-04 and CP-09(01).

Mapped Controls

CIS 12.1 Network infrastructure on current, supported software

Rationale

SA-22 replaces network components and services once vendor support ends. SI-02 installs security-relevant software and firmware updates on network devices within a set time.

Gaps

CIS asks for a review of network software versions at least once a month, to confirm each is still supported. Run that review as part of SA-22.

Mapped Controls

CIS 12.2 Secure network design and segmentation

Rationale

PL-08 develops a security architecture, in step with the enterprise architecture, that shows how the organisation protects confidentiality, integrity and availability. SC-07 divides the network into subnetworks behind managed interfaces, arranged to fit that architecture.

Gaps

CIS asks for the network design itself to cover least privilege and availability. Write both into the network part of the PL-08 architecture.

Mapped Controls

CIS 12.3 Secure administration of network infrastructure

Rationale

CM-02 keeps a current baseline configuration of network devices under configuration control. Infrastructure as code held in version control is one way to do that. SC-08 protects management traffic in transit, and SC-08(01) encrypts it, as SSH and HTTPS do.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 12.4 Network architecture diagrams and documentation

Rationale

PL-02 asks for a system security plan that describes the system's components and its connections to other systems, reviewed on a set cycle. PL-08 documents the security architecture and updates it as the enterprise architecture changes.

Gaps

CIS centres the safeguard on diagrams of the network architecture. Draw them and keep them with the PL-02 plan and the PL-08 architecture.

Mapped Controls

CIS 12.5 Central network authentication, authorisation and accounting

Rationale

IA-13 uses central identity providers and authorisation servers to make authentication and authorisation decisions. AU-12(01) compiles audit records from network components into one system-wide trail, which covers accounting.

Gaps

CIS asks for authentication, authorisation and accounting on the network to run centrally. Connect network devices and network access controls to the IA-13 services, and send their accounting records to the AU-12(01) trail.

Mapped Controls

CIS 12.6 Secure protocols for network access and Wi-Fi

Rationale

IA-03 authenticates devices before they join the network, which is what 802.1X does. AC-18(01) protects wireless access with user or device authentication and encryption, as WPA2 Enterprise does. SC-08 protects the confidentiality and integrity of traffic in transit through secure protocols.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 12.7 Remote access through a managed VPN and central sign-in

Rationale

AC-17 sets usage rules for each type of remote access and authorises it before any connection. AC-17(02) encrypts remote sessions, as a VPN does, and AC-17(03) routes them through managed access control points. IA-02 authenticates organisational users through the organisation's sign-in services before they reach its resources.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 12.8 Separate, segmented machines for administration

Rationale

SC-02 separates system management functions from user functions, for example on separate computers. SC-07(15) routes privileged access through a dedicated managed interface, and SC-07(29) isolates chosen functions on their own subnetworks. SC-32(01) places privileged functions in separate physical domains.

Gaps

CIS asks for administrative machines to stay off the internet. Block their internet access with SC-07 boundary rules.

Mapped Controls

CIS 13.1 Central correlation and alerting for security events

Rationale

AU-06(03) correlates audit records held in different places, and AU-06(04) brings them together for central review and analysis. SI-04(02) analyses events in near real time with automated tools, such as a SIEM. SI-04(05) raises alerts on signs of compromise, and SI-04(16) correlates monitoring data across the system.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 13.2 Intrusion detection on hosts

Rationale

SI-04 sets up monitoring across the system. SI-04(23) adds host-based monitoring on the components the organisation chooses, which is the job a host intrusion detection tool does.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 13.3 Intrusion detection on the network

Rationale

SI-04 places monitoring devices at strategic points across the network to watch for attacks. SI-04(01) connects the individual intrusion detection tools into one system-wide intrusion detection system.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 13.4 Filtering traffic between internal network segments

Rationale

AC-04 enforces approved information flows within the system and between connected systems. SC-07 monitors and controls traffic at key internal interfaces, such as the points where network segments meet.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 13.5 Remote access based on device health

Rationale

AC-17 sets configuration and connection requirements for each type of remote access, and authorises each type before anyone uses it. IA-03(04) bases device authentication on attestation of the device's configuration and state, which comes from the configuration management process.

Gaps

CIS links how much access a device gets to its health: current anti-malware, a compliant configuration, and an up-to-date operating system and applications. Write these checks into AC-17's connection requirements, and confirm them through IA-03(04) attestation.

Mapped Controls

CIS 13.6 Network flow logs for review and alerting

Rationale

AU-12 generates records on network components for the events the organisation selects, such as flow records. SI-04 collects monitoring data from across the network, and SI-04(04) watches inbound and outbound traffic for unusual activity.

Gaps

CIS names the data to collect from network devices: flow logs, full traffic capture or both. Select that data as logged events in AU-12.

Mapped Controls

CIS 13.7 Intrusion prevention on hosts

Rationale

SI-04(23) puts host-based monitoring on the components the organisation chooses. SI-04(07) acts automatically to stop suspicious events as soon as that monitoring finds them, which is what an intrusion prevention tool does.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 13.8 Intrusion prevention on the network

Rationale

SC-07 controls communications at managed interfaces, where inline devices can block malicious traffic. SI-04(04) monitors traffic entering and leaving the system, and SI-04(07) acts automatically to stop suspicious events.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 13.9 Access control at network ports, such as 802.1X

Rationale

IA-03 identifies and authenticates devices before they make a local or network connection, as 802.1X does at each network port. IA-03(01) makes that authentication cryptographic and two-way, for example with certificates.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 13.10 Traffic filtering at the application layer

Rationale

AC-04 enforces the organisation's flow policy on the content passing between systems, and AC-04(08) applies policy filters to that content. SC-07(08) routes traffic through proxy servers at managed interfaces, and SC-07(17) enforces the expected protocol formats.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 13.11 Monthly tuning of security alert thresholds

Rationale

SI-04(13) profiles common traffic and event patterns, then uses those profiles to tune monitoring devices. SI-04 also adjusts the level of monitoring when risk changes.

Gaps

CIS asks the organisation to tune its alert thresholds every month or more often. Add that cycle to the tuning SI-04(13) describes.

Mapped Controls

CIS 14.1 Security awareness programme for the workforce

Rationale

AT-01 sets a documented policy and procedures for awareness and training, reviewed on a set cycle. AT-02 gives every user security literacy training when they join and at a set frequency after, and keeps the content up to date.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 14.2 Awareness of phishing and other social engineering

Rationale

AT-02 gives every user security literacy training. AT-02(03) adds a topic on social engineering and social mining, teaching users to recognise an attempt and report it.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 14.3 Password and multi-factor authentication training

Rationale

AT-02 trains every user in the actions that keep systems secure, on topics the organisation sets. The course can cover multi-factor authentication, passwords and the care of credentials.

Gaps

CIS makes good authentication practice a required training topic. Add it to the AT-02 course content.

Mapped Controls

CIS 14.4 Sensitive data handling and clear desk training

Rationale

AT-02 gives every user security literacy training on topics the organisation sets. Those topics can include the safe handling of sensitive data from storage to disposal, along with clear desk and clear screen habits.

Gaps

CIS makes data handling a required training topic, clear desks and disposal included. Add it to the AT-02 course content.

Mapped Controls

CIS 14.5 Training on how data leaks by accident

Rationale

AT-02 teaches every user the actions that protect information, on topics the organisation sets. The course can show the common ways data leaks by mistake, such as misdirected messages or lost devices.

Gaps

CIS makes accidental data exposure a required training topic. Include it in the AT-02 course content.

Mapped Controls

CIS 14.6 Incident spotting and reporting for all staff

Rationale

AT-02(04) teaches users to recognise suspicious messages and unusual system behaviour. IR-02 gives users incident response training matched to their role, which for most staff means spotting an incident and knowing whom to tell.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 14.7 Staff reporting of missing updates and tool failures

Rationale

AT-02 gives every user security literacy training on the actions that keep systems secure, with topics the organisation sets. The course can teach staff to check that their devices are up to date and to tell IT when a security tool fails.

Gaps

CIS makes missing updates and failed automated tools a required training topic, with staff telling IT about each failure. Add it to the AT-02 course content.

Mapped Controls

CIS 14.8 Training on insecure networks and home network setup

Rationale

AT-02 gives every user security literacy training on topics the organisation sets. The course can cover the risks of working over untrusted networks and how to set up a home network securely.

Gaps

CIS makes insecure networks a required training topic. Where staff work remotely, it adds guidance on securing their home networks. Include both in the AT-02 course content.

Mapped Controls

CIS 14.9 Security skills training matched to each role

Rationale

AT-03 gives security training to the roles the organisation names, shaped to the work each role does. It runs before people gain access or take up their duties, and on a set cycle after that.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 15.1 Register of service providers

Rationale

SA-09 names the people who oversee each external service, which gives every provider an internal contact. PM-30(01) identifies and ranks the suppliers of critical systems and services.

Gaps

CIS asks for a register of every known provider, with its classification and an internal contact, reviewed every year. Keep that register yourself, starting from SA-09's oversight roles.

Mapped Controls

CIS 15.2 Policy for managing service providers

Rationale

SA-01 and SR-01 set documented policies and procedures for acquisition and for supply chain risk management, each reviewed on a set cycle. The acquisition policy in SA-01 covers the external services the organisation buys.

Gaps

CIS asks the policy to cover each stage of working with a provider, from classification and inventory through assessment and monitoring to decommissioning. Write those stages into the SA-01 and SR-01 policies.

Mapped Controls

CIS 15.3 Classification of service providers

Rationale

PM-30(01) identifies the suppliers of critical systems and services and ranks them by priority. RA-03(01) assesses supply chain risk for systems and services and updates it as conditions change, which gives each provider a risk rating.

Gaps

CIS asks for a classification scheme with factors such as data sensitivity, availability needs, regulation and risk. Define that scheme and classify each provider with it, drawing on the RA-03(01) risk ratings.

Mapped Controls

CIS 15.4 Security terms in contracts with service providers

Rationale

SA-04 writes security requirements, and who is responsible for them, into acquisition contracts. SA-09 requires external service providers to meet the organisation's security requirements and to use the controls it names. SR-08 sets up agreements under which suppliers report compromises and share assessment results.

Gaps

CIS asks for a yearly review of each provider contract to find missing security terms. Add that review, checking each contract against the SA-04 and SA-09 requirements.

Mapped Controls

CIS 15.5 Assessment of service providers

Rationale

SA-09(01) assesses the risk before the organisation outsources a security service. SA-09 monitors each provider's compliance with the required controls on an ongoing basis. SR-06 assesses and reviews suppliers and the risks they bring on a set cycle.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 15.6 Ongoing monitoring of service providers

Rationale

SA-09 tracks each provider's compliance with the required controls on an ongoing basis, using methods the organisation chooses. SR-06 reassesses each supplier's risk on a set cycle.

Gaps

CIS names sources to watch, such as the provider's release notes and the dark web. Add them to the methods SA-09 uses to monitor providers.

Mapped Controls

CIS 15.7 Secure exit from a service provider

Rationale

AC-02 disables or removes accounts at the end of their use, including the user and service accounts linked to the provider. SR-12 disposes of the organisation's data and components by set methods, which can include data held on a provider's systems.

Gaps

CIS treats leaving a provider as one process. Write an exit procedure for each provider that brings the account steps in AC-02 and the disposal steps in SR-12 together.

Mapped Controls

CIS 16.1 Secure development process for applications

Rationale

SA-03 runs development under a life cycle that builds in security and assigns security roles. SA-15 asks for a documented development process that addresses security and names its standards and tools, with a review on a set cycle. SA-11 plans security testing and carries it out throughout development.

Gaps

CIS also makes developer training and checks on third-party code part of the process. Add both to the process that SA-15 documents.

Mapped Controls

CIS 16.2 Intake and handling of reported software vulnerabilities

Rationale

RA-05(11) gives outside parties a public channel to report vulnerabilities. SA-10 has the developer track security flaws through to resolution and report what it finds. SI-02 identifies and corrects flaws, and SI-02(03) measures the time each fix takes against set benchmarks.

Gaps

CIS asks for a severity rating on each tracked vulnerability and a handling policy published for outside reporters. Rate each one in the tracking system and publish the policy.

Mapped Controls

CIS 16.3 Root cause analysis of vulnerabilities in code

Rationale

SI-02(07) asks the organisation to analyse the root causes of flaws and act to remove them. It then checks that those actions dealt with the cause.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 16.4 Software bill of materials for third-party components

Rationale

CM-08 keeps an inventory of system components, at a level of detail that can include the third-party libraries built into the software. SR-04 documents where each component comes from and tracks its changes, which is what a software bill of materials records. SA-22 checks that each component still has support and replaces those whose support has ended.

Gaps

CIS asks the bill of materials to record the risk each component poses and to include components planned for future use. Review it at least monthly, and set that cycle in CM-08.

Mapped Controls

CIS 16.5 Current third-party libraries from trusted sources

Rationale

SI-02 applies security updates, which keeps third-party components current. SR-04 tracks where each component comes from, and SR-04(03) checks that it is genuine and unaltered. SR-05(02) assesses each component before the organisation takes it on or updates it.

Gaps

CIS asks the organisation to prefer mature libraries and frameworks with a proven security record. Add that preference to the checks SR-05(02) makes before selection.

Mapped Controls

CIS 16.6 Severity scale and release threshold for application flaws

Rationale

RA-05 scores the impact of each vulnerability with a standard measure and fixes vulnerabilities in order of risk. SA-15(01) sets quality metrics that each release must meet, and these can include a security threshold.

Gaps

CIS asks for a minimum security level that code must reach before release. Set it among the SA-15(01) quality metrics, and review the rating system every year.

Mapped Controls

CIS 16.7 Hardened baselines for application infrastructure

Rationale

CM-06 applies settings from common secure configurations, such as industry benchmarks, to servers, databases and similar components. It chooses the most restrictive settings that operations allow. CM-02 keeps those hardened settings as controlled baselines.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 16.8 Production separated from non-production environments

Rationale

CM-02(06) manages development and test baselines separately from the production baseline. CM-04(01) tests changes in a physically or logically separate environment before they reach production.

Gaps

CIS asks for a standing separation between production and every non-production environment. Apply it to all non-production work, beyond the testing of changes.

Mapped Controls

CIS 16.9 Secure coding training for developers

Rationale

AT-03 provides role-based security training on a set cycle. For developers, that means training in secure coding for the work they do.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 16.10 Security principles built into application design

Rationale

SA-08 applies security design principles, among them least privilege in SA-08(14), mediated access in SA-08(05) and secure defaults in SA-08(23). SI-10 checks each input for validity, such as its size and format. CM-07 limits each component to the ports and services it needs, which shrinks the attack surface.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 16.11 Proven modules for security functions in applications

Rationale

IA-13 relies on established identity providers and authorisation servers to handle identity and access. SC-13 uses the approved type of cryptography for each purpose, which keeps the application on accepted algorithms.

Gaps

CIS also asks for audit logging and other security functions to come from vetted platform modules. Build them on the features the platform already provides.

Mapped Controls

CIS 16.12 Static and dynamic analysis of application code

Rationale

SA-11(01) has developers run static code analysis during development and record the results. SA-11(08) adds dynamic code analysis, which tests the code as it runs.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 16.13 Manual penetration testing of applications

Rationale

CA-08 runs penetration tests on chosen systems, applications among them, at a set frequency. SA-11(05) has developers penetration test their own software at a depth the organisation sets.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 16.14 Threat modelling of application designs

Rationale

SA-11(02) has the developer carry out threat modelling during development. It pairs the threat model with an analysis of the system's vulnerabilities.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 17.1 Named incident handling lead and backup

Rationale

IR-08 asks for an incident response plan that assigns responsibility for incident response to named people or roles. That plan is where the organisation names who manages incident handling.

Gaps

CIS asks for a lead and one or more backups, plus an internal overseer whenever a service provider handles incidents. Name them in the IR-08 plan and review the choice every year.

Mapped Controls

CIS 17.2 Contact list for incident notification

Rationale

IR-06 reports incident information to the authorities the organisation names. That needs their contact details to hand. IR-08 asks for a plan that covers how incident information is shared and goes to named contacts.

Gaps

CIS asks for a contact list of the parties to inform, such as service providers, insurers, regulators and law enforcement. Keep it with the IR-08 plan and check each entry every year.

Mapped Controls

CIS 17.3 Incident reporting process for all staff

Rationale

IR-06 has staff report suspected incidents to the incident response team within a time the organisation sets. IR-01 puts the incident response procedures in writing and reviews them on a set cycle.

Gaps

CIS asks the process to state the minimum details each report must contain. Publish the process where the whole workforce can find it.

Mapped Controls

CIS 17.4 Documented process for responding to incidents

Rationale

IR-01 sets an incident response policy and procedures that cover roles and compliance, and reviews them on a set cycle. IR-08 adds an approved plan that sets out who does what and how information is shared, and keeps it up to date.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 17.5 Incident response roles across business functions

Rationale

IR-08 asks for a plan that describes how the incident response capability is organised. The plan assigns each responsibility to named people or roles.

Gaps

CIS lists the business functions to involve, such as legal, human resources, public relations and facilities. Give each of them a role in the IR-08 plan.

Mapped Controls

CIS 17.6 Primary and backup channels for incident communication

Rationale

IR-08 asks the incident response plan to cover how incident information is shared. SC-47 sets up alternate communication paths, so command and control carry on when an incident disrupts the usual ones.

Gaps

CIS asks the organisation to choose a primary and a secondary means of communication for incidents. Name both in the IR-08 plan and review them every year.

Mapped Controls

CIS 17.7 Incident response drills and simulations

Rationale

IR-03 tests the incident response capability on a set cycle. IR-02(01) adds simulated events to incident response training, so staff practise their response.

Gaps

CIS asks for an exercise at least once a year. Set that frequency in IR-03.

Mapped Controls

CIS 17.8 Lessons learned after each incident

Rationale

IR-04 feeds the lessons from each incident into the organisation's procedures, training and testing. It then makes the changes those lessons call for.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 17.9 Criteria that separate events from incidents

Rationale

IR-08 asks the incident response plan to define which incidents the organisation must report. That gives a starting point for separating events from incidents.

Gaps

CIS asks for written thresholds that tell a security event apart from an incident. Set them in the IR-08 plan and review them every year.

Mapped Controls

CIS 18.1 Penetration testing programme with defined scope and limits

Rationale

CA-08 sets how often penetration tests run and what they cover, and CA-08(03) adds tests of physical facilities. CA-02 plans each assessment with its scope, procedures and roles, much as rules of engagement do for a penetration test.

Gaps

CIS also asks the programme to set limits, such as attack types the testers must avoid, and to state what retrospectives it requires. Add both to the CA-02 assessment plan.

Mapped Controls

CIS 18.2 External penetration testing by specialists

Rationale

CA-08 runs penetration tests on a set cycle, and CA-08(01) has an independent tester or team carry them out. RA-05(04) finds what an attacker could discover about the system, which covers the reconnaissance step.

Gaps

CIS asks for an external test at least once a year. Set that frequency in CA-08.

Mapped Controls

CIS 18.3 Prioritised fixes for penetration test results

Rationale

CA-05 keeps a plan of action and milestones for the weaknesses that assessments find, and updates it as the fixes go in. RA-07 decides how to respond to each finding according to the organisation's risk tolerance.

Gaps

SP 800-53 states this more generally than CIS. Check the controls against CIS's wording.

Mapped Controls

CIS 18.4 Defence review and detection tuning after penetration tests

Rationale

CA-02 assesses whether controls work as intended, detective controls included. SI-04 adjusts monitoring as risk changes, and SI-04(09) tests the intrusion monitoring tools, so the organisation can tune detection after a test.

Gaps

CIS asks the organisation to tune its detection rules after each test, where needed, so they catch the techniques the testers used. Add that step to every penetration test.

Mapped Controls

CIS 18.5 Internal penetration testing

Rationale

CA-08 runs penetration tests on the systems the organisation chooses, internal ones among them. It also sets how often those tests take place.

Gaps

CIS asks for an internal test at least once a year. Set that frequency in CA-08.

Mapped Controls

Methodology and Disclaimer

This coverage analysis maps from CIS Controls v8.1.2 clauses/requirements back to NIST SP 800-53 Rev 5 controls, assessing how well the SP 800-53 control set addresses each framework requirement.

Coverage weighting represents an informed estimate based on control-objective alignment, not a definitive compliance determination. Weightings consider whether SP 800-53 controls address the intent of each framework requirement, even where terminology and structure differ.

This analysis should be validated by qualified assessors for use in compliance or audit activities. The authoritative source for any compliance determination is always the framework itself.