NIST SP 800-171 & CMMC 2.0 3.1.18

Requirement

Control connection of mobile devices.

Assessment Objectives

  • Mobile devices that process, store, or transmit CUI are identified
  • Mobile device connections are authorized
  • Mobile device connections are monitored and logged

Potential Assessment Methods and Objects [NIST SP 800-171A]

Examine

  • Access control policy
  • Authorizations for mobile device connections to organizational systems
  • Procedures addressing access control for mobile device usage (including restrictions)
  • System design documentation
  • Configuration management plan
  • System security plan
  • System audit logs and records
  • System configuration settings and associated documentation
  • Other relevant documents or records

Interview

  • Personnel using mobile devices to access organizational systems
  • System or network administrators
  • Personnel with information security responsibilities

Test

  • Access control capability authorizing mobile device connections to organizational systems

Discussion [NIST SP 800-171 REV. 2]

A mobile device is a computing device that has a small form factor such that it can easily be carried by a single individual; is designed to operate without a physical connection (e.g., wirelessly transmit or receive information); possesses local, non-removable or removable data storage; and includes a self-contained power source. Mobile devices may also include voice communication capabilities, on-board sensors that allow the device to capture information, or built-in features for synchronizing local data with remote locations. Examples of mobile devices include smart phones, e-readers, and tablets. Due to the large variety of mobile devices with different technical characteristics and capabilities, organizational restrictions may vary for the different types of devices. Usage restrictions and implementation guidance for mobile devices include: device identification and authentication; configuration management; implementation of mandatory protective software (e.g., malicious code detection, firewall); scanning devices for malicious code; updating virus protection software; scanning for critical software updates and patches; conducting primary operating system (and possibly other resident software) integrity checks; and disabling unnecessary hardware (e.g., wireless, infrared). The need to provide adequate security for mobile devices goes beyond this requirement. Many controls for mobile devices are reflected in other CUI security requirements.

Further Discussion

Establish guidelines and acceptable requirements for proper configuration, use, and management of mobile devices. Devices that process, store, or transmit CUI must be identified with a device-specific identifier. There are many different types of identifiers, and it is important to select one that can accommodate all devices and be used in a consistent manner. These identifiers are important for facilitating the required monitoring and logging function. In addition to smartphones, consider the security of other portable devices such as e-readers and tablets. AC.L2-3.1.16, AC.L2-3.1.17, and AC.L2-3.1.18 are complementary requirements in that they all establish control for the connection of mobile devices and wireless devices through the use of authentication, authorization, and encryption mechanisms.

Examples

Example 1

Your organization has a policy stating that all mobile devices, including iPads, tablets, mobile phones, and Personal Digital Assistants (PDAs), must be approved and registered with the IT department before connecting to the network that contains CUI. The IT department uses a Mobile Device Management solution to monitor mobile devices and enforce policies across the enterprise [b,c].

Potential Assessment Considerations

  • Is a list of mobile devices that are permitted to process, store, or transmit CUI maintained [a,b]?
  • Is the system configured to only permit connections from identified, authorized mobile devices [b]?

References

  1. NIST SP 800-171 Rev. 2 3.1.18

Need help putting this into practice? See our NIST SP 800-171 & CMMC compliance services or read our NIST SP 800-171 & CMMC articles.

See LakeRidge in action.

Talk with our team about your framework, your gaps, and the right plan.

Get a demo

See LakeRidge in action.

Loading the booking calendar…