Patching Nist SP 1800 31b Draft

NIST SPECIAL PUBLICATION 1800-31B
Improving Enterprise Patching

for General IT Systems:
Utilizing Existing Tools and Performing Processes in
Better Ways
Volume B:
Security Risks and Capabilities
Tyler Diamond*
Alper Kerman
Murugiah Souppaya
National Cybersecurity Center of Excellence
Information Technology Laboratory
Brian Johnson
Chris Peloquin
Vanessa Ruffin
The MITRE Corporation
McLean, Virginia
Karen Scarfone
Scarfone Cybersecurity
Clifton, Virginia
*Former employee; all work for this publication was done while at employer
November 2021
DRAFT
This publication is available free of charge from

https://www.nccoe.nist.gov/projects/building-blocks/patching-enterprise
DRAFT
1 DISCLAIMER
2 Certain commercial entities, equipment, products, or materials may be identified by name or company
3 logo or other insignia in order to acknowledge their participation in this collaboration or to describe an
4 experimental procedure or concept adequately. Such identification is not intended to imply special sta-
5 tus or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it in-
6 tended to imply that the entities, equipment, products, or materials are necessarily the best available
7 for the purpose.
8 National Institute of Standards and Technology Special Publication 1800-31B, Natl. Inst. Stand. Technol.
9 Spec. Publ. 1800-31B, 49 pages, (November 2021), CODEN: NSPUE2
10 FEEDBACK
11 You can improve this guide by contributing feedback. As you review and adopt this solution for your
12 own organization, we ask you and your colleagues to share your experience and advice with us.
13 Comments on this publication may be submitted to: [email protected].
14 Public comment period: November 17, 2021 through January 10, 2022
15 All comments are subject to release under the Freedom of Information Act.
16 National Cybersecurity Center of Excellence

17 National Institute of Standards and Technology
18 100 Bureau Drive
19 Mailstop 2002
20 Gaithersburg, MD 20899
21 Email: [email protected]
NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems ii

DRAFT
22 NATIONAL CYBERSECURITY CENTER OF EXCELLENCE

23 The National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards
24 and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and
25 academic institutions work together to address businesses’ most pressing cybersecurity issues. This
26 public-private partnership enables the creation of practical cybersecurity solutions for specific
27 industries, as well as for broad, cross-sector technology challenges. Through consortia under
28 Cooperative Research and Development Agreements (CRADAs), including technology partners—from
29 Fortune 50 market leaders to smaller companies specializing in information technology security—the
30 NCCoE applies standards and best practices to develop modular, adaptable example cybersecurity
31 solutions using commercially available technology. The NCCoE documents these example solutions in
32 the NIST Special Publication 1800 series, which maps capabilities to the NIST Cybersecurity Framework
33 and details the steps needed for another entity to re-create the example solution. The NCCoE was
34 established in 2012 by NIST in partnership with the State of Maryland and Montgomery County,
35 Maryland.
36 To learn more about the NCCoE, visit https://www.nccoe.nist.gov/. To learn more about NIST, visit
37 https://www.nist.gov.
38 NIST CYBERSECURITY PRACTICE GUIDES

39 NIST Cybersecurity Practice Guides (Special Publication 1800 series) target specific cybersecurity
40 challenges in the public and private sectors. They are practical, user-friendly guides that facilitate the
41 adoption of standards-based approaches to cybersecurity. They show members of the information
42 security community how to implement example solutions that help them align with relevant standards
43 and best practices, and provide users with the materials lists, configuration files, and other information
44 they need to implement a similar approach.
45 The documents in this series describe example implementations of cybersecurity practices that
46 businesses and other organizations may voluntarily adopt. These documents do not describe regulations
47 or mandatory practices, nor do they carry statutory authority.
48 ABSTRACT
49 Despite widespread recognition that patching is effective and attackers regularly exploit unpatched
50 software, many organizations do not adequately patch. There are myriad reasons why, not the least of
51 which are that it’s resource-intensive and that the act of patching can reduce system and service
52 availability. Also, many organizations struggle to prioritize patches, test patches before deployment, and
53 adhere to policies for how quickly patches are applied in different situations. To address these
54 challenges, the NCCoE is collaborating with cybersecurity technology providers to develop an example
55 solution that addresses these challenges. This NIST Cybersecurity Practice Guide explains how tools can
56 be used to implement the patching and inventory capabilities organizations need to handle both routine
NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems iii

DRAFT
57 and emergency patching situations, as well as implement workarounds, isolation methods, or other
58 alternatives to patching. It also explains recommended security practices for patch management
59 systems themselves.
60 KEYWORDS
61 cyber hygiene; enterprise patch management; firmware; patch; patch management; software; update;
62 upgrade; vulnerability management
63 ACKNOWLEDGMENTS
64 We are grateful to the following individuals for their generous contributions of expertise and time.
Name Organization
Peter Romness Cisco
Matthew Hyatt Cisco
John Loucaides Eclypsium
Travis Raines Eclypsium
Timothy Jones Forescout
Tom May Forescout
Michael Correa Forescout
Jeffrey Ward IBM MaaS360 with Watson
Joseph Linehan IBM MaaS360 with Watson
Cesare Coscia IBM MaaS360 with Watson
Jim Doran IBM Research Team
Shripad Nadgowda IBM Research Team
Victoria Mosby Lookout
NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems iv

DRAFT
Name Organization
Tim LeMaster Lookout
Dan Menicucci Microsoft
Steve Rachui Microsoft
Parisa Grayeli The MITRE Corporation
Yemi Fashina The MITRE Corporation
Nedu Irrechukwu The MITRE Corporation
Joshua Klosterman The MITRE Corporation
Allen Tan The MITRE Corporation
Josh Moll Tenable
Chris Jensen Tenable
Jeremiah Stallcup Tenable
John Carty VMware
Kevin Hansen VMware
Rob Robertson VMware
Rob Hilberding VMware
Brian Williams VMware
65
66 The Technology Partners/Collaborators who participated in this build submitted their capabilities in
67 response to a notice in the Federal Register. Respondents with relevant capabilities or product
68 components were invited to sign a Cooperative Research and Development Agreement (CRADA) with
69 NIST, allowing them to participate in a consortium to build this example solution. We worked with:
NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems v

DRAFT
Technology Partner/Collaborator Build Involvement
Cisco Cisco Firepower Threat Defense (FTD)

Cisco Identity Services Engine (ISE)
Eclypsium Eclypsium Administration and Analytics Service
Forescout Forescout Platform
IBM IBM Code Risk Analyzer

IBM MaaS360 with Watson
Lookout Lookout Mobile Endpoint Security
Microsoft Microsoft Endpoint Configuration Manager
Tenable Nessus
Tenable.io
Tenable.sc
VMware VMware vRealize Automation SaltStack Config
70 DOCUMENT CONVENTIONS
71 The terms “shall” and “shall not” indicate requirements to be followed strictly to conform to the
72 publication and from which no deviation is permitted. The terms “should” and “should not” indicate that
73 among several possibilities, one is recommended as particularly suitable without mentioning or
74 excluding others, or that a certain course of action is preferred but not necessarily required, or that (in
75 the negative form) a certain possibility or course of action is discouraged but not prohibited. The terms
76 “may” and “need not” indicate a course of action permissible within the limits of the publication. The
77 terms “can” and “cannot” indicate a possibility and capability, whether material, physical, or causal.
78 CALL FOR PATENT CLAIMS

79 This public review includes a call for information on essential patent claims (claims whose use would be
80 required for compliance with the guidance or requirements in this Information Technology Laboratory
81 (ITL) draft publication). Such guidance and/or requirements may be directly stated in this ITL Publication
NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems vi

DRAFT
82 or by reference to another publication. This call also includes disclosure, where known, of the existence
83 of pending U.S. or foreign patent applications relating to this ITL draft publication and of any relevant
84 unexpired U.S. or foreign patents.
85 ITL may require from the patent holder, or a party authorized to make assurances on its behalf, in writ-
86 ten or electronic form, either:
87 a) assurance in the form of a general disclaimer to the effect that such party does not hold and does not
88 currently intend holding any essential patent claim(s); or
89 b) assurance that a license to such essential patent claim(s) will be made available to applicants desiring
90 to utilize the license for the purpose of complying with the guidance or requirements in this ITL draft
91 publication either:
92 1. under reasonable terms and conditions that are demonstrably free of any unfair discrimination;
93 or
94 2. without compensation and under reasonable terms and conditions that are demonstrably free
95 of any unfair discrimination.
96 Such assurance shall indicate that the patent holder (or third party authorized to make assurances on its
97 behalf) will include in any documents transferring ownership of patents subject to the assurance, provi-
98 sions sufficient to ensure that the commitments in the assurance are binding on the transferee, and that
99 the transferee will similarly include appropriate provisions in the event of future transfers with the goal
100 of binding each successor-in-interest.
101 The assurance shall also indicate that it is intended to be binding on successors-in-interest regardless of
102 whether such provisions are included in the relevant transfer documents.
103 Such statements should be addressed to: [email protected]
NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems vii

DRAFT
104 Contents
105 1 Summary .............................................................................................. 1
106 1.1 Challenge ....................................................................................................................... 1
107 1.2 Solution.......................................................................................................................... 2
108 1.3 Benefits.......................................................................................................................... 2
109 2 How to Use This Guide ......................................................................... 2
110 2.1 Typographic Conventions .............................................................................................. 4
111 3 Approach ............................................................................................. 5
112 3.1 Audience ........................................................................................................................ 5
113 3.2 Scope ............................................................................................................................. 5
114 3.3 Assumptions .................................................................................................................. 6
115 3.4 Scenarios ....................................................................................................................... 6
116 3.4.1 Scenario 0: Asset identification and assessment ..........................................................6
117 3.4.2 Scenario 1: Routine patching ........................................................................................6
118 3.4.3 Scenario 2: Routine patching with cloud delivery model .............................................7
119 3.4.4 Scenario 3: Emergency patching ...................................................................................7
120 3.4.5 Scenario 4: Emergency workaround (and backout if needed) .....................................7
121 3.4.6 Scenario 5: Isolation of unpatchable assets..................................................................7
122 3.4.7 Scenario 6: Patch management system security (or other system with administrative
123 privileged access) ..........................................................................................................8
124 3.5 Risk Assessment ............................................................................................................ 8
125 3.5.1 Threats, Vulnerabilities, and Risks ................................................................................8
126 3.5.2 Security Control Map ....................................................................................................9
127 4 Components of the Example Solution ................................................ 13

128 4.1 Collaborators ............................................................................................................... 13
129 4.1.1 Cisco ............................................................................................................................13
130 4.1.2 Eclypsium ....................................................................................................................13
131 4.1.3 Forescout ....................................................................................................................13
132 4.1.4 IBM ..............................................................................................................................14
NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems viii

DRAFT
133 4.1.5 Lookout .......................................................................................................................14

134 4.1.6 Microsoft .....................................................................................................................14
135 4.1.7 Tenable .......................................................................................................................15
136 4.1.8 VMware.......................................................................................................................15
137 4.2 Technologies................................................................................................................ 15
138 4.2.1 Cisco Firepower Threat Defense (FTD) & Firepower Management Center (FMC) .....17
139 4.2.2 Cisco Identity Services Engine (ISE).............................................................................17
140 4.2.3 Eclypsium Administration and Analytics Service ........................................................17
141 4.2.4 Forescout Platform .....................................................................................................18
142 4.2.5 IBM Code Risk Analyzer ..............................................................................................19
143 4.2.6 IBM MaaS360 with Watson ........................................................................................19
144 4.2.7 Lookout .......................................................................................................................20
145 4.2.8 Microsoft Endpoint Configuration Manager...............................................................20
146 4.2.9 Tenable.io ...................................................................................................................20
147 4.2.10 Tenable.sc and Nessus ................................................................................................20
148 4.2.11 VMware vRealize Automation SaltStack Config .........................................................21
149 Appendix A Patch Management System Security Practices .................... 22

150 A.1 Security Measures ....................................................................................................... 22
151 A.2 Component Support of Security Measures ................................................................. 26
152 A.2.1 Cisco FTD Support of Security Measures ....................................................................26
153 A.2.2 Cisco ISE Support of Security Measures......................................................................28
154 A.2.3 Eclypsium Administration and Analytics Service Support of Security Measures .......30
155 A.2.4 Forescout Platform Support of Security Measures.....................................................32
156 A.2.5 IBM Code Risk Analyzer Support of Security Measures..............................................34
157 A.2.6 IBM MaaS360 with Watson Support of Security Measures .......................................37
158 A.2.7 Lookout MES Support of Security Measures ..............................................................38
159 A.2.8 Microsoft Endpoint Configuration Manager (ECM) Support of Security Measures ...40
160 A.2.9 Tenable.sc Support of Security Measures ..................................................................42
161 A.2.10 VMware vRealize Automation SaltStack Config Support of Security Measures .........44
162 Appendix B List of Acronyms .................................................................. 47
NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems ix

DRAFT
163 List of Tables

164 Table 3-1: Mapping Security Characteristics of the Example Solution for Scenarios 0-5 ...................... 10
165 Table 3-2: Mapping Security Characteristics of the Example Solution for Scenario 6 ........................... 12
166 Table 4-1: Technologies Used in the Build .........................................................................................16
NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems x

DRAFT
167 1 Summary
168 The National Cybersecurity Center of Excellence (NCCoE) at the National Institute of Standards and
169 Technology (NIST) recognizes the challenges that organizations face in keeping software up to date with
170 patches. Patches correct security and functionality problems in software and firmware. From a security
171 perspective, patches are most often of interest because they are mitigating software flaw vulnerabilities;
172 applying patches to eliminate these vulnerabilities significantly reduces the opportunities for
173 exploitation.
174 Patches serve other purposes than just fixing software flaws; they can also add new features to software
175 and firmware, including security capabilities. Sometimes there are alternatives to patches, such as
176 temporary workarounds involving software or security control reconfiguration, but these workarounds
177 are not permanent fixes and they may impact functionality.
178 The NCCoE developed the Critical Cybersecurity Hygiene: Patching the Enterprise (Patching) project to
179 provide approaches for improving enterprise patching practices for general information technology (IT)
180 systems. The aim is to help organizations balance security with mission impact and business objectives.
181 This project utilizes commercial tools to aid with functions that include asset discovery characterization
182 and prioritization, and patch implementation tracking and verification. It includes actionable and
183 prescriptive guidance on establishing policies and processes for the entire patching lifecycle. This
184 volume explains why we built the example solution to address patching challenges, including the risk
185 analysis we performed and the security capabilities that the example solution provides.
186 1.1 Challenge

187 There are a few root causes for many data breaches, malware infections such as ransomware, and other
188 security incidents, and known—but unpatched—vulnerabilities in software are one of them.
189 Implementing a few security hygiene practices, such as patching operating systems, applications, and
190 firmware, can address those root causes. That prevents many incidents from occurring by minimizing
191 the attack surface and lowers the potential impact of incidents that occur. In other words, security
192 hygiene practices make it harder for attackers to succeed and reduce the damage they can cause.
193 Unfortunately, security hygiene is easier said than done. Despite widespread recognition that (a)
194 patching is effective and (b) attackers regularly exploit unpatched software, many organizations do not
195 adequately patch. There are myriad reasons why, not the least of which are that it is resource-intensive
196 and that the act of patching is perceived to reduce system and service availability. However, delaying
197 patch deployment gives attackers a larger window of opportunity to take advantage of the exposure.
198 Many organizations struggle to inventory their assets, prioritize patches, have defined and consistent
199 process and procedures for deployment, and adhere to policies and metrics for how quickly patches are
200 applied in different situations. Also, deploying enterprise patch management tools that operate with
NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems 1

DRAFT
201 privileged access within an enterprise can itself create additional security risks for an organization if the
202 tools are not secured properly.
203 1.2 Solution

204 To address these challenges, the NCCoE is collaborating with cybersecurity technology providers to
205 develop an example solution. It will demonstrate how tools can be used to 1) implement the inventory
206 and patching capabilities organizations need to handle both routine and emergency patching situations,
207 as well as 2) implement workarounds, isolation methods, or other alternatives to patching. The solution
208 will also demonstrate recommended security practices for protecting the patch management systems
209 themselves against threats.
210 This draft covers both phases of the example solution, which involves patching, updating, and
211 configuring two types of general IT assets. Phase 1 focuses on desktop and laptop computers and on-
212 premises servers, and phase 2 adds mobile devices and containers.
213 The NCCoE has also created a companion publication, NIST Special Publication (SP) 800-40 Revision 4
214 (Draft), Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology. It
215 complements the implementation focus of this guide by recommending creation of an enterprise
216 strategy to simplify and operationalize patching while also reducing risk.
217 1.3 Benefits

218 The demonstrated approach offers several benefits to organizations that implement it, including the
219 following:
220  Vulnerabilities in the organization’s IT systems that are susceptible to cyber attacks are
221 addressed more quickly, which reduces risk and lowers the likelihood of an incident occurring.
222  Increased automation provides a traceable and repeatable process and leads to a decrease in
223 hours worked by the organization’s security administrators, system administrations, and others
224 who have patching responsibilities.
225  It improves compliance with laws, regulations, mandates, local organization policy, and other
226 requirements to keep the organization’s software patched.
227  The practices it demonstrates can play an important role as your organization embarks on a
228 journey to zero trust.
229 2 How to Use This Guide

230 This NIST Cybersecurity Practice Guide demonstrates a standards-based example solution and provides
231 users with the information they need to replicate the proposed approach for improving enterprise

DRAFT
232 patching practices for general IT systems. This design is modular and can be deployed in whole or in
233 part.
234 This guide contains three volumes:
235  NIST SP 1800-31A: Executive Summary – why we wrote this guide, the challenge we address,
236 why it could be important to your organization, and our approach to solving the challenge
237  NIST SP 1800-31B: Security Risks and Capabilities – why we built the example implementation,
238 including the risk analysis performed and the security capabilities provided by the
239 implementation (you are here)
240  NIST SP 1800-31C: How-To Guides – what we built, with instructions for building the example
241 implementation, including all the details that would allow you to replicate all or parts of this
242 project
243 Depending on your role in your organization, you might use this guide in different ways:
244 Business decision makers, including chief security and technology officers, will be interested in the
245 Executive Summary, NIST SP 1800-31A, which describes the following topics:
246  challenges that enterprises face in mitigating risk from software vulnerabilities
247  example solution built at the NCCoE
248  benefits of adopting the example solution
249 Business decision makers can also use NIST SP 800-40 Revision 4 (Draft), Guide to Enterprise Patch
250 Management Planning: Preventive Maintenance for Technology.
251 Technology or security program managers who are concerned with how to identify, understand, assess,
252 and mitigate risk will be interested in this part of the guide, NIST SP 1800-31B, which describes what we
253 did and why. The following sections will be of particular interest:
254  Section 3.5.1, Threats, Vulnerabilities, and Risks, provides a description of the risk analysis we
255 performed.
256  Section 3.5.2, Security Control Map, maps the security characteristics of this example solution to
257 cybersecurity standards and best practices.
258 You might share the Executive Summary, NIST SP 1800-31A, with your leadership team members to help
259 them understand the importance of adopting standards-based, automated patch management. Also,
260 NIST SP 800-40 Revision 4 (Draft), Guide to Enterprise Patch Management Planning: Preventive
261 Maintenance for Technology may be helpful to you and your leadership team.
262 IT professionals who may be interested in implementing an approach similar to ours will find the entire
263 practice guide useful. In particular, the How-To portion of the guide, NIST SP 1800-31C could be used to
264 replicate all or parts of the build created in our lab. Furthermore, the How-To portion of the guide

DRAFT
265 provides specific product installation, configuration, and integration instructions for implementing the
266 example solution. We have omitted the general installation and configuration steps outlined in
267 manufacturers’ product documentation since they are typically made available by manufacturers.
268 Instead, we focused on describing how we incorporated the products together in our environment to
269 create the example solution.
270 This guide assumes that the reader of this document is a seasoned IT professional with experience in
271 implementing security solutions within an enterprise setting. While we have used a suite of commercial
272 products to address this challenge, this guide does not endorse these particular products. Your
273 organization can adopt this solution or one that adheres to these guidelines in whole, or you can use this
274 guide as a starting point for tailoring and implementing parts of an automated enterprise patch
275 management system. Your organization’s security experts should identify the products that will best
276 integrate with your existing tools and IT system infrastructure. We hope that you will seek products that
277 are congruent with applicable standards and recommended practices. Section 4.2, Technologies, lists
278 the products we used and maps them to the cybersecurity controls provided by this example solution.
279 A NIST Cybersecurity Practice Guide does not describe “the” solution, but a possible solution. This is a
280 draft guide. We seek feedback on its contents and welcome your input. Comments, suggestions, and
281 success stories will improve subsequent versions of this guide. Please contribute your thoughts to
282 [email protected].
283 2.1 Typographic Conventions

284 The following table presents typographic conventions used in this volume.
Typeface/Symbol Meaning Example

Italics file names and path names; references For language use and style guidance,
to documents that are not hyperlinks; see the NCCoE Style Guide.
new terms; and placeholders
Bold names of menus, options, command Choose File > Edit.
buttons, and fields
Monospace command-line input, onscreen mkdir
computer output, sample code
examples, and status codes
Monospace Bold command-line user input contrasted service sshd start
with computer output

DRAFT
Typeface/Symbol Meaning Example

blue text link to other parts of the document, a All publications from NIST’s NCCoE are
web URL, or an email address available at
https://www.nccoe.nist.gov.
285 3 Approach
286 The NCCoE issued an open invitation to technology providers to participate in demonstrating how
287 organizations can use technologies to improve enterprise patch management for their general IT assets.
288 Cooperative Research and Development Agreements (CRADAs) were established with qualified
289 respondents, and a build team was assembled. The team fleshed out the initial architecture, and the
290 collaborators’ components were composed into an example implementation, i.e., build. The build team
291 documented the architecture and design of the build. As the build progressed, the team documented
292 the steps taken to install and configure each component of the build.
293 Finally, the team verified that the build provided the desired capabilities. This included conducting a risk
294 assessment and a security characteristic analysis, then documenting the results, including mapping the
295 security contributions of the demonstrated approach to the Framework for improving Critical
296 Infrastructure Cybersecurity (NIST Cybersecurity Framework), NIST SP 800-53, the Security Measures for
297 “EO-Critical Software” Use Under Executive Order (EO) 14028, and other relevant standards and
298 guidelines.
299 3.1 Audience

300 This guide is intended for chief information officers (CIOs), chief information security officers (CISOs),
301 cybersecurity directors and managers, and others who are responsible for managing organizational risk
302 related to patch management. It also contains information of use for security engineers and architects,
303 system administrators, security operations personnel, and others who are involved in enterprise patch
304 management.
305 3.2 Scope

306 This project only covers general IT systems: desktops/laptops, servers, virtual machines and containers,
307 and mobile devices running current software. There are additional challenges with patching legacy IT
308 systems, as well as industrial control systems (ICS), Internet of Things (IoT) devices, and other
309 technologies stemming from operational technology (OT), so they will not be covered in this project.
310 All aspects of security hygiene other than those related to patching are out of the scope of this project.

DRAFT
311 3.3 Assumptions

312 This project is guided by the following assumptions:
313  An IT endpoint for an enterprise would have firmware, operating system(s), and application(s) to
314 be patched. The endpoint may be in a fixed location within the organization’s own facilities or in
315 a fixed location at a third-party facility (e.g., a data center), or it may be intended for use in
316 multiple locations, such as a laptop used at the office and for telework. The proposed approach
317 for improving enterprise patching practices would have to account for all these possibilities.
318  Problems sometimes occur with patches, such as a failure during installation, a patch that
319 cannot take effect until the endpoint is rebooted, or a patch that is uninstalled because of
320 operational concerns or because an attacker rolled it back in order to have an entry point to the
321 system. This project follows a “verify everything and trust nothing” philosophy that does not
322 assume installing a patch automatically means the patch is successfully and permanently
323 applied.
324  There are no standard protocols, formats, etc. for patch management, including patch
325 distribution, integrity verification, installation, and installation verification. It is also highly
326 unlikely for a single patch management system to be able to handle all patch management
327 responsibilities for all software on IT endpoints. For example, some applications may handle
328 patching themselves and not be capable of integrating with a patch management system for
329 patch acquisition and installation.
330 3.4 Scenarios

331 This project will address all the scenarios described below.
332 3.4.1 Scenario 0: Asset identification and assessment

333 This scenario identifies the assets and classifies them based on vulnerability impact levels to prioritize
334 the order of remediation. It leverages tools to discover assets across the enterprise and the cloud and to
335 enumerate their firmware, operating systems (OSes), and applications. Knowing which software and
336 software versions are in use and predetermining remediation priorities are critically important to all
337 other patching processes. Without accurate, up-to-date, and comprehensive information, an
338 organization will have difficulties effectively and efficiently performing patching processes, thus
339 increasing risk. While many enterprises have constant asset attrition, it is important to have full and
340 accurate inventory of critical assets and the best possible inventory for the full enterprise.
341 3.4.2 Scenario 1: Routine patching

342 This is the standard procedure for patches that are on a regular release cycle and haven’t been elevated
343 to an active emergency status (see Scenario 3). Routine patching includes endpoint firmware, OS, and
344 applications, and server OS and applications hosted on-premises or in the cloud (e.g., Infrastructure as a

DRAFT
345 Service). Most patching falls under this scenario or Scenario 2. However, because routine patching does
346 not have the urgency of emergency patching, and routine patch installation can interrupt operations
347 (e.g., device reboots), it is often postponed and otherwise neglected. This provides many additional
348 windows of opportunity for attackers.
349 3.4.3 Scenario 2: Routine patching with cloud delivery model

350 This is the standard procedure for patches that are delivered through a cloud delivery model, such as a
351 mobile device or a “Windows as a Service (WaaS)” model with Windows operating systems, Apple
352 Software Update, and mobile device software updates for Android and iOS devices provided by device
353 manufacturers or mobile operators. This scenario is similar in importance to Scenario 1, Routine
354 Patching. However, organizations may not be as accustomed to cloud-delivered patches (which are
355 frequently cumulative for the whole system vs. discrete patches), so this scenario is somewhat more
356 likely to be overlooked by organizations, which increases risk.
357 3.4.4 Scenario 3: Emergency patching

358 This is the emergency procedure to address active patching emergencies in a crisis situation, such as
359 extreme severity vulnerabilities like MS17-010, as well as vulnerabilities that are being actively exploited
360 in the wild. The scope of targets is the same as scenario 1. Emergency patching needs to be handled as
361 efficiently as possible to prevent imminent exploitation of vulnerable devices. Key characteristics include
362 identifying vulnerable assets, triaging and applying patches based on a priority list, and tracking and
363 monitoring the state of those assets.
364 3.4.5 Scenario 4: Emergency workaround (and backout if needed)

365 This is the emergency procedure in a crisis situation to temporarily mitigate risk for vulnerabilities prior
366 to a vendor releasing a patch. It is typically required when the vulnerability is being actively exploited in
367 the wild. The workaround can vary and may or may not need to be rolled back afterward. The scope of
368 targets is the same as scenario 1. Organizations need to be prepared to quickly implement a wide
369 variety of emergency workarounds to protect vulnerable devices. Without processes, procedures, and
370 tools in place to implement workarounds, too much time may be lost and vulnerable devices may be
371 compromised before workarounds are in place. This may require disabling system functionality, having
372 automated mechanisms to apply these changes, and having capabilities to revert back these changes
373 when a permanent and approved patch is released.
374 3.4.6 Scenario 5: Isolation of unpatchable assets

375 This is the reference architecture and implementation of isolation methods to mitigate the risk of
376 systems which cannot be easily patched. This is typically required if routine patching is not able to
377 accommodate these systems within a reasonable timeframe (usually X days or less). Most systems in
378 this scope are legacy unsupported systems or systems with very high operational uptime requirements.

DRAFT
379 Isolation is a form of workaround that can be highly effective at stopping threats against vulnerable
380 devices. Organizations need to be prepared to implement isolation methods when needed and to undo
381 the isolation at the appropriate time to restore regular device access and functionality.
382 3.4.7 Scenario 6: Patch management system security (or other system with
383 administrative privileged access)
384 This is a reference architecture and implementation of recommended security practices for systems like
385 patch management systems which have administrative privileged access over many other systems. This
386 will include practices like least privilege, privileged access workstations, and software updates.
387 3.5 Risk Assessment

388 NIST SP 800-30 Revision 1, Guide for Conducting Risk Assessments, states that risk is “a measure of the
389 extent to which an entity is threatened by a potential circumstance or event, and typically a function of:
390 (i) the adverse impacts that would arise if the circumstance or event occurs; and (ii) the likelihood of
391 occurrence.” The guide further defines risk assessment as “the process of identifying, estimating, and
392 prioritizing risks to organizational operations (including mission, functions, image, reputation),
393 organizational assets, individuals, other organizations, and the Nation, resulting from the operation of
394 an information system. Part of risk management incorporates threat and vulnerability analyses, and
395 considers mitigations provided by security controls planned or in place.”
396 The NCCoE recommends that any discussion of risk management, particularly at the enterprise level,
397 begins with a comprehensive review of NIST SP 800-37 Revision 2, Risk Management Framework for
398 Information Systems and Organizations—material that is available to the public. The Risk Management
399 Framework (RMF) guidance, as a whole, proved to be invaluable in giving us a baseline to assess risks,
400 from which we developed the project, the security characteristics of the build, and this guide. Also, the
401 NIST Cybersecurity Framework and NIST SP 800-53 Revision 5, Security and Privacy Controls for
402 Information Systems and Organizations informed our risk assessment and subsequent
403 recommendations from which we developed the security characteristics of the build and this guide.
404 3.5.1 Threats, Vulnerabilities, and Risks

405 The objective of this project is to demonstrate example solutions for each of the scenarios described in
406 Section 3.4. Scenarios 0 through 5 collectively address improving the mitigation of software
407 vulnerabilities in small to large IT enterprises for general IT assets. The last scenario, Scenario 6 (see
408 Section 3.4.7) focuses on the security of the patch management technologies themselves. Scenario 6 has
409 a different set of threats, vulnerabilities, and risks than the other scenarios, so it is discussed separately
410 in this section.

DRAFT
411 Scenarios 0 through 5
412 Collectively, the objective of Scenarios 0 through 5 is to ensure that software vulnerabilities are
413 mitigated, either through patching or by using additional security controls, for firmware, operating
414 systems, applications, and any other forms of software. The pertinent threats encompass the enormous
415 range of attackers and attacks that target software vulnerabilities. Major risks can be grouped into three
416 categories:
417  Vulnerabilities aren’t mitigated, leaving them susceptible to compromise. Potential causes of
418 this include organizations being unaware of vulnerabilities or vulnerable assets, patching being
419 delayed because of limited resources, users declining to install patches or reboot devices in
420 order for patches to take effect, and organizations choosing not to implement workarounds or
421 isolation techniques to protect unpatchable assets.
422  Installing patches causes unintended side effects. Examples include breaking the patched
423 software or other software on the asset, inadvertently altering configuration settings to weaken
424 security, adding software functionality without adequately securing that functionality, and
425 disrupting interoperability with other software or assets.
426  Patch integrity is compromised. A patch’s integrity could be compromised at several places in
427 the path from vendor to asset. Examples include the software vendor itself being compromised,
428 the organization downloading patches from an unauthorized source, patches being tampered
429 with while in transit to the organization, and patches being altered in storage at the
430 organization.
431 Scenario 6
432 The objective of Scenario 6 is to protect the example solution itself from compromise. To be effective,
433 the example solution requires administrative privileged access for many assets, so this makes it an
434 attractive target for attackers. The example solution also holds sensitive information regarding what
435 computing assets the organization has and what vulnerabilities each asset has, so safeguarding this
436 information from attackers is important. Vulnerabilities that the example solution might have include
437 software vulnerabilities in its own components, misconfigurations, and security design errors, such as
438 not encrypting its network communications.
439 3.5.2 Security Control Map

440 Table 3-1 provides a security mapping for Scenarios 0 through 5. It maps the characteristics of the
441 commercial products that the NCCoE has applied to the applicable standards and best practices
442 described in the Framework for Improving Critical Infrastructure Cybersecurity (Cybersecurity
443 Framework) [1] and NIST SP 800-53 Revision 5. This exercise is meant to demonstrate the real-world
444 applicability of standards and recommended practices, but does not imply that products with these
445 characteristics will meet your industry's requirements for regulatory approval or accreditation.

DRAFT
446 Table 3-1: Mapping Security Characteristics of the Example Solution for Scenarios 0-5
Cybersecurity Framework Cybersecurity Framework SP 800-53 Revision 5

Category Subcategory Controls
Asset Management (ID.AM): ID.AM-1: Physical devices and CM-8, System Component
The data, personnel, devices, systems within the organization Inventory
systems, and facilities that are inventoried
enable the organization to ID.AM-2: Software platforms and CM-8, System Component
achieve business purposes are applications within the Inventory
identified and managed organization are inventoried
consistent with their relative
importance to organizational
objectives and the
organization’s risk strategy.
Identity Management, PR.AC-4: Access permissions and AC-3, Access Enforcement
Authentication and Access authorizations are managed,
Control (PR.AC): Access to incorporating the principles of
physical and logical assets and least privilege and separation of
associated facilities is limited to duties
authorized users, processes, PR.AC-5: Network integrity is AC-3, Access Enforcement
and devices, and is managed protected (e.g., network
consistent with the assessed segregation, network
risk of unauthorized access to segmentation)
authorized activities and
transactions.
Data Security (PR.DS): Infor- PR.DS-6: Integrity checking SI-7, Software, Firmware, and
mation and records (data) are mechanisms are used to verify Information Integrity
managed consistent with the software, firmware, and
organization’s risk strategy to information integrity
protect the confidentiality, in-
tegrity, and availability of infor-
mation.

DRAFT

Information Protection PR.IP-3: Configuration change CM-3, Configuration Change
Processes and Procedures control processes are in place Control
(PR.IP): Security policies (that PR.IP-12: A vulnerability RA-3, Risk Assessment
address purpose, scope, roles, management plan is developed RA-5, Vulnerability
responsibilities, management and implemented Monitoring and Scanning
commitment, and coordination
among organizational entities), RA-7, Risk Response
processes, and procedures are SI-2, Flaw Remediation
maintained and used to manage
protection of information
systems and assets.
Protective Technology (PR.PT): PR.PT-1: Audit/log records are AU-6, Audit Record Review,
Technical security solutions are determined, documented, Analysis, and Reporting
managed to ensure the security implemented, and reviewed in
and resilience of systems and accordance with policy
assets, consistent with related
policies, procedures, and agree-
ments.
Security Continuous DE.CM-1: The network is CA-7, Continuous Monitoring
Monitoring (DE.CM): The monitored to detect potential
information system and assets cybersecurity events
are monitored to identify DE.CM-8: Vulnerability scans are RA-3, Risk Assessment
cybersecurity events and verify performed SI-4, System Monitoring
the effectiveness of protective
measures.
447 Table 3-2 provides a security mapping for Scenario 6. Although it has the same format as Table 3-1, the
448 two tables have different functions. Table 3-1 lists the Cybersecurity Framework Subcategories and SP
449 800-53 Revision 5 security controls that the example solution supports. Table 3-2 lists the Cybersecurity
450 Framework Subcategories and SP 800-53 Revision 5 security controls that are needed to support the
451 example solution—to mitigate the risks of the solution itself.

DRAFT
452 Table 3-2: Mapping Security Characteristics of the Example Solution for Scenario 6

Identity Management, PR.AC-4: Access permissions and AC-3, Access Enforcement
Authentication and Access authorizations are managed, AC-5, Separation of Duties
Control (PR.AC): Access to incorporating the principles of AC-6, Least Privilege
physical and logical assets and least privilege and separation of
associated facilities is limited to duties
authorized users, processes, PR.AC-7: Users, devices, and other AC-2, Account Management
and devices, and is managed assets are authenticated (e.g., IA-2, Identification and
consistent with the assessed single-factor, multi- factor) Authentication
risk of unauthorized access to commensurate with the risk of the (Organizational Users)
authorized activities and transaction (e.g., individuals’
transactions. IA-3, Device Identification
security and privacy risks and and Authentication
other organizational risks)
IA-4, Identifier Management
IA-5, Authenticator
Management
IA-9, Service Identification
and Authentication
Data Security (PR.DS): PR.DS-1: Data-at-rest is protected SC-28, Protection of
Information and records (data) Information at Rest
are managed consistent with PR.DS-2: Data-in-transit is SC-8, Transmission
the organization’s risk strategy protected Confidentiality and Integrity
to protect the confidentiality,
integrity, and availability of
information.
Protective Technology (PR.PT): PR.PT-3: The principle of least CM-7, Least Functionality
Technical security solutions are functionality is incorporated by
managed to ensure the security configuring systems to provide
and resilience of systems and only essential capabilities
assets, consistent with related
policies, procedures, and
agreements.

DRAFT
453 4 Components of the Example Solution

454 This section highlights the components of the example solution and the collaborators who contributed
455 those components and participated in the solution design, implementation, configuration,
456 troubleshooting, and/or testing. More information on each component, including instructions for
457 installing and configuring it as part of the example solution, is provided in NIST SP 1800-31C, How-To
458 Guides.
459 4.1 Collaborators

460 Collaborators that participated in this build and the capabilities of their contributions to the example
461 solution are described briefly in the subsections below.
462 4.1.1 Cisco

463 Cisco Systems is a provider of enterprise, telecommunications, and industrial networking solutions. Cisco
464 Identity Services Engine (ISE) enables a dynamic and automated approach to policy enforcement that
465 simplifies the delivery of highly secure, micro-segmented network access control. ISE empowers
466 software-defined access and automates network segmentation within IT and OT environments. Cisco
467 Firepower Threat Defense (FTD) is a threat-focused, next-generation firewall with unified management.
468 It provides advanced threat protection before, during, and after attacks. By delivering comprehensive,
469 unified policy management of firewall functions, application control, threat prevention, and advanced
470 malware protection from the network to the endpoint, it increases visibility and security posture while
471 reducing risks. Learn more about Cisco Systems at https://www.cisco.com.
472 4.1.2 Eclypsium

473 Eclypsium is the enterprise firmware security company. The cloud-based solution identifies, verifies, and
474 fortifies firmware and hardware in laptops, servers, network gear, and devices. Eclypsium
475 Administration and Analytics Service secures against persistent and stealthy firmware attacks, provides
476 continuous device integrity, delivers firmware patching at scale, and prevents ransomware and
477 malicious implants. Eclypsium also provides an on-premises version that has parity with the cloud-based
478 platform.
479 4.1.3 Forescout

480 Forescout assesses device security posture in real time upon connection and initiates remediation
481 workflows with your existing security tools to enforce compliance. It continuously monitors all devices
482 for new threats and reassesses their patch level hygiene every time the device leaves and returns to the
483 corporate network. Forescout works to assess all device types, including transient devices often missed
484 by point-in-time scans, without requiring agents. Forescout’s solution goes beyond simple device
485 authentication to identify every device, assess its security posture, trigger remediation workflows, and

DRAFT
486 implement access control across heterogeneous networks to unpatched assets. It continuously monitors
487 all connected devices and automates response when noncompliance or unpatched assets are detected.
488 4.1.4 IBM

489 IBM MaaS360 with Watson is a unified endpoint management (UEM) solution that transforms how
490 organizations support users, apps, content, and data across every type of mobile device: laptops,
491 smartphones, tablets, and IoT. IBM MaaS360 was built almost twenty years ago as a cloud-based
492 Software-as-a-Service (SaaS) platform that integrates with preferred security and productivity tools,
493 allowing modern business leaders to derive immediate value. IBM MaaS360 is the only UEM platform
494 that leverages the power of the Watson Artificial Intelligence engine to deliver contextually relevant
495 security insights for administrators, while ensuring continuous monitoring of the riskiest end users.
496 IBM Code Risk Analyzer was developed in conjunction with IBM Research projects and customer
497 feedback. It enables developers to quickly assess and remediate security and legal risks that they are
498 potentially introducing into their source code, and it provides feedback directly in Git artifacts (for
499 example, pull/merge requests) as part of continuous delivery in a DevOps pipeline. IBM Code Risk
500 Analyzer is provided as a set of Tekton tasks, which can be easily incorporated into delivery pipelines.
501 4.1.5 Lookout

502 Lookout is an integrated endpoint-to-cloud security solution provider with mobile endpoint protection
503 offerings. Lookout’s Mobile Endpoint Security (MES) solution provides cloud-centric behavior-based
504 detection capabilities; it performs behavioral analysis based on telemetry data from nearly 200 million
505 devices and over 120 million apps. This analysis enables Lookout to deliver efficient protection with a
506 lightweight app on the device that optimizes processor speed and battery life. In addition, continuously
507 monitoring changes to the endpoint enables detection of risks that span from jailbreaking or rooting a
508 device to advanced device compromise. With insight into both real-time changes on a device and the
509 aggregate view of behavior across the broader mobile ecosystem, Lookout endpoint protection can
510 detect zero-day threats.
511 4.1.6 Microsoft

512 Microsoft Endpoint Manager helps deliver the modern workplace and modern management to keep
513 your data secure in the cloud and on-premises. Endpoint Manager includes the services and tools you
514 use to manage and monitor mobile devices, desktop computers, virtual machines, embedded devices,
515 and servers. Endpoint Manager combines several services, including Configuration Manager (Microsoft
516 Endpoint Configuration Manager), an on-premises management solution for desktops, servers, and
517 laptops that are on your network or internet-based. Endpoint Configuration Manager can be integrated
518 with Intune, Azure Active Directory (AD), Microsoft Defender for Endpoint, and other cloud services.
519 Endpoint Configuration Manager can deploy apps, software updates, and operating systems, and also be
520 used to monitor compliance and to query and act on clients in real time.

DRAFT
521 4.1.7 Tenable

522 Tenable.sc is Tenable’s on-premises vulnerability management solution. Built on Nessus technology, the
523 Tenable.sc family of products identifies, investigates, and prioritizes vulnerabilities. You get real-time,
524 continuous assessment of your security and compliance posture so you can discover unknown assets
525 and vulnerabilities, monitor unexpected network changes, and prioritize weaknesses to minimize your
526 cyber risk and prevent breaches. Tenable.sc includes over 350 pre-built, highly customizable dashboards
527 and reports to give you immediate insight into your security compliance, effectiveness, and risk. You can
528 continuously measure, analyze, and visualize the effectiveness of your security program, based on high-
529 level business objectives and underlying customizable policies that executives care about.
530 Powered by Nessus technology and managed in the cloud, Tenable.io provides the industry’s most
531 comprehensive vulnerability coverage with the ability to predict which security issues to remediate first.
532 Using an advanced asset identification algorithm, Tenable.io provides the most accurate information
533 about dynamic assets and vulnerabilities in ever-changing environments. As a cloud-delivered solution,
534 its intuitive dashboard visualizations, comprehensive risk-based prioritization, and seamless integration
535 with third-party solutions help security teams maximize efficiency and scale for greater productivity.
536 4.1.8 VMware

537 VMware vRealize Automation includes SaltStack Config, a modern configuration management platform
538 with the performance, speed, and agility IT teams need to manage large, complex IT systems and
539 improve efficiency at scale. For this project, vRealize Automation SaltStack Config provides device
540 configuration and software distribution capabilities. Specifically, it allows for configuration changes to be
541 made to devices by updating or removing software as well as updating settings such as network
542 information.
543 SaltStack SecOps, an add-on to the vRealize products, gives system administrators the ability to create
544 security policies and scan assets to determine whether they are compliant with supported, industry-
545 recognized security benchmarks. SaltStack SecOps also has the ability to scan your system for Common
546 Vulnerabilities and Exposures (CVEs), then immediately apply the updates or patches to remediate the
547 advisories.
548 4.2 Technologies

549 Table 4-1 lists all the technologies used in this project, the primary functions that each technology
550 provides to the project, and the Cybersecurity Framework Subcategories that the technology supports in
551 this project. Please refer to Table 3-1 for an explanation of the NIST Cybersecurity Framework
552 Subcategory codes.

DRAFT
553 Table 4-1: Technologies Used in the Build
Technology Primary Functions Cybersecurity Framework

Subcategories
Cisco Firepower Threat Network policy enforcement PR.AC-4, PR.AC-5, DE.CM‐1
Defense (FTD) and Cisco
Firepower Management
Center (FMC)
Cisco Identity Services Asset discovery and inventory; ID.AM-2, PR.AC-4, PR.AC-5
Engine (ISE) network access control
Eclypsium Administration Hardware and firmware inventory; ID.AM-1, ID.AM-2, PR.DS-6,
and Analytics Service firmware vulnerability assessment, PR.IP-12
integrity monitoring, and updating
Forescout Platform Asset discovery and inventory; ID.AM-2, PR.AC-4, PR.AC-5,
security policy enforcement PR.IP-3, PR.PT-1
IBM Code Risk Analyzer Vulnerability scanning for source code PR.IP-12
IBM MaaS360 with Watson Asset inventory; configuration ID.AM-2, PR.IP-3, PR.IP-12
management; software updates
Lookout Mobile Endpoint Security policy enforcement; PR.AC-4, PR.IP-3, PR.IP-12
Security (MES) vulnerability scanning and reporting;
software discovery and inventory;
firmware vulnerability assessment and
policy enforcement
Microsoft Endpoint Asset discovery; configuration ID.AM-2, PR.IP-3, PR.IP-12
Configuration Manager management; software updates
Tenable.sc, Tenable.io, and Asset discovery and inventory; ID.AM-2, PR.PT-1, DE.CM-8
Nessus vulnerability scanning and reporting
VMware vRealize Vulnerability scanning and PR.IP-3, PR.IP-12, DE.CM-8
Automation SaltStack remediation; configuration
Config and SaltStack management; software updates
SecOps
554 The following sections summarize the security capabilities that each technology provided to the
555 example solution.

DRAFT
556 4.2.1 Cisco Firepower Threat Defense (FTD) & Firepower Management Center
557 (FMC)
558 Cisco Firepower Threat Defense (FTD) is a virtual firewall that was utilized as the networking backbone
559 that connected all of the lab subnets. This build also used the Cisco FTD firewall to provide network
560 access management capabilities, including enforcing network access control using firewall rules. Cisco
561 FTD was deployed and managed in the lab via a separate Cisco Firepower Management Center (FMC)
562 virtual machine.
563 To support the unpatchable asset scenario (Scenario 5), the integration between Cisco FTD and Cisco
564 Identity Services Engine (ISE) via pxGrid allowed for the firewall to ingest security group tags (SGTs) that
565 were applied by ISE. SGTs were then used in custom firewall rules to restrict network access to any
566 machine that was given a quarantine tag. Section 4.2.2 has more information on this integration.
567 4.2.2 Cisco Identity Services Engine (ISE)

568 In this build Cisco Identity Services Engine (ISE) provided asset discovery and inventory, and network
569 access control to enforce administrator-created security and access control policies. Cisco ISE had
570 integrations with several other example solution technologies, including the following:
571  An integration between ISE and AD allowed the user of a device to be identified. This
572 information could then be used in custom policy.
573  A Dynamic Host Configuration Protocol (DHCP) relay was established between ISE and the lab
574 DHCP server. This integration allowed for ISE to identify any device that was assigned an IP
575 address. This allowed devices to be discovered as they joined the network.
576  Cisco ISE was configured to integrate with Tenable.sc via an adapter. Cisco ISE leveraged this
577 adapter to prompt Tenable to scan devices newly connected to the network. Cisco ISE could
578 then ingest this scan data to find the Common Vulnerability Scoring System (CVSS) scores of
579 device vulnerabilities. An ISE policy was written to apply a quarantine action, via SGTs, to any
580 device with a CVSS score equal to or greater than 7 (corresponding to high and critical
581 vulnerabilities).
582  Cisco Platform Exchange Grid (pxGrid) was configured to share contextual information about
583 authenticated devices to the firewall. Cisco ISE was utilized to apply SGTs to devices as they
584 were assessed for vulnerabilities. These SGTs were then passed to the lab firewall via pxGrid,
585 where they could be used in custom firewall rules. PxGrid was also used to share
586 communications between Forescout and Cisco ISE. Forescout could apply a quarantine tag to
587 observed devices, which would then be shared with ISE.
588 4.2.3 Eclypsium Administration and Analytics Service

589 In this build, we utilized Eclypsium Administration and Analytics Service to provide agent-based
590 identification of hardware and firmware for our laptop, desktop, and server endpoints while also

DRAFT
591 monitoring the firmware for vulnerable or end-of-life versions. Eclypsium monitored laptop and virtual
592 machine (VM) firmware integrity, and alerted if a component or its associated firmware has changed. It
593 also monitored endpoints for known security vulnerabilities from out-of-date firmware. Finally, we
594 utilized Eclypsium’s beta firmware update script, which automatically finds the latest known Basic
595 Input/Output System (BIOS) firmware version for the system, downloads the update, and executes it to
596 update the BIOS.
597 4.2.4 Forescout Platform

598 In this build the Forescout platform was configured to perform endpoint discovery by detecting
599 endpoints and determining software information about those endpoints based on a set of attributes.
600 Forescout also provided the capability to isolate or restrict assets that cannot be patched and to
601 respond to emergency scenarios, such as providing a workaround or deploying an emergency patch.
602 Forescout had several integrations with other example solution technologies:
603  The User Directory plugin was configured so that the Forescout platform integrated with the
604 lab’s AD Domain Controller. This plugin provided Lightweight Directory Access Protocol (LDAP)
605 services to Forescout, allowing directory-based users to log in into Forescout as well as providing
606 user directory information such as the current active domain users logged into each endpoint.
607  The Domain Name System (DNS) Query Extension configuration setting allowed Forescout to
608 query the DNS server to determine the hostnames of devices identified by Forescout.
609  The Tenable VM plugin provided the Forescout platform with vulnerability and scan status
610 information which can be used to create custom policies. This plugin also enabled Forescout to
611 utilize vulnerability management information that Tenable.sc collected from endpoints, and
612 allowed Forescout to determine if scans had been performed on endpoints within the lab.
613  The Microsoft Systems Management Server (SMS)/System Center Configuration Manager
614 (SCCM) module was configured to allow the Forescout platform to integrate with Microsoft
615 Endpoint Configuration Manager. This module allowed for a custom policy to be created that
616 used data from Microsoft Endpoint Configuration Manager.
617  The Linux plugin was configured to collect information from and manage Linux-based endpoints
618 via two methods: secure shell (SSH) access to the endpoint, and agent-based integration with
619 the endpoint.
620  The HPS Inspection Engine was configured to collect information from Windows endpoints via
621 two methods. The first method utilized a directory-based integration with the lab’s AD Domain
622 Services instance, which collected domain-based information on the Windows endpoint. The
623 second method utilized an agent-based integration called SecureConnector that allowed
624 Forescout to collect and manage Windows endpoints.
625  The pxGrid plugin was configured to integrate with Cisco ISE. This plugin gave the Forescout
626 platform the ability to utilize Cisco ISE to apply adaptive network control (ANC) policies to
627 endpoints for restricting their network access.

DRAFT
628  The Switch plugin was configured to integrate Forescout with the physical Cisco switch located
629 in the lab. The plugin used information from the switch to collect information about endpoints
630 that were physically connected to the switch.
631 Our implementation utilized multiple policies to support the use case scenarios. Examples of capabilities
632 that the policies provided are described below:
633  Check for a particular application running on Windows; if present, stop execution and uninstall
634 it.
635  Check an endpoint for known critical vulnerabilities; if any are present, use Cisco ISE to
636 quarantine the endpoint via the pxGrid plugin.
637  Force a Windows update to occur on an endpoint with Windows Update enabled.
638  Determine if a Windows endpoint has the Microsoft Endpoint Configuration Manager agent
639 installed.
640 4.2.5 IBM Code Risk Analyzer

641 IBM Code Risk Analyzer was used to demonstrate vulnerability scanning and reporting for pre-deployed
642 code as part of a DevOps pipeline to deliver a cloud-native application. Integration with Git allowed the
643 Code Risk Analyzer to perform vulnerability assessments against applications and base images. The Code
644 Risk Analyzer would then print a bill-of-materials, which indicates the composition of a deployment. This
645 allows an administrator to see all of an application’s dependencies and their sources, providing visibility
646 into application components which could have vulnerabilities.
647 4.2.6 IBM MaaS360 with Watson

648 IBM MaaS360 with Watson was used to demonstrate how to securely manage an enterprise’s devices by
649 enabling deployment, control of content, and policy controls. Enterprises can manage organization-
650 owned and user-owned devices using this product. The lab used MaaS360 for asset identification and
651 assessment, routine patching and emergency patching, emergency workarounds, and isolation of assets
652 that cannot be patched. The first phase of this lab build used MaaS360’s comprehensive enterprise
653 mobility management (EMM) capability to manage a MacBook Pro and a Windows 10 virtual desktop.
654 The second phase used MaaS360’s Mobile Device Manager (MDM) capability to manage Android and
655 Apple iOS devices.
656 This build also used Maas360’s Cloud Extender, which allows enterprises to integrate mobile devices
657 with corporate on-premises and cloud-based resources. The Cloud Extender was installed on the AD
658 server to allow users to log in with AD accounts.

DRAFT
659 4.2.7 Lookout

660 Lookout MES was used in this build to perform security compliance, vulnerability scanning, and
661 firmware/software discovery for mobile endpoints. Our implementation of Lookout MES was integrated
662 with IBM MaaS360. Lookout MES shared custom device attributes, such as device threat, with MaaS360,
663 which could in turn provide policy enforcement. The Lookout for Work mobile client was able to provide
664 firmware and application vulnerability assessment for mobile endpoints. Administrators could use
665 Lookout to see which vulnerabilities were affecting deployed endpoints and find risk grades (i.e., A, B, C,
666 D, or F) for installed applications.
667 4.2.8 Microsoft Endpoint Configuration Manager

668 Microsoft Endpoint Configuration Manager was used in this build to perform configuration
669 management, including software and firmware patching, for Windows-based hosts. Our implementation
670 of Endpoint Configuration Manager included Windows Server Update Services (WSUS), an update
671 service primarily used for downloading, distributing, and managing updates for Microsoft Windows-
672 based systems. The example build used Microsoft Endpoint Configuration Manager to demonstrate the
673 identification of endpoints utilizing Heartbeat discovery and Windows Domain discovery methods, the
674 patching of Windows endpoints via Microsoft updates and third-party update sources, and the
675 deployment of custom scripts to endpoints.
676 4.2.9 Tenable.io

677 In the example build, Tenable.io was used to provide vulnerability scanning and reporting for Docker
678 container images. Containers are built from images and vulnerabilities are patched in images, not
679 deployed containers, so images are the focus of scanning. Tenable.io scanned the repository of a Red
680 Hat OpenShift cluster in the lab environment. Tenable.io was scheduled to routinely pull the latest
681 images from the OpenShift cluster and perform vulnerability scans on them. Scan information was
682 reported in the container security section of the Tenable.io Web Console. Administrators could see
683 vulnerability information for containers deployed in their respective networks.
684 4.2.10 Tenable.sc and Nessus

685 This example build utilized two Tenable products in the first phase of this project, Nessus and
686 Tenable.sc. We used Nessus to scan Linux, Windows, and macOS endpoints and network switches for
687 vulnerability data, and then feed this information to Tenable.sc for reporting. Tenable.sc, a vulnerability
688 management product, collected the information from Nessus and reported that information to
689 administrators using dashboards and reports. Also, Tenable.sc had integrations with other example
690 solution technologies:

DRAFT
691  An integration between Tenable.sc and Cisco ISE was performed to initiate scans of any newly
692 connected network devices. Tenable.sc would pass scan data to Cisco ISE, where a custom policy
693 was written to quarantine devices based on their CVSS scores.
694  An integration between Forescout and Tenable was leveraged to scan devices as hosts joined
695 the network. Forescout could prompt Tenable to scan hosts to determine if an endpoint had
696 critical vulnerabilities. This information was ingested by Forescout for the purpose of
697 quarantining endpoints.
698 4.2.11 VMware vRealize Automation SaltStack Config

699 In this example build, vRealize Automation SaltStack Config was used to provide configuration
700 management and patch deployment. In the first phase of the build, it was used to manage Windows
701 workstations and servers, a macOS laptop, and Linux/Unix-based VMs and servers. SaltStack Config was
702 configured to run jobs, applying different states or configurations, on endpoints. The job that was
703 written for this project, in support of the emergency workaround scenario, could uninstall an application
704 based on the current version of the product. SaltStack Config also had an add-on component called
705 SaltStack SecOps which was utilized to scan devices for known vulnerabilities and provide mitigation
706 actions, including missing updates for endpoints.

DRAFT
707 Appendix A Patch Management System Security Practices

708 Section 3.4.7 describes Scenario 6, “Patch management system security (or other system with
709 administrative privileged access).” In support of Scenario 6, this appendix describes recommended
710 security practices for systems like patch management systems which have administrative privileged
711 access over many other systems as defined as “critical software” in Executive Order (EO) 14028. It then
712 summarizes how the example solution components described in this practice guide could support each
713 of those recommended security practices.
714 A.1 Security Measures

715 The table below defines security measures for software of critical importance. Note that these security
716 measures are not intended to be comprehensive. They are based on those in the NIST publication
717 Security Measures for “EO-Critical Software” Use Under Executive Order (EO) 14028. A security measure
718 (SM) is a high-level security outcome statement that is intended to apply to critical software or to all
719 platforms, users, administrators, data, or networks (as specified) that are part of running critical
720 software. The security measures are grouped by five objectives:
721 1. Protect critical software and critical software platforms (the platforms on which critical software
722 runs, such as endpoints, servers, and cloud resources) from unauthorized access and usage.
723 2. Protect the confidentiality, integrity, and availability of data used by critical software and critical
724 software platforms.
725 3. Identify and maintain critical software platforms and the software deployed to those platforms
726 to protect the critical software from exploitation.
727 4. Quickly detect, respond to, and recover from threats and incidents involving critical software
728 and critical software platforms.
729 5. Strengthen the understanding and performance of humans’ actions that foster the security of
730 critical software and critical software platforms.
731 Each row in the table defines one security measure and lists mappings to it from the NIST Cybersecurity
732 Framework and NIST SP 800-53 Revision 5, Security and Privacy Controls for Information Systems and
733 Organizations. These mappings are in the forms of Cybersecurity Framework Subcategories and SP 800-
734 53 security controls, respectively. The mappings are general and informational; any particular situation
735 might have somewhat different mappings.

DRAFT
Cybersecurity SP 800-53 Rev.

Security Measure (SM) Framework 5 Controls
Subcategories
Objective 1: Protect critical software and critical software platforms from unauthorized access and
usage.
SM 1.1: Use multi-factor authentication that is verifier PR.AC-1, AC-2, IA-2, IA-
impersonation-resistant for all users and administrators of PR.AC-7 4, IA-5
critical software and critical software platforms.
SM 1.2: Uniquely identify and authenticate each service PR.AC-1, AC-2, IA-9
attempting to access critical software or critical software PR.AC-7
platforms.
SM 1.3: Follow privileged access management principles for PR.AC-1, AC-2, IA-2, SC-
network-based administration of critical software and critical PR.AC-7, 2, SC-7
software platforms. Examples of possible implementations PR.MA-1, enhancement
include using hardened platforms dedicated to administration PR.MA-2 15
and verified before each use, requiring unique identification of
each administrator, and proxying and logging all administrative
sessions to critical software platforms.
SM 1.4: Employ boundary protection techniques as appropriate PR.AC-3, SC-7
to minimize direct access to critical software, critical software PR.AC-5
platforms, and associated data. Examples of such techniques
include network segmentation, isolation, software-defined
perimeters, and proxies.
Objective 2: Protect the confidentiality, integrity, and availability of data used by critical software and
critical software platforms.
SM 2.1: Establish and maintain a data inventory for critical ID.AM-3, CM-8, PM-5
software and critical software platforms. DE.AE-1
SM 2.2: Use fine-grained access control for data and resources PR.AC-4 AC-2, AC-3, AC-
used by critical software and critical software platforms to 6
enforce the principle of least privilege to the extent possible.
SM 2.3: Protect data at rest by encrypting the sensitive data used PR.DS-1 SC-28
by critical software and critical software platforms consistent
with NIST’s cryptographic standards.
SM 2.4: Protect data in transit by using mutual authentication PR.AC-3, AC-4, AC-17,
whenever feasible and by encrypting sensitive data PR.AC-7, SC-8
communications for critical software and critical software PR.DS-2, PR.PT-
platforms consistent with NIST’s cryptographic standards. 4, DE.CM-7

DRAFT

Subcategories
SM 2.5: Back up data, exercise backup restoration, and be PR.IP-4 CP-9, CP-10
prepared to recover data used by critical software and critical
software platforms at any time from backups.
Objective 3: Identify and maintain critical software platforms and the software deployed to those
platforms to protect the critical software from exploitation.
SM 3.1: Establish and maintain a software inventory for all ID.AM-1, CM-8, PM-5,
platforms running critical software and all software (both critical ID.AM-2, ID.SC- RA-9
and non-critical) deployed to each platform. 2
SM 3.2: Use patch management practices to maintain critical ID.RA-1, ID.RA- CA-7, RA-5, SI-
software platforms and all software deployed to those platforms. 2, ID.RA-6, 2, SI-5, SR-8
Practices include: PR.IP-12,
 rapidly identify, document, and mitigate known vulnerabili- DE.CM-8,
ties (e.g., patching, updating, upgrading software to sup- RS.MI-3
ported version) to continuously reduce the exposure time
 monitor the platforms and software to ensure the mitigations
are not removed outside of change control processes
SM 3.3: Use configuration management practices to maintain ID.RA-1, ID.RA- AC-5, AC-6, CA-
critical software platforms and all software deployed to those 2, ID.RA-6, 7, CM-2, CM-3,
platforms. Practices include: PR.AC-4, PR.IP- CM-6, CM-7,
 identify the proper hardened security configuration for each 1, PR.IP-3, RA-5, SI-5
critical software platform and all software deployed to that PR.PT-3,
platform (hardened security configurations enforce the princi- DE.CM-8,
ples of least privilege, separation of duties, and least func- RS.MI-3
tionality)
 implement the configurations for the platforms and software
 control and monitor the platforms and software to ensure the
configuration is not changed outside of change control pro-
cesses
Objective 4: Quickly detect, respond to, and recover from threats and incidents involving critical
software and critical software platforms.
SM 4.1: Configure logging to record the necessary information PR.PT-1 AU-2, AU-3,
about security events involving critical software platforms and all AU-4, AU-5,
software running on those platforms. AU-8, AU-9,
AU-11, AU-12

DRAFT

Subcategories
SM 4.2: Continuously monitor the security of critical software DE.CM-7 CA-7, SI-4
platforms and all software running on those platforms.
SM 4.3: Employ endpoint security protection on critical software PR.DS-5, PR.DS- SI-3, SI-4, SI-7
platforms to protect the platforms and all software running on 6, DE.AE-2,
them. Capabilities include: DE.CM-4,
 protecting the software, data, and platform by identifying, re- DE.CM-7,
viewing, and minimizing the attack surface and exposure to DE.DP-4
known threats
 permitting only verified software to execute (e.g., file integ-
rity verification, signed executables, allowlisting)
 proactively detecting threats and stopping them when possi-
ble
 responding to and recovering from incidents
 providing the necessary information for security operations,
threat hunting, incident response, and other security needs
SM 4.4: Employ network security protection to monitor the PR.DS-5, AU-13, AU-14,
network traffic to and from critical software platforms to protect DE.AE-1, SC-7, SI-3
the platforms and their software using networks. Capabilities DE.AE-3,
include: DE.CM-1,
 proactively detecting threats at all layers of the stack, includ- DE.CM-4,
ing the application layer, and stopping them when possible DE.CM-7,
 providing the necessary information for security operations, DE.DP-4
threat hunting, incident response, and other security needs
SM 4.5: Train all security operations personnel and incident PR.AT-5, PR.IP- AT-3, CP-3, IR-2
response team members, based on their roles and 9, PR.IP-10
responsibilities, on how to handle incidents involving critical
software or critical software platforms.
Objective 5: Strengthen the understanding and performance of humans’ actions that foster the
security of critical software and critical software platforms.
SM 5.1: Train all users of critical software, based on their roles PR.AT-1 AT-2, AT-3
and responsibilities, on how to securely use the software and the
critical software platforms.
SM 5.2: Train all administrators of critical software and critical PR.AT-2 AT-3, CP-3
software platforms, based on their roles and responsibilities, on
how to securely administer the software and/or platforms.

DRAFT

Subcategories
SM 5.3: Conduct frequent awareness activities to reinforce the PR.AT-1, PR.AT- AT-3
training for all users and administrators of critical software and 2
platforms, and to measure the training’s effectiveness for
continuous improvement purposes.
736 A.2 Component Support of Security Measures

737 This section provides summary tables for how each technology provider’s components in the example
738 solution could support the security measures defined above. The technical mechanisms, configuration
739 settings, or other ways in which the components could provide this support were not necessarily utilized
740 in the example solution build. The information is provided here to offer examples of how these security
741 measures might be implemented, not to serve as recommendations for how to implement them.
742 Each table in this section has the same four columns:
743  SM #: This lists a security measure ID from the previous section and hyperlinks to the definition
744 of that ID.
745  Question: This contains a question NIST asked the technology providers to answer for their
746 components regarding the associated security measure.
747  Technical Mechanism or Configuration: This is a summary of the answer from the component’s
748 technology provider. The content submitted by each technology provider has been edited for
749 brevity.
750  Refs.: This provides hyperlinks to any applicable references specified by the technology
751 provider. This column is blank if no reference was needed or available, or if there is a single
752 reference for all entries in a table, in which case the reference is defined immediately before the
753 table.
754 In each table, rows with no answer or an answer of “no” or “not applicable” have been omitted for
755 brevity.
756 A.2.1 Cisco FTD Support of Security Measures

SM # Question Technical Mechanism or Configuration Refs.
SM Does the software platform allow for the Certificates from a Personal Identity Ref1
1.1 use of a two-factor authentication Verification (PIV) card or Common Access
method for access? Card (CAC) can be used along with soft
certificates to authenticate admin users.

DRAFT

SM Does the software platform identify and Services using the PxGrid solution to Ref1
1.2 authenticate users and machine accounts gather data from the system or publish
that try to access the platform? require the use of certificates to secure
the communications channel.
SM Does the system allow for creating The Cisco FMC admin console supports Ref1
1.3 accounts with different access levels to role-based access control. There are
enforce least management? predefined roles, and custom roles with
permissions can be created.
SM Does the system allow for the use of Administrators can limit access by IP Ref1
1.4 discretionary access control lists (DACLs), address and port.
network segmentation, or isolation for
access to the platform?
SM Does the system allow for creating The Cisco FMC admin console and Ref1
2.2 accounts with different access levels to command-line interface (CLI) both
enforce least management? support role-based access control.
SM Does the system support performing Cisco FMC enables backup and restore of Ref1
2.5 regular backups and restorations? configuration and monitoring. FMC also
provides backup and restore of the
devices it manages.
SM Does the platform allow for the Cisco distributes several types of Ref1
3.2 deployment of patches and OS updates? upgrades and updates for Firepower
deployments. These include OS versions,
patches, vulnerability databases, intrusion
rules, and geolocation databases. These
are all deployed centrally from FMC.
SM Does the security tool support logging FMC allows for sending all logs to a third- Ref1
4.1 and sending that data to rsyslog or party SIEM using syslog or eStreamer.
Security Information and Event
Management (SIEM)?
SM Does the platform allow for logging The system can generate logs of the Ref1
4.4 connection events to the tool? connection events its managed devices
detect. Connection events include
Security Intelligence events (connections
blocked by the reputation-based Security
Intelligence feature.)

DRAFT

SM Are there training courses in how to use Cisco provides training resources through
5.1 the products? Are there different courses direct offering, partner, knowledge
for different roles? partners, and on-demand through Cisco
Live.
SM Are there training courses for teaching Cisco provides training resources through
5.2 administrators how to utilize the direct offering, partner, knowledge
platform? partners, and on-demand through Cisco
Live.
SM Are trainings updated and metrics Cisco regularly collects metrics from
5.3 collected to improve trainings? completed user training to make
improvements and updates.
757
758 A.2.2 Cisco ISE Support of Security Measures

SM Does the software platform allow for the Certificates from a PIV or CAC can be used Ref1
1.1 use of a two-factor authentication along with soft certificates to
method for access? authenticate admin users.
SM Does the software platform identify and Services using the ISE PxGrid solution to Ref1
1.2 authenticate users and machine accounts gather data from the system or publish
that try to access the platform? require the use of certificates to secure
the communications channel.
SM Does the system allow for creating The Cisco ISE admin console and CLI both Ref1
1.3 accounts with different access levels to support role-based access control.
enforce least management?
SM Does the system allow for the use of Both the admin user interface (UI) and CLI Ref1
1.4 DACLs, network segmentation, or can be configured to limit IP access to the
isolation for access to the platform? system.
SM Does the system allow for creating The Cisco ISE admin console and CLI both Ref1
2.2 accounts with different access levels to support role-based access control.
SM Does the system use or contain an option Cisco ISE can be configured for Federal Ref1
2.4 to enable the use of NIST-certified Information Processing Standards (FIPS)
cryptographic standards for protecting compliance. In this mode, only the
data in transit? protocols listed here are allowed to be
used for authentication: EAP-TLS, PEAP,
EAP-FAST, EAP-TTLS

DRAFT

SM Does the system support performing Cisco ISE backs up to a repository both the Ref1
2.5 regular backups and restorations? configuration and event data. The system
provides high-availability (HA) capabilities
with redundant service pairs.
SM Does the platform allow for the Cisco ISE provides a centralized patching Ref1
3.2 deployment of patches and OS updates? mechanism through the admin node to
apply patches to all systems that are a
member of the deployment. Patches are
rollups, so administrators do not have to
install multiple patches. Patches include
vulnerability fixes and bug fixes.
SM Does the platform allow for configuration Cisco ISE allows administrators to turn on Ref1
3.3 management practices such as removal and off features and functions. Cisco ISE
or disabling of services to maintain does not allow access to the underlying
security? OS, so services are only enabled and
disabled based on the packages needed to
support the enabled services.
SM Does the security tool support logging Log events for the following categories Ref1
4.1 and sending that data to rsyslog or a are sent by all nodes in the deployment to
SIEM? the logging targets: Administrative and
Operational Audit, System Diagnostics,
and System Statistics.
SM Does the platform allow for logging The web interface can specify remote Ref1
4.4 connection events to the tool? syslog server targets to which system log
messages are sent. Log messages are sent
to the remote syslog server targets in
accordance with the syslog protocol
standard (RFC 3164).
SM Are there training courses in how to use Cisco provides training resources through
5.1 the products? Are there different courses direct offering, partner, knowledge
for different roles? partners, and on-demand through Cisco
Live.
SM Are there training courses for teaching Cisco provides training resources through
5.2 administrators how to utilize the direct offering, partner, knowledge
platform? partners, and on-demand through Cisco
Live.

DRAFT

SM Are trainings updated and metrics Cisco regularly collects metrics from
5.3 collected to improve trainings? completed user training to make
improvements and updates.
759
760 A.2.3 Eclypsium Administration and Analytics Service Support of Security

761 Measures
762 All entries in this table have the same two references: the Eclypsium-supplied Solution Guide and
763 Deployment Guide. The Solution Guide is built into the product, and Eclypsium provides the Deployment
764 Guide at purchase, so it was not possible to provide hyperlinks for this table.

SM Does the software platform allow for the Eclypsium integrates with multiple
1.1 use of a two-factor authentication authentication mechanisms, many of
method for access? which support multi-factor authentication
(MFA).
SM Does the software platform identify and Unique application programming
1.2 authenticate users and machine accounts interface (API) tokens are managed by
that try to access the platform? Eclypsium administrators.
SM Does the system allow for creating The Eclypsium platform contains
1.3 accounts with different access levels to Admin/User access roles. Only
enforce least management? administrators can change systemwide
analysis policies.
SM Does the system allow for the use of The Linux OS hosting Eclypsium can be
1.4 DACLs, network segmentation, or configured to allow for the creation of
isolation for access to the platform? network-based access restrictions.
SM Does the system allow for creating The Eclypsium platform contains
2.2 accounts with different access levels to Admin/User access roles. Only
enforce least management? administrators can change systemwide
analysis policies.
SM Does the system use or contain an option The data-at-rest encryption
2.3 to enable the use of NIST-certified implementation is done as part of the
cryptographic standards for protecting backend platform onto which Eclypsium is
data at rest? deployed. In the cloud, the provider's key
management system may be used. In an
on-premises deployment, the OS or
hardware-based encryption on the
physical servers may be used.

DRAFT

SM Does the system use or contain an option All communications occur over Transport
2.4 to enable the use of NIST-certified Layer Security (TLS). FIPS mode can be
cryptographic standards for protecting enabled and utilized where desired.
data in transit?
SM Does the system support performing Backups of the Eclypsium backend are
2.5 regular backups and restorations? performed as part of the platform onto
which it is deployed. Standard
mechanisms for Linux server
backup/restore will operate normally.
SM Does the product list all software This information is in the Solution Guide.
3.1 dependencies and currently installed When scanning firmware on target
applications/services? systems, similar information may be
inferred from binary analysis.
SM Does the platform allow for the The cloud version is managed by
3.2 deployment of patches and OS updates? Eclypsium to provide updates. The on-
premises version is the responsibility of
the customer. The OS can be configured
to perform updates. On target systems,
Eclypsium will indicate whether firmware
is up to date.
SM Does the platform allow for configuration Eclypsium directly manages the
3.3 management practices such as removal configuration of cloud deployments. In an
or disabling of services to maintain on-premises environment, configuration
security? management becomes the responsibility
of the customer. Normal configuration
management for Linux servers will apply
to the Eclypsium backend.
SM Does the security tool support logging In most instances, syslog is integrated
4.1 and sending that data to rsyslog or a with SIEM tools. Eclypsium alerts for
SIEM? target systems are forwarded over syslog
to such tools when configured.
SM Does the platform monitor the security There is an audit trail of users who have
4.2 and vulnerabilities associated with all logged in and the actions they performed.
software and dependencies used? Updates are also sent out to help
remediate software running on the
platform.

DRAFT

SM Is anti-malware or antivirus able to be Eclypsium scanners and the Eclypsium
4.3 installed on the system running your backend are compatible with running
platform? other endpoint security software on the
same device.
SM Does the platform allow for logging In cloud deployments, Eclypsium manages
4.4 connection events to the tool? network security protections. In an on-
premises deployment, this would be
inherited from the environment into
which Eclypsium is deployed.
SM Are there training courses or procedures Eclypsium security operations personnel
4.5 in the event of an incident involving the receive security and incident response
tool or platform? training. Customer training is available
from Eclypsium to cover firmware security
and incident response scenarios.
SM Are there training courses in how to use Eclypsium has the latest training catalog.
5.1 the products? Are there different courses
for different roles?
SM Are there training courses for teaching Eclypsium has the latest training catalog.
5.2 administrators how to utilize the
platform?
SM Are trainings updated and metrics Eclypsium has the latest training catalog.
5.3 collected to improve trainings?
765
766 A.2.4 Forescout Platform Support of Security Measures

SM Does the software platform allow for the The Forescout platform's integration with Ref1
1.1 use of a two-factor authentication PIV and Homeland Security Presidential
method for access? Directive 12 (HSPD-12) cards allows for
this capability.
SM Does the system allow for creating The Forescout platform supports a range Ref1
1.3 accounts with different access levels to of accounts with different access levels as
enforce least management? required to support least privilege.

DRAFT

SM Does the system allow for the use of Forescout supports the use of DACLs, Ref1
1.4 DACLs, network segmentation, or virtual local area network (VLAN)
isolation for access to the platform? assignment, and any other network-based
control offered by the network devices in
use for device isolation as needed.
SM Does the software list and maintain an This is enabled via Forescout's native Ref1
2.1 inventory of all software criticalities and policy.
integrations?
SM Does the system allow for creating The Forescout platform supports a range Ref1
2.2 accounts with different access levels to of accounts with different access levels as
enforce least management? required to support least privilege.
SM Does the system use or contain an option Forescout natively encrypts the data at Ref1
2.3 to enable the use of NIST-certified rest on the hard drives but can also verify
cryptographic standards for protecting and establish the encryption level of
data at rest? managed endpoints.
SM Does the system support performing Forescout supports backup/restore of Ref1
2.5 regular backups and restorations? data and configurations of all appliances.
SM Does the product list all software Forescout can identify applications and
3.1 dependencies and currently installed services that are installed and/or running
applications/services? on Windows, Linux, and macOS. Remote
inspection capabilities are enabled either
by integration with AD (LDAP) or via an
agent (Secure Connector). This in turn can
be enhanced by creating Forescout
security policies to identify all software
with enhanced privileges and known
CVEs.
SM Does the platform allow for the Forescout integrates with a variety of Ref1
3.2 deployment of patches and OS updates? patch and OS management tools.
Forescout has native remediations via
scripting on endpoints via policy.
SM Does the platform allow for configuration Forescout can perform control actions Ref1
3.3 management practices such as removal against any managed endpoint. Services
or disabling of services to maintain as a property are an attribute detected
security? running/installed on the endpoint. These
attributes (services) can in turn can be
stopped/started or removed as required
via policy.

DRAFT

SM Does the security tool support logging The Forescout platform will send rich Ref1
4.1 and sending that data to rsyslog or a device context information to a SIEM Ref2
SIEM? system for logging and event analysis.
SM Does the platform monitor the security Forescout supports a default Windows Ref1
4.2 and vulnerabilities associated with all Vulnerability CVE/Patch plugin (published
software and dependencies used? by Microsoft) to actively scan all Windows
clients/servers in real time via policy. The
Forescout platform also provides Security
Policy Templates (SPT) covering zero-day
information and assesses software and
hardware for these issues. SPT includes
vulnerability and response templates with
relevant data for vulnerabilities as
documented by Forescout security labs.
SM Does the platform allow for logging All successful and failed connections to Ref1
4.4 connection events to the tool? the Forescout platform are logged in
system event logs. Administrators can
view these logs. An option is also available
to forward event messages to third-party
logging systems via syslog.
SM Are there training courses in how to use Forescout offers training and Ref1
5.1 the products? Are there different courses certifications for administrators.
for different roles?
SM Are there training courses for teaching Forescout offers training and Ref1
5.2 administrators how to utilize the certifications for engineers.
platform?
767
768 A.2.5 IBM Code Risk Analyzer Support of Security Measures

SM Does the software platform allow for the It leverages the IBM Cloud authentication
1.1 use of a two-factor authentication mechanism, which provides multi-factor
method for access? authentication for all users and
administrators.
SM Does the software platform identify and All users and machines are identified
1.2 authenticate users and machine accounts using the Identity and Access
that try to access the platform? Management feature of IBM Cloud.

DRAFT

SM Does the system allow for creating Accounts can be created and assigned to
1.3 accounts with different access levels to appropriate roles that have different
enforce least management? access levels. This functionality is
provided by the Identify and Access
Management feature of IBM Cloud.
SM Does the system allow for the use of Network segmentation and isolation is
1.4 DACLs, network segmentation, or done by using Kubernetes clusters and
isolation for access to the platform? Istio as the service mesh. Strict policies
exist for egress and ingress.
SM Does the software list and maintain an The software keeps a bill of materials for
2.1 inventory of all software criticalities and each component. This bill of materials
integrations? contains a full list of third-party
dependencies. Integration is allowed with
only IBM-authorized software.
SM Does the system allow for creating This feature is achieved by using the
2.2 accounts with different access levels to Identity and Access Management (IAM)
enforce least management? feature of IBM Cloud. IAM has
comprehensive features for granular
access for users, administrators, and
machines.
SM Does the system use or contain an option All data at rest, whether in databases or
2.3 to enable the use of NIST-certified file systems, is encrypted using NIST-
cryptographic standards for protecting certified cryptographic standards.
data at rest?
SM Does the system use or contain an option All data in transit is encrypted using NIST-
2.4 to enable the use of NIST-certified certified cryptographic standards. This
cryptographic standards for protecting includes data that is flowing between
data in transit? microservices inside a cluster.
SM Does the system support performing The system data is backed up regularly for
2.5 regular backups and restorations? offsite storage. Disaster recovery
procedures are reviewed and tested
regularly by IBM engineers.
SM Does the product list all software A bill of materials is created for each
3.1 dependencies and currently installed microservice. Integrations with databases
applications/services? and other systems are tracked. Change
management is rigorously followed.

DRAFT

SM Does the platform allow for the The OS, middleware, and application
3.2 deployment of patches and OS updates? components are regularly patched using
automated pipelines. These components
are scanned for any vulnerabilities and
patches are deployed within strict
timeframes.
SM Does the platform allow for configuration The system is configured and deployed
3.3 management practices such as removal using various standard techniques such as
or disabling of services to maintain Kubernetes Helm charts and YAML files.
security? The service can be disabled in all regions
within minutes by disabling DNS entries,
reverse proxies, etc.
SM Does the security tool support logging Syslog data is streamed to centralized
4.1 and sending that data to rsyslog or a logging mechanisms. The security events
SIEM? data is also made available to clients using
the Activity Tracker mechanism.
SM Does the platform monitor the security Continuous monitoring for security is
4.2 and vulnerabilities associated with all accomplished by using firewalls and
software and dependencies used? service mesh.
SM Is anti-malware or antivirus able to be All systems running the system have anti-
4.3 installed on the system running your malware software running on them.
platform? Comprehensive reports are generated to
ensure compliance.
SM Does the platform allow for logging All successful and unsuccessful
4.4 connection events to the tool? connections are logged in the Activity
Tracker and in the Identity and Access
Management system of IBM Cloud.
SM Are there training courses or procedures Process documentation, runbooks,
4.5 in the event of an incident involving the training, and technology are in place to
tool or platform? respond to incidents in a timely manner.
High-severity incidents are tracked at
executive levels. Root-cause analysis is
performed and actionable tasks are
documented. Best practices are shared
across all teams in IBM Cloud.
SM Are there training courses in how to use Self-service tutorials are available to users
5.1 the products? Are there different courses based on their roles. Comprehensive
for different roles? documentation is available as well.

DRAFT

SM Are there training courses for teaching IBM Garage teams host courses for all
5.2 administrators how to utilize the aspects of the IBM Cloud platform.
platform?
SM Are trainings updated and metrics Regular trainings are conducted for all
5.3 collected to improve trainings? developers and administrators that are
responsible for operating the IBM Cloud.
The training materials are revised as new
best practices become available.
769
770 A.2.6 IBM MaaS360 with Watson Support of Security Measures

SM Does the software platform identify and Connections to IBM MaaS360 are Ref1
1.2 authenticate users and machine authenticated with API keys or credentials.
accounts that try to access the
platform?
SM Does the system allow for creating In the MaaS360 admin console, roles can Ref1
1.3 accounts with different access levels to be assigned to each administrator based
enforce least management? on their individual needs.
SM Does the system allow for creating In the MaaS360 admin console, custom Ref1
2.2 accounts with different access levels to roles can be defined with granular access
enforce least management? rights.
SM Are there training courses in how to use IBM MaaS360 offers training courses that Ref1
5.1 the products? Are there different are catered to the role an individual will
courses for different roles? hold utilizing the product.
SM Are there training courses for teaching IBM MaaS360 offers training courses for Ref1
5.2 administrators how to utilize the administrative users. Ref2
platform?
SM Are trainings updated and metrics Release Notes are regularly updated with Ref1
5.3 collected to improve trainings? new and updated feature information, and
the “MaaS360 Latest” panel provides
videos and tutorials on new and updated
capabilities. Each training course has a star
rating system for effectiveness and
improvement purposes.
771

DRAFT
772 A.2.7 Lookout MES Support of Security Measures

SM # Description Technical Mechanism or Configuration Refs.
SM Does the software platform allow for Organizations can integrate their existing
1.1 the use of a two-factor authentication Security Assertion Markup Language
method for access? (SAML) 2.0 MFA solutions for authorization
purposes into the Lookout MES Console.
SM Does the software platform identify and Lookout identifies and authenticates each
1.2 authenticate users and machine user or machine account that attempts to
accounts that try to access the access the platform. Audit logs also collect
platform? actions taken by each account.
SM Does the system allow for creating Lookout allows for the creation of several
1.3 accounts with different access levels to administrative types with decreasing levels
enforce least management? of access.
SM Does the software list and maintain an The Lookout MES Console provides a full
2.1 inventory of all software criticalities and application inventory list of all devices
integrations? within the customer’s user fleet.
SM Does the system allow for creating Lookout allows for the creation of several
2.2 accounts with different access levels to administrative types with decreasing levels
enforce least management? of access.
SM Does the system use or contain an Data at rest is encrypted using Advanced
2.3 option to enable the use of NIST- Encryption Standard (AES) 256-bit
certified cryptographic standards for encryption.
protecting data at rest?
SM Does the system use or contain an Data in transit is encrypted using TLS
2.4 option to enable the use of NIST- version 1.2.
certified cryptographic standards for
protecting data in transit?
SM Does the system support performing Daily backups and snapshots of the
2.5 regular backups and restorations? production environment are taken and
stored via Amazon’s S3 service within
multiple zones and US regions. Regular
integrity checks occur through restorations
occurring multiple times annually. These
restores populate new production
instances which are then verified and
monitored.

DRAFT

SM Does the product list all software The Lookout MES Console provides a full
3.1 dependencies and currently installed application inventory list of all devices
applications/services? within the customer's user fleet.
SM Does the platform allow for the Patches to the Lookout MES Console are
3.2 deployment of patches and OS updates? controlled and maintained by Lookout
backoffice support.
SM Does the security tool support logging Lookout uses a representational state
4.1 and sending that data to rsyslog or a transfer (REST) API to capture and send all
SIEM? console-related logs (e.g., device changes,
threat information, system audit events) to
SIEMs and syslog readers.
SM Does the platform monitor the security Lookout is Federal Risk and Authorization
4.2 and vulnerabilities associated with all Management Program (FedRAMP)
software and dependencies used? Moderate and therefore follows strict
patch management controls for patching
our own software.
SM Does the platform allow for logging Lookout captures connection events to the
4.4 connection events to the tool? tool and activities conducted within the
tool via our auditing capabilities.
SM Are there training courses or procedures Internally, Lookout has established
4.5 in the event of an incident involving the procedures for how to respond to a
tool or platform? security incident (leak, compromise, etc.).
These procedures follow strict FedRAMP
Moderate policies.
SM Are there training courses in how to use Lookout provides first-touch training and
5.1 the products? Are there different guidance for using the Lookout MES and
courses for different roles? for integration guidance with a customer's
MDM. Additionally, frequently asked
questions (FAQs), integration guides, and
console user guides are available to all
administrators via the Lookout Support
Knowledge portal.

DRAFT

SM Are there training courses for teaching Lookout provides first-touch training and
5.2 administrators how to utilize the guidance for using the Lookout MES and
platform? for integration guidance with a customer's
MDM. Additionally, FAQs, integration
guides, and console user guides are
available to all administrators via the
Lookout Support Knowledge portal.
773
774 A.2.8 Microsoft Endpoint Configuration Manager (ECM) Support of Security

775 Measures
SM Does the software platform allow for the Access to ECM Site Collections can be Ref1
1.1 use of a two-factor authentication restricted via strong authentication. This
method for access? can include MFA and passwordless
options like Windows Hello for Business.
SM Does the software platform identify and ECM natively audits logins and activities Ref1
1.2 authenticate users and machine accounts and can be reported on by utilizing ECM
that try to access the platform? Reports.
SM Does the system allow for creating ECM supports achieving least privilege Ref1
1.3 accounts with different access levels to through security roles, scopes, and
enforce least management? collections.
SM Does the system allow for the use of Microsoft provides guidance around the Ref1
1.4 DACLs, network segmentation, or ports and protocols required by ECM.
isolation for access to the platform? Customers can use this to implement
firewalls between services and clients.
SM Does the software list and maintain an Configuration Manager uses an in-console Ref1
2.1 inventory of all software criticalities and service method called Updates and
integrations? Servicing. It makes it easy to find and
install recommended updates for your
Configuration Manager infrastructure.
SM Does the system allow for creating ECM supports achieving least privilege Ref1
2.2 accounts with different access levels to through security roles, scopes, and
enforce least management? collections.

DRAFT

SM Does the system use or contain an option ECM supports encryption at rest natively Ref1
2.3 to enable the use of NIST-certified and through the use of BitLocker.
cryptographic standards for protecting
data at rest?
SM Does the system use or contain an option ECM supports encryption for data in Ref1
2.4 to enable the use of NIST-certified transport.
data in transit?
SM Does the system support performing Backup and restore operations are core Ref1
2.5 regular backups and restorations? resiliency capabilities in ECM.
SM Does the product list all software ECM lists the software dependencies that Ref1
3.1 dependencies and currently installed are required for the platform to operate
applications/services? on the server in addition to client end
nodes.
SM Does the platform allow for the Configuration Manager uses an in-console Ref1
3.2 deployment of patches and OS updates? service method called Updates and
Servicing. It makes it easy to find and
install recommended updates for your
Configuration Manager infrastructure.
SM Does the platform allow for configuration Configuration Manager supports installing Ref1
3.3 management practices such as removal specific roles, for example management
or disabling of services to maintain points, distribution points, and software
security? update points, which contain the services
required to run that service only.
SM Does the security tool support logging Logs are stored in the ECM database, log
4.1 and sending that data to rsyslog or a files, and Windows Event Logs.
SIEM? Implementation guidance is specific to the
capabilities of the SIEM.
SM Does the platform monitor the security Configuration Manager includes software Ref1
4.2 and vulnerabilities associated with all update monitoring, which can be used to
software and dependencies used? identify vulnerable software on its
infrastructure.
SM Is anti-malware or antivirus able to be Anti-malware and anti-virus solutions can Ref1
4.3 installed on the system running your be installed on the host operating system.
platform? Microsoft recommends allowlisting the
files and processes related to ECM.

DRAFT

SM Does the platform allow for logging Client and management point logging can Ref1
4.4 connection events to the tool? be configured at various levels to meet
customer requirements.
SM Are there training courses in how to use Microsoft offers training courses that are Ref1
5.1 the products? Are there different courses catered to the role an individual will have
for different roles? utilizing the product.
SM Are there training courses for teaching Microsoft provides e-learning and Ref1
5.2 administrators how to utilize the certification preparation guides for ECM
platform? on the Microsoft Learn portal. Hands-on
or train-the-trainer models are provided
through an implementation partner.
SM Are trainings updated and metrics Courses and certifications are periodically
5.3 collected to improve trainings? updated based on product enhancements
and feedback from customers.
776
777 A.2.9 Tenable.sc Support of Security Measures

SM Does the software platform allow for the MFA is achieved through certificate-based Ref1
1.1 use of a two-factor authentication authentication and SAML authentication. Ref2
method for access?
SM Does the software platform identify and This is default behavior. Connections are Ref1
1.2 authenticate users and machine accounts authenticated with API keys or Ref2
that try to access the platform? credentials, then handled via session
cookie.
SM Does the system allow for creating This is default behavior provided by role- Ref1
1.3 accounts with different access levels to based access control.
SM Does the system allow for the use of Tenable.sc can bind https interface to a Ref1
1.4 DACLs, network segmentation, or single IP/network interface card (NIC) and Ref2
isolation for access to the platform? utilize sideband networks for
management/administration.
SM Does the system allow for creating This is default behavior provided by role- Ref1
2.2 accounts with different access levels to based access control.

DRAFT

SM Does the system use or contain an option Tenable.sc provides encryption for critical Ref1
2.3 to enable the use of NIST-certified resources (target credentials). For
cryptographic standards for protecting vulnerability data and application
data at rest? configuration information, an external
data-at-rest solution is required.
SM Does the system use or contain an option This is default behavior. Ref1
2.4 to enable the use of NIST-certified
data in transit?
SM Does the system support performing Tenable supports administrator backup of Ref1
2.5 regular backups and restorations? the opt/sc directory. Backups can be
scripted to run on the host OS.
SM Does the security tool support logging The Tenable.sc application can use the Ref1
4.1 and sending that data to rsyslog or a host OS’s syslog implementation to
SIEM? leverage an external syslog or SIEM.
SM Does the platform monitor the security Tenable.sc can scan an environment Ref1
4.2 and vulnerabilities associated with all passively (with the use of Nessus Network Ref2
software and dependencies used? Monitor/NNM) and actively to achieve
continuous monitoring.
SM Is anti-malware or antivirus able to be Anti-malware and anti-virus solutions can Ref1
4.3 installed on the system running your be installed. Tenable recommends Ref2
platform? allowlisting the files and processes related
to Nessus and Tenable.sc.
SM Does the platform allow for logging NNM not only does passive analysis for Ref1
4.4 connection events to the tool? vulnerabilities, but it can also provide
logging of connection events as
Informational events.
SM Are there training courses or procedures Tenable has many training options Ref1
4.5 in the event of an incident involving the available to customers of our products, Ref2
tool or platform? including instructional videos, free Ref3
trainings, and paid trainings for deeper
dives and larger groups.
SM Are there training courses in how to use Tenable offers training courses that are Ref1
5.1 the products? Are there different courses catered to the role an individual will have Ref2
for different roles? utilizing the product. Ref3

DRAFT

SM Are there training courses for teaching Tenable offers training courses for Ref1
5.2 administrators how to utilize the administrative users. Ref2
platform? Ref3
SM Are trainings updated and metrics Tenable continually collects feedback and
5.3 collected to improve trainings? introduces changes based on product
updates and user feedback.
778 A.2.10 VMware vRealize Automation SaltStack Config Support of Security

779 Measures
SM Does the software platform identify and This can be set up in the SaltStack Config Ref1
1.2 authenticate users and machine accounts component or done through integration
that try to access the platform? with LDAP, AD, SAML, or OpenID Connect
(OIDC) providers.
SM Does the system allow for creating This can be set up in SaltStack Config or Ref1
1.3 accounts with different access levels to done through integration with LDAP, AD,
enforce least management? SAML, or OIDC providers.
SM Does the system allow for the use of The Linux OS hosting SaltStack Config can
1.4 DACLs, network segmentation, or be configured to perform network
isolation for access to the platform? isolation.
SM Does the software list and maintain an VMWare tracks each product used by
2.1 inventory of all software criticalities and SaltStack Config and any updates and
integrations? vulnerabilities in those products.
SM Does the system allow for creating This can be set up in SaltStack Config or Ref1
2.2 accounts with different access levels to done through integration with LDAP, AD,
enforce least management? SAML, or OIDC providers.
SM Does the system use or contain an option SaltStack Config has a FIPS-compliant Ref1
2.3 to enable the use of NIST-certified mode that can be configured at
cryptographic standards for protecting installation time to support encryption of
data at rest? data at rest.
SM Does the system use or contain an option SaltStack Config supports encryption for
2.4 to enable the use of NIST-certified data in transit by default. Key generation
cryptographic standards for protecting uses standard algorithms found in the
data in transit? OpenSSL library. These algorithms rely on
OS-generated random seed data.

DRAFT

SM Does the system support performing SaltStack Config allows administrators to Ref1
2.5 regular backups and restorations? perform manual backups.
SM Does the product list all software SaltStack provides a list of all dependent
3.1 dependencies and currently installed software and libraries used within the
applications/services? product.
SM Does the platform allow for the The Linux system hosting SaltStack can be Ref1
3.2 deployment of patches and OS updates? updated by administrators. The SaltStack
SecOps component can be utilized to
perform updates on SaltStack nodes and
client end nodes.
SM Does the platform allow for configuration SaltStack Config allows for configuration Ref1
3.3 management practices such as removal management through the implementation
or disabling of services to maintain of Salt states, the beacon and reactor
security? system, and/or orchestration.
SM Does the security tool support logging Salt returners can be used/configured to Ref1
4.1 and sending that data to rsyslog or a send logs to third-party tools like rsyslog,
SIEM? splunk, etc.
SM Does the platform monitor the security VMWare tracks each product used by
4.2 and vulnerabilities associated with all SaltStack Config and tracks any updates
software and dependencies used? and vulnerabilities that are announced by
the product owners.
SM Is anti-malware or antivirus able to be Anti-malware and anti-virus solutions can
4.3 installed on the system running your be installed on the host Linux OS.
platform?
SM Does the platform allow for logging You can set the logging level to debug or Ref1
4.4 connection events to the tool? turn on the audit trail, and that will
provide connection events.
SM Are there training courses or procedures There is official training for customers of Ref1
4.5 in the event of an incident involving the the platform. Also, support contracts can
tool or platform? be purchased to help troubleshoot and fix
incidents with the product.
SM Are there training courses in how to use VMware provides training on the Ref1
5.1 the products? Are there different courses underlying platform (SaltStack Config and
for different roles? vRealize Automation) as well as the
security operations product.

DRAFT

SM Are there training courses for teaching VMware provides training on the Ref1
5.2 administrators how to utilize the underlying platform (SaltStack Config and
platform? vRealize Automation) as well as the
security operations product.

DRAFT
780 Appendix B List of Acronyms
AD Active Directory
AES Advanced Encryption Standard
ANC Adaptive Network Control
API Application Programming Interface
BIOS Basic Input/Output System
CAC Common Access Card
CIO Chief Information Officer
CISO Chief Information Security Officer
CLI Command-Line Interface
CRADA Cooperative Research and Development Agreement
CVE Common Vulnerabilities and Exposures
CVSS Common Vulnerability Scoring System
DACL Discretionary Access Control List
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System
ECM (Microsoft) Endpoint Configuration Manager
EMM Enterprise Mobility Management
EO Executive Order
FAQ Frequently Asked Questions
FedRAMP Federal Risk and Authorization Management Program
FIPS Federal Information Processing Standards
FMC (Cisco) Firepower Management Center
FTD (Cisco) Firepower Threat Defense
HA High Availability

DRAFT
HSPD-12 Homeland Security Presidential Directive 12

IAM Identity and Access Management
ICS Industrial Control System
IoT Internet of Things
IP Internet Protocol
ISE (Cisco) Identity Services Engine
IT Information Technology
LDAP Lightweight Directory Access Protocol
MDM Mobile Device Manager
MES (Lookout) Mobile Endpoint Security
MFA Multi-Factor Authentication
NCCoE National Cybersecurity Center of Excellence
NIC Network Interface Card
NIST National Institute of Standards and Technology
NNM (Tenable) Nessus Network Monitor
OIDC OpenID Connect
OS Operating System
OT Operational Technology
PC Personal Computer
PIV Personal Identity Verification
REST Representational State Transfer
RMF Risk Management Framework
SaaS Software as a Service
SAML Security Assertion Markup Language
SAN Storage Area Network
SCCM (Microsoft) System Center Configuration Manager

DRAFT
SGT Security Group Tag

SIEM Security Information and Event Management
SM Security Measure
SMS (Microsoft) Systems Management Server
SP Special Publication
SPT (Forescout) Security Policy Templates
SSH Secure Shell
TLS Transport Layer Security
UEM Unified Endpoint Management
UI User Interface
VLAN Virtual Local Area Network
VM Virtual Machine
WaaS Windows as a Service
WSUS (Microsoft) Windows Server Update Services

Patching Nist SP 1800 31b Draft

Uploaded by

Copyright:

Available Formats

Patching Nist SP 1800 31b Draft

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Patching Nist SP 1800 31b Draft

Uploaded by

Copyright:

Available Formats

NIST SPECIAL PUBLICATION 1800-31B

Improving Enterprise Patching

This publication is available free of charge from

13 Comments on this publication may be submitted to: [email protected].

16 National Cybersecurity Center of Excellence

NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems ii

22 NATIONAL CYBERSECURITY CENTER OF EXCELLENCE

38 NIST CYBERSECURITY PRACTICE GUIDES

NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems iii

Peter Romness Cisco

Matthew Hyatt Cisco

John Loucaides Eclypsium

Travis Raines Eclypsium

Timothy Jones Forescout

Tom May Forescout

Michael Correa Forescout

Jeffrey Ward IBM MaaS360 with Watson

Joseph Linehan IBM MaaS360 with Watson

Cesare Coscia IBM MaaS360 with Watson

Jim Doran IBM Research Team

Shripad Nadgowda IBM Research Team

Victoria Mosby Lookout

NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems iv

Tim LeMaster Lookout

Dan Menicucci Microsoft

Steve Rachui Microsoft

Parisa Grayeli The MITRE Corporation

Yemi Fashina The MITRE Corporation

Nedu Irrechukwu The MITRE Corporation

Joshua Klosterman The MITRE Corporation

Allen Tan The MITRE Corporation

Josh Moll Tenable

Chris Jensen Tenable

Jeremiah Stallcup Tenable

John Carty VMware

Kevin Hansen VMware

Rob Robertson VMware

Rob Hilberding VMware

Brian Williams VMware

NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems v

Technology Partner/Collaborator Build Involvement

Cisco Cisco Firepower Threat Defense (FTD)

Eclypsium Eclypsium Administration and Analytics Service

Forescout Forescout Platform

IBM IBM Code Risk Analyzer

Lookout Lookout Mobile Endpoint Security

Microsoft Microsoft Endpoint Configuration Manager

VMware VMware vRealize Automation SaltStack Config

78 CALL FOR PATENT CLAIMS

NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems vi

103 Such statements should be addressed to: [email protected]

NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems vii

127 4 Components of the Example Solution ................................................ 13

NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems viii

133 4.1.5 Lookout .......................................................................................................................14

149 Appendix A Patch Management System Security Practices .................... 22

162 Appendix B List of Acronyms .................................................................. 47

NIST SP 1800-31B: Improving Enterprise Patching for General IT Systems ix