An independent reference

Every CMMC term and Level 2 Requirement

CMMCpedia explains CMMC, the Cybersecurity Maturity Model Certification, one page per term and one page per requirement. Each page quotes the official source as Official Source Material. The author's own Practitioner Guidance follows, clearly labeled.

Everything the site publishes is listed below: first the terms by topic, then all 110 requirements by family, in the order NIST SP 800-171 gives them. You can also search the requirements, browse the vocabulary, read the whole reference on one page, or download it as a Markdown export.

The contract

10 terms

• 32 CFR Part 170

  The regulation that creates the CMMC Program: the levels, the assessment types, the scoping rules, and the affirmation you sign each year.

  Also called 32 CFR 170, Part 170, the CMMC Program rule

• 48 CFR (the DFARS rule)

  The acquisition regulations. This is where the clauses live that put NIST SP 800-171 and CMMC into a contract you actually signed.

  Also called 48 CFR, DFARS, Defense Federal Acquisition Regulation Supplement

• DFARS 252.204-7012

  The contract clause that put NIST SP 800-171 on your systems and requires you to report a cyber incident to DoD within 72 hours.

  Also called 7012, DFARS 7012, Safeguarding Covered Defense Information and Cyber Incident Reporting

• DFARS 252.204-7019

  The solicitation provision that makes a current NIST SP 800-171 score in SPRS a condition of being considered for award.

  Also called 7019, DFARS 7019, Notice of NIST SP 800-171 DoD Assessment Requirements

• DFARS 252.204-7020

  The clause that keeps your NIST SP 800-171 score in SPRS, lets the Government assess you, and blocks subcontract awards without a score.

  Also called 7020, DFARS 7020, NIST SP 800-171 DoD Assessment Requirements

• DFARS 252.204-7021

  The contract clause that requires a current CMMC status at the level the contract names, an annual affirmation, and flow-down to subcontracts.

  Also called 7021, DFARS 7021, Contractor Compliance With the Cybersecurity Maturity Model Certification Level Requirements

• FAR 52.204-21

  The clause holding the 15 basic safeguarding requirements for Federal Contract Information. It is the whole of CMMC Level 1.

  Also called 52.204-21, FAR 52.204-21, Basic Safeguarding of Covered Contractor Information Systems

• Flow-down

  Passing a contract requirement to your suppliers. Under 32 CFR 170.23 the CMMC level you flow down depends on what each supplier will handle.

  Also called flowdown, flow down, flow-down clause

• Prime contractor

  The company holding the contract directly with the Government. It owns the CMMC obligation for the whole supply chain beneath it.

  Also called prime, primes

• Subcontractor

  Any company furnishing supplies or services under a prime contract. CMMC reaches every tier that handles FCI or CUI, not just the first.

  Also called sub, subs, supplier

What you protect

7 terms

• Controlled technical information (CTI)

  Controlled technical information with military or space use. It is the CUI category most defense work produces, and it must carry distribution statement B to F.

  Also called CTI, controlled technical info

• Controlled Unclassified Information (CUI)

  CUI is unclassified information a law, regulation, or Government-wide policy requires you to protect. Handling it puts you at CMMC Level 2.

  Also called CUI, Controlled Unclassified Information

• CUI marking

  The banner and designation block an agency applies to CUI. Marking is the Government's job, and an unmarked document can still be CUI.

  Also called CUI markings, banner marking, CUI banner marking, CUI designation indicator

• CUI Registry

  The National Archives list of every approved CUI category, its marking, and the law behind it. It is the authoritative list, and it is public.

  Also called the Registry, NARA CUI Registry

• Export-controlled information

  Information whose export could harm national security. It is a CUI category, but export-controlled and CUI are not the same set of information.

  Also called export control, EXPT, export-controlled

• Federal Contract Information (FCI)

  FCI is information a contract provides to you or generates for the Government that is not for public release. Holding only FCI means CMMC Level 1.

  Also called FCI, Federal Contract Information

• ITAR

  The International Traffic in Arms Regulations, which control defense articles and technical data. Showing that data to a foreign person is an export.

  Also called International Traffic in Arms Regulations, 22 CFR 120

Scope and assets

12 terms

• Boundary

  The line between what is inside your assessment scope and what is outside it. An assessor tests whether the line is actually enforced.

  Also called assessment boundary, scope boundary, boundary protection

• Contractor risk managed asset

  An asset that could handle CUI but is not intended to, kept away by written policy. It gets a plan review rather than a full assessment.

  Also called CRMA, contractor risk managed assets

• CUI asset

  An asset that can process, store, or transmit CUI. These are assessed against all 110 Level 2 requirements, so the count drives your cost.

  Also called CUI assets, Controlled Unclassified Information asset

• Customer responsibility matrix

  The document from a service provider that says which requirements it meets and which are yours. The rule requires one for every ESP.

  Also called CRM, customer responsibility matrices

• Enclave

  A separated environment built to hold the controlled work and nothing else. It is the usual way a small company keeps its assessment small.

  Also called CUI enclave, secure enclave

• External service provider

  An outside provider handling your CUI or your security protection data. What it handles decides how it enters your assessment.

  Also called ESP, external service providers

• Inheritance

  Relying on someone else's control to meet a requirement. It is allowed, and you still have to show the control exists and works.

  Also called inherited controls, inheriting

• Out-of-scope asset

  An asset that cannot handle CUI and protects nothing that does. It is not assessed, and you must be ready to justify the claim.

  Also called out-of-scope assets, OOS asset

• Scope

  The set of assets that will be assessed. Scope is the single decision that drives your cost, your evidence burden, and your assessment length.

  Also called CMMC Assessment Scope, assessment scope, scoping

• Security protection asset

  An asset that provides security functions for your assessment scope. It is in scope and assessed against the requirements it is relevant to.

  Also called SPA, security protection assets

• Shared responsibility matrix

  A cloud provider's description of which parts of security it owns and which you own. Read it as the starting point, not as your evidence.

  Also called SRM, shared responsibility model, shared responsibility matrices

• Specialized asset

  Equipment that can handle CUI but cannot be fully secured: IoT, OT, Government furnished equipment, restricted systems, and test equipment.

  Also called specialized assets

Assessment

17 terms

• Assessment objective

  One lettered determination statement inside a requirement. Every applicable objective must be met, or the whole requirement is scored not met.

  Also called assessment objectives, determination statement

• Assessor

  The certified person who conducts your assessment. Assessors test objectives against evidence, and they do not advise you on how to fix gaps.

  Also called assessors, CMMC Certified Assessor, CCA, assessment team

• C3PAO

  A CMMC Third-Party Assessment Organization. It is the company that performs a Level 2 certification assessment and charges you for it.

  Also called CMMC Third-Party Assessment Organization, third-party assessor organization

• Cyber AB

  The Accreditation Body. It is the single organization DoD contracts with to authorize and accredit the assessors and other ecosystem members.

  Also called Accreditation Body, CMMC Accreditation Body, The Cyber AB

• DCMA DIBCAC

  The Government team that assesses defense contractors directly. It performs Level 3 assessments and the High assessments under DFARS 252.204-7020.

  Also called DIBCAC, Defense Industrial Base Cybersecurity Assessment Center

• Enduring exception

  A system where full compliance is not feasible and never will be. Documented in your SSP with mitigations, it is assessed as met.

  Also called enduring exceptions

• Evidence

  What you show an assessor to prove a requirement is met. It must be final, not draft, and it must match what your plan claims.

  Also called assessment evidence, artifacts

• NIST SP 800-171

  The publication holding the 110 security requirements that make up CMMC Level 2. Revision 2 is the version the CMMC Program uses.

  Also called 800-171, SP 800-171, NIST 800-171

• NIST SP 800-171A

  The companion publication holding the assessment objectives. It is the document an assessor actually works from, so it is the one to read.

  Also called 800-171A, SP 800-171A, NIST 800-171A

• Not applicable

  A finding that a requirement or objective does not apply to your environment. It counts the same as met, and it needs a written reason.

  Also called N/A, not applicable finding

• Plan of Action and Milestones (POA&M)

  A POA&M lists the CMMC requirements you have not met, who fixes each one, and by when. It buys a Conditional status and 180 days, not a pass.

  Also called POA&M, POAM, Plan of Action and Milestones

• Policy

  A short written statement of what your organization requires. It is approved, dated, and it says what people must do, not how.

  Also called policies, security policy

• Procedure

  The written steps that carry out a policy. It names who does what, in order, and it produces the records your assessment relies on.

  Also called procedures, standard operating procedure

• Self-assessment

  An assessment you conduct on your own system. It carries the same requirements as a certification assessment and the same legal weight.

  Also called self-assessments, Level 2 self-assessment, Level 1 self-assessment

• SPRS

  The Supplier Performance Risk System. It holds your NIST SP 800-171 score, your CMMC status, and the annual affirmation you sign.

  Also called Supplier Performance Risk System

• System Security Plan (SSP)

  The document describing your system and how it meets each requirement. It is itself a requirement, and it cannot go on a POA&M.

  Also called SSP, system security plan

• Temporary deficiency

  A known gap with a fix under way, documented in an operational plan of action. Handled properly, it is assessed as met.

  Also called temporary deficiencies

Certification

11 terms

• Affirmation

  The annual statement by a senior official that you still meet the requirements. It is entered in SPRS and it carries personal weight.

  Also called affirmations, affirmation of continuous compliance, affirming official

• CMMC

  The Cybersecurity Maturity Model Certification. It is the program that verifies a defense contractor meets the security requirements already in its contract.

  Also called Cybersecurity Maturity Model Certification

• Conditional certification

  The status you hold when your assessment left items on a POA&M. It lasts 180 days and expires if the closeout does not happen.

  Also called Conditional CMMC Status, conditional status

• Data flow diagram

  A drawing of how CUI moves through your organization. It is the artifact that makes a scoping decision defensible, and it is usually done first.

  Also called data flow diagrams, CUI data flow

• FedRAMP

  The Federal program that authorizes cloud services. A cloud service holding your CUI must meet the FedRAMP Moderate baseline or its equivalent.

  Also called Federal Risk and Authorization Management Program, FedRAMP Moderate

• Final certification

  The status you hold when every requirement is met. It lasts one year at Level 1 and three years at Level 2 and Level 3.

  Also called Final CMMC Status, final status

• FIPS 140 validation

  A cryptographic module tested and certificated under the NIST validation program. Encryption that is merely strong does not satisfy the requirement.

  Also called FIPS validation, FIPS 140, FIPS-validated cryptography

• Level 1

  The 15 basic safeguarding requirements for FCI, assessed by you every year. No plan of action is permitted at Level 1, ever.

  Also called CMMC Level 1, Level 1 (Self)

• Level 2

  The 110 requirements of NIST SP 800-171, assessed by you or by a C3PAO depending on what your contract says. This is where most CMMC work happens.

  Also called CMMC Level 2, Level 2 (Self), Level 2 (C3PAO)

• Level 3

  The 24 additional requirements from NIST SP 800-172, assessed by the Government. Final Level 2 (C3PAO) is a prerequisite for even starting.

  Also called CMMC Level 3, Level 3 (DIBCAC)

• Network diagram

  The drawing of your assessment scope. Table 3 requires one for every in-scope asset category, and an assessment starts from it.

  Also called network diagrams, scope diagram

Access Control AC

22 requirements

1. AC.L2-3.1.1

   Authorized Access Control

   Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).

2. AC.L2-3.1.2

   Transaction & Function Control

   Limit system access to the types of transactions and functions that authorized users are permitted to execute.

3. AC.L2-3.1.3

   Control CUI Flow

   Control the flow of CUI in accordance with approved authorizations.

4. AC.L2-3.1.4

   Separation of Duties

   Separate the duties of individuals to reduce the risk of malevolent activity without collusion.

5. AC.L2-3.1.5

   Least Privilege

   Employ the principle of least privilege, including for specific security functions and privileged accounts.

6. AC.L2-3.1.6

   Non-Privileged Account Use

   Use non-privileged accounts or roles when accessing nonsecurity functions.

7. AC.L2-3.1.7

   Privileged Functions

   Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.

8. AC.L2-3.1.8

   Unsuccessful Logon Attempts

   Limit unsuccessful logon attempts.

9. AC.L2-3.1.9

   Privacy & Security Notices

   Provide privacy and security notices consistent with applicable CUI rules.

10. AC.L2-3.1.10

    Session Lock

    Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.

11. AC.L2-3.1.11

    Session Termination

    Terminate (automatically) a user session after a defined condition.

12. AC.L2-3.1.12

    Control Remote Access

    Monitor and control remote access sessions.

13. AC.L2-3.1.13

    Remote Access Confidentiality

    Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.

14. AC.L2-3.1.14

    Remote Access Routing

    Route remote access via managed access control points.

15. AC.L2-3.1.15

    Privileged Remote Access

    Authorize remote execution of privileged commands and remote access to security-relevant information.

16. AC.L2-3.1.16

    Wireless Access Authorization

    Authorize wireless access prior to allowing such connections.

17. AC.L2-3.1.17

    Wireless Access Protection

    Protect wireless access using authentication and encryption.

18. AC.L2-3.1.18

    Mobile Device Connection

    Control connection of mobile devices.

19. AC.L2-3.1.19

    Encrypt CUI on Mobile

    Encrypt CUI on mobile devices and mobile computing platforms.

20. AC.L2-3.1.20

    External Connections

    Verify and control/limit connections to and use of external systems.

21. AC.L2-3.1.21

    Portable Storage Use

    Limit use of portable storage devices on external systems.

22. AC.L2-3.1.22

    Control Public Information

    Control information posted or processed on publicly accessible information systems.

Awareness and Training AT

3 requirements

1. AT.L2-3.2.1

   Role-Based Risk Awareness

   Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems.

2. AT.L2-3.2.2

   Role-Based Training

   Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.

3. AT.L2-3.2.3

   Insider Threat Awareness

   Provide security awareness training on recognizing and reporting potential indicators of insider threat.

Audit and Accountability AU

9 requirements

1. AU.L2-3.3.1

   System Auditing

   Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity.

2. AU.L2-3.3.2

   User Accountability

   Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions.

3. AU.L2-3.3.3

   Event Review

   Review and update logged events.

4. AU.L2-3.3.4

   Audit Failure Alerting

   Alert in the event of an audit logging process failure.

5. AU.L2-3.3.5

   Audit Correlation

   Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.

6. AU.L2-3.3.6

   Reduction & Reporting

   Provide audit record reduction and report generation to support on-demand analysis and reporting.

7. AU.L2-3.3.7

   Authoritative Time Source

   Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.

8. AU.L2-3.3.8

   Audit Protection

   Protect audit information and audit logging tools from unauthorized access, modification, and deletion.

9. AU.L2-3.3.9

   Audit Management

   Limit management of audit logging functionality to a subset of privileged users.

Configuration Management CM

9 requirements

1. CM.L2-3.4.1

   System Baselining

   Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.

2. CM.L2-3.4.2

   Security Configuration Enforcement

   Establish and enforce security configuration settings for information technology products employed in organizational systems.

3. CM.L2-3.4.3

   System Change Management

   Track, review, approve or disapprove, and log changes to organizational systems.

4. CM.L2-3.4.4

   Security Impact Analysis

   Analyze the security impact of changes prior to implementation.

5. CM.L2-3.4.5

   Access Restrictions for Change

   Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

6. CM.L2-3.4.6

   Least Functionality

   Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.

7. CM.L2-3.4.7

   Nonessential Functionality

   Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

8. CM.L2-3.4.8

   Application Execution Policy

   Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software.

9. CM.L2-3.4.9

   User-Installed Software

   Control and monitor user-installed software.

Identification and Authentication IA

11 requirements

1. IA.L2-3.5.1

   Identification

   Identify information system users, processes acting on behalf of users, or devices.

2. IA.L2-3.5.2

   Authentication

   Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.

3. IA.L2-3.5.3

   Multifactor Authentication

   Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.

4. IA.L2-3.5.4

   Replay-Resistant Authentication

   Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.

5. IA.L2-3.5.5

   Identifier Reuse

   Prevent reuse of identifiers for a defined period.

6. IA.L2-3.5.6

   Identifier Handling

   Disable identifiers after a defined period of inactivity.

7. IA.L2-3.5.7

   Password Complexity

   Enforce a minimum password complexity and change of characters when new passwords are created.

8. IA.L2-3.5.8

   Password Reuse

   Prohibit password reuse for a specified number of generations.

9. IA.L2-3.5.9

   Temporary Passwords

   Allow temporary password use for system logons with an immediate change to a permanent password.

10. IA.L2-3.5.10

    Cryptographically-Protected Passwords

    Store and transmit only cryptographically-protected passwords.

11. IA.L2-3.5.11

    Obscure Feedback

    Obscure feedback of authentication information.

Incident Response IR

3 requirements

1. IR.L2-3.6.1

   Incident Handling

   Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

2. IR.L2-3.6.2

   Incident Reporting

   Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

3. IR.L2-3.6.3

   Incident Response Testing

   Test the organizational incident response capability.

Maintenance MA

6 requirements

1. MA.L2-3.7.1

   Perform Maintenance

   Perform maintenance on organizational systems.

2. MA.L2-3.7.2

   System Maintenance Control

   Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.

3. MA.L2-3.7.3

   Equipment Sanitization

   Ensure equipment removed for off-site maintenance is sanitized of any CUI.

4. MA.L2-3.7.4

   Media Inspection

   Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.

5. MA.L2-3.7.5

   Nonlocal Maintenance

   Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.

6. MA.L2-3.7.6

   Maintenance Personnel

   Supervise the maintenance activities of maintenance personnel without required access authorization.

Media Protection MP

9 requirements

1. MP.L2-3.8.1

   Media Protection

   Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.

2. MP.L2-3.8.2

   Media Access

   Limit access to CUI on system media to authorized users.

3. MP.L2-3.8.3

   Media Disposal

   Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse.

4. MP.L2-3.8.4

   Media Markings

   Mark media with necessary CUI markings and distribution limitations.

5. MP.L2-3.8.5

   Media Accountability

   Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.

6. 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.

7. MP.L2-3.8.7

   Removable Media

   Control the use of removable media on system components.

8. MP.L2-3.8.8

   Shared Media

   Prohibit the use of portable storage devices when such devices have no identifiable owner.

9. MP.L2-3.8.9

   Protect Backups

   Protect the confidentiality of backup CUI at storage locations.

Personnel Security PS

2 requirements

1. PS.L2-3.9.1

   Screen Individuals

   Screen individuals prior to authorizing access to organizational systems containing CUI.

2. PS.L2-3.9.2

   Personnel Actions

   Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.

Physical Protection PE

6 requirements

1. PE.L2-3.10.1

   Limit Physical Access

   Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.

2. PE.L2-3.10.2

   Monitor Facility

   Protect and monitor the physical facility and support infrastructure for organizational systems.

3. PE.L2-3.10.3

   Escort Visitors

   Escort visitors and monitor visitor activity.

4. PE.L2-3.10.4

   Physical Access Logs

   Maintain audit logs of physical access.

5. PE.L2-3.10.5

   Manage Physical Access

   Control and manage physical access devices.

6. PE.L2-3.10.6

   Alternative Work Sites

   Enforce safeguarding measures for CUI at alternate work sites.

Risk Assessment RA

3 requirements

1. RA.L2-3.11.1

   Risk Assessments

   Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI.

2. RA.L2-3.11.2

   Vulnerability Scan

   Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.

3. RA.L2-3.11.3

   Vulnerability Remediation

   Remediate vulnerabilities in accordance with risk assessments.

Security Assessment CA

4 requirements

1. CA.L2-3.12.1

   Security Control Assessment

   Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.

2. CA.L2-3.12.2

   Plan of Action

   Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.

3. CA.L2-3.12.3

   Security Control Monitoring

   Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.

4. CA.L2-3.12.4

   System Security Plan

   Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems.

System and Communications Protection SC

16 requirements

1. SC.L2-3.13.1

   Boundary Protection

   Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.

2. SC.L2-3.13.2

   Security Engineering

   Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.

3. SC.L2-3.13.3

   Role Separation

   Separate user functionality from system management functionality.

4. SC.L2-3.13.4

   Shared Resource Control

   Prevent unauthorized and unintended information transfer via shared system resources.

5. SC.L2-3.13.5

   Public-Access System Separation

   Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.

6. SC.L2-3.13.6

   Network Communication by Exception

   Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).

7. SC.L2-3.13.7

   Split Tunneling

   Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (i.e., split tunneling).

8. SC.L2-3.13.8

   Data in Transit

   Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.

9. SC.L2-3.13.9

   Connections Termination

   Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.

10. SC.L2-3.13.10

    Key Management

    Establish and manage cryptographic keys for cryptography employed in organizational systems.

11. SC.L2-3.13.11

    CUI Encryption

    Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.

12. SC.L2-3.13.12

    Collaborative Device Control

    Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.

13. SC.L2-3.13.13

    Mobile Code

    Control and monitor the use of mobile code.

14. SC.L2-3.13.14

    Voice over Internet Protocol

    Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.

15. SC.L2-3.13.15

    Communications Authenticity

    Protect the authenticity of communications sessions.

16. SC.L2-3.13.16

    Data at Rest

    Protect the confidentiality of CUI at rest.

System and Information Integrity SI

7 requirements

1. SI.L2-3.14.1

   Flaw Remediation

   Identify, report, and correct system flaws in a timely manner.

2. SI.L2-3.14.2

   Malicious Code Protection

   Provide protection from malicious code at designated locations within organizational systems.

3. SI.L2-3.14.3

   Security Alerts & Advisories

   Monitor system security alerts and advisories and take action in response.

4. SI.L2-3.14.4

   Update Malicious Code Protection

   Update malicious code protection mechanisms when new releases are available.

5. SI.L2-3.14.5

   System & File Scanning

   Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.

6. SI.L2-3.14.6

   Monitor Communications for Attacks

   Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.

7. SI.L2-3.14.7

   Identify Unauthorized Use

   Identify unauthorized use of organizational systems.