CIS RAM Workbook Version CC
CIS RAM Workbook Version CC
CIS RAM Workbook Version CC
0
Provided by CIS® (Center for Internet Security, Inc.)
The CIS RAM Workbook provides templates and examples that are referenced in CIS RAM 1.0. That docu
information security risk assessments by illustrating risk assessment steps, and by encouraging its reader
Workbook provides one tab per template. Each tab is named in the CIS RAM to assist the reader's use of
Users of the CIS RAM Workbook should copy these templates for use in their organizations and should m
programs and business context. Users should refer to the Principles and Practices in the CIS RAM to ensu
the objectives in those principles and practices.
CIS RAM also incorporates the CIS Controls™ Version 7, which is licensed under a Creative Commons Attribution-N
link can be found at https://creativecommons.org/licenses/by-nc-nd/4.0/legalcode).
To further clarify the Creative Commons license related to the CIS Controls and CIS RAM, you are authorized to cop
your organization and outside of your organization for non-commercial purposes only, provided that (i) appropriate c
Additionally, if you remix, transform or build upon the CIS Controls or CIS RAM, you may not distribute the modified
subject to the prior approval of CIS® (Center for Internet Security, Inc.).
link can be found at https://creativecommons.org/licenses/by-nc-nd/4.0/legalcode).
To further clarify the Creative Commons license related to the CIS Controls and CIS RAM, you are authorized to cop
your organization and outside of your organization for non-commercial purposes only, provided that (i) appropriate c
Additionally, if you remix, transform or build upon the CIS Controls or CIS RAM, you may not distribute the modified
subject to the prior approval of CIS® (Center for Internet Security, Inc.).
as a process for reasonable implementation of the CIS Controls. CIS RAM describes risk
expectations of regulators and legal authorities for demonstrating compliance, and due
s established risk assessment standards, such as ISO/IEC 27005, NIST SP 800-30, and
successful information security programs. By extending these standards, CIS RAM helps
ns for "reasonable" and "appropriate" safeguards and risk, and "multi-factor" or "due care"
d in CIS RAM 1.0. That document provides instructions for designing and conducting
d by encouraging its readers to attempt those steps for their organization. CIS RAM
o assist the reader's use of each tab.
organizations and should modify them to make them most applicable to their security
ices in the CIS RAM to ensure that any modifications made to these templates conform to
reative Commons Attribution-Non Commercial-No Derivatives 4.0 International Public License (the
AM, you are authorized to copy and redistribute the content as a framework for use by you, within
provided that (i) appropriate credit is given to CIS, and (ii) a link to the license is provided.
ay not distribute the modified materials. Commercial use of the CIS Controls or CIS RAM is
Title Project Plan for Tier 1 Organizations
5 Propose Safeguards
1 Day
2 Hours
2 Hours
Scope Dependent
Scope Dependent
End Date Status
Title Project Plan for Tier 2 Organizations
5 Propose Safeguards
1 Day
2 Hours
2 Hours
Scope Dependent
Scope Dependent
End Date Status
Title Scope Definition for Tier 1 Organizations
Likelihood
Foreseeability
Score
1 Not foreseeable. This is not plausible in the environment.
2 Foreseeable. This is plausible, but not expected.
3 Expected. We are certain this will occur at some time.
Likelihoo
Impact Risk
d
x =
Threshold Threshold Threshold
2 x 2 = 4
… therefore …
Likelihoo
Impact Risk
d
x =
Threshold Threshold Threshold
x =
… therefore …
Likelihood Score
Foreseeability
1 Not foreseeable. This is not plausible in the environment.
2 Foreseeable. This is plausible, but not expected.
3 Expected. We are certain this will eventually occur.
4 Common. This happens repeatedly.
5 Current. This may be happening now.
Likelihoo
Impact to Obligations Impact Risk
d
x =
Patients must not be harmed by
Threshold Threshold Threshold
compromised information.
Likelihoo
Impact to Obligations Impact Risk
d
Define the organization's x =
information security obligations to Threshold Threshold Threshold
prevent harm to others.
bility
nment.
Title Impact and Acceptable Risk Criteria for Tiers 3 & 4 Organizations
Likelihood Score
Foreseeability
1 Not foreseeable. This is not plausible in the environment.
2 Foreseeable. This is plausible, but not expected.
3 Expected. We are certain this will eventually occur.
4 Common. This happens repeatedly.
5 Current. This may be happening now.
Organizations
Likelihoo
Impact to Obligations Impact Risk
d
x =
Patients must not be harmed by
Threshold Threshold Threshold
compromised information.
Likelihoo
Impact to Obligations Impact Risk
d
Define the organization's x =
information security obligations to Threshold Threshold Threshold
prevent harm to others.
bility
nment.
The risks stated in this risk register were identified by evaluating how well the
Summary
[Name of organization or scope of the assessment]
CIS Control
Unique ID Asset Type CIS Control Name
Number
Continuous Vulnerability
Example System 3.4
Management
Continuous Vulnerability
Example System 3.4
Management
Continuous Vulnerability
20 3.2
Management
Continuous Vulnerability
21 3.3
Management
Continuous Vulnerability
22 3.4
Management
Continuous Vulnerability
23 3.5
Management
Continuous Vulnerability
24 3.6
Management
Continuous Vulnerability
25 3.7
Management
Controlled Use of
26 4.1
Administrative Privileges
Controlled Use of
27 4.2
Administrative Privileges
Controlled Use of
28 4.3
Administrative Privileges
Controlled Use of
29 4.4
Administrative Privileges
Controlled Use of
30 4.5
Administrative Privileges
Controlled Use of
31 4.6
Administrative Privileges
Controlled Use of
32 4.7
Administrative Privileges
Controlled Use of
33 4.8
Administrative Privileges
Controlled Use of
34 4.9
Administrative Privileges
Implement a Security
137 Awareness and Training 17.2
Program
Implement a Security
138 Awareness and Training 17.3
Program
Implement a Security
139 Awareness and Training 17.4
Program
Implement a Security
140 Awareness and Training 17.5
Program
Implement a Security
141 Awareness and Training 17.6
Program
Implement a Security
142 Awareness and Training 17.7
Program
Implement a Security
143 Awareness and Training 17.8
Program
Implement a Security
144 Awareness and Training 17.9
Program
Title Description
Use of DNS Filtering Use DNS filtering services to help block access to
Services known malicious domains.
To lower the chance of spoofed or modified emails
from valid domains, implement Domain-based
Implement DMARC and Message Authentication, Reporting and
Enable Receiver-Side Conformance (DMARC) policy and verification,
Verification starting by implementing the Sender Policy
Framework (SPF) and the DomainKeys Identified
Mail(DKIM) standards.
Block all e-mail attachments entering the
Block Unnecessary File
organization's e-mail gateway if the file types are
Types
unnecessary for the organization's business.
Sandbox All Email Use sandboxing to analyze and block inbound
Attachments email attachments with malicious behavior.
Utilize centrally managed anti-malware software to
Utilize Centrally Managed
continuously monitor and defend each of the
Anti-malware Software
organization's workstations and servers.
Ensure Anti-Malware Ensure that the organization's anti-malware
Software and Signatures software updates its scanning engine and signature
are Updated database on a regular basis.
Ensure Backups Have At Ensure that all backups have at least one backup
least One Non-Continuously destination that is not continuously addressable
Addressable Destination through operating system calls.
Encrypt Data on USB If USB storage devices are required, all data stored
Storage Devices on such devices must be encrypted while at rest.
Disable Peer-to-peer
Wireless Network Disable peer-to-peer (adhoc) wireless network
Capabilities on Wireless capabilities on wireless clients.
Clients
2 Accept
(CIS Control 12.7) Acquire and
implement an open-source IPS
solution to detect, and alert on
attacks on the enterprise
management application, and
6 Reduce other vulnerable systems in the
environment. After gaining
confidence in the types of
detected actions and alerts,
deploy IPS capability to protect
high-risk systems.
Implement a SIEM-as-a-
Service. To prevent being
overwhelmed by log messages
and alerts, focus SIEM first on
high-risk systems, such as the
9 Reduce
enterprise management
application. Alert on any data
manipulation and downloads
conducted by administrator
accounts.
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
How foreseeable is it that
What impact could this
this safeguard risk would
What risk would this safeguard risk pose to our
occur and create an
recommended control pose mission?
impact?
to the mission, objectives, or
obligations? Use risk assessment criteria as
Use risk assessment
guidance
criteria as guidance
Safeguard Threat
Safeguard Risk Safeguard Mission Impact
Likelihood
After a baseline is
established, we will be able
to distinguish between
organization-owned systems,
and systems that we do not
control. Alerting can be set
after baseline is complete.
Moderate cost in personnel
time to implement and 3 1
configure the IPS system.
Safeguard
Safeguard Obligations Impact
Risk Score
3 3
0
1 3
1 2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
The risks stated in this risk register were
identified by evaluating how well the CIS
Summary Controls are applied to information assets at
[Name of organization or scope of the
assessment]
Date Completed MM/DD/YYYY
Acceptable Risk Score is le 9
Information
CIS Control CIS Control CIS Control
Unique ID asset or asset Asset Type
Name Number Title
class
Disable
Wireless Wireless
Diary device
Example Network Access 15.9 Peripheral
controllers
Control Access of
Devices
Account Require Multi-
Diary device
Example System Monitoring 16.3 factor
controllers
and Control Authentication
Utilize
Centrally
Diary device Malware
Example System 8.1 Managed
controllers Defenses
Anti-malware
Software
Inventory and Utilize an
Control of Active
1 1.1
Hardware Discovery
Assets Tool
Inventory and
Address
Control of
6 1.6 Unauthorized
Hardware
Assets
Assets
Inventory and
Deploy Port
Control of
7 1.7 Level Access
Hardware
Control
Assets
Utilize Client
Inventory and
Certificates to
Control of
8 1.8 Authenticate
Hardware
Hardware
Assets
Assets
Inventory and Maintain
Control of Inventory of
9 2.1
Software Authorized
Assets Software
Inventory and
Address
Control of
14 2.6 unapproved
Software
software
Assets
Inventory and
Utilize
Control of
15 2.7 Application
Software
Whitelisting
Assets
Physically or
Inventory and
Logically
Control of
18 2.10 Segregate
Software
High Risk
Assets
Applications
Run
Continuous Automated
19 Vulnerability 3.1 Vulnerability
Management Scanning
Tools
Perform
Continuous
Authenticated
20 Vulnerability 3.2
Vulnerability
Management
Scanning
Protect
Continuous
Dedicated
21 Vulnerability 3.3
Assessment
Management
Accounts
Deploy
Automated
Continuous
Operating
22 Vulnerability 3.4
System Patch
Management
Management
Tools
Deploy
Automated
Continuous
Software
23 Vulnerability 3.5
Patch
Management
Management
Tools
Compare
Continuous
Back-to-back
24 Vulnerability 3.6
Vulnerability
Management
Scans
Continuous
Utilize a Risk-
25 Vulnerability 3.7
rating Process
Management
Controlled Maintain
Use of Inventory of
26 4.1
Administrative Administrative
Privileges Accounts
Controlled
Change
Use of
27 4.2 Default
Administrative
Passwords
Privileges
Ensure the
Controlled
Use of
Use of
28 4.3 Dedicated
Administrative
Administrative
Privileges
Accounts
Controlled
Use of Use Unique
29 4.4
Administrative Passwords
Privileges
Use
Controlled Multifactor
Use of Authentication
30 4.5
Administrative For All
Privileges Administrative
Access
Use of
Controlled Dedicated
Use of Machines For
31 4.6
Administrative All
Privileges Administrative
Tasks
Controlled
Use of Limit Access
32 4.7
Administrative to Script Tools
Privileges
Secure
Configuration
for Hardware
Establish
and Software
Secure
35 on Mobile 5.1
Configuration
Devices,
s
Laptops,
Workstations
and Servers
Secure
Configuration
for Hardware
and Software Maintain
36 on Mobile 5.2 Secure
Devices, Images
Laptops,
Workstations
and Servers
Secure
Configuration
for Hardware
and Software Securely
37 on Mobile 5.3 Store Master
Devices, Images
Laptops,
Workstations
and Servers
Secure
Configuration
for Hardware Deploy
and Software System
38 on Mobile 5.4 Configuration
Devices, Management
Laptops, Tools
Workstations
and Servers
Secure
Configuration
for Hardware Implement
and Software Automated
39 on Mobile 5.5 Configuration
Devices, Monitoring
Laptops, Systems
Workstations
and Servers
Maintenance,
Utilize Three
Monitoring
40 6.1 Synchronized
and Analysis
Time Sources
of Audit Logs
Maintenance,
Monitoring Activate audit
41 6.2
and Analysis logging
of Audit Logs
Maintenance,
Enable
Monitoring
42 6.3 Detailed
and Analysis
Logging
of Audit Logs
Maintenance, Ensure
Monitoring adequate
43 6.4
and Analysis storage for
of Audit Logs logs
Maintenance,
Monitoring Central Log
44 6.5
and Analysis Management
of Audit Logs
Maintenance,
Deploy SIEM
Monitoring
45 6.6 or Log
and Analysis
Analytic tool
of Audit Logs
Maintenance,
Monitoring Regularly
46 6.7
and Analysis Review Logs
of Audit Logs
Maintenance,
Monitoring Regularly
47 6.8
and Analysis Tune SIEM
of Audit Logs
Ensure Use of
Email and Only Fully
48 Web Browser 7.1 Supported
Protections Browsers and
Email Clients
Disable
Unnecessary
Email and or
49 Web Browser 7.2 Unauthorized
Protections Browser or
Email Client
Plugins
Limit Use of
Scripting
Email and
Languages in
50 Web Browser 7.3
Web
Protections
Browsers and
Email Clients
Maintain and
Email and Enforce
51 Web Browser 7.4 Network-
Protections Based URL
Filters
Subscribe to
Email and
URL-
52 Web Browser 7.5
Categorizatio
Protections
n service
Email and
Log all URL
53 Web Browser 7.6
requests
Protections
Utilize
Centrally
Malware
58 8.1 Managed
Defenses
Anti-malware
Software
Ensure Anti-
Malware
Malware
59 8.2 Software and
Defenses
Signatures
are Updated
Enable
Operating
System Anti-
Malware Exploitation
60 8.3
Defenses Features/
Deploy Anti-
Exploit
Technologies
Configure
Anti-Malware
Malware
61 8.4 Scanning of
Defenses
Removable
Devices
Configure
Malware Devices Not
62 8.5
Defenses To Auto-run
Content
Centralize
Malware
63 8.6 Anti-malware
Defenses
Logging
Enable DNS
Malware
64 8.7 Query
Defenses
Logging
Enable
Malware Command-
65 8.8
Defenses line Audit
Logging
Limitation and
Control of Perform
Network Regular
68 9.3
Ports, Automated
Protocols, and Port Scans
Services
Limitation and
Control of Apply Host-
Network based
69 9.4
Ports, Firewalls or
Protocols, and Port Filtering
Services
Limitation and
Control of
Implement
Network
70 9.5 Application
Ports,
Firewalls
Protocols, and
Services
Ensure
Data
Regular
71 Recovery 10.1
Automated
Capabilities
Back Ups
Perform
Data
Complete
72 Recovery 10.2
System
Capabilities
Backups
Data
Test Data on
73 Recovery 10.3
Backup Media
Capabilities
Data Ensure
74 Recovery 10.4 Protection of
Capabilities Backups
Ensure
Backups
Data Have At least
75 Recovery 10.5 One Non-
Capabilities Continuously
Addressable
Destination
Secure
Maintain
Configuration
Standard
for Network
Security
76 Devices, such 11.1
Configuration
as Firewalls,
s for Network
Routers and
Devices
Switches
Secure
Configuration
Document
for Network
Traffic
77 Devices, such 11.2
Configuration
as Firewalls,
Rules
Routers and
Switches
Use
Secure
Automated
Configuration
Tools to Verify
for Network
Standard
78 Devices, such 11.3
Device
as Firewalls,
Configuration
Routers and
s and Detect
Switches
Changes
Install the
Secure
Latest Stable
Configuration
Version of
for Network
Any Security-
79 Devices, such 11.4
related
as Firewalls,
Updates on
Routers and
All Network
Switches
Devices
Manage
Secure
Network
Configuration
Devices Using
for Network
Multi-Factor
80 Devices, such 11.5
Authentication
as Firewalls,
and
Routers and
Encrypted
Switches
Sessions
Secure
Use
Configuration
Dedicated
for Network
Machines For
81 Devices, such 11.6
All Network
as Firewalls,
Administrative
Routers and
Tasks
Switches
Secure
Manage
Configuration
Network
for Network
Infrastructure
82 Devices, such 11.7
Through a
as Firewalls,
Dedicated
Routers and
Network
Switches
Maintain an
Boundary Inventory of
83 12.1
Defense Network
Boundaries
Scan for
Unauthorized
Connections
Boundary
84 12.2 across
Defense
Trusted
Network
Boundaries
Deny
Communicatio
Boundary ns with
85 12.3
Defense Known
Malicious IP
Addresses
Deny
Communicatio
Boundary
86 12.4 n over
Defense
Unauthorized
Ports
Configure
Monitoring
Boundary Systems to
87 12.5
Defense Record
Network
Packets
Deploy
Boundary Network-
88 12.6
Defense based IDS
Sensor
Deploy
Network-
Boundary Based
89 12.7
Defense Intrusion
Prevention
Systems
Deploy
NetFlow
Boundary Collection on
90 12.8
Defense Networking
Boundary
Devices
Deploy
Boundary Application
91 12.9
Defense Layer Filtering
Proxy Server
Decrypt
Boundary Network
92 12.10
Defense Traffic at
Proxy
Require All
Remote Login
Boundary
93 12.11 to Use Multi-
Defense
factor
Authentication
Manage All
Devices
Boundary Remotely
94 12.12
Defense Logging into
Internal
Network
Maintain an
Data Inventory
95 13.1
Protection Sensitive
Information
Remove
Sensitive
Data or
Data
96 13.2 Systems Not
Protection
Regularly
Accessed by
Organization
Monitor and
Block
Data
97 13.3 Unauthorized
Protection
Network
Traffic
Only Allow
Access to
Data Authorized
98 13.4
Protection Cloud Storage
or Email
Providers
Monitor and
Detect Any
Data
99 13.5 Unauthorized
Protection
Use of
Encryption
Encrypt the
Data Hard Drive of
100 13.6
Protection All Mobile
Devices.
Manage
System's
External
Data Removable
102 13.8
Protection Media's
Read/write
Configuration
s
Encrypt Data
Data on USB
103 13.9
Protection Storage
Devices
Disable
Controlled
Workstation to
Access Based
106 14.3 Workstation
on the Need
Communicatio
to Know
n
Protect
Controlled
Information
Access Based
109 14.6 through
on the Need
Access
to Know
Control Lists
Enforce
Controlled Access
Access Based Control to
110 14.7
on the Need Data through
to Know Automated
Tools
Controlled Encrypt
Access Based Sensitive
111 14.8
on the Need Information at
to Know Rest
Enforce Detail
Controlled Logging for
Access Based Access or
112 14.9
on the Need Changes to
to Know Sensitive
Data
Maintain an
Wireless Inventory of
113 Access 15.1 Authorized
Control Wireless
Access Points
Detect
Wireless
Wireless
Access Points
114 Access 15.2
Connected to
Control
the Wired
Network
Use a
Wireless Wireless
115 Access 15.3 Intrusion
Control Detection
System
Disable
Wireless Wireless
116 Access 15.4 Access on
Control Devices if Not
Required
Disable Peer-
to-peer
Wireless Wireless
118 Access 15.6 Network
Control Capabilities
on Wireless
Clients
Leverage the
Advanced
Wireless Encryption
119 Access 15.7 Standard
Control (AES) to
Encrypt
Wireless Data
Use Wireless
Authentication
Wireless Protocols that
120 Access 15.8 Require
Control Mutual, Multi-
Factor
Authentication
Disable
Wireless Wireless
121 Access 15.9 Peripheral
Control Access of
Devices
Create
Separate
Wireless Wireless
122 Access 15.10 Network for
Control Personal and
Untrusted
Devices
Maintain an
Account
Inventory of
123 Monitoring 16.1
Authentication
and Control
Systems
Configure
Account
Centralized
124 Monitoring 16.2
Point of
and Control
Authentication
Encrypt or
Account
Hash all
126 Monitoring 16.4
Authentication
and Control
Credentials
Encrypt
Transmittal of
Account
Username
127 Monitoring 16.5
and
and Control
Authentication
Credentials
Account Maintain an
128 Monitoring 16.6 Inventory of
and Control Accounts
Establish
Account
Process for
129 Monitoring 16.7
Revoking
and Control
Access
Account Disable
131 Monitoring 16.9 Dormant
and Control Accounts
Ensure All
Account Accounts
132 Monitoring 16.1 Have An
and Control Expiration
Date
Lock
Account
Workstation
133 Monitoring 16.11
Sessions
and Control
After Inactivity
Monitor
Account Attempts to
134 Monitoring 16.12 Access
and Control Deactivated
Accounts
Alert on
Account
Account Login
Monitoring 16.13
Behavior
and Control
Deviation
Implement a
Security Perform a
Awareness 17.1 Skills Gap
and Training Analysis
Program
Implement a
Security Deliver
Awareness 17.2 Training to Fill
and Training the Skills Gap
Program
Implement a
Implement a
Security
Security
Awareness 17.3
Awareness
and Training
Program
Program
Implement a
Update
Security
Awareness
Awareness 17.4
Content
and Training
Frequently
Program
Implement a
Train
Security
Workforce on
Awareness 17.5
Secure
and Training
Authentication
Program
Train
Implement a
Workforce on
Security
Identifying
Awareness 17.6
Social
and Training
Engineering
Program
Attacks
Implement a
Train
Security
Workforce on
Awareness 17.7
Sensitive
and Training
Data Handling
Program
Train
Implement a
Workforce on
Security
Causes of
Awareness 17.8
Unintentional
and Training
Data
Program
Exposure
Train
Implement a
Workforce
Security
Members on
Awareness 17.9
Identifying
and Training
and Reporting
Program
Incidents
Establish
Application
Secure
Software 18.1
Coding
Security
Practices
Ensure
Explicit Error
Application Checking is
Software 18.2 Performed for
Security All In-house
Developed
Software
Verify That
Application Acquired
Software 18.3 Software is
Security Still
Supported
Use Only
Standardized
Application and
Software 18.5 Extensively
Security Reviewed
Encryption
Algorithms
Ensure
Software
Application Development
Software 18.6 Personnel are
Security Trained in
Secure
Coding
Apply Static
Application
and Dynamic
Software 18.7
Code Analysis
Security
Tools
Establish a
Process to
Application Accept and
Software 18.8 Address
Security Reports of
Software
Vulnerabilities
Separate
Application Production
Software 18.9 and Non-
Security Production
Systems
Deploy Web
Application
Application
Software 18.1
Firewalls
Security
(WAFs)
Use Standard
Application Hardening
Software 18.11 Configuration
Security Templates for
Databases
Incident Document
Response Incident
19.1
and Response
Management Procedures
Assign Job
Incident
Titles and
Response
19.2 Duties for
and
Incident
Management
Response
Designate
Incident Management
Response Personnel to
19.3
and Support
Management Incident
Handling
Devise
Incident Organization-
Response wide
19.4
and Standards for
Management Reporting
Incidents
Maintain
Incident Contact
Response Information
19.5
and For Reporting
Management Security
Incidents
Publish
Information
Incident
Regarding
Response
19.6 Reporting
and
Computer
Management
Anomalies
and Incidents
Conduct
Incident Periodic
Response Incident
19.7
and Scenario
Management Sessions for
Personnel
Create
Incident
Incident
Response
19.8 Scoring and
and
Prioritization
Management
Schema
Penetration Establish a
Tests and Penetration
20.1
Red Team Testing
Exercises Program
Conduct
Penetration Regular
Tests and External and
20.2
Red Team Internal
Exercises Penetration
Tests
Penetration Perform
Tests and Periodic Red
20.3
Red Team Team
Exercises Exercises
Include Tests
for Presence
Penetration
of
Tests and
20.4 Unprotected
Red Team
System
Exercises
Information
and Artifacts
Create Test
Penetration Bed for
Tests and Elements Not
20.5
Red Team Typically
Exercises Tested in
Production
Use
Penetration Vulnerability
Tests and Scanning and
20.6
Red Team Penetration
Exercises Testing Tools
in Concert
Ensure
Results from
Penetration
Penetration
Test are
Tests and
20.7 Documented
Red Team
Using Open,
Exercises
Machine-
readable
Standards
Control and
Monitor
Penetration
Accounts
Tests and
20.8 Associated
Red Team
with
Exercises
Penetration
Testing
How
foreseeable is
What impact
it that this
could this
threat would
What vulnerabilities What threats could threat pose to
occur and
How the control is are present, given compromise our mission?
CIS Control create an
currently the way the CIS information assets as
Description impact?
implemented Control is a result of the Use risk
Implemented vulnerabilities? assessment
Use risk
criteria as
assessment
guidance
criteria as
guidance
Threat Mission
Description Current Control Vulnerability Threat
Likelihood Impact
[Supplemented by
CIS Control 16.3]
Each diary device is Hackers may walk
Diary device
joined to the diary through clinics with
controllers are using
device controller Bluetooth devices
a deprecated
using a one-time, that are prepared
version of Bluetooth
six-digit code that is with device-specific
Disable wireless to support older
displayed on the soft-certs to hack
peripheral access diary devices.
controller and diary device
of devices (such Bluetooth devices
entered at the controllers using
as Bluetooth and with seized soft-
device. At this point, attacks such as 1 3
NFC), unless such certs can
all file transfers and Blueborne. Hackers
access is required manipulate
firmware updates are must steal soft-certs
for a business Bluetooth services
enabled. However, from diary devices,
purpose. on the diary device
files may only be then guess one-time
controllers to gain
accessed by devices six-digit codes to
access to files and
that use soft-certs access patient files
commands on the
that are associated on diary device
controllers.
with access controllers.
privileges on diary
device controllers.
While diary devices
can connect to diary
Require multi-
device controllers
factor Hackers must steal
over Bluetooth using Six-digit codes may
authentication for soft-certs from diary
a one-time, six-digit be guessed, or soft-
all user accounts, devices, then guess
code, access to certs may be stolen
on all systems, one-time six-digit 1 3
existing files with from diary devices
whether managed codes to access
patient information and stored on
onsite or by a patient files on diary
on the controller is attacker systems.
third-party device controllers.
granted using the
provider.
unique soft-cert on
each diary device.
limited because
common vectors for
receiving malware
such as email
clients and web
browsers are not
installed on the
controllers.
Attackers would
need to download
malware
executables from
the Internet using
scripts or bash
commands.
Utilize centrally
managed anti- Hackers may implant
Command line, by
malware software Anti-malware malware on diary
design, is only
to continuously software is not device controllers
accessible over
monitor and permitted on the through web 3 3
terminal connections
defend each of diary device application exploits
to the console port.
the organization's controllers while they operate in
workstations and clinical settings.
Bluetooth attacks
servers.
may still permit
malware
executables to be
uploaded to a file
space associated
with an anonymous
account. The web
admin application on
each controller has
been tested as
vulnerable to
arbitrary code
execution, cross-site
scripting, and other
attacks.
Utilize an active
discovery tool to
identify devices
connected to the
organization's
network and
update the
hardware asset
inventory.
Utilize a passive
discovery tool to
identify devices
connected to the
organization's
network and
automatically
update the
organization's
hardware asset
inventory.
Use Dynamic
Host
Configuration
Protocol (DHCP)
logging on all
DHCP servers or
IP address
management tools
to update the
organization's
hardware asset
inventory.
Maintain an
accurate and up-
to-date inventory
of all technology
assets with the
potential to store
or process
information. This
inventory shall
include all
hardware assets,
whether
connected to the
organization's
network or not.
Ensure that the
hardware asset
inventory records
the network
address,
hardware
address, machine
name, data asset
owner, and
department for
each asset and
whether the
hardware asset
has been
approved to
connect to the
network.
Ensure that
unauthorized
assets are either
removed from the
network,
quarantined or the
inventory is
updated in a
timely manner.
Use client
certificates to
authenticate
hardware assets
connecting to the
organization's
trusted network.
Maintain an up-to-
date list of all
authorized
software that is
required in the
enterprise for any
business purpose
on any business
system.
Utilize software
inventory tools
throughout the
organization to
automate the
documentation of
all software on
business systems.
The software
inventory system
should track the
name, version,
publisher, and
install date for all
software,
including
operating systems
authorized by the
organization.
The software
inventory system
should be tied into
the hardware
asset inventory so
all devices and
associated
software are
tracked from a
single location.
Ensure that
unauthorized
software is either
removed or the
inventory is
updated in a
timely manner
Utilize application
whitelisting
technology on all
assets to ensure
that only
authorized
software executes
and all
unauthorized
software is
blocked from
executing on
assets.
The organization's
application
whitelisting
software must
ensure that only
authorized
software libraries
(such as *.dll,
*.ocx, *.so, etc)
are allowed to
load into a system
process.
The organization's
application
whitelisting
software must
ensure that only
authorized,
digitally signed
scripts (such as
*.ps1,
*.py, macros, etc)
are allowed to run
on a system.
Physically or
logically
segregated
systems should
be used to isolate
and run software
that is required for
business
operations but
incur higher risk
for the
organization.
Utilize an up-to-
date SCAP-
compliant
vulnerability
scanning tool to
automatically scan
all systems on the
network on a
weekly or more
frequent basis to
identify all
potential
vulnerabilities on
the organization's
systems.
Perform
authenticated
vulnerability
scanning with
agents running
locally on each
system or with
remote scanners
that are
configured with
elevated rights on
the system being
tested.
Use a dedicated
account for
authenticated
vulnerability
scans, which
should not be
used for any other
administrative
activities and
should be tied to
specific machines
at specific IP
addresses.
Deploy automated
software update
tools in order to
ensure that the
operating systems
are running the
most recent
security updates
provided by the
software vendor.
Deploy automated
software update
tools in order to
ensure that third-
party software on
all systems is
running the most
recent security
updates provided
by the software
vendor.
Regularly
compare the
results from back-
to-back
vulnerability scans
to verify that
vulnerabilities
have been
remediated in a
timely manner.
Utilize a risk-rating
process to
prioritize the
remediation of
discovered
vulnerabilities.
Use automated
tools to inventory
all administrative
accounts,
including domain
and local
accounts, to
ensure that only
authorized
individuals have
elevated
privileges.
Before deploying
any new asset,
change all default
passwords to
have values
consistent with
administrative
level accounts.
Ensure that all
users with
administrative
account access
use a dedicated or
secondary
account for
elevated activities.
This account
should only be
used for
administrative
activities and not
internet browsing,
email, or similar
activities.
Where multi-factor
authentication is
not supported
(such as local
administrator,
root, or service
accounts),
accounts will use
passwords that
are unique to that
system.
Use multi-factor
authentication and
encrypted
channels for all
administrative
account access.
Ensure
administrators use
a dedicated
machine for all
administrative
tasks or tasks
requiring
administrative
access. This
machine will be
segmented from
the organization's
primary network
and not be
allowed Internet
access. This
machine will not
be used for
reading e-mail,
composing
documents, or
browsing the
Internet.
Limit access to
scripting tools
(such as Microsoft
PowerShell and
Python) to only
administrative or
development
users with the
need to access
those capabilities.
Configure
systems to issue a
log entry and alert
when an account
is added to or
removed from any
group assigned
administrative
privileges.
Configure
systems to issue a
log entry and alert
on unsuccessful
logins to an
administrative
account.
Maintain
documented,
standard security
configuration
standards for all
authorized
operating systems
and software.
Maintain secure
images or
templates for all
systems in the
enterprise based
on the
organization's
approved
configuration
standards. Any
new system
deployment or
existing system
that becomes
compromised
should be imaged
using one of those
images or
templates.
Utilize a Security
Content
Automation
Protocol (SCAP)
compliant
configuration
monitoring system
to verify all
security
configuration
elements, catalog
approved
exceptions, and
alert when
unauthorized
changes occur.
Ensure that
appropriate logs
are being
aggregated to a
central log
management
system for
analysis and
review.
Deploy Security
Information and
Event
Management
(SIEM) or log
analytic tool for
log correlation and
analysis.
On a regular
basis, review logs
to identify
anomalies or
abnormal events.
On a regular
basis, tune your
SIEM system to
better identify
actionable events
and decrease
event noise.
Ensure that only
fully supported
web browsers and
email clients are
allowed to
execute in the
organization,
ideally only using
the latest version
of the browsers
and email clients
provided by the
vendor.
Uninstall or
disable any
unauthorized
browser or email
client plugins or
add-on
applications.
Enforce network-
based URL filters
that limit a
system's ability to
connect to
websites not
approved by the
organization. This
filtering shall be
enforced for each
of the
organization's
systems, whether
they are physically
at an
organization's
facilities or not.
Subscribe to URL
categorization
services to ensure
that they are up-
to-date with the
most recent
website category
definitions
available.
Uncategorized
sites shall be
blocked by
default.
Use sandboxing
to analyze and
block inbound
email attachments
with malicious
behavior.
Utilize centrally
managed anti-
malware software
to continuously
monitor and
defend each of
the organization's
workstations and
servers.
Ensure that the
organization's
anti-malware
software updates
its scanning
engine and
signature
database on a
regular basis.
Enable anti-
exploitation
features such as
Data Execution
Prevention (DEP)
or Address Space
Layout
Randomization
(ASLR) that are
available in an
operating system
or deploy
appropriate
toolkits that can
be configured to
apply protection to
a broader set of
applications and
executables.
Configure devices
so that they
automatically
conduct an anti-
malware scan of
removable media
when inserted or
connected.
Configure devices
to not auto-run
content from
removable media.
Enable command-
line audit logging
for command
shells, such as
Microsoft
PowerShell and
Bash.
Associate active
ports, services
and protocols to
the hardware
assets in the
asset inventory.
Perform
automated port
scans on a regular
basis against all
systems and alert
if unauthorized
ports are detected
on a system.
Apply host-based
firewalls or port
filtering tools on
end systems, with
a default-deny
rule that drops all
traffic except
those services
and ports that are
explicitly allowed.
Place application
firewalls in front of
any critical
servers to verify
and validate the
traffic going to the
server. Any
unauthorized
traffic should be
blocked and
logged.
Maintain standard,
documented
security
configuration
standards for all
authorized
network devices.
All configuration
rules that allow
traffic to flow
through network
devices should be
documented in a
configuration
management
system with a
specific business
reason for each
rule, a specific
individual’s name
responsible for
that business
need, and an
expected duration
of the need.
Compare all
network device
configuration
against approved
security
configurations
defined for each
network device in
use and alert
when any
deviations are
discovered.
Manage all
network devices
using multi-factor
authentication and
encrypted
sessions.
Ensure network
engineers use a
dedicated
machine for all
administrative
tasks or tasks
requiring elevated
access. This
machine shall be
segmented from
the organization's
primary network
and not be
allowed Internet
access. This
machine shall not
be used for
reading e-mail,
composing
documents, or
surfing the
Internet.
Manage the
network
infrastructure
across network
connections that
are separated
from the business
use of that
network, relying
on separate
VLANs or,
preferably, on
entirely different
physical
connectivity for
management
sessions for
network devices.
Maintain an up-to-
date inventory of
all of the
organization's
network
boundaries.
Perform regular
scans from
outside each
trusted network
boundary to
detect any
unauthorized
connections which
are accessible
across the
boundary.
Deny
communications
with known
malicious or
unused Internet IP
addresses and
limit access only
to trusted and
necessary IP
address ranges at
each of the
organization's
network
boundaries,.
Deny
communication
over unauthorized
TCP or UDP ports
or application
traffic to ensure
that only
authorized
protocols are
allowed to cross
the network
boundary in or out
of the network at
each of the
organization's
network
boundaries.
Configure
monitoring
systems to record
network packets
passing through
the boundary at
each of the
organization's
network
boundaries.
Deploy network-
based Intrusion
Detection
Systems (IDS)
sensors to look for
unusual attack
mechanisms and
detect
compromise of
these systems at
each of the
organization's
network
boundaries.
Deploy network-
based Intrusion
Prevention
Systems (IPS) to
block malicious
network traffic at
each of the
organization's
network
boundaries.
Enable the
collection of
NetFlow and
logging data on all
network boundary
devices.
Decrypt all
encrypted network
traffic at the
boundary proxy
prior to analyzing
the content.
However, the
organization may
use whitelists of
allowed sites that
can be accessed
through the proxy
without decrypting
the traffic.
Require all remote
login access to
the organization's
network to encrypt
data in transit and
use multi-factor
authentication.
Scan all
enterprise devices
remotely logging
into the
organization's
network prior to
accessing the
network to ensure
that each of the
organization's
security policies
has been
enforced in the
same manner as
local network
devices.
Maintain an
inventory of all
sensitive
information
stored, processed,
or transmitted by
the organization's
technology
systems, including
those located
onsite or at a
remote service
provider.
Remove sensitive
data or systems
not regularly
accessed by the
organization from
the network.
These systems
shall only be used
as stand alone
systems
(disconnected
from the network)
by the business
unit needing to
occasionally use
the system or
completely
virtualized and
powered off until
needed.
Deploy an
automated tool on
network
perimeters that
monitors for
unauthorized
transfer of
sensitive
information and
blocks such
transfers while
alerting
information
security
professionals.
If USB storage
devices are
required,
enterprise
software should
be used that can
configure systems
to allow the use of
specific devices.
An inventory of
such devices
should be
maintained.
Configure
systems not to
write data to
external
removable media,
if there is no
business need for
supporting such
devices.
If USB storage
devices are
required, all data
stored on such
devices must be
encrypted while at
rest.
Segment the
network based on
the label or
classification level
of the information
stored on the
servers, locate all
sensitive
information on
separated Virtual
Local Area
Networks
(VLANs).
Enable firewall
filtering between
VLANs to ensure
that only
authorized
systems are able
to communicate
with other
systems
necessary to fulfill
their specific
responsibilities.
Disable all
workstation to
workstation
communication to
limit an attacker's
ability to move
laterally and
compromise
neighboring
systems, through
technologies such
as Private VLANs
or
microsegmentatio
n.
Encrypt all
sensitive
information in
transit.
Utilize an active
discovery tool to
identify all
sensitive
information
stored, processed,
or transmitted by
the organization's
technology
systems, including
those located
onsite or at a
remote service
provider and
update the
organization's
sensitive
information
inventory.
Protect all
information stored
on systems with
file system,
network share,
claims,
application, or
database specific
access control
lists. These
controls will
enforce the
principle that only
authorized
individuals should
have access to
the information
based on their
need to access
the information as
a part of their
responsibilities.
Use an automated
tool, such as host-
based Data Loss
Prevention, to
enforce access
controls to data
even when data is
copied off a
system.
Encrypt all
sensitive
information at rest
using a tool that
requires a
secondary
authentication
mechanism not
integrated into the
operating system,
in order to access
the information.
Enforce detailed
audit logging for
access to
sensitive data or
changes to
sensitive data
(utilizing tools
such as File
Integrity
Monitoring or
Security
Information and
Event Monitoring).
Maintain an
inventory of
authorized
wireless access
points connected
to the wired
network.
Configure network
vulnerability
scanning tools to
detect and alert
on unauthorized
wireless access
points connected
to the wired
network.
Use a wireless
intrusion detection
system (WIDS) to
detect and alert
on unauthorized
wireless access
points connected
to the network.
Disable wireless
access on devices
that do not have a
business purpose
for wireless
access.
Configure wireless
access on client
machines that do
have an essential
wireless business
purpose, to allow
access only to
authorized
wireless networks
and to restrict
access to other
wireless networks.
Disable peer-to-
peer (adhoc)
wireless network
capabilities on
wireless clients.
Leverage the
Advanced
Encryption
Standard (AES) to
encrypt wireless
data in transit.
Ensure that
wireless networks
use authentication
protocols such as
Extensible
Authentication
Protocol-
Transport Layer
Security
(EAP/TLS), that
requires mutual,
multi-factor
authentication.
Disable wireless
peripheral access
of devices (such
as Bluetooth and
NFC), unless such
access is required
for a business
purpose.
Create a separate
wireless network
for personal or
untrusted devices.
Enterprise access
from this network
should be treated
as untrusted and
filtered and
audited
accordingly.
Maintain an
inventory of each
of the
organization's
authentication
systems, including
those located
onsite or at a
remote service
provider.
Configure access
for all accounts
through as few
centralized points
of authentication
as possible,
including network,
security, and
cloud systems.
Require multi-
factor
authentication for
all user accounts,
on all systems,
whether managed
onsite or by a
third-party
provider.
Encrypt or hash
with a salt all
authentication
credentials when
stored.
Maintain an
inventory of all
accounts
organized by
authentication
system.
Establish and
follow an
automated
process for
revoking system
access by
disabling accounts
immediately upon
termination or
change of
responsibilities of
an employee or
contractor .
Disabling these
accounts, instead
of deleting
accounts, allows
preservation of
audit trails.
Disable any
account that
cannot be
associated with a
business process
or business
owner.
Automatically
disable dormant
accounts after a
set period of
inactivity.
Automatically lock
workstation
sessions after a
standard period of
inactivity.
Monitor attempts
to access
deactivated
accounts through
audit logging.
Alert when users
deviate from
normal login
behavior, such as
time-of-day,
workstation
location and
duration.
Perform a skills
gap analysis to
understand the
skills and
behaviors
workforce
members are not
adhering to, using
this information to
build a baseline
education
roadmap.
Deliver training to
address the skills
gap identified to
positively impact
workforce
members' security
behavior.
Create a security
awareness
program for all
workforce
members to
complete on a
regular basis to
ensure they
understand and
exhibit the
necessary
behaviors and
skills to help
ensure the
security of the
organization. The
organization's
security
awareness
program should
be communicated
in a continuous
and engaging
manner.
Train workforce
members on the
importance of
enabling and
utilizing secure
authentication.
Train the
workforce on how
to identify different
forms of social
engineering
attacks, such as
phishing, phone
scams and
impersonation
calls.
Train workforce
on how to identify
and properly
store, transfer,
archive and
destroy sensitive
information.
Train workforce
members to be
aware of causes
for unintentional
data exposures,
such as losing
their mobile
devices or
emailing the
wrong person due
to autocomplete in
email.
Train employees
to be able to
identify the most
common
indicators of an
incident and be
able to report
such an incident.
Establish secure
coding practices
appropriate to the
programming
language and
development
environment being
used.
For in-house
developed
software, ensure
that explicit error
checking is
performed and
documented for all
input, including for
size, data type,
and acceptable
ranges or formats.
Use only
standardized and
extensively
reviewed
encryption
algorithms.
Establish a
process to accept
and address
reports of
software
vulnerabilities,
including
providing a means
for external
entities to contact
your security
group.
Maintain separate
environments for
production and
nonproduction
systems.
Developers
should not have
unmonitored
access to
production
environments.
Protect web
applications by
deploying web
application
firewalls (WAFs)
that inspect all
traffic flowing to
the web
application for
common web
application
attacks. For
applications that
are not web-
based, specific
application
firewalls should be
deployed if such
tools are available
for the given
application type. If
the traffic is
encrypted, the
device should
either sit behind
the encryption or
be capable of
decrypting the
traffic prior to
analysis. If neither
option is
appropriate, a
host-based web
application firewall
should be
deployed.
For applications
that rely on a
database, use
standard
hardening
configuration
templates. All
systems that are
part of critical
business
processes should
also be tested.
Ensure that there
are written
incident response
plans that defines
roles of personnel
as well as phases
of incident
handling/manage
ment.
Designate
management
personnel, as well
as backups, who
will support the
incident handling
process by acting
in key decision-
making roles.
Devise
organization-wide
standards for the
time required for
system
administrators and
other workforce
members to report
anomalous events
to the incident
handling team, the
mechanisms for
such reporting,
and the kind of
information that
should be
included in the
incident
notification.
Assemble and
maintain
information on
third-party contact
information to be
used to report a
security incident,
such as Law
Enforcement,
relevant
government
departments,
vendors, and
ISAC partners.
Publish
information for all
workforce
members,
regarding
reporting
computer
anomalies and
incidents to the
incident handling
team. Such
information should
be included in
routine employee
awareness
activities.
Establish a
program for
penetration tests
that includes a full
scope of blended
attacks, such as
wireless, client-
based, and web
application
attacks.
Conduct regular
external and
internal
penetration tests
to identify
vulnerabilities and
attack vectors that
can be used to
exploit enterprise
systems
successfully.
Perform periodic
Red Team
exercises to test
organizational
readiness to
identify and stop
attacks or to
respond quickly
and effectively.
Include tests for
the presence of
unprotected
system
information and
artifacts that
would be useful to
attackers,
including network
diagrams,
configuration files,
older penetration
test reports, e-
mails or
documents
containing
passwords or
other information
critical to system
operation.
Wherever
possible, ensure
that Red Teams
results are
documented using
open, machine-
readable
standards (e.g.,
SCAP). Devise a
scoring method
for determining
the results of Red
Team exercises
so that results can
be compared over
time.
Any user or
system accounts
used to perform
penetration testing
should be
controlled and
monitored to
make sure they
are only being
used for legitimate
purposes, and are
removed or
restored to normal
function after
testing is over.
How
What impact What impact foreseeable is
could this could this What risk it that this
Risk -
threat pose to threat pose to Will we What would this safeguard risk
Likelihood x
our our accept, safeguard can recommended would occur
Highest
objectives? obligations? reduce, we use to control pose and create an
Impact Score.
transfer, or better to the impact?
Use risk Use risk avoid this implement the mission,
Acceptable
assessment assessment risk? CIS Control? objectives, or Use risk
risk < '9'
criteria as criteria as obligations? assessment
guidance guidance criteria as
guidance
Risk Safeguard
Objectives Obligations Recommende Safeguard
Risk Score Treatment Threat
Impact Impact d Safeguard Risk
Option Likelihood
4 2 4 Accept
4 2 4 Accept
All attempts at
accessing
SSH services
[CIS Control
in diary device
12.11]
controllers will
Require all
be blocked
usage of SSH
unless clients
and all
use soft-certs
authentication
to access
on diary
SSH
device
4 3 12 Reduce sessions. 1
controllers to
Attackers may
use soft-certs
seize and re-
stored on
use soft-certs
client devices
during 8-hour
as a second
long clinical
factor of
visits and may
authentication
attack
.
controllers as
a result.
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
What impact What impact What impact
could this could this could this
safeguard risk safeguard risk safeguard risk
pose to our pose to our pose to our
mission? objectives? obligations? Safeguard
Risk Score
Use risk Use risk Use risk
assessment assessment assessment
criteria as criteria as criteria as
guidance guidance guidance
0
0
3 3 2 3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
The risks stated in this risk register were identified by evaluating how
Summary well the CIS Controls are applied to information assets at [Name of
organization or scope of the assessment]
Misuse/Escalate Privilege:
Example Ransomware Malware encrypts the local storage
volume.
Misuse/Escalate Privilege:
Example Ransomware Malware encrypts the local storage
volume.
4
5
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
risk register were identified by evaluating how
e applied to information assets at [Name of
f the assessment]
Continuous Vulnerability
3.2
Management
Continuous Vulnerability
3.3
Management
Continuous Vulnerability
3.4
Management
Continuous Vulnerability
3.5
Management
Continuous Vulnerability
3.6
Management
Continuous Vulnerability
3.7
Management
Controlled Use of
4.1
Administrative Privileges
Controlled Use of
4.2
Administrative Privileges
Controlled Use of
4.3
Administrative Privileges
Controlled Use of
4.4
Administrative Privileges
Controlled Use of
4.5
Administrative Privileges
Controlled Use of
4.6
Administrative Privileges
Controlled Use of
4.7
Administrative Privileges
Controlled Use of
4.8
Administrative Privileges
Controlled Use of
4.9
Administrative Privileges
Implement a Security
Awareness and Training 17.2
Program
Implement a Security
Awareness and Training 17.3
Program
Implement a Security
Awareness and Training 17.4
Program
Implement a Security
Awareness and Training 17.5
Program
Implement a Security
Awareness and Training 17.6
Program
Implement a Security
Awareness and Training 17.7
Program
Implement a Security
Awareness and Training 17.8
Program
Implement a Security
Awareness and Training 17.9
Program
Title Description
Physically or logically
segregated systems should be
Physically or Logically Segregate High Risk used to isolate and run
Applications software that is required for
business operations but incur
higher risk for the organization.
Utilize an up-to-date SCAP-
compliant vulnerability
scanning tool to automatically
scan all systems on the
Run Automated Vulnerability Scanning Tools
network on a weekly or more
frequent basis to identify all
potential vulnerabilities on the
organization's systems.
Perform authenticated
vulnerability scanning with
agents running locally on each
Perform Authenticated Vulnerability Scanning system or with remote
scanners that are configured
with elevated rights on the
system being tested.
Where multi-factor
authentication is not supported
(such as local administrator,
Use Unique Passwords
root, or service accounts),
accounts will use passwords
that are unique to that system.
Subscribe to URL
categorization services to
ensure that they are up-to-date
Subscribe to URL-Categorization service with the most recent website
category definitions available.
Uncategorized sites shall be
blocked by default.
Enable anti-exploitation
features such as Data
Execution Prevention (DEP) or
Address Space Layout
Randomization (ASLR) that are
Enable Operating System Anti-Exploitation
available in an operating
Features/ Deploy Anti-Exploit Technologies
system or deploy appropriate
toolkits that can be configured
to apply protection to a broader
set of applications and
executables.
Maintain standard,
Maintain Standard Security Configurations for documented security
Network Devices configuration standards for all
authorized network devices.
Maintain an up-to-date
inventory of all of the
Maintain an Inventory of Network Boundaries
organization's network
boundaries.
Perform regular scans from
outside each trusted network
Scan for Unauthorized Connections across Trusted boundary to detect any
Network Boundaries unauthorized connections
which are accessible across
the boundary.
Deploy network-based
Intrusion Detection Systems
(IDS) sensors to look for
unusual attack mechanisms
Deploy Network-based IDS Sensor
and detect compromise of
these systems at each of the
organization's network
boundaries.
Deploy network-based
Intrusion Prevention Systems
Deploy Network-Based Intrusion Prevention (IPS) to block malicious
Systems network traffic at each of the
organization's network
boundaries.
Maintain an inventory of
Maintain an Inventory of Authorized Wireless authorized wireless access
Access Points points connected to the wired
network.
Maintain separate
environments for production
and nonproduction systems.
Separate Production and Non-Production Systems
Developers should not have
unmonitored access to
production environments.
Devise organization-wide
standards for the time required
for system administrators and
other workforce members to
Devise Organization-wide Standards for Reporting report anomalous events to the
Incidents incident handling team, the
mechanisms for such reporting,
and the kind of information that
should be included in the
incident notification.
Use risk assessment Use risk assessment Use risk assessment criteria Acceptable risk < '6'
criteria as guidance criteria as guidance as guidance
3 4 4 8
3 4 4 12
3 4 4 12
3 4 4 16
3 2 2 9
3 4 4 12
3 4 4 12
3 4 4 12
3 4 4 12
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
What risk would this
What safeguard can we
Will we accept, reduce, recommended control pose to
use to better implement the
transfer, or avoid this risk? the mission, objectives, or
CIS Control?
obligations?
Accept
2 1 2 1
3 2 2 4
3 2 2 4
3 2 2 4
2 1 2 1
2 1 2 1
2 3 2 1
2 4 2 1
Safeguard Risk
Score
Safeguard Risk
Score
12
12
12
4
6
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Community Attack Model (Top) The Community Attack Model (top) aligns the actions within an attack path with
Respond honeypot
Recover
describe the threats against assets that would occur in the attack path.
control of administrative
privilege
patching; hardened
continuous vulnerability control of admin privilege; data
configurations; HIPS; anti-
assessment; firewall; mail security; hardened
malware; containerization; app
gateway filtering; web filtering; configuration; continuous
whitelisting; Data Execution
secure remote access; NIPS vulnerability assessment
Protection
HIPS; anti-malware;
audit logs; Anti-malware; account monitoring; control of
containerization; app
Network Intrusion Detection admin privilege; audit logs;
whitelisting; Data Execution
system Configuration Monitoring
Prevention;
audit logs; Configuration
Incident Response - Execution Management; Account
Management
Asset: Email server, SMTP Asset: Email client, end-user Asset: End-user OS, storage
gateway. OS, personnel, proxy server, volume.
advanced malware appliance.
their environment correlations between CIS Controls and the Community Attack Model cells, they should add those controls.
sinkhole
egress filtering; NW
segmentation; data security
Impact
Impact to Our Mission Impact to Obligations
Score
Impact
Impact to Our Mission Impact to Objectives
Score
Impact
Impact to Obligations Impact to Our Mission
Score
We promote opportunities to
Our customers’ intellectual
households and small businesses
property must be kept confidential
Defined in our community by providing
to preserve their market
affordable financial products and
advantage.
advisory services.
A notable increase in
A single customer experiences
overextended customers occurs,
market repercussions based on a 4
but could be recovered over less
security incident.
than four fiscal years.
Impact
Impact to Objectives Impact to Obligations
Score