This document contains mappings of the CIS Critical Security Controls (CIS Controls) and CIS Safeguards t

Technology (NIST) Cybersecurity Framework (CSF) v2.0

Contact Information
CIS
31 Tech Valley Drive
East Greenbush, NY 12061
518.266.3460
controlsinfo@cisecurity.org

Editors
Thomas Sager
License for Use

This work is licensed under a Creative Commons Attribution-Non Commercial-No Derivatives 4.0 International Publi
nc-nd/4.0/legalcode

To further clarify the Creative Commons license related to the CIS ControlsTM content, you are authorized to copy a
organization and outside of your organization for non-commercial purposes only, provided that (i) appropriate credit
remix, transform or build upon the CIS Controls, you may not distribute the modified materials. Users of the CIS Con
(http://www.cisecurity.org/controls/) when referring to the CIS Controls in order to ensure that users are employing th
the prior approval of CIS® (Center for Internet Security, Inc.).
es 4.0 International Public License (the link can be found at https://creativecommons.org/licenses/by-

are authorized to copy and redistribute the content as a framework for use by you, within your
hat (i) appropriate credit is given to CIS, and (ii) a link to the license is provided. Additionally, if you
als. Users of the CIS Controls framework are also required to refer to
at users are employing the most up-to-date guidance. Commercial use of the CIS Controls is subject to
Mapping Methodology
Mapping Methodology

This page describes the methodology used to map the CIS Critical Security Controls to NIST Cybersecurit
Reference link for NIST CSF v2.0
https://www.nist.gov/cyberframework
The methodology used to create the mapping can be useful to anyone attempting to understand the relatio
The overall goal for CIS mappings is to be as specific as possible, leaning towards under-mapping versus
The general strategy used is to identify all of the aspects within a control and attempt to discern if both item

CIS Control 6.1 - Establish an Access Granting Process

Establish and follow a process, preferably automated, for granting access to enterprise assets upon new h

For a defensive mitigation to map to this CIS Safeguard it must have at least one of the following:
• A clearly documented process, covering both new employees and changes in access.
• All relevant enteprise access control must be covered under this process, there can be no seperation whe
• Automated tools are ideally used, such as a SSO provider or routing access control through a directory s
• The same process is followed every time a user's rights change, so a user never amasses greater rights

If the two concepts are effectively equal, they are mapped with the relationship "equivalent". If they are not
The relationships can be further analyzed to understand how similar or different the two defensive mitigatio
The relationship column will contain one of four possible values:
• Equivalent: The defensive mitigation contains the exact same security concept as the CIS Control.
• Superset: The CIS Control is partially or mostly related to the defensive mitigation in question, but the CIS
• Subset: The CIS Safeguard is partially or mostly related, yet is still subsumed within the defensive mitigat
• No relationship: This will be represented by a blank cell.

The relationships should be read from left to right, like a sentence. CIS Safeguard X is Equivalent to this <
Examples:
CIS Safeguard 16.8 "Separate Production and Non-Production Systems" is EQUIVALENT to NIST CSF PR
CIS Safeguard 3.5 "Securely Dispose of Data" is a SUBSET of NIST CSF PR.DS-3 "Assets are formally m

The CIS Controls are written with certain principles in mind, such as only having one ask per Safeguard. T
can often be "Subset."
Mappings are available from a variety of sources online, and different individuals may make their own deci
other mapping.
If you have comments, questions, or would like to report an error, please join the CIS Controls Mappings c
https://workbench.cisecurity.org/communities/94
Remember to download the CIS Controls Version 8 Guide where you can learn more about:

- This Version of the CIS Controls

- The CIS Controls Ecosystem ("It's not about the list')
- How to Get Started
- Using or Transitioning from Prior Versions of the CIS Controls
- Structure of the CIS Controls
- Implementation Groups
- Why is this Controls critical
- Procedures and tools
https://www.cisecurity.org/controls/v8/

A free tool with a dynamic list of the CIS Safeguards that can be filtered by Implemtation Groups and
mappings to multiple frameworks.
https://www.cisecurity.org/controls/v8/

Join our community where you can discuss the CIS Controls with our global army of experts and
voluneers!
https://workbench.cisecurity.org/dashboard
 CIS
CIS Safeguard Title
Control
1 Inventory and Control of Enterprise Assets

Actively manage (inventory, track, and correct) all enterprise as

mobile; network devices; non-computing/Internet of Things (Io
infrastructure physically, virtually, remotely, and those within c
totality of assets that need to be monitored and protected withi
identifying unauthorized and unmanaged assets to remove or r

Establish and Maintain Detailed

1 1.1
Enterprise Asset Inventory

Establish and Maintain Detailed

1 1.1
Enterprise Asset Inventory

1 1.2 Address Unauthorized Assets

1 1.3 Utilize an Active Discovery Tool

Use Dynamic Host

Configuration Protocol (DHCP)
1 1.4
Logging to Update Enterprise
Asset Inventory
 Use a Passive Asset Discovery
1 1.5
Tool

2 Inventory and Control of Software Assets

Actively manage (inventory, track, and correct) all software (op
network so that only authorized software is installed and can e
software is found and prevented from installation or execution.

Establish and Maintain a

2 2.1
Software Inventory

Ensure Authorized Software is

2 2.2
Currently Supported

2 2.3 Address Unauthorized Software

Utilize Automated Software

2 2.4
Inventory Tools

2 2.5 Allowlist Authorized Software

2 2.6 Allowlist Authorized Libraries

2 2.7 Allowlist Authorized Scripts

3 Data Protection

Develop processes and technical controls to identify, classify,

 Establish and Maintain a Data
3 3.1
Management Process

Establish and Maintain a Data

3 3.2
Inventory

Configure Data Access Control

3 3.3
Lists

3 3.4 Enforce Data Retention

3 3.5 Securely Dispose of Data

Encrypt Data on End-User

3 3.6
Devices

Establish and Maintain a Data

3 3.7
Classification Scheme

3 3.8 Document Data Flows

Encrypt Data on Removable

3 3.9
Media
Encrypt Sensitive Data in
3 3.10
Transit

3 3.11 Encrypt Sensitive Data at Rest

Segment Data Processing and

3 3.12
Storage Based on Sensitivity

Deploy a Data Loss Prevention

3 3.13
Solution
3 3.14 Log Sensitive Data Access
4 Secure Configuration of Enterprise Assets and Software
Establish and maintain the secure configuration of enterprise a
mobile; network devices; non-computing/IoT devices; and serv
applications).

Establish and Maintain a

4 4.1
Secure Configuration Process

Establish and Maintain a

4 4.2 Secure Configuration Process
for Network Infrastructure

Configure Automatic Session

4 4.3
Locking on Enterprise Assets

Implement and Manage a

4 4.4
Firewall on Servers

Implement and Manage a

4 4.5
Firewall on End-User Devices

Securely Manage Enterprise

4 4.6
Assets and Software

Manage Default Accounts on

4 4.7
Enterprise Assets and Software

Uninstall or Disable
4 4.8 Unnecessary Services on
Enterprise Assets and Software

Configure Trusted DNS Servers

4 4.9
on Enterprise Assets
 Enforce Automatic Device
4 4.10 Lockout on Portable End-User
Devices

Enforce Remote Wipe

4 4.11 Capability on Portable End-User
Devices

Separate Enterprise
4 4.12 Workspaces on Mobile End-
User Devices

5 Account Management

Use processes and tools to assign and manage authorization t

administrator accounts, as well as service accounts, to enterpr

Establish and Maintain an

5 5.1
Inventory of Accounts

5 5.2 Use Unique Passwords

5 5.3 Disable Dormant Accounts

Restrict Administrator Privileges

5 5.4 to Dedicated Administrator
Accounts

Establish and Maintain an

5 5.5
Inventory of Service Accounts

Centralize Account
5 5.6
Management
6 Access Control Management
Use processes and tools to create, assign, manage, and revoke
administrator, and service accounts for enterprise assets and s
Establish an Access Granting
6 6.1
Process
 Establish an Access Revoking
6 6.2
Process

Require MFA for Externally-

6 6.3
Exposed Applications

Require MFA for Remote

6 6.4
Network Access
Require MFA for Administrative
6 6.5
Access
Establish and Maintain an
6 6.6 Inventory of Authentication and
Authorization Systems

6 6.7 Centralize Access Control

Define and Maintain Role-

6 6.8
Based Access Control

7 Continuous Vulnerability Management

Develop a plan to continuously assess and track vulnerabilities
infrastructure, in order to remediate, and minimize, the window
private industry sources for new threat and vulnerability inform

Establish and Maintain a

7 7.1 Vulnerability Management
Process

Establish and Maintain a

7 7.2
Remediation Process

Perform Automated Operating

7 7.3
System Patch Management
Perform Automated Application
7 7.4
Patch Management
Perform Automated
7 7.5 Vulnerability Scans of Internal
Enterprise Assets
 Perform Automated
Vulnerability Scans of
7 7.6
Externally-Exposed Enterprise
Assets
Remediate Detected
7 7.7
Vulnerabilities
8 Audit Log Management

Collect, alert, review, and retain audit logs of events that could
attack.

Establish and Maintain an Audit

8 8.1
Log Management Process

8 8.2 Collect Audit Logs

Ensure Adequate Audit Log

8 8.3
Storage
Standardize Time
8 8.4
Synchronization

8 8.5 Collect Detailed Audit Logs

8 8.6 Collect DNS Query Audit Logs

Collect URL Request Audit
8 8.7
Logs
Collect Command-Line Audit
8 8.8
Logs

8 8.9 Centralize Audit Logs

8 8.10 Retain Audit Logs

8 8.11 Conduct Audit Log Reviews

8 8.12 Collect Service Provider Logs

9 Email and Web Browser Protections

Improve protections and detections of threats from email and w

attackers to manipulate human behavior through direct engage
 Ensure Use of Only Fully
9 9.1 Supported Browsers and Email
Clients

9 9.2 Use DNS Filtering Services

Maintain and Enforce Network-

9 9.3
Based URL Filters

Restrict Unnecessary or
9 9.4 Unauthorized Browser and
Email Client Extensions

9 9.5 Implement DMARC

9 9.6 Block Unnecessary File Types

Deploy and Maintain Email
9 9.7 Server Anti-Malware
Protections
10 Malware Defenses

Prevent or control the installation, spread, and execution of ma

enterprise assets.

Deploy and Maintain Anti-

10 10.1
Malware Software

Configure Automatic Anti-

10 10.2
Malware Signature Updates
Disable Autorun and Autoplay
10 10.3
for Removable Media
Configure Automatic Anti-
10 10.4 Malware Scanning of
Removable Media

Enable Anti-Exploitation
10 10.5
Features

Centrally Manage Anti-Malware

10 10.6
Software
Use Behavior-Based Anti-
10 10.7
Malware Software
11 Data Recovery
 Establish and maintain data recovery practices sufficient to res
and trusted state.

Establish and Maintain a Data

11 11.1
Recovery Process

11 11.2 Perform Automated Backups

11 11.3 Protect Recovery Data

Establish and Maintain an

11 11.4 Isolated Instance of Recovery
Data

11 11.5 Test Data Recovery

11 11.5 Test Data Recovery

Network Infrastructure
12
Management

Establish, implement, and actively manage (track, report, corre

attackers from exploiting vulnerable network services and acce

Ensure Network Infrastructure is

12 12.1
Up-to-Date

Establish and Maintain a

12 12.2
Secure Network Architecture

Securely Manage Network

12 12.3
Infrastructure

Establish and Maintain

12 12.4
Architecture Diagram(s)

Centralize Network
12 12.5 Authentication, Authorization,
and Auditing (AAA)

Use of Secure Network

12 12.6 Management and
Communication Protocols
 Ensure Remote Devices Utilize
a VPN and are Connecting to
12 12.7
an Enterprise’s AAA
Infrastructure
Establish and Maintain
Dedicated Computing
12 12.8
Resources for All Administrative
Work

Network Monitoring and

13
Defense

Operate processes and tooling to establish and maintain comp

against security threats across the enterprise’s network infrast

Centralize Security Event

13 13.1
Alerting

Deploy a Host-Based Intrusion

13 13.2
Detection Solution

Deploy a Network Intrusion

13 13.3
Detection Solution

Perform Traffic Filtering

13 13.4
Between Network Segments

Manage Access Control for

13 13.5
Remote Assets

Collect Network Traffic Flow

13 13.6
Logs

Deploy a Host-Based Intrusion

13 13.7
Prevention Solution

Deploy a Network Intrusion

13 13.8
Prevention Solution

Deploy Port-Level Access

13 13.9
Control

Perform Application Layer

13 13.10
Filtering
 Tune Security Event Alerting
13 13.11
Thresholds
14 Security Awareness and Skills Training

Establish and maintain a security awareness program to influe

conscious and properly skilled to reduce cybersecurity risks to

Establish and Maintain a

14 14.1
Security Awareness Program

Establish and Maintain a

14 14.1
Security Awareness Program

Train Workforce Members to

14 14.2 Recognize Social Engineering
Attacks
Train Workforce Members on
14 14.3
Authentication Best Practices

Train Workforce on Data

14 14.4
Handling Best Practices

Train Workforce Members on

14 14.5 Causes of Unintentional Data
Exposure

Train Workforce Members on

14 14.6 Recognizing and Reporting
Security Incidents

Train Workforce on How to

Identify and Report if Their
14 14.7
Enterprise Assets are Missing
Security Updates
 Train Workforce on the Dangers
of Connecting to and
14 14.8
Transmitting Enterprise Data
Over Insecure Networks

Conduct Role-Specific Security

14 14.9
Awareness and Skills Training

Conduct Role-Specific Security

14 14.9
Awareness and Skills Training

15 Service Provider Management

Develop a process to evaluate service providers who hold sens
critical IT platforms or processes, to ensure these providers ar
appropriately.

Establish and Maintain an

15 15.1
Inventory of Service Providers

Establish and Maintain an

15 15.1
Inventory of Service Providers

Establish and Maintain a

15 15.2 Service Provider Management
Policy

Establish and Maintain a

15 15.2 Service Provider Management
Policy

15 15.3 Classify Service Providers

 Ensure Service Provider
15 15.4 Contracts Include Security
Requirements

Ensure Service Provider

15 15.4 Contracts Include Security
Requirements

Ensure Service Provider

15 15.4 Contracts Include Security
Requirements

15 15.5 Assess Service Providers

15 15.6 Monitor Service Providers

15 15.6 Monitor Service Providers

15 15.6 Monitor Service Providers

Securely Decommission
15 15.7
Service Providers

16 Application Software Security

 Manage the security life cycle of in-house developed, hosted, o
remediate security weaknesses before they can impact the ent

Establish and Maintain a

16 16.1 Secure Application
Development Process

Establish and Maintain a

16 16.2 Process to Accept and Address
Software Vulnerabilities

Perform Root Cause Analysis

16 16.3
on Security Vulnerabilities

Establish and Manage an

16 16.4 Inventory of Third-Party
Software Components

Use Up-to-Date and Trusted

16 16.5 Third-Party Software
Components

Establish and Maintain a

Severity Rating System and
16 16.6
Process for Application
Vulnerabilities
 Use Standard Hardening
16 16.7 Configuration Templates for
Application Infrastructure

Separate Production and Non-

16 16.8
Production Systems

Train Developers in Application

16 16.9 Security Concepts and Secure
Coding

Apply Secure Design Principles

16 16.10
in Application Architectures

Leverage Vetted Modules or

16 16.11 Services for Application
Security Components

Implement Code-Level Security

16 16.12
Checks

Conduct Application Penetration

16 16.13
Testing
16 16.14 Conduct Threat Modeling

17 Incident Response Management

Establish a program to develop and maintain an incident respo
defined roles, training, and communications) to prepare, detect

Designate Personnel to Manage

17 17.1
Incident Handling

Establish and Maintain Contact

17 17.2 Information for Reporting
Security Incidents

Establish and Maintain Contact

17 17.2 Information for Reporting
Security Incidents

Establish and Maintain Contact

17 17.2 Information for Reporting
Security Incidents

Establish and Maintain an

17 17.3 Enterprise Process for
Reporting Incidents

Establish and Maintain an

17 17.4
Incident Response Process
 Assign Key Roles and
17 17.5
Responsibilities

Define Mechanisms for

17 17.6 Communicating During Incident
Response

Conduct Routine Incident

17 17.7
Response Exercises

17 17.8 Conduct Post-Incident Reviews

Establish and Maintain Security

17 17.9
Incident Thresholds

18 Penetration Testing

Test the effectiveness and resiliency of enterprise assets throu

controls (people, processes, and technology), and simulating t

Establish and Maintain a

18 18.1
Penetration Testing Program

Perform Periodic External

18 18.2
Penetration Tests

Remediate Penetration Test

18 18.3
Findings

18 18.4 Validate Security Measures

 Perform Periodic Internal
18 18.5
Penetration Tests
 Description

l of Enterprise Assets

entory, track, and correct) all enterprise assets (end-user devices, including portable and
ces; non-computing/Internet of Things (IoT) devices; and servers) connected to the
ally, virtually, remotely, and those within cloud environments, to accurately know the
need to be monitored and protected within the enterprise. This will also support
zed and unmanaged assets to remove or remediate.

Establish and maintain an accurate, detailed, and up-to-date inventory of all enterprise
assets with the potential to store or process data, to include: end-user devices
(including portable and mobile), network devices, non-computing/IoT devices, and
servers. Ensure the inventory records the network address (if static), hardware
address, machine name, enterprise asset owner, department for each asset, and
whether the asset has been approved to connect to the network. For mobile end-user
devices, MDM type tools can support this process, where appropriate. This inventory
includes assets connected to the infrastructure physically, virtually, remotely, and those
within cloud environments. Additionally, it includes assets that are regularly connected
to the enterprise’s network infrastructure, even if they are not under control of the
enterprise. Review and update the inventory of all enterprise assets bi-annually, or
more frequently.

Establish and maintain an accurate, detailed, and up-to-date inventory of all enterprise
assets with the potential to store or process data, to include: end-user devices
(including portable and mobile), network devices, non-computing/IoT devices, and
servers. Ensure the inventory records the network address (if static), hardware
address, machine name, enterprise asset owner, department for each asset, and
whether the asset has been approved to connect to the network. For mobile end-user
devices, MDM type tools can support this process, where appropriate. This inventory
includes assets connected to the infrastructure physically, virtually, remotely, and those
within cloud environments. Additionally, it includes assets that are regularly connected
to the enterprise’s network infrastructure, even if they are not under control of the
enterprise. Review and update the inventory of all enterprise assets bi-annually, or
more frequently.

Ensure that a process exists to address unauthorized assets on a weekly basis. The
enterprise may choose to remove the asset from the network, deny the asset from
connecting remotely to the network, or quarantine the asset.
Utilize an active discovery tool to identify assets connected to the enterprise’s network.
Configure the active discovery tool to execute daily, or more frequently.

Use DHCP logging on all DHCP servers or Internet Protocol (IP) address management
tools to update the enterprise’s asset inventory. Review and use logs to update the
enterprise’s asset inventory weekly, or more frequently.
 Use a passive discovery tool to identify assets connected to the enterprise’s network.
Review and use scans to update the enterprise’s asset inventory at least weekly, or
more frequently.
l of Software Assets
entory, track, and correct) all software (operating systems and applications) on the
authorized software is installed and can execute, and that unauthorized and unmanaged
d prevented from installation or execution.

Establish and maintain a detailed inventory of all licensed software installed on

enterprise assets. The software inventory must document the title, publisher, initial
install/use date, and business purpose for each entry; where appropriate, include the
Uniform Resource Locator (URL), app store(s), version(s), deployment mechanism,
and decommission date. Review and update the software inventory bi-annually, or
more frequently.

Ensure that only currently supported software is designated as authorized in the

software inventory for enterprise assets. If software is unsupported, yet necessary for
the fulfillment of the enterprise’s mission, document an exception detailing mitigating
controls and residual risk acceptance. For any unsupported software without an
exception documentation, designate as unauthorized. Review the software list to verify
software support at least monthly, or more frequently.

Ensure that unauthorized software is either removed from use on enterprise assets or
receives a documented exception. Review monthly, or more frequently.
Utilize software inventory tools, when possible, throughout the enterprise to automate
the discovery and documentation of installed software.
Use technical controls, such as application allowlisting, to ensure that only authorized
software can execute or be accessed. Reassess bi-annually, or more frequently.
Use technical controls to ensure that only authorized software libraries, such as
specific .dll, .ocx, .so, etc., files, are allowed to load into a system process. Block
unauthorized libraries from loading into a system process. Reassess bi-annually, or
more frequently.
Use technical controls, such as digital signatures and version control, to ensure that
only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute.
Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.

nd technical controls to identify, classify, securely handle, retain, and dispose of data.
Establish and maintain a data management process. In the process, address data
sensitivity, data owner, handling of data, data retention limits, and disposal
requirements, based on sensitivity and retention standards for the enterprise. Review
and update documentation annually, or when significant enterprise changes occur that
could impact this Safeguard.

Establish and maintain a data inventory, based on the enterprise’s data management
process. Inventory sensitive data, at a minimum. Review and update inventory
annually, at a minimum, with a priority on sensitive data.

Configure data access control lists based on a user’s need to know. Apply data access
control lists, also known as access permissions, to local and remote file systems,
databases, and applications.
Retain data according to the enterprise’s data management process. Data retention
must include both minimum and maximum timelines.
Securely dispose of data as outlined in the enterprise’s data management process.
Ensure the disposal process and method are commensurate with the data sensitivity.
Encrypt data on end-user devices containing sensitive data. Example implementations
can include: Windows BitLocker®, Apple FileVault®, Linux® dm-crypt.
Establish and maintain an overall data classification scheme for the enterprise.
Enterprises may use labels, such as “Sensitive,” “Confidential,” and “Public,” and
classify their data according to those labels. Review and update the classification
scheme annually, or when significant enterprise changes occur that could impact this
Safeguard.
Document data flows. Data flow documentation includes service provider data flows
and should be based on the enterprise’s data management process. Review and
update documentation annually, or when significant enterprise changes occur that
could impact this Safeguard.

Encrypt data on removable media.

Encrypt sensitive data in transit. Example implementations can include: Transport

Layer Security (TLS) and Open Secure Shell (OpenSSH).

Encrypt sensitive data at rest on servers, applications, and databases containing

sensitive data. Storage-layer encryption, also known as server-side encryption, meets
the minimum requirement of this Safeguard. Additional encryption methods may
include application-layer encryption, also known as client-side encryption, where
access to the data storage device(s) does not permit access to the plain-text data.

Segment data processing and storage based on the sensitivity of the data. Do not
process sensitive data on enterprise assets intended for lower sensitivity data.
Implement an automated tool, such as a host-based Data Loss Prevention (DLP) tool
to identify all sensitive data stored, processed, or transmitted through enterprise
assets, including those located onsite or at a remote service provider, and update the
enterprise's sensitive data inventory.
 Log sensitive data access, including modification and disposal.
of Enterprise Assets and Software
in the secure configuration of enterprise assets (end-user devices, including portable and
ces; non-computing/IoT devices; and servers) and software (operating systems and

Establish and maintain a secure configuration process for enterprise assets (end-user
devices, including portable and mobile, non-computing/IoT devices, and servers) and
software (operating systems and applications). Review and update documentation
annually, or when significant enterprise changes occur that could impact this
Safeguard.
Establish and maintain a secure configuration process for network devices. Review
and update documentation annually, or when significant enterprise changes occur that
could impact this Safeguard.

Configure automatic session locking on enterprise assets after a defined period of

inactivity. For general purpose operating systems, the period must not exceed 15
minutes. For mobile end-user devices, the period must not exceed 2 minutes.

Implement and manage a firewall on servers, where supported. Example

implementations include a virtual firewall, operating system firewall, or a third-party
firewall agent.

Implement and manage a host-based firewall or port-filtering tool on end-user devices,

with a default-deny rule that drops all traffic except those services and ports that are
explicitly allowed.

Securely manage enterprise assets and software. Example implementations include

managing configuration through version-controlled-infrastructure-as-code and
accessing administrative interfaces over secure network protocols, such as Secure
Shell (SSH) and Hypertext Transfer Protocol Secure (HTTPS). Do not use insecure
management protocols, such as Telnet (Teletype Network) and HTTP, unless
operationally essential.

Manage default accounts on enterprise assets and software, such as root,

administrator, and other pre-configured vendor accounts. Example implementations
can include: disabling default accounts or making them unusable.

Uninstall or disable unnecessary services on enterprise assets and software, such as

an unused file sharing service, web application module, or service function.

Configure trusted DNS servers on enterprise assets. Example implementations

include: configuring assets to use enterprise-controlled DNS servers and/or reputable
externally accessible DNS servers.
 Enforce automatic device lockout following a predetermined threshold of local failed
authentication attempts on portable end-user devices, where supported. For laptops,
do not allow more than 20 failed authentication attempts; for tablets and smartphones,
no more than 10 failed authentication attempts. Example implementations include
Microsoft® InTune Device Lock and Apple® Configuration Profile maxFailedAttempts.

Remotely wipe enterprise data from enterprise-owned portable end-user devices when
deemed appropriate such as lost or stolen devices, or when an individual no longer
supports the enterprise.

Ensure separate enterprise workspaces are used on mobile end-user devices, where
supported. Example implementations include using an Apple® Configuration Profile or
Android™ Work Profile to separate enterprise applications and data from personal
applications and data.

ools to assign and manage authorization to credentials for user accounts, including
ts, as well as service accounts, to enterprise assets and software.

Establish and maintain an inventory of all accounts managed in the enterprise. The
inventory must include both user and administrator accounts. The inventory, at a
minimum, should contain the person’s name, username, start/stop dates, and
department. Validate that all active accounts are authorized, on a recurring schedule at
a minimum quarterly, or more frequently.

Use unique passwords for all enterprise assets. Best practice implementation includes,
at a minimum, an 8-character password for accounts using MFA and a 14-character
password for accounts not using MFA.
Delete or disable any dormant accounts after a period of 45 days of inactivity, where
supported.
Restrict administrator privileges to dedicated administrator accounts on enterprise
assets. Conduct general computing activities, such as internet browsing, email, and
productivity suite use, from the user’s primary, non-privileged account.

Establish and maintain an inventory of service accounts. The inventory, at a minimum,

must contain department owner, review date, and purpose. Perform service account
reviews to validate that all active accounts are authorized, on a recurring schedule at a
minimum quarterly, or more frequently.

Centralize account management through a directory or identity service.

ools to create, assign, manage, and revoke access credentials and privileges for user,
rvice accounts for enterprise assets and software.
Establish and follow a process, preferably automated, for granting access to enterprise
assets upon new hire, rights grant, or role change of a user.
 Establish and follow a process, preferably automated, for revoking access to enterprise
assets, through disabling accounts immediately upon termination, rights revocation, or
role change of a user. Disabling accounts, instead of deleting accounts, may be
necessary to preserve audit trails.

Require all externally-exposed enterprise or third-party applications to enforce MFA,

where supported. Enforcing MFA through a directory service or SSO provider is a
satisfactory implementation of this Safeguard.

Require MFA for remote network access.

Require MFA for all administrative access accounts, where supported, on all enterprise
assets, whether managed on-site or through a third-party provider.
Establish and maintain an inventory of the enterprise’s authentication and authorization
systems, including those hosted on-site or at a remote service provider. Review and
update the inventory, at a minimum, annually, or more frequently.
Centralize access control for all enterprise assets through a directory service or SSO
provider, where supported.

Define and maintain role-based access control, through determining and documenting
the access rights necessary for each role within the enterprise to successfully carry out
its assigned duties. Perform access control reviews of enterprise assets to validate that
all privileges are authorized, on a recurring schedule at a minimum annually, or more
frequently.
ility Management
ntinuously assess and track vulnerabilities on all enterprise assets within the enterprise’s
er to remediate, and minimize, the window of opportunity for attackers. Monitor public and
ces for new threat and vulnerability information.

Establish and maintain a documented vulnerability management process for enterprise

assets. Review and update documentation annually, or when significant enterprise
changes occur that could impact this Safeguard.

Establish and maintain a risk-based remediation strategy documented in a remediation

process, with monthly, or more frequent, reviews.

Perform operating system updates on enterprise assets through automated patch

management on a monthly, or more frequent, basis.
Perform application updates on enterprise assets through automated patch
management on a monthly, or more frequent, basis.
Perform automated vulnerability scans of internal enterprise assets on a quarterly, or
more frequent, basis. Conduct both authenticated and unauthenticated scans, using a
SCAP-compliant vulnerability scanning tool.
 Perform automated vulnerability scans of externally-exposed enterprise assets using a
SCAP-compliant vulnerability scanning tool. Perform scans on a monthly, or more
frequent, basis.
Remediate detected vulnerabilities in software through processes and tooling on a
monthly, or more frequent, basis, based on the remediation process.

and retain audit logs of events that could help detect, understand, or recover from an

Establish and maintain an audit log management process that defines the enterprise’s
logging requirements. At a minimum, address the collection, review, and retention of
audit logs for enterprise assets. Review and update documentation annually, or when
significant enterprise changes occur that could impact this Safeguard.
Collect audit logs. Ensure that logging, per the enterprise’s audit log management
process, has been enabled across enterprise assets.
Ensure that logging destinations maintain adequate storage to comply with the
enterprise’s audit log management process.
Standardize time synchronization. Configure at least two synchronized time sources
across enterprise assets, where supported.
Configure detailed audit logging for enterprise assets containing sensitive data. Include
event source, date, username, timestamp, source addresses, destination addresses,
and other useful elements that could assist in a forensic investigation.
Collect DNS query audit logs on enterprise assets, where appropriate and supported.
Collect URL request audit logs on enterprise assets, where appropriate and supported.
Collect command-line audit logs. Example implementations include collecting audit
logs from PowerShell®, BASH™, and remote administrative terminals.
Centralize, to the extent possible, audit log collection and retention across enterprise
assets.
Retain audit logs across enterprise assets for a minimum of 90 days.
Conduct reviews of audit logs to detect anomalies or abnormal events that could
indicate a potential threat. Conduct reviews on a weekly, or more frequent, basis.
Collect service provider logs, where supported. Example implementations include
collecting authentication and authorization events, data creation and disposal events,
and user management events.
ser Protections

and detections of threats from email and web vectors, as these are opportunities for
ate human behavior through direct engagement.
 Ensure only fully supported browsers and email clients are allowed to execute in the
enterprise, only using the latest version of browsers and email clients provided through
the vendor.
Use DNS filtering services on all enterprise assets to block access to known malicious
domains.
Enforce and update network-based URL filters to limit an enterprise asset from
connecting to potentially malicious or unapproved websites. Example implementations
include category-based filtering, reputation-based filtering, or through the use of block
lists. Enforce filters for all enterprise assets.

Restrict, either through uninstalling or disabling, any unauthorized or unnecessary

browser or email client plugins, extensions, and add-on applications.

To lower the chance of spoofed or modified emails from valid domains, implement
DMARC policy and verification, starting with implementing the Sender Policy
Framework (SPF) and the DomainKeys Identified Mail (DKIM) standards.
Block unnecessary file types attempting to enter the enterprise’s email gateway.
Deploy and maintain email server anti-malware protections, such as attachment
scanning and/or sandboxing.

e installation, spread, and execution of malicious applications, code, or scripts on

Deploy and maintain anti-malware software on all enterprise assets.

Configure automatic updates for anti-malware signature files on all enterprise assets.

Disable autorun and autoplay auto-execute functionality for removable media.

Configure anti-malware software to automatically scan removable media.

Enable anti-exploitation features on enterprise assets and software, where possible,

such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit
Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.

Centrally manage anti-malware software.

Use behavior-based anti-malware software.

in data recovery practices sufficient to restore in-scope enterprise assets to a pre-incident

Establish and maintain a data recovery process. In the process, address the scope of
data recovery activities, recovery prioritization, and the security of backup data. Review
and update documentation annually, or when significant enterprise changes occur that
could impact this Safeguard.
Perform automated backups of in-scope enterprise assets. Run backups weekly, or
more frequently, based on the sensitivity of the data.
Protect recovery data with equivalent controls to the original data. Reference
encryption or data separation, based on requirements.
Establish and maintain an isolated instance of recovery data. Example
implementations include, version controlling backup destinations through offline, cloud,
or off-site systems or services.
Test backup recovery quarterly, or more frequently, for a sampling of in-scope
enterprise assets.
Test backup recovery quarterly, or more frequently, for a sampling of in-scope
enterprise assets.

, and actively manage (track, report, correct) network devices, in order to prevent
ting vulnerable network services and access points.

Ensure network infrastructure is kept up-to-date. Example implementations include

running the latest stable release of software and/or using currently supported network-
as-a-service (NaaS) offerings. Review software versions monthly, or more frequently,
to verify software support.
Establish and maintain a secure network architecture. A secure network architecture
must address segmentation, least privilege, and availability, at a minimum.
Securely manage network infrastructure. Example implementations include version-
controlled-infrastructure-as-code, and the use of secure network protocols, such as
SSH and HTTPS.

Establish and maintain architecture diagram(s) and/or other network system

documentation. Review and update documentation annually, or when significant
enterprise changes occur that could impact this Safeguard.

Centralize network AAA.

Use secure network management and communication protocols (e.g., 802.1X, Wi-Fi
Protected Access 2 (WPA2) Enterprise or greater).
 Require users to authenticate to enterprise-managed VPN and authentication services
prior to accessing enterprise resources on end-user devices.

Establish and maintain dedicated computing resources, either physically or logically

separated, for all administrative tasks or tasks requiring administrative access. The
computing resources should be segmented from the enterprise's primary network and
not be allowed internet access.

nd tooling to establish and maintain comprehensive network monitoring and defense

ats across the enterprise’s network infrastructure and user base.

Centralize security event alerting across enterprise assets for log correlation and
analysis. Best practice implementation requires the use of a SIEM, which includes
vendor-defined event correlation alerts. A log analytics platform configured with
security-relevant correlation alerts also satisfies this Safeguard.
Deploy a host-based intrusion detection solution on enterprise assets, where
appropriate and/or supported.
Deploy a network intrusion detection solution on enterprise assets, where appropriate.
Example implementations include the use of a Network Intrusion Detection System
(NIDS) or equivalent cloud service provider (CSP) service.

Perform traffic filtering between network segments, where appropriate.

Manage access control for assets remotely connecting to enterprise resources.
Determine amount of access to enterprise resources based on: up-to-date anti-
malware software installed, configuration compliance with the enterprise’s secure
configuration process, and ensuring the operating system and applications are up-to-
date.
Collect network traffic flow logs and/or network traffic to review and alert upon from
network devices.
Deploy a host-based intrusion prevention solution on enterprise assets, where
appropriate and/or supported. Example implementations include use of an Endpoint
Detection and Response (EDR) client or host-based IPS agent.

Deploy a network intrusion prevention solution, where appropriate. Example

implementations include the use of a Network Intrusion Prevention System (NIPS) or
equivalent CSP service.

Deploy port-level access control. Port-level access control utilizes 802.1x, or similar
network access control protocols, such as certificates, and may incorporate user
and/or device authentication.
Perform application layer filtering. Example implementations include a filtering proxy,
application layer firewall, or gateway.
 Tune security event alerting thresholds monthly, or more frequently.

and Skills Training

in a security awareness program to influence behavior among the workforce to be security

rly skilled to reduce cybersecurity risks to the enterprise.

Establish and maintain a security awareness program. The purpose of a security

awareness program is to educate the enterprise’s workforce on how to interact with
enterprise assets and data in a secure manner. Conduct training at hire and, at a
minimum, annually. Review and update content annually, or when significant
enterprise changes occur that could impact this Safeguard.

Establish and maintain a security awareness program. The purpose of a security

awareness program is to educate the enterprise’s workforce on how to interact with
enterprise assets and data in a secure manner. Conduct training at hire and, at a
minimum, annually. Review and update content annually, or when significant
enterprise changes occur that could impact this Safeguard.

Train workforce members to recognize social engineering attacks, such as phishing,

pre-texting, and tailgating.

Train workforce members on authentication best practices. Example topics include

MFA, password composition, and credential management.

Train workforce members on how to identify and properly store, transfer, archive, and
destroy sensitive data. This also includes training workforce members on clear screen
and desk best practices, such as locking their screen when they step away from their
enterprise asset, erasing physical and virtual whiteboards at the end of meetings, and
storing data and assets securely.

Train workforce members to be aware of causes for unintentional data exposure.

Example topics include mis-delivery of sensitive data, losing a portable end-user
device, or publishing data to unintended audiences.

Train workforce members to be able to recognize a potential incident and be able to

report such an incident.

Train workforce to understand how to verify and report out-of-date software patches or
any failures in automated processes and tools. Part of this training should include
notifying IT personnel of any failures in automated processes and tools.
 Train workforce members on the dangers of connecting to, and transmitting data over,
insecure networks for enterprise activities. If the enterprise has remote workers,
training must include guidance to ensure that all users securely configure their home
network infrastructure.

Conduct role-specific security awareness and skills training. Example implementations

include secure system administration courses for IT professionals, (OWASP® Top 10
vulnerability awareness and prevention training for web application developers, and
advanced social engineering awareness training for high-profile roles.

Conduct role-specific security awareness and skills training. Example implementations

include secure system administration courses for IT professionals, (OWASP® Top 10
vulnerability awareness and prevention training for web application developers, and
advanced social engineering awareness training for high-profile roles.

evaluate service providers who hold sensitive data, or are responsible for an enterprise’s
r processes, to ensure these providers are protecting those platforms and data

Establish and maintain an inventory of service providers. The inventory is to list all
known service providers, include classification(s), and designate an enterprise contact
for each service provider. Review and update the inventory annually, or when
significant enterprise changes occur that could impact this Safeguard.

Establish and maintain an inventory of service providers. The inventory is to list all
known service providers, include classification(s), and designate an enterprise contact
for each service provider. Review and update the inventory annually, or when
significant enterprise changes occur that could impact this Safeguard.

Establish and maintain a service provider management policy. Ensure the policy
addresses the classification, inventory, assessment, monitoring, and decommissioning
of service providers. Review and update the policy annually, or when significant
enterprise changes occur that could impact this Safeguard.

Establish and maintain a service provider management policy. Ensure the policy
addresses the classification, inventory, assessment, monitoring, and decommissioning
of service providers. Review and update the policy annually, or when significant
enterprise changes occur that could impact this Safeguard.

Classify service providers. Classification consideration may include one or more

characteristics, such as data sensitivity, data volume, availability requirements,
applicable regulations, inherent risk, and mitigated risk. Update and review
classifications annually, or when significant enterprise changes occur that could impact
this Safeguard.
 Ensure service provider contracts include security requirements. Example
requirements may include minimum security program requirements, security incident
and/or data breach notification and response, data encryption requirements, and data
disposal commitments. These security requirements must be consistent with the
enterprise’s service provider management policy. Review service provider contracts
annually to ensure contracts are not missing security requirements.

Ensure service provider contracts include security requirements. Example

requirements may include minimum security program requirements, security incident
and/or data breach notification and response, data encryption requirements, and data
disposal commitments. These security requirements must be consistent with the
enterprise’s service provider management policy. Review service provider contracts
annually to ensure contracts are not missing security requirements.

Ensure service provider contracts include security requirements. Example

requirements may include minimum security program requirements, security incident
and/or data breach notification and response, data encryption requirements, and data
disposal commitments. These security requirements must be consistent with the
enterprise’s service provider management policy. Review service provider contracts
annually to ensure contracts are not missing security requirements.

Assess service providers consistent with the enterprise’s service provider management
policy. Assessment scope may vary based on classification(s), and may include review
of standardized assessment reports, such as Service Organization Control 2 (SOC 2)
and Payment Card Industry (PCI) Attestation of Compliance (AoC), customized
questionnaires, or other appropriately rigorous processes. Reassess service providers
annually, at a minimum, or with new and renewed contracts.

Monitor service providers consistent with the enterprise’s service provider

management policy. Monitoring may include periodic reassessment of service provider
compliance, monitoring service provider release notes, and dark web monitoring.

Monitor service providers consistent with the enterprise’s service provider

management policy. Monitoring may include periodic reassessment of service provider
compliance, monitoring service provider release notes, and dark web monitoring.

Monitor service providers consistent with the enterprise’s service provider

management policy. Monitoring may include periodic reassessment of service provider
compliance, monitoring service provider release notes, and dark web monitoring.

Securely decommission service providers. Example considerations include user and

service account deactivation, termination of data flows, and secure disposal of
enterprise data within service provider systems.
Security
ife cycle of in-house developed, hosted, or acquired software to prevent, detect, and
eaknesses before they can impact the enterprise.

Establish and maintain a secure application development process. In the process,

address such items as: secure application design standards, secure coding practices,
developer training, vulnerability management, security of third-party code, and
application security testing procedures. Review and update documentation annually, or
when significant enterprise changes occur that could impact this Safeguard.

Establish and maintain a process to accept and address reports of software

vulnerabilities, including providing a means for external entities to report. The process
is to include such items as: a vulnerability handling policy that identifies reporting
process, responsible party for handling vulnerability reports, and a process for intake,
assignment, remediation, and remediation testing. As part of the process, use a
vulnerability tracking system that includes severity ratings, and metrics for measuring
timing for identification, analysis, and remediation of vulnerabilities. Review and update
documentation annually, or when significant enterprise changes occur that could
impact this Safeguard.

Third-party application developers need to consider this an externally-facing policy that

helps to set expectations for outside stakeholders.

Perform root cause analysis on security vulnerabilities. When reviewing vulnerabilities,

root cause analysis is the task of evaluating underlying issues that create
vulnerabilities in code, and allows development teams to move beyond just fixing
individual vulnerabilities as they arise.

Establish and manage an updated inventory of third-party components used in

development, often referred to as a “bill of materials,” as well as components slated for
future use. This inventory is to include any risks that each third-party component could
pose. Evaluate the list at least monthly to identify any changes or updates to these
components, and validate that the component is still supported.

Use up-to-date and trusted third-party software components. When possible, choose
established and proven frameworks and libraries that provide adequate
security. Acquire these components from trusted sources or evaluate the software for
vulnerabilities before use.

Establish and maintain a severity rating system and process for application
vulnerabilities that facilitates prioritizing the order in which discovered vulnerabilities
are fixed. This process includes setting a minimum level of security acceptability for
releasing code or applications. Severity ratings bring a systematic way of triaging
vulnerabilities that improves risk management and helps ensure the most severe bugs
are fixed first. Review and update the system and process annually.
Use standard, industry-recommended hardening configuration templates for
application infrastructure components. This includes underlying servers, databases,
and web servers, and applies to cloud containers, Platform as a Service (PaaS)
components, and SaaS components. Do not allow in-house developed software to
weaken configuration hardening.

Maintain separate environments for production and non-production systems.

Ensure that all software development personnel receive training in writing secure code
for their specific development environment and responsibilities. Training can include
general security principles and application security standard practices. Conduct
training at least annually and design in a way to promote security within the
development team, and build a culture of security among the developers.

Apply secure design principles in application architectures. Secure design principles

include the concept of least privilege and enforcing mediation to validate every
operation that the user makes, promoting the concept of "never trust user input."
Examples include ensuring that explicit error checking is performed and documented
for all input, including for size, data type, and acceptable ranges or formats. Secure
design also means minimizing the application infrastructure attack surface, such as
turning off unprotected ports and services, removing unnecessary programs and files,
and renaming or removing default accounts.

Leverage vetted modules or services for application security components, such as

identity management, encryption, and auditing and logging. Using platform features in
critical security functions will reduce developers’ workload and minimize the likelihood
of design or implementation errors. Modern operating systems provide effective
mechanisms for identification, authentication, and authorization and make those
mechanisms available to applications. Use only standardized, currently accepted, and
extensively reviewed encryption algorithms. Operating systems also provide
mechanisms to create and maintain secure audit logs.

Apply static and dynamic analysis tools within the application life cycle to verify that
secure coding practices are being followed.

Conduct application penetration testing. For critical applications, authenticated

penetration testing is better suited to finding business logic vulnerabilities than code
scanning and automated security testing. Penetration testing relies on the skill of the
tester to manually manipulate an application as an authenticated and unauthenticated
user.
 Conduct threat modeling. Threat modeling is the process of identifying and addressing
application security design flaws within a design, before code is created. It is
conducted through specially trained individuals who evaluate the application design
and gauge security risks for each entry point and access level. The goal is to map out
the application, architecture, and infrastructure in a structured way to understand its
weaknesses.

anagement
o develop and maintain an incident response capability (e.g., policies, plans, procedures,
g, and communications) to prepare, detect, and quickly respond to an attack.

Designate one key person, and at least one backup, who will manage the enterprise’s
incident handling process. Management personnel are responsible for the coordination
and documentation of incident response and recovery efforts and can consist of
employees internal to the enterprise, third-party vendors, or a hybrid approach. If using
a third-party vendor, designate at least one person internal to the enterprise to oversee
any third-party work. Review annually, or when significant enterprise changes occur
that could impact this Safeguard.

Establish and maintain contact information for parties that need to be informed of
security incidents. Contacts may include internal staff, third-party vendors, law
enforcement, cyber insurance providers, relevant government agencies, Information
Sharing and Analysis Center (ISAC) partners, or other stakeholders. Verify contacts
annually to ensure that information is up-to-date.

Establish and maintain contact information for parties that need to be informed of
security incidents. Contacts may include internal staff, third-party vendors, law
enforcement, cyber insurance providers, relevant government agencies, Information
Sharing and Analysis Center (ISAC) partners, or other stakeholders. Verify contacts
annually to ensure that information is up-to-date.

Establish and maintain contact information for parties that need to be informed of
security incidents. Contacts may include internal staff, third-party vendors, law
enforcement, cyber insurance providers, relevant government agencies, Information
Sharing and Analysis Center (ISAC) partners, or other stakeholders. Verify contacts
annually to ensure that information is up-to-date.

Establish and maintain an enterprise process for the workforce to report security
incidents. The process includes reporting timeframe, personnel to report to,
mechanism for reporting, and the minimum information to be reported. Ensure the
process is publicly available to all of the workforce. Review annually, or when
significant enterprise changes occur that could impact this Safeguard.
Establish and maintain an incident response process that addresses roles and
responsibilities, compliance requirements, and a communication plan. Review
annually, or when significant enterprise changes occur that could impact this
Safeguard.
 Assign key roles and responsibilities for incident response, including staff from legal,
IT, information security, facilities, public relations, human resources, incident
responders, and analysts, as applicable. Review annually, or when significant
enterprise changes occur that could impact this Safeguard.

Determine which primary and secondary mechanisms will be used to communicate

and report during a security incident. Mechanisms can include phone calls, emails, or
letters. Keep in mind that certain mechanisms, such as emails, can be affected during
a security incident. Review annually, or when significant enterprise changes occur that
could impact this Safeguard.

Plan and conduct routine incident response exercises and scenarios for key personnel
involved in the incident response process to prepare for responding to real-world
incidents. Exercises need to test communication channels, decision making, and
workflows. Conduct testing on an annual basis, at a minimum.
Conduct post-incident reviews. Post-incident reviews help prevent incident recurrence
through identifying lessons learned and follow-up action.

Establish and maintain security incident thresholds, including, at a minimum,

differentiating between an incident and an event. Examples can include: abnormal
activity, security vulnerability, security weakness, data breach, privacy incident, etc.
Review annually, or when significant enterprise changes occur that could impact this
Safeguard.

s and resiliency of enterprise assets through identifying and exploiting weaknesses in

cesses, and technology), and simulating the objectives and actions of an attacker.

Establish and maintain a penetration testing program appropriate to the size,

complexity, and maturity of the enterprise. Penetration testing program characteristics
include scope, such as network, web application, Application Programming Interface
(API), hosted services, and physical premise controls; frequency; limitations, such as
acceptable hours, and excluded attack types; point of contact information; remediation,
such as how findings will be routed internally; and retrospective requirements.

Perform periodic external penetration tests based on program requirements, no less

than annually. External penetration testing must include enterprise and environmental
reconnaissance to detect exploitable information. Penetration testing requires
specialized skills and experience and must be conducted through a qualified party. The
testing may be clear box or opaque box.

Remediate penetration test findings based on the enterprise’s policy for remediation
scope and prioritization.
Validate security measures after each penetration test. If deemed necessary, modify
rulesets and capabilities to detect the techniques used during testing.
Perform periodic internal penetration tests based on program requirements, no less
than annually. The testing may be clear box or opaque box.
 Relationship CSF Subcategories

Equivalent ID.AM-01

Subset ID.AM-08

Subset PR.PS-03
Subset ID.AM-02

Subset PR.PS-02

Subset PR.PS-02

Equivalent PR.PS-05
Equivalent ID.AM-07

Subset ID.AM-08

Subset ID.AM-05

Subset ID.AM-03

Subset PR.DS-02

Subset PR.DS-01

Subset PR.IR-01
Subset PR.PS-01

Subset PR.PS-01
Subset PR.AA-05

Subset GV.RR-04
Subset GV.RR-04

Equivalent PR.AA-05

Superset ID.RA-01

Superset ID.IM-02
Equivalent PR.PS-04

Superset DE.AE-02
Subset DE.CM-09

Subset DE.CM-03
Subset PR.DS-11

Subset PR.DS-11

Subset PR.DS-11

Superset RC.RP-03

Subset PR.IR-01
Subset DE.CM-01
Subset GV.RR-01

Equivalent PR.AT-01
Subset GV.RR-02

Equivalent PR.AT-02

Subset GV.SC-04

Subset ID.AM-04

Subset GV.SC-01

Superset DE.CM-06

Subset GV.SC-04
Subset GV.SC-02

Equivalent GV.SC-05

Superset GV.SC-08

Equivalent GV.SC-06

Superset GV.SC-07

Subset GV.SC-09

Subset DE.CM-06

Subset GV.SC-10
Superset PR.PS-06
Subset RS.CO-02

Subset RS.CO-03

Subset RC.CO-04

Superset RS.MA-01
Subset RC.CO-04

Equivalent RS.AN-03

Equivalent RS.MA-05
 Descriptions

Inventories of hardware managed by the organization are

maintained

Systems, hardware, software, services, and data are

managed throughout their life cycles

Hardware is maintained, replaced, and removed

commensurate with risk
Inventories of software, services, and systems managed
by the organization are maintained

Software is maintained, replaced, and removed

commensurate with risk

Software is maintained, replaced, and removed

commensurate with risk

Installation and execution of unauthorized software are

prevented
Inventories of data and corresponding metadata for
designated data types are maintained

Systems, hardware, software, services, and data are

managed throughout their life cycles

Assets are prioritized based on classification, criticality,

resources, and impact on the mission

Representations of the organization's authorized network

communication and internal and external network data
flows are maintained

The confidentiality, integrity, and availability of data-in-

transit are protected

The confidentiality, integrity, and availability of data-at-rest

are protected

Networks and environments are protected from

unauthorized logical access and usage
Configuration management practices are established and
applied

Configuration management practices are established and

applied
Access permissions, entitlements, and authorizations are
defined in a policy, managed, enforced, and reviewed, and
incorporate the principles of least privilege and separation
of duties

Cybersecurity is included in human resources practices

Cybersecurity is included in human resources practices

Access permissions, entitlements, and authorizations are

defined in a policy, managed, enforced, and reviewed, and
incorporate the principles of least privilege and separation
of duties

Vulnerabilities in assets are identified, validated, and

recorded

Improvements are identified from security tests and

exercises, including those done in coordination with
suppliers and relevant third parties
Log records are generated and made available for
continuous monitoring

Potentially adverse events are analyzed to better

understand associated activities
Computing hardware and software, runtime environments,
and their data are monitored to find potentially adverse
events

Personnel activity and technology usage are monitored to

find potentially adverse events
Backups of data are created, protected, maintained, and
tested
Backups of data are created, protected, maintained, and
tested

Backups of data are created, protected, maintained, and

tested
The integrity of backups and other restoration assets is
verified before using them for restoration

Networks and environments are protected from

unauthorized logical access and usage
Networks and network services are monitored to find
potentially adverse events
Organizational leadership is responsible and accountable
for cybersecurity risk and fosters a culture that is risk-
aware, ethical, and continually improving

Personnel are provided awareness and training so they

possess the knowledge and skills to perform general tasks
with security risks in mind
Roles, responsibilities, and authorities related to
cybersecurity risk management are established,
communicated, understood, and enforced

Individuals in specialized roles are provided awareness

and training so they possess the knowledge and skills to
perform relevant tasks with security risks in mind

Suppliers are known and prioritized by criticality

Inventories of services provided by suppliers are

maintained

A cybersecurity supply chain risk management program,

strategy, objectives, policies, and processes are
established and agreed to by organizational stakeholders

External service provider activities and services are

monitored to find potentially adverse events

Suppliers are known and prioritized by criticality

Cybersecurity roles and responsibilities for suppliers,
customers, and partners are established, communicated,
and coordinated internally and externally

Requirements to address cybersecurity risks in supply

chains are established, prioritized, and integrated into
contracts and other types of agreements with suppliers
and other relevant third parties

Relevant suppliers and other third parties are included in

incident planning, response, and recovery activities

Planning and due diligence are performed to reduce risks

before entering into formal supplier or other third-party
relationships

The risks posed by a supplier, their products and services,

and other third parties are understood, recorded,
prioritized, assessed, responded to, and monitored over
the course of the relationship

Supply chain security practices are integrated into

cybersecurity and enterprise risk management programs,
and their performance is monitored throughout the
technology product and service life cycle

External service provider activities and services are

monitored to find potentially adverse events

Cybersecurity supply chain risk management plans

include provisions for activities that occur after the
conclusion of a partnership or service agreement
Secure software development practices are integrated and
their performance is monitored throughout the software
development life cycle
Internal and external stakeholders are notified of incidents

Information is shared with designated internal and external

stakeholders

Public updates on incident recovery are shared using

approved methods and messaging

The incident response plan is executed once an incident is

declared in coordination with relevant third parties
Public updates on incident recovery are shared using
approved methods and messaging

Analysis is performed to establish what has taken place

during an incident and the root cause of the incident

The criteria for initiating incident recovery are applied

The following Subcategorys of NIST CSF 2.0 are NOT mapped to the CIS Controls
GV.OC-01

GV.OC-02

GV.OC-03

GV.OC-04

GV.OC-05
GV.RM-01
GV.RM-02

GV.RM-03

GV.RM-04

GV.RM-05

GV.RM-06

GV.RM-07

GV.RR-03

GV.PO-01

GV.PO-02

GV.OV-01

GV.OV-02

GV.OV-03

GV.SC-03
ID.RA-02
ID.RA-03
ID.RA-04

ID.RA-05

ID.RA-06
ID.RA-07
ID.IM-03

ID.IM-04
PR.AA-02
PR.AA-03
PR.AA-04
PR.AA-06
PR.DS-10
PR.IR-02

PR.IR-03
PR.IR-04
DE.CM-02
DE.AE-03
DE.AE-04
DE.AE-06
DE.AE-07
DE.AE-08
RS.MA-02
RS.MA-03
RS.MA-04

RS.AN-06
RS.AN-07
RS.AN-08
RS.MI-01
RS.MI-02

RC.RP-01
RC.RP-02

RC.RP-04

RC.RP-05

RC.RP-06

RC.CO-03
wing Subcategorys of NIST CSF 2.0 are NOT mapped to the CIS Controls
The organizational mission is understood and informs cybersecurity risk management
Internal and external stakeholders are understood, and their needs and expectations
regarding cybersecurity risk management are understood and considered
Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy
and civil liberties obligations - are understood and managed
Critical objectives, capabilities, and services that stakeholders depend on or expect from
the organization are understood and communicated
Outcomes, capabilities, and services that the organization depends on are understood and
communicated
Risk management
Risk objectives
appetite and risk arestatements
tolerance establishedare
and agreed to by
established, organizationaland
communicated, stakeholders
maintained
Cybersecurity risk management activities and outcomes are included in enterprise risk
management processes
Strategic direction that describes appropriate risk response options is established and
communicated
Lines of communication across the organization are established for cybersecurity risks,
including risks from suppliers and other third parties
A standardized method for calculating, documenting, categorizing, and prioritizing
cybersecurity risks is established and communicated
Strategic opportunities (i.e., positive risks) are characterized and are included in
organizational cybersecurity risk discussions
Adequate resources are allocated commensurate with cybersecurity risk strategy, roles
and responsibilities, and policies
Policy for managing cybersecurity risks is established based on organizational context,
cybersecurity strategy, and priorities and is communicated and enforced
Policy for managing cybersecurity risks is reviewed, updated, communicated, and
enforced to reflect changes in requirements, threats, technology, and organizational
mission
Cybersecurity risk management strategy outcomes are reviewed to inform and adjust
strategy and direction
The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage
of organizational requirements and risks
Organizational cybersecurity risk management performance is measured and reviewed for
adjustments needed
Cybersecurity supply chain risk management is integrated into cybersecurity and
enterprise risk management, risk assessment, and improvement processes
Cyber threat intelligence is received from information sharing forums and sources
Internal and
Potential external
impacts andthreats to theoforganization
likelihoods are identified
threats exploiting and recorded
vulnerabilities are identified and
recorded
Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and
inform risk response prioritization
Risk responses are chosen from the available options, prioritized, planned, tracked, and
communicated
Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
Improvements are identified from execution of operational processes, procedures, and
activities
Cybersecurity plans that affect operations are established, communicated, maintained,
and improved
Identities are proofed and bound to credentials based on the context of interactions
Users, services, and hardware are authenticated
Identity assertions are protected, conveyed, and verified
Physical access to assets is managed, monitored, and enforced commensurate with risk
The confidentiality, integrity, and availability of data-in-use are protected
The organization's technology assets are protected from environmental threats
Mechanisms are implemented to achieve resilience requirements in normal and adverse
situations
Adequate resource capacity to ensure availability is maintained
The physical environment is monitored to find potentially adverse events
Information is correlated from multiple sources
The estimated impact and scope of adverse events are understood
Information on adverse events is provided to authorized staff and tools
Cyber threat intelligence and other contextual information are integrated into the analysis
Incidents are declared when adverse events meet the defined incident criteria
Incident reports are triaged and validated
Incidents are categorized and prioritized
Incidents are escalated or elevated as needed
Actions performed during an investigation are recorded and the records' integrity and
provenance
Incident dataare
andpreserved
metadata are collected, and their integrity and provenance are
preserved
An incident's magnitude is estimated and validated
Incidents are contained
Incidents are eradicated
The recovery portion of the incident response plan is executed once initiated from the
incident response process
Recovery actions are selected, scoped, prioritized, and performed
Critical mission functions and cybersecurity risk management are considered to establish
post-incident operational norms
The integrity of restored assets is verified, systems and services are restored, and normal
operating status is confirmed
The criteria for determining the end of incident recovery are applied, and incident-related
documentation is completed
Recovery activities and progress in restoring operational capabilities are communicated to
designated internal and external stakeholders
The following CIS Controls Safeguards are NOT mapped to NIST CSF 2.0

1.3

1.4

1.5
2.4

2.6

2.7

3.1

3.3
3.4

3.6
3.9

3.13
3.14

4.3

4.4

4.5

4.6

4.7

4.8

4.9

4.10
4.11

4.12

5.2
5.3

5.4

5.5
5.6

6.3
6.4

6.5

6.6
6.7
7.3
7.4

7.5

7.6

7.7

8.1
8.3
8.4

8.5
8.6
8.7

8.8
8.9
8.10

8.12
 9.1
9.2

9.3

9.4

9.5
9.6
9.7
10.2
10.3
10.4

10.5
10.6

11.1

11.4

12.1

12.3

12.4
12.5
12.6

12.7

12.8
13.2

13.3
13.4

13.5
13.6
 13.7

13.8

13.9
13.10
13.11
14.2
14.3

14.4

14.5
14.6

14.7

14.8

16.2

16.3

16.4

16.5

16.6

16.7
16.8

16.9
16.10

16.11
16.12

16.13

16.14

17.1

17.3

17.5

17.7

18.1

18.2
18.3

18.4
18.5
The following CIS Controls Safeguards are NOT mapped to NIST CSF 2.0

Utilize an Active Discovery Tool

Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory

Use a Passive Asset Discovery Tool

Utilize Automated Software Inventory Tools

Allowlist Authorized Libraries

Allowlist Authorized Scripts

Establish and Maintain a Data Management Process

Configure Data Access Control Lists

Enforce Data Retention

Encrypt Data on End-User Devices

Encrypt Data on Removable Media

Deploy a Data Loss Prevention Solution

Log Sensitive Data Access

Configure Automatic Session Locking on Enterprise Assets

Implement and Manage a Firewall on Servers

Implement and Manage a Firewall on End-User Devices

Securely Manage Enterprise Assets and Software

Manage Default Accounts on Enterprise Assets and Software

Uninstall or Disable Unnecessary Services on Enterprise Assets and Software

Configure Trusted DNS Servers on Enterprise Assets

Enforce Automatic Device Lockout on Portable End-User Devices

Enforce Remote Wipe Capability on Portable End-User Devices

Separate Enterprise Workspaces on Mobile End-User Devices

Use Unique Passwords

Disable Dormant Accounts

Restrict Administrator Privileges to Dedicated Administrator Accounts

Establish and Maintain an Inventory of Service Accounts

Centralize Account Management

Require MFA for Externally-Exposed Applications

Require MFA for Remote Network Access

Require MFA for Administrative Access

Establish and Maintain an Inventory of Authentication and Authorization Systems

Centralize Access Control
Perform Automated Operating System Patch Management
Perform Automated Application Patch Management

Perform Automated Vulnerability Scans of Internal Enterprise Assets

Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets

Remediate Detected Vulnerabilities

Establish and Maintain an Audit Log Management Process

Ensure Adequate Audit Log Storage
Standardize Time Synchronization

Collect Detailed Audit Logs

Collect DNS Query Audit Logs
Collect URL Request Audit Logs

Collect Command-Line Audit Logs

Centralize Audit Logs
Retain Audit Logs

Collect Service Provider Logs

Ensure Use of Only Fully Supported Browsers and Email Clients
Use DNS Filtering Services

Maintain and Enforce Network-Based URL Filters

Restrict Unnecessary or Unauthorized Browser and Email Client Extensions

Implement DMARC
Block Unnecessary File Types
Deploy and Maintain Email Server Anti-Malware Protections
Configure Automatic Anti-Malware Signature Updates
Disable Autorun and Autoplay for Removable Media
Configure Automatic Anti-Malware Scanning of Removable Media

Enable Anti-Exploitation Features

Centrally Manage Anti-Malware Software

Establish and Maintain a Data Recovery Process

Establish and Maintain an Isolated Instance of Recovery Data

Ensure Network Infrastructure is Up-to-Date

Securely Manage Network Infrastructure

Establish and Maintain Architecture Diagram(s)

Centralize Network Authentication, Authorization, and Auditing (AAA)
Use of Secure Network Management and Communication Protocols

Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise’s AAA Infrastructure

Establish and Maintain Dedicated Computing Resources for All Administrative Work
Deploy a Host-Based Intrusion Detection Solution

Deploy a Network Intrusion Detection Solution

Perform Traffic Filtering Between Network Segments

Manage Access Control for Remote Assets

Collect Network Traffic Flow Logs
Deploy a Host-Based Intrusion Prevention Solution

Deploy a Network Intrusion Prevention Solution

Deploy Port-Level Access Control

Perform Application Layer Filtering
Tune Security Event Alerting Thresholds
Train Workforce Members to Recognize Social Engineering Attacks
Train Workforce Members on Authentication Best Practices

Train Workforce on Data Handling Best Practices

Train Workforce Members on Causes of Unintentional Data Exposure

Train Workforce Members on Recognizing and Reporting Security Incidents

Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates

Train Workforce on the Dangers of Connecting to and Transmitting Enterprise Data Over Insecure Networks

Establish and Maintain a Process to Accept and Address Software Vulnerabilities

Perform Root Cause Analysis on Security Vulnerabilities

Establish and Manage an Inventory of Third-Party Software Components

Use Up-to-Date and Trusted Third-Party Software Components

Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities

Use Standard Hardening Configuration Templates for Application Infrastructure

Separate Production and Non-Production Systems

Train Developers in Application Security Concepts and Secure Coding

Apply Secure Design Principles in Application Architectures

Leverage Vetted Modules or Services for Application Security Components

Implement Code-Level Security Checks

Conduct Application Penetration Testing

Conduct Threat Modeling

Designate Personnel to Manage Incident Handling

Establish and Maintain an Enterprise Process for Reporting Incidents

Assign Key Roles and Responsibilities

Conduct Routine Incident Response Exercises

Establish and Maintain a Penetration Testing Program

Perform Periodic External Penetration Tests

Remediate Penetration Test Findings

Validate Security Measures

Perform Periodic Internal Penetration Tests
Utilize an active discovery tool to identify assets connected to the enterprise’s network. Configure the active discove
daily, or more frequently.
Use DHCP logging on all DHCP servers or Internet Protocol (IP) address management tools to update the enterpris
Review and use logs to update the enterprise’s asset inventory weekly, or more frequently.
Use a passive discovery tool to identify assets connected to the enterprise’s network. Review and use scans to upda
asset
Utilizeinventory
software at least weekly,
inventory or more
tools, when frequently.
possible, throughout the enterprise to automate the discovery and documenta
software.
Use technical controls to ensure that only authorized software libraries, such as specific .dll, .ocx, .so, etc., files, are
a system process. Block unauthorized libraries from loading into a system process. Reassess bi-annually, or more fr
Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as
etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequen
Establish and maintain a data management process. In the process, address data sensitivity, data owner, handling o
retention limits, and disposal requirements, based on sensitivity and retention standards for the enterprise. Review a
documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
Configure data access control lists based on a user’s need to know. Apply data access control lists, also known as a
to local and remote file systems, databases, and applications.
Retain data according to the enterprise’s data management process. Data retention must include both minimum and
Encrypt data on end-user devices containing sensitive data. Example implementations can include: Windows BitLoc
FileVault®, Linux® dm-crypt.
Encrypt data on removable media.
Implement an automated tool, such as a host-based Data Loss Prevention (DLP) tool to identify all sensitive data sto
transmitted through enterprise assets, including those located onsite or at a remote service provider, and update the
sensitive data inventory.
Log sensitive data access, including modification and disposal.
Configure automatic session locking on enterprise assets after a defined period of inactivity. For general purpose op
period must not exceed 15 minutes. For mobile end-user devices, the period must not exceed 2 minutes.
Implement and manage a firewall on servers, where supported. Example implementations include a virtual firewall, o
firewall, or a third-party firewall agent.
Implement and manage a host-based firewall or port-filtering tool on end-user devices, with a default-deny rule that d
except those services and ports that are explicitly allowed.

Securely manage enterprise assets and software. Example implementations include managing configuration through
infrastructure-as-code and accessing administrative interfaces over secure network protocols, such as Secure Shell
Transfer Protocol Secure (HTTPS). Do not use insecure management protocols, such as Telnet (Teletype Network)
operationally essential.
Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured v
Example implementations can include: disabling default accounts or making them unusable.
Uninstall or disable unnecessary services on enterprise assets and software, such as an unused file sharing service
module, or service function.
Configure trusted DNS servers on enterprise assets. Example implementations include: configuring assets to use en
DNS servers and/or reputable externally accessible DNS servers.
Enforce automatic device lockout following a predetermined threshold of local failed authentication attempts on porta
devices, where supported. For laptops, do not allow more than 20 failed authentication attempts; for tablets and sma
than 10 failed authentication attempts. Example implementations include Microsoft® InTune Device Lock and Apple
Profile maxFailedAttempts.
Remotely wipe enterprise data from enterprise-owned portable end-user devices when deemed appropriate such as
devices, or when enterprise
Ensure separate an individual no longer are
workspaces supports themobile
used on enterprise.
end-user devices, where supported. Example implemen
an Apple® Configuration Profile or Android™ Work Profile to separate enterprise applications and data from persona
data.
Use unique passwords for all enterprise assets. Best practice implementation includes, at a minimum, an 8-characte
accounts using MFA and a 14-character password for accounts not using MFA.
Delete or disable any dormant accounts after a period of 45 days of inactivity, where supported.
Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computin
internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.
Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department own
purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule
quarterly, or more frequently.
Centralize account management through a directory or identity service.
Require all externally-exposed enterprise or third-party applications to enforce MFA, where supported. Enforcing MF
service or SSO provider is a satisfactory implementation of this Safeguard.
Require MFA for remote network access.
Require MFA for all administrative access accounts, where supported, on all enterprise assets, whether managed on
third-party provider.
Establish and maintain an inventory of the enterprise’s authentication and authorization systems, including those ho
remote service provider. Review and update the inventory, at a minimum, annually, or more frequently.
Centralize access control for all enterprise assets through a directory service or SSO provider, where supported.
Perform operating system updates on enterprise assets through automated patch management on a monthly, or mo
Perform application updates on enterprise assets through automated patch management on a monthly, or more freq
Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct
and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.
Perform automated vulnerability scans of externally-exposed enterprise assets using a SCAP-compliant vulnerability
Perform scans on a monthly, or more frequent, basis.
Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis,
remediation process.
Establish and maintain an audit log management process that defines the enterprise’s logging requirements. At a m
collection, review, and retention of audit logs for enterprise assets. Review and update documentation annually, or w
enterprise changes occur that could impact this Safeguard.
Ensure that logging destinations maintain adequate storage to comply with the enterprise’s audit log management p
Standardize time synchronization. Configure at least two synchronized time sources across enterprise assets, where
Configure detailed audit logging for enterprise assets containing sensitive data. Include event source, date, usernam
source addresses, destination addresses, and other useful elements that could assist in a forensic investigation.
Collect DNS query audit logs on enterprise assets, where appropriate and supported.
Collect URL request audit logs on enterprise assets, where appropriate and supported.
Collect command-line audit logs. Example implementations include collecting audit logs from PowerShell®, BASH™
administrative terminals.
Centralize, to the extent possible, audit log collection and retention across enterprise assets.
Retain audit logs across enterprise assets for a minimum of 90 days.
Collect service provider logs, where supported. Example implementations include collecting authentication and auth
creation and disposal events, and user management events.
Ensure only fully supported browsers and email clients are allowed to execute in the enterprise, only using the latest
and email clients provided through the vendor.
Use DNS filtering services on all enterprise assets to block access to known malicious domains.
Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious o
websites. Example implementations include category-based filtering, reputation-based filtering, or through the use o
filters for all enterprise assets.
Restrict, either through uninstalling or disabling, any unauthorized or unnecessary browser or email client plugins, ex
on applications.
To lower the chance of spoofed or modified emails from valid domains, implement DMARC policy and verification, st
implementing the Sender Policy Framework (SPF) and the DomainKeys Identified Mail (DKIM) standards.
Block unnecessary file types attempting to enter the enterprise’s email gateway.
Deploy and maintain email server anti-malware protections, such as attachment scanning and/or sandboxing.
Configure automatic updates for anti-malware signature files on all enterprise assets.
Disable autorun and autoplay auto-execute functionality for removable media.
Configure anti-malware software to automatically scan removable media.
Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execu
(DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™
Centrally manage anti-malware software.
Establish and maintain a data recovery process. In the process, address the scope of data recovery activities, recov
the security of backup data. Review and update documentation annually, or when significant enterprise changes occ
this Safeguard.
Establish and maintain an isolated instance of recovery data. Example implementations include, version controlling b
through offline, cloud,
Ensure network or off-site
infrastructure is systems or services.
kept up-to-date. Example implementations include running the latest stable release
using currently supported network-as-a-service (NaaS) offerings. Review software versions monthly, or more freque
software support.
Securely manage network infrastructure. Example implementations include version-controlled-infrastructure-as-code
secure network protocols, such as SSH and HTTPS.
Establish and maintain architecture diagram(s) and/or other network system documentation. Review and update doc
or when significant enterprise changes occur that could impact this Safeguard.
Centralize network AAA.
Use secure network management and communication protocols (e.g., 802.1X, Wi-Fi Protected Access 2 (WPA2) En
Require users to authenticate to enterprise-managed VPN and authentication services prior to accessing enterprise
user devices.
Establish and maintain dedicated computing resources, either physically or logically separated, for all administrative
requiring administrative access. The computing resources should be segmented from the enterprise's primary netwo
allowed internet access.
Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
Deploy a network intrusion detection solution on enterprise assets, where appropriate. Example implementations inc
Network Intrusion Detection System (NIDS) or equivalent cloud service provider (CSP) service.
Perform traffic filtering between network segments, where appropriate.
Manage access control for assets remotely connecting to enterprise resources. Determine amount of access to ente
based on: up-to-date anti-malware software installed, configuration compliance with the enterprise’s secure configur
ensuring the operating system and applications are up-to-date.
Collect network traffic flow logs and/or network traffic to review and alert upon from network devices.
 Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Exam
include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.
Deploy a network intrusion prevention solution, where appropriate. Example implementations include the use of a Ne
Prevention System (NIPS) or equivalent CSP service.
Deploy port-level access control. Port-level access control utilizes 802.1x, or similar network access control protocol
certificates, and may incorporate user and/or device authentication.
Perform application layer filtering. Example implementations include a filtering proxy, application layer firewall, or ga
Tune security event alerting thresholds monthly, or more frequently.
Train
Train workforce
workforce members
members to
onrecognize socialbest
authentication engineering
practices.attacks,
Example such as phishing,
topics pre-texting,
include MFA, passwordandcomposition,
tailgating. and
management.
Train workforce members on how to identify and properly store, transfer, archive, and destroy sensitive data. This al
workforce members on clear screen and desk best practices, such as locking their screen when they step away from
asset, erasing physical and virtual whiteboards at the end of meetings, and storing data and assets securely.
Train workforce members to be aware of causes for unintentional data exposure. Example topics include mis-deliver
losing a portable end-user device, or publishing data to unintended audiences.
Train workforce members to be able to recognize a potential incident and be able to report such an incident.
Train workforce to understand how to verify and report out-of-date software patches or any failures in automated pro
Part
Trainofworkforce
this training should on
members include notifyingofITconnecting
the dangers personnelto,
of and
any failures in automated
transmitting data over,processes and tools.for enterpr
insecure networks
enterprise has remote workers, training must include guidance to ensure that all users securely configure their home
infrastructure.
Establish and maintain a process to accept and address reports of software vulnerabilities, including providing a me
entities to report. The process is to include such items as: a vulnerability handling policy that identifies reporting proc
party for handling vulnerability reports, and a process for intake, assignment, remediation, and remediation testing. A
process, use a vulnerability tracking system that includes severity ratings, and metrics for measuring timing for ident
and remediation of vulnerabilities. Review and update documentation annually, or when significant enterprise chang
impact this Safeguard.

Third-party application developers need to consider this an externally-facing policy that helps to set expectations for
stakeholders.
Perform root cause analysis on security vulnerabilities. When reviewing vulnerabilities, root cause analysis is the tas
underlying issues that create vulnerabilities in code, and allows development teams to move beyond just fixing indivi
as they arise.
Establish and manage an updated inventory of third-party components used in development, often referred to as a “
well as components slated for future use. This inventory is to include any risks that each third-party component could
list at least monthly to identify any changes or updates to these components, and validate that the component is still
Use up-to-date and trusted third-party software components. When possible, choose established and proven framew
that provide adequate security. Acquire these components from trusted sources or evaluate the software for vulnera

Establish and maintain a severity rating system and process for application vulnerabilities that facilitates prioritizing t
discovered vulnerabilities are fixed. This process includes setting a minimum level of security acceptability for releas
applications. Severity ratings bring a systematic way of triaging vulnerabilities that improves risk management and h
severe bugs are fixed first. Review and update the system and process annually.
Use standard, industry-recommended hardening configuration templates for application infrastructure components. T
underlying servers, databases, and web servers, and applies to cloud containers, Platform as a Service (PaaS) com
components. Do not allow in-house developed software to weaken configuration hardening.
Maintain separate environments for production and non-production systems.
Ensure that all software development personnel receive training in writing secure code for their specific developmen
responsibilities. Training can include general security principles and application security standard practices. Conduc
annually and design in a way to promote security within the development team, and build a culture of security among
Apply secure design principles in application architectures. Secure design principles include the concept of least priv
mediation to validate every operation that the user makes, promoting the concept of "never trust user input." Examp
that explicit error checking is performed and documented for all input, including for size, data type, and acceptable ra
Secure design also means minimizing the application infrastructure attack surface, such as turning off unprotected p
removing unnecessary programs and files, and renaming or removing default accounts.

Leverage vetted modules or services for application security components, such as identity management, encryption
logging. Using platform features in critical security functions will reduce developers’ workload and minimize the likelih
implementation errors. Modern operating systems provide effective mechanisms for identification, authentication, an
make those mechanisms available to applications. Use only standardized, currently accepted, and extensively review
algorithms. Operating systems also provide mechanisms to create and maintain secure audit logs.
Apply static and dynamic analysis tools within the application life cycle to verify that secure coding practices are bein
Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to
logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the t
manipulate an application as an authenticated and unauthenticated user.

Conduct threat modeling. Threat modeling is the process of identifying and addressing application security design fla
before code is created. It is conducted through specially trained individuals who evaluate the application design and
for each entry point and access level. The goal is to map out the application, architecture, and infrastructure in a stru
understand its weaknesses.
Designate one key person, and at least one backup, who will manage the enterprise’s incident handling process. Ma
are responsible for the coordination and documentation of incident response and recovery efforts and can consist of
to the enterprise, third-party vendors, or a hybrid approach. If using a third-party vendor, designate at least one pers
enterprise to oversee any third-party work. Review annually, or when significant enterprise changes occur that could
Safeguard.
Establish and maintain an enterprise process for the workforce to report security incidents. The process includes rep
personnel to report to, mechanism for reporting, and the minimum information to be reported. Ensure the process is
all of the workforce. Review annually, or when significant enterprise changes occur that could impact this Safeguard
Assign key roles and responsibilities for incident response, including staff from legal, IT, information security, facilitie
human resources, incident responders, and analysts, as applicable. Review annually, or when significant enterprise
could impact this Safeguard.
Plan and conduct routine incident response exercises and scenarios for key personnel involved in the incident respo
prepare for responding to real-world incidents. Exercises need to test communication channels, decision making, an
Conduct testing on an annual basis, at a minimum.

Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterpr
testing program characteristics include scope, such as network, web application, Application Programming Interface
services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types
information; remediation, such as how findings will be routed internally; and retrospective requirements.
Perform periodic external penetration tests based on program requirements, no less than annually. External penetra
include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires
experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
Validate security measures after each penetration test. If deemed necessary, modify rulesets and capabilities to dete
used during
Perform testing.
periodic internal penetration tests based on program requirements, no less than annually. The testing may b
opaque box.