NIAP Oversees Evaluations of Commercial IT Products for Use in National Security Systems

Short Name: pp_mdf_v3.3

Technology Type: Mobility

CC Version: 3.1

Date: 2022.09.12

Transition End Date: 2023.03.22

Preceded By: pp_mdf_v3.2

Conformance Claim: None

Protection Profile 

Control Mapping 

PP OVERVIEW

This assurance standard specifies information security requirements for Mobile Devices for use in an enterprise. A Mobile Device in the context of this assurance standard is a device, which is composed of a hardware platform and its system software. The device typically provides wireless connectivity and may include software for functions like secure messaging, email, web, VPN connection, and VoIP (Voice over IP), for access to the protected enterprise network, enterprise data and applications, and for communicating to other Mobile Devices.

Examples of a "Mobile Device" that should claim conformance to this Protection Profile include smartphones, tablet computers, and other Mobile Devices with similar capabilities.

The Mobile Device provides essential services, such as cryptographic services, data-at-rest protection, and key storage services to support the secure operation of applications on the device. Additional security features such as security policy enforcement, application mandatory access control, anti-exploitation features, user authentication, and software integrity protection are implemented in order to address threats.

This assurance standard describes these essential security services provided by the Mobile Device and serves as a foundation for a secure mobile architecture. The wireless connectivity shall be validated against the PP-Module for WLAN Client. If the mobile device contains Bluetooth functionality (i.e., has Bluetooth hardware), the Bluetooth connectivity shall be evaluated against the PP-Module for Bluetooth. As illustrated in Figure 2, it is expected that a typical deployment would also include either third-party or bundled components. Whether these components are bundled as part of the Mobile Device by the manufacturer or developed by a third-party, they must be separately validated against the related assurance standards such as the PP-Module for MDM Agent, PP-Module for VPN Client, PP-Module for VVoIP, and cPP-Module for Biometrics. It is the responsibility of the architect of the overall secure mobile architecture to ensure validation of these components. Additional applications that may come pre-installed on the Mobile Device that are not validated are considered to be potentially flawed, but not malicious. Examples include email client and web browser.

Assigned to the following Validated Products

• VID11317 – Google Pixel Devices on Android 13
• VID11349 – Apple iOS 16: iPhones
• VID11350 – Apple iPadOS 16: iPads
• VID11410 – Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 13 – Fall
• VID11412 – Motorola Mobility LLC Mobile Devices on Android 13
• VID11419 – Google Pixel Devices on Android 14

Active Related Technical Decisions

• 0724 – Format corrections for FAU_GEN.1.1 in MDF 3.3
  • References:  FAU_GEN.1.1
• 0704 – Part 3 (Extended) in CC Conformance Claims for MDF 3.3
  • References:  Section 2
• 0689 – RFC Update in FIA_X509_EXT.1 for MDF PP v3.3
  • References:  FIA_X509_EXT.1
• 0677 – Correction to Symbol in FCS_RBG_EXT.1 Test EA for MDF 3.3
  • References:  FCS_RBG_EXT.1