Model Overview
Model Overview
References ....................................................................................................... 41
Cybersecurity Maturity Model Certification (CMMC) Model Overview Version 2.13 iii
Introduction
Introduction
The theft of intellectual property and sensitive information from all industrial sectors because
of malicious cyber activity threatens economic security and national security. The Council of
Economic Advisors estimates that malicious cyber activity cost the U.S. economy between $57
billion and $109 billion in 2016 [1]. The Center for Strategic and International Studies
estimates that the total global cost of cybercrime was as high as $600 billion in 2017 [2]. Over
a ten-year period, that burden would equate to an estimated $570 billion to $1.09 trillion
dollars in costs.
Malicious cyber actors have targeted and continue to target the Defense Industrial Base
(DIB) sector and the Department of Defense (DoD) supply chain. These attacks not only focus
on the large prime contractors, but also target subcontractors that make up the lower tiers
of the DoD supply chain. Many of these subcontractors are small entities that provide critical
support and innovation. Overall, the DIB sector consists of over 220,000 companies1 that
process, store, or transmit Controlled Unclassified Information (CUI) or Federal Contract
Information (FCI) in support of the warfighter and contribute towards the research,
engineering, development, acquisition, production, delivery, sustainment, and operations of
DoD systems, networks, installations, capabilities, and services. The aggregate loss of
intellectual property and controlled unclassified information from the DoD supply chain can
undercut U.S. technical advantages and innovation, as well as significantly increase the risk
to national security.
As part of multiple lines of effort focused on the security and resiliency of the DIB sector, the
DoD is working with industry to enforce the safeguarding requirements of the following
types of unclassified information within the supply chain:
• Federal Contract Information (FCI): is defined in 32 CFR § 170.4 and 48 CFR 4.1901 [3].
• Controlled Unclassified Information (CUI): is defined in 32 CFR § 2002.4 (h) [4].
To this end, the Office of the Under Secretary of Defense for Acquisition and Sustainment
(OUSD(A&S)) and DoD Chief Information Officer (CIO) have developed the Cybersecurity
Maturity Model Certification (CMMC) in concert with DoD stakeholders, University Affiliated
Research Centers (UARCs), Federally Funded Research and Development Centers (FFRDCs),
and the DIB sector.
1
Based on information from the Federal Procurement Data System, the average number of unique prime contractors
is approximately 212,657 and the number of known unique subcontractors is approximately 8,309. (FPDS from
FY18-FY21).
This document focuses on the Cybersecurity Maturity Model Certification (CMMC) Model as
set forth in section 170.14 of title 32, Code of Federal Regulations (CFR). The model
incorporates the security requirements from: 1) FAR 52.204-21, Basic Safeguarding of Covered
Contractor Information Systems, 2) NIST SP 800-171 Rev 2, Protecting Controlled Unclassified
Information in Nonfederal Systems and Organizations, and 3) a subset of the requirements from
NIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified
Information: A Supplement to NIST Special Publication 800-171. The CMMC Program is
designed to provide increased assurance to the DoD that defense contractors and
subcontractors are compliant with information protection requirements for FCI and CUI, and
are protecting such information at a level commensurate with risk from cybersecurity
threats, including Advanced Persistent Threats (APTs).
When implementing the CMMC model, an organization can achieve a specific CMMC level for
its entire enterprise network or for a particular enclave(s), depending on where the
information to be protected is handled and stored.
CMMC Model
2.1 Overview
The CMMC Model incorporates the security requirements from: 1) FAR 52.204-21, Basic
Safeguarding of Covered Contractor Information Systems, 2) NIST SP 800-171 Rev 2,
Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, and
3) a subset of the requirements from NIST SP 800-172, Enhanced Security Requirements for
Protecting Controlled Unclassified Information: A Supplement to NIST Special Publication
800—171. These source documents may be revised in the future, however the CMMC
security requirements will remain unchanged until the CMMC final rule is published. Any
further modifications to the CMMC rule will follow appropriate rulemaking procedures.
The CMMC Model consists of domains that map to the Security Requirement Families defined
in NIST SP 800-171 Rev 2.
Descriptions
• Level 1 Requirements. The security requirements in Level 1 are those set forth in FAR
clause 52.204-21(b)(1)(i) – (b)(1)(xv).
• Level 2 Requirements. The security requirements in Level 2 are identical to the
requirements in NIST SP 800-171 Rev 2.
• Level 3 Requirements. The security requirements in Level 3 are derived from NIST SP
800-172 with DoD-approved parameters where applicable, as identified in 32 CFR §
170.14(c)(4). DoD defined selections and parameters for the NIST SP 800-172
requirements are italicized, where applicable.
CMMC Overview
Level 1
Level 1 focuses on the protection of FCI and consists of the security requirements that
correspond to the 15 basic safeguarding requirements specified in 48 CFR 52.204-21,
commonly referred to as the FAR Clause.
Level 2
Level 2 focuses on the protection of CUI and incorporates the 110 security requirements
specified in NIST SP 800-171 Rev 2.
Level 3
Level 3 focuses on the protection of CUI and encompasses a subset of the NIST SP 800-
172 security requirements [5] with DoD-approved parameters. DoD-approved
parameters are denoted with underlining in section 2.4.1 below.
This subsection itemizes the security requirements for each domain and at each level. Each
requirement has a requirement identification number in the format – DD.L#-REQ – where:
Below the identification number, a short name identifier is provided for each requirement,
meant to be used for quick reference only. Finally, each requirement has a complete
requirement statement.
Level 1
AC.L1-b.1.i Limit information system access to authorized users, processes acting on
Authorized Access Control [FCI Data] behalf of authorized users, or devices (including other information systems).
AC.L1-b.1.ii Limit information system access to the types of transactions and functions
Transaction & Function Control [FCI that authorized users are permitted to execute.
Data]
AC.L1-b.1.iii Verify and control/limit connections to and use of external information
External Connections [FCI Data] systems.
AC.L1-b.1.iv Control information posted or processed on publicly accessible information
Control Public Information [FCI Data] systems.
Level 2
AC.L2-3.1.1 Limit system access to authorized users, processes acting on behalf of
Authorized Access Control [CUI Data] authorized users, and devices (including other systems).
AC.L2-3.1.2 Limit system access to the types of transactions and functions that
Transaction & Function Control [CUI authorized users are permitted to execute.
Data]
AC.L2-3.1.3 Control the flow of CUI in accordance with approved authorizations.
Control CUI Flow
AC.L2-3.1.4 Separate the duties of individuals to reduce the risk of malevolent activity
Separation of Duties without collusion.
AC.L2-3.1.5 Employ the principle of least privilege, including for specific security
Least Privilege functions and privileged accounts.
AC.L2-3.1.6 Use non-privileged accounts or roles when accessing nonsecurity functions.
Non-Privileged Account Use
AC.L2-3.1.7 Prevent non-privileged users from executing privileged functions and
Privileged Functions capture the execution of such functions in audit logs.
AC.L2-3.1.8 Limit unsuccessful logon attempts.
Unsuccessful Logon Attempts
AC.L2-3.1.9 Provide privacy and security notices consistent with applicable CUI rules.
Privacy & Security Notices
AC.L2-3.1.10 Use session lock with pattern-hiding displays to prevent access and viewing
Session Lock of data after a period of inactivity.
AC.L2-3.1.11 Terminate (automatically) a user session after a defined condition.
Session Termination
AC.L2-3.1.12 Monitor and control remote access sessions.
Control Remote Access
AC.L2-3.1.13 Employ cryptographic mechanisms to protect the confidentiality of remote
Remote Access Confidentiality access sessions.
AC.L2-3.1.14 Route remote access via managed access control points.
Remote Access Routing
AC.L2-3.1.15 Authorize remote execution of privileged commands and remote access to
Privileged Remote Access security-relevant information.
AC.L2-3.1.16 Authorize wireless access prior to allowing such connections.
Wireless Access Authorization
AC.L2-3.1.17 Protect wireless access using authentication and encryption.
Wireless Access Protection
AC.L2-3.1.18 Control connection of mobile devices.
Mobile Device Connection
AC.L2-3.1.19 Encrypt CUI on mobile devices and mobile computing platforms.
Encrypt CUI on Mobile
AC.L2-3.1.20 Verify and control/limit connections to and use of external systems.
External Connections [CUI Data]
AC.L2-3.1.21 Limit use of portable storage devices on external systems.
Portable Storage Use
AC.L2-3.1.22 Control CUI posted or processed on publicly accessible systems.
Control Public Information [CUI Data]
Level 3
AC.L3-3.1.2e Restrict access to systems and system components to only those
Organizationally Controlled Assets information resources that are owned, provisioned, or issued by the
organization.
AC.L3-3.1.3e Employ secure information transfer solutions to control information
Secured Information Transfer flows between security domains on connected systems.
Level 2
AT.L2-3.2.1 Inform managers, systems administrators, and users of organizational
Role-Based Risk Awareness systems of the security risks associated with their activities and of the
applicable policies, standards, and procedures related to the security of
those systems.
AT.L2-3.2.2 Train personnel to carry out their assigned information security-related
Role-Based Training duties and responsibilities.
AT.L2-3.2.3 Provide security awareness training on recognizing and reporting potential
Insider Threat Awareness indicators of insider threat.
Level 3
AT.L3-3.2.1e Provide awareness training upon initial hire, following a significant cyber
Advanced Threat Awareness event, and at least annually, focused on recognizing and responding to
threats from social engineering, advanced persistent threat actors,
breaches, and suspicious behaviors; update the training at least annually or
when there are significant changes to the threat.
AT.L3-3.2.2e Include practical exercises in awareness training for all users, tailored by
Practical Training Exercises roles, to include general users, users with specialized roles, and privileged
users, that are aligned with current threat scenarios and provide feedback
to individuals involved in the training and their supervisors.
Level 2
AU.L2-3.3.1 Create and retain system audit logs and records to the extent needed to
System Auditing enable the monitoring, analysis, investigation, and reporting of unlawful or
unauthorized system activity.
AU.L2-3.3.2 Uniquely trace the actions of individual system users, so they can be held
User Accountability accountable for their actions.
AU.L2-3.3.3 Review and update logged events.
Event Review
Level 2
CM.L2-3.4.1 Establish and maintain baseline configurations and inventories of
System Baselining organizational systems (including hardware, software, firmware, and
documentation) throughout the respective system development life cycles.
CM.L2-3.4.2 Establish and enforce security configuration settings for information
Security Configuration Enforcement technology products employed in organizational systems.
CM.L2-3.4.3 Track, review, approve or disapprove, and log changes to organizational
System Change Management systems.
CM.L2-3.4.4 Analyze the security impact of changes prior to implementation.
Security Impact Analysis
CM.L2-3.4.5 Define, document, approve, and enforce physical and logical access
Access Restrictions for Change restrictions associated with changes to organizational systems.
CM.L2-3.4.6 Employ the principle of least functionality by configuring organizational
Least Functionality systems to provide only essential capabilities.
CM.L2-3.4.7 Restrict, disable, or prevent the use of nonessential programs, functions,
Nonessential Functionality ports, protocols, and services.
CM.L2-3.4.8 Apply deny-by-exception (blacklisting) policy to prevent the use of
Application Execution Policy unauthorized software or deny-all, permit-by-exception (whitelisting) policy
to allow the execution of authorized software.
CM.L2-3.4.9 Control and monitor user-installed software.
User-Installed Software
Level 3
CM.L3-3.4.1e Establish and maintain an authoritative source and repository to provide a
Authoritative Repository trusted source and accountability for approved and implemented system
components.
CM.L3-3.4.2e Employ automated mechanisms to detect misconfigured or unauthorized
Automated Detection & Remediation system components; after detection, remove the components or place the
components in a quarantine or remediation network to facilitate patching,
re-configuration, or other mitigations.
CM.L3-3.4.3e Employ automated discovery and management tools to maintain an up-to-
Automated Inventory date, complete, accurate, and readily available inventory of system
components.
Level 1
IA.L1-b.1.v Identify information system users, processes acting on behalf of users, or
Identification [FCI Data] devices.
IA.L1-b.1.vi Authenticate (or verify) the identities of those users, processes, or devices,
Authentication [FCI Data] as a prerequisite to allowing access to organizational information systems.
Level 2
IA.L2-3.5.1 Identify system users, processes acting on behalf of users, and devices.
Identification [CUI Data]
IA.L2-3.5.2 Authenticate (or verify) the identities of users, processes, or devices, as a
Authentication [CUI Data] prerequisite to allowing access to organizational systems.
IA.L2-3.5.3 Use multifactor authentication for local and network access to privileged
Multifactor Authentication accounts and for network access to non-privileged accounts.
IA.L2-3.5.4 Employ replay-resistant authentication mechanisms for network access to
Replay-Resistant Authentication privileged and non-privileged accounts.
IA.L2-3.5.5 Prevent reuse of identifiers for a defined period.
Identifier Reuse
IA.L2-3.5.6 Disable identifiers after a defined period of inactivity.
Identifier Handling
IA.L2-3.5.7 Enforce a minimum password complexity and change of characters when
Password Complexity new passwords are created.
IA.L2-3.5.8 Prohibit password reuse for a specified number of generations.
Password Reuse
IA.L2-3.5.9 Allow temporary password use for system logons with an immediate change
Temporary Passwords to a permanent password.
Level 3
IA.L3-3.5.1e Identify and authenticate systems and system components, where possible,
Bidirectional Authentication before establishing a network connection using bidirectional authentication
that is cryptographically based and replay resistant.
IA.L3-3.5.3e Employ automated or manual/procedural mechanisms to prohibit system
Block Untrusted Assets components from connecting to organizational systems unless the
components are known, authenticated, in a properly configured state, or in
a trust profile.
Level 2
IR.L2-3.6.1 Establish an operational incident-handling capability for organizational
Incident Handling systems that includes preparation, detection, analysis, containment,
recovery, and user response activities.
IR.L2-3.6.2 Track, document, and report incidents to designated officials and/or
Incident Reporting authorities both internal and external to the organization.
IR.L2-3.6.3 Test the organizational incident response capability.
Incident Response Testing
Level 3
IR.L3-3.6.1e Establish and maintain a security operations center capability that operates
Security Operations Center 24/7, with allowance for remote/on-call staff.
IR.L3-3.6.2e Establish and maintain a cyber incident response team that can be deployed
Cyber Incident Response Team by the organization within 24 hours.
MAINTENANCE (MA)
Level 2
MA.L2-3.7.1 Perform maintenance on organizational systems.
Perform Maintenance
MA.L2-3.7.2 Provide controls on the tools, techniques, mechanisms, and personnel used
System Maintenance Control to conduct system maintenance.
MA.L2-3.7.3 Sanitize equipment removed for off-site maintenance of any CUI.
Equipment Sanitization
MA.L2-3.7.4 Check media containing diagnostic and test programs for malicious code
Media Inspection before the media are used in organizational systems.
MA.L2-3.7.5 Require multifactor authentication to establish nonlocal maintenance
Nonlocal Maintenance sessions via external network connections and terminate such connections
when nonlocal maintenance is complete.
MA.L2-3.7.6 Supervise the maintenance activities of maintenance personnel without
Maintenance Personnel required access authorization.
Level 1
MP.L1-b.1.vii Sanitize or destroy information system media containing Federal Contract
Media Disposal [FCI Data] Information before disposal or release for reuse.
Level 2
MP.L2-3.8.1 Protect (i.e., physically control and securely store) system media containing
Media Protection CUI, both paper and digital.
MP.L2-3.8.2 Limit access to CUI on system media to authorized users.
Media Access
MP.L2-3.8.3 Sanitize or destroy system media containing CUI before disposal or release
Media Disposal [CUI Data] for reuse.
MP.L2-3.8.4 Mark media with necessary CUI markings and distribution limitations.
Media Markings
MP.L2-3.8.5 Control access to media containing CUI and maintain accountability for
Media Accountability media during transport outside of controlled areas.
MP.L2-3.8.6 Implement cryptographic mechanisms to protect the confidentiality of CUI
Portable Storage Encryption stored on digital media during transport unless otherwise protected by
alternative physical safeguards.
MP.L2-3.8.7 Control the use of removable media on system components.
Removable Media
MP.L2-3.8.8 Prohibit the use of portable storage devices when such devices have no
Shared Media identifiable owner.
MP.L2-3.8.9 Protect the confidentiality of backup CUI at storage locations.
Protect Backups
Level 2
PS.L2-3.9.1 Screen individuals prior to authorizing access to organizational systems
Screen Individuals containing CUI.
PS.L2-3.9.2 Protect organizational systems containing CUI during and after personnel
Personnel Actions actions such as terminations and transfers.
Level 3
PS.L3-3.9.2e Protect organizational systems when adverse information develops or is
Adverse Information obtained about individuals with access to CUI.
Level 1
PE.L1-b.1.viii Limit physical access to organizational information systems, equipment, and
Limit Physical Access [FCI Data] the respective operating environments to authorized individuals.
PE.L1-b.1.ix Escort visitors and monitor visitor activity; maintain audit logs of physical
Manage Visitors & Physical Access access; and control and manage physical access devices.
[FCI Data]
Level 2
PE.L2-3.10.1 Limit physical access to organizational systems, equipment, and the
Limit Physical Access [CUI Data] respective operating environments to authorized individuals.
PE.L2-3.10.2 Protect and monitor the physical facility and support infrastructure for
Monitor Facility organizational systems.
PE.L2-3.10.3 Escort visitors and monitor visitor activity.
Escort Visitors [CUI Data]
PE.L2-3.10.4 Maintain audit logs of physical access.
Physical Access Logs [CUI Data]
PE.L2-3.10.5 Control and manage physical access devices.
Manage Physical Access [CUI Data]
PE.L2-3.10.6 Enforce safeguarding measures for CUI at alternate work sites.
Alternative Work Sites
Level 2
RA.L2-3.11.1 Periodically assess the risk to organizational operations (including mission,
Risk Assessments functions, image, or reputation), organizational assets, and individuals,
resulting from the operation of organizational systems and the associated
processing, storage, or transmission of CUI.
RA.L2-3.11.2 Scan for vulnerabilities in organizational systems and applications
Vulnerability Scan periodically and when new vulnerabilities affecting those systems and
applications are identified.
Level 3
RA.L3-3.11.1e Employ threat intelligence, at a minimum from open or commercial sources,
Threat-Informed Risk Assessment and any DoD-provided sources, as part of a risk assessment to guide and
inform the development of organizational systems, security architectures,
selection of security solutions, monitoring, threat hunting, and response and
recovery activities.
RA.L3-3.11.2e Conduct cyber threat hunting activities on an on-going aperiodic basis or
Threat Hunting when indications warrant, to search for indicators of compromise in
organizational systems and detect, track, and disrupt threats that evade
existing controls.
RA.L3-3.11.3e Employ advanced automation and analytics capabilities in support of
Advanced Risk Identification analysts to predict and identify risks to organizations, systems, and system
components.
RA.L3-3.11.4e Document or reference in the system security plan the security solution
Security Solution Rationale selected, the rationale for the security solution, and the risk determination.
RA.L3-3.11.5e Assess the effectiveness of security solutions at least annually or upon
Security Solution Effectiveness receipt of relevant cyber threat information, or in response to a relevant
cyber incident, to address anticipated risk to organizational systems and the
organization based on current and accumulated threat intelligence.
RA.L3-3.11.6e Assess, respond to, and monitor supply chain risks associated with
Supply Chain Risk Response organizational systems and system components.
RA.L3-3.11.7e Develop a plan for managing supply chain risks associated with
Supply Chain Risk Plan organizational systems and system components; update the plan at least
annually, and upon receipt of relevant cyber threat information, or in
response to a relevant cyber incident.
Level 2
CA.L2-3.12.1 Periodically assess the security controls in organizational systems to
Security Control Assessment determine if the controls are effective in their application.
CA.L2-3.12.2 Develop and implement plans of action designed to correct deficiencies and
Operational Plan of Action reduce or eliminate vulnerabilities in organizational systems.
CA.L2-3.12.3 Monitor security controls on an ongoing basis to determine the continued
Security Control Monitoring effectiveness of the controls.
CA.L2-3.12.4 Develop, document, and periodically update system security plans that
System Security Plan describe system boundaries, system environments of operation, how
security requirements are implemented, and the relationships with or
connections to other systems.
Level 3
CA.L3-3.12.1e Conduct penetration testing at least annually or when significant security
Penetration Testing changes are made to the system, leveraging automated scanning tools and
ad hoc tests using subject matter experts.
Level 1
SC.L1-b.1.x Monitor, control, and protect organizational communications (i.e.,
Boundary Protection [FCI Data] information transmitted or received by organizational information systems)
at the external boundaries and key internal boundaries of the information
systems.
SC.L1-b.1.xi Implement subnetworks for publicly accessible system components that are
Public-Access System Separation physically or logically separated from internal networks.
[FCI Data]
Level 2
SC.L2-3.13.1 Monitor, control, and protect organizational communications (i.e.,
Boundary Protection [CUI Data] information transmitted or received by organizational information systems)
at the external boundaries and key internal boundaries of the information
systems.
SC.L2-3.13.2 Employ architectural designs, software development techniques, and
Security Engineering systems engineering principles that promote effective information security
within organizational systems.
SC.L2-3.13.3 Separate user functionality from system management functionality.
Role Separation
SC.L2-3.13.4 Prevent unauthorized and unintended information transfer via shared
Shared Resource Control system resources.
SC.L2-3.13.5 Implement subnetworks for publicly accessible system components that are
Public-Access System Separation physically or logically separated from internal networks.
[CUI Data]
SC.L2-3.13.6 Deny network communications traffic by default and allow network
Network Communication by communications traffic by exception (i.e., deny all, permit by exception).
Exception
SC.L2-3.13.7 Prevent remote devices from simultaneously establishing non-remote
Split Tunneling connections with organizational systems and communicating via some other
connection to resources in external networks (i.e., split tunneling).
SC.L2-3.13.8 Implement cryptographic mechanisms to prevent unauthorized disclosure of
Data in Transit CUI during transmission unless otherwise protected by alternative physical
safeguards.
Level 3
SC.L3-3.13.4e Employ physical isolation techniques or logical isolation techniques or both
Isolation in organizational systems and system components.
Level 1
SI.L1-b.1.xii Identify, report, and correct information and information system flaws in a
Flaw Remediation [FCI Data] timely manner.
SI.L1-b.1.xiii Provide protection from malicious code at appropriate locations within
Malicious Code Protection [FCI Data] organizational information systems.
SI.L1-b.1.xiv Update malicious code protection mechanisms when new releases are
Update Malicious Code Protection available.
[FCI Data]
SI.L1-b.1.xv Perform periodic scans of the information system and real-time scans of files
System & File Scanning [FCI Data] from external sources as files are downloaded, opened, or executed.
Level 2
SI.L2-3.14.1 Identify, report, and correct system flaws in a timely manner.
Flaw Remediation [CUI Data]
SI.L2-3.14.2 Provide protection from malicious code at designated locations within
Malicious Code Protection [CUI organizational systems.
Data]
SI.L2-3.14.3 Monitor system security alerts and advisories and take action in response.
Security Alerts & Advisories
SI.L2-3.14.4 Update malicious code protection mechanisms when new releases are
Update Malicious Code Protection available.
[CUI Data]
SI.L2-3.14.5 Perform periodic scans of organizational systems and real-time scans of files
System & File Scanning [CUI Data] from external sources as files are downloaded, opened, or executed.
SI.L2-3.14.6 Monitor organizational systems, including inbound and outbound
Monitor Communications for communications traffic, to detect attacks and indicators of potential attacks.
Attacks
SI.L2-3.14.7 Identify unauthorized use of organizational systems.
Identify Unauthorized Use
Level 3
SI.L3-3.14.1e Verify the integrity of security critical and essential software using root of
Integrity Verification trust mechanisms or cryptographic signatures.
SI.L3-3.14.3e Include specialized assets such as IoT, IIoT, OT, GFE, Restricted Information
Specialized Asset Security Systems and test equipment in the scope of the specified enhanced security
requirements or are segregated in purpose-specific networks.
SI.L3-3.14.6e Use threat indicator information and effective mitigations obtained from, at
Threat-Guided Intrusion Detection a minimum, open or commercial sources, and any DoD-provided sources, to
guide and inform intrusion detection and threat hunting.
• Level 1: the basic safeguarding requirements for FCI specified in FAR Clause 52.204-21.
• Level 2: the security requirements for CUI specified in NIST SP 800-171 Rev 2 per DFARS
Clause 252.204-7012
• Level 3: selected enhanced security requirements for CUI specified in NIST SP 800-172
with DoD-approved parameters where applicable.
MAINTENANCE (MA)
MP.L2-3.8.6
Portable Storage Encryption
Implement cryptographic mechanisms to
protect the confidentiality of CUI stored on
digital media during transport unless
otherwise protected by alternative physical
safeguards.
• NIST SP 800-171 Rev 2 3.8.6
MP.L2-3.8.7
Removable Media
Control the use of removable media on
system components.
• NIST SP 800-171 Rev 2 3.8.7
MP.L2-3.8.8
Shared Media
Prohibit the use of portable storage devices
when such devices have no identifiable
owner.
• NIST SP 800-171 Rev 2 3.8.8
MP.L2-3.8.9
Protect Backups
Protect the confidentiality of backup CUI at
storage locations.
• NIST SP 800-171 Rev 2 3.8.9
References
1. U.S. Executive Office of the President, Council of Economic Advisers (CEA), The Cost of
Malicious Cyber Activity to the U.S. Economy, available online at
https://www.whitehouse.gov/wp-content/uploads/2018/02/The-Cost-of-Malicious-
Cyber-Activity-to-the-U.S.-Economy.pdf, February 2018
2. Center for Strategic and International Studies (CSIS) and McAfee, Economic Impact of
Cybercrime - No Slowing Down, February 2018