National Information Assurance Partnership
Common Criteria Evaluation and Validation Scheme
Validation Report
Motorola Mobility LLC Mobile Devices on Android 14
Report Number: CCEVS-VR-VID11577-2025
Dated: June 6, 2025
Version: 1.0
National Institute of Standards and Technology Department of Defense
Information Technology Laboratory ATTN: NIAP, Suite 6982
100 Bureau Drive 9800 Savage Road
Gaithersburg, MD 20899 Fort Meade, MD 20755-6982
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
ii
ACKNOWLEDGEMENTS
Validation Team
Jerome Myers
David Thompson
The Aerospace Corporation
Common Criteria Testing Laboratory
Nate Feldman
Raymond Smoley
Rizheng Sun
Khai Van
Gossamer Security Solutions, Inc.
Columbia, MD
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
iii
Table of Contents
1 Executive Summary .......................................................................................................................................1
2 Identification ..................................................................................................................................................2
3 Architectural Information...............................................................................................................................3
3.1 TOE Description.........................................................................................................3
3.2 TOE Evaluated Platforms...........................................................................................4
3.3 TOE Architecture .......................................................................................................4
3.4 Physical Boundaries ...................................................................................................4
4 Security Policy ...............................................................................................................................................4
4.1 Security audit..............................................................................................................5
4.2 Cryptographic support................................................................................................5
4.3 User data protection....................................................................................................5
4.4 Identification and authentication ................................................................................6
4.5 Security management .................................................................................................6
4.6 Protection of the TSF..................................................................................................6
4.7 TOE access .................................................................................................................7
4.8 Trusted path/channels.................................................................................................7
5 Assumptions & Clarification of Scope...........................................................................................................7
6 Documentation...............................................................................................................................................8
7 IT Product Testing..........................................................................................................................................8
7.1 Developer Testing ......................................................................................................8
7.2 Evaluation Team Independent Testing.......................................................................9
8 Evaluated Configuration ................................................................................................................................9
9 Results of the Evaluation................................................................................................................................9
9.1 Evaluation of the Security Target (ASE)....................................................................9
9.2 Evaluation of the Development (ADV)....................................................................10
9.3 Evaluation of the Guidance Documents (AGD).......................................................10
9.4 Evaluation of the Life Cycle Support Activities (ALC)...........................................10
9.5 Evaluation of the Test Documentation and the Test Activity (ATE).......................10
9.6 Vulnerability Assessment Activity (VAN) ..............................................................11
9.7 Summary of Evaluation Results ...............................................................................11
10 Validator Comments/Recommendations......................................................................................................11
11 Annexes........................................................................................................................................................11
12 Security Target.............................................................................................................................................11
13 Glossary .......................................................................................................................................................11
14 Bibliography.................................................................................................................................................12
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
1
1 Executive Summary
This report documents the assessment of the National Information Assurance Partnership
(NIAP) validation team of the evaluation of Motorola Mobility LLC Mobile Devices on
Android 14 (the Target of Evaluation, or TOE) provided by Motorola Mobility LLC. It
presents the evaluation results, their justifications, and the conformance results.
This Validation Report is not an endorsement of the Target of Evaluation by any agency of
the U.S. government, and no warranty is either expressed or implied.
The evaluation was performed by the Gossamer Security Solutions (Gossamer) Common
Criteria Testing Laboratory (CCTL) in Columbia, MD, United States of America, and was
completed in May 2025. The information in this report is largely derived from the Evaluation
Technical Report (ETR) and associated test reports, all written by Gossamer Security
Solutions. The evaluation determined that the product is both Common Criteria Part 2
Extended and Part 3 Extended conformant, and meets the assurance requirements of the:
• PP-Configuration for Mobile Device Fundamentals, Biometric enrollment and
verification – for unlocking the device, Bluetooth, and WLAN Clients, Version 1.0,
11 October 2022, which includes the following components:
o Base PP: Mobile Device Fundamentals, Version 3.3, 12 September 2022
o Collaborative PP-Module for Biometric enrolment and verification - for
unlocking the device, Version 1.1, 12 September 2022
o PP-Module for Bluetooth, Version 1.0, 15 April 2021
o PP-Module for WLAN Clients, Version 1.0, 31 March 2022
• Functional Package for Transport Layer Security (TLS), Version 1.1, 12 February
2019.
These security requirement documents are collectively referenced in this report as the PP-Set.
The Target of Evaluation (TOE) identified in this Validation Report has been evaluated at a
NIAP approved Common Criteria Testing Laboratory using the Common Methodology for IT
Security Evaluation (Version 3.1, Rev 5) for conformance to the Common Criteria for IT
Security Evaluation (Version 3.1, Rev 5). This Validation Report applies only to the specific
version of the TOE as evaluated. The evaluation has been conducted in accordance with the
provisions of the NIAP Common Criteria Evaluation and Validation Scheme and the
conclusions of the testing laboratory in the evaluation technical report are consistent with the
evidence provided.
The validation team monitored the activities of the evaluation team, provided guidance on
technical issues and evaluation processes, and reviewed the individual work units and
successive versions of the ETR. The validation team found that the evaluation showed that the
product satisfies all of the functional requirements and assurance requirements stated in the
Security Target (ST). Therefore the validation team concludes that the testing laboratory’s
findings are accurate, the conclusions justified, and the conformance results are correct. The
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
2
conclusions of the testing laboratory in the evaluation technical report are consistent with the
evidence produced.
The technical information included in this report was obtained from the Motorola Mobility
LLC Mobile Devices on Android 14 Security Target, version 0.4, June 3, 2025 and analysis
performed by the Validation Team.
2 Identification
The CCEVS is a joint National Security Agency (NSA) and National Institute of Standards
and Technology (NIST) effort to establish commercial facilities to perform trusted product
evaluations. Under this program, security evaluations are conducted by commercial testing
laboratories called Common Criteria Testing Laboratories (CCTLs) using the Common
Evaluation Methodology (CEM) in accordance with National Voluntary Laboratory
Assessment Program (NVLAP) accreditation.
The NIAP Validation Body assigns Validators to monitor the CCTLs to ensure quality and
consistency across evaluations. Developers of information technology products desiring a
security evaluation contract with a CCTL and pay a fee for their product’s evaluation. Upon
successful completion of the evaluation, the product is added to NIAP’s Validated Products
List.
Table 1 provides information needed to completely identify the product, including:
• The Target of Evaluation (TOE): the fully qualified identifier of the product as
evaluated.
• The Security Target (ST), describing the security features, claims, and assurances of
the product.
• The conformance results of the evaluation.
• The Protection Profiles to which the product is conformant.
• The organizations and individuals participating in the evaluation.
Table 1: Evaluation Identifiers
Item Identifier
Evaluation Scheme United States NIAP Common Criteria Evaluation and Validation Scheme
TOE Motorola Mobility LLC Mobile Devices on Android 14
(Specific models identified in Section 8)
Protection Profile PP-Configuration for Mobile Device Fundamentals, Biometric enrollment and
verification – for unlocking the device, Bluetooth, and WLAN Clients, Version
1.0, 11 October 2022 (CFG_MDF-BIO-BT-WLANC_V1.0) which includes the
Base PP: Mobile Device Fundamentals, Version 3.3, 12 September 2022 with the
collaborative PP-Module for Biometric enrolment and verification - for unlocking
the device, Version 1.1, 12 September 2022; the PP-Module for Bluetooth,
Version 1.0, 15 April 2021; and the PP-Module for WLAN Clients, Version 1.0,
31 March 2022; plus the Functional Package for Transport Layer Security (TLS),
Version 1.1, 12 February 2019.
ST Motorola Mobility LLC Mobile Devices on Android 14 Security Target, version
0.4, June 3, 2025
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
3
Item Identifier
Evaluation Technical
Report
Evaluation Technical Report for Motorola Mobility LLC Mobile Devices on
Android 14, Version 0.2 June 3, 2025
CC Version Common Criteria for Information Technology Security Evaluation, Version 3.1,
rev 5
Conformance Result CC Part 2 extended, CC Part 3 extended
Sponsor Motorola Mobility LLC
Developer Motorola Mobility LLC
Common Criteria
Testing Lab (CCTL)
Gossamer Security Solutions, Inc.
Columbia, MD
CCEVS Validators Jerome Myers and David Thompson of The Aerospace Corporation.
3 Architectural Information
Note: The following architectural description is based on the description presented in the
Security Target.
The Motorola Mobility LLC Devices are end-user mobile devices. The TOE allows basic
telephony features (make and receive phone calls, send and receive SMS/MMS messages) as
well as advanced network connectivity (allowing connections to both 802.11 Wi-Fi and
2G/3G/4G LTE/5G mobile data networks). The Devices use the Android operating system,
providing access to applications from the Google Play store. The TOE supports using client
certificates to connect to access points offering WPA2/WPA3 networks with 802.1x/EAP-
TLS, or alternatively connecting to cellular base stations when utilizing mobile data.
The TOE offers mobile applications an Application Programming Interface (API) including
that provided by the Android framework and supports API calls to the Android Management
APIs.
3.1 TOE Description
The TOE encompasses mobile devices that support enterprises and individual users alike.
Some features and settings must be enabled for the TOE to operate in its evaluated
configuration. The following features and settings must be enabled:
1. Require a lockscreen password
2. Disable Smart Lock
3. Enable Encryption of Wi-Fi and Bluetooth secrets by enabling ‘niap_mode’
4. Disable Debugging Features (Developer options)
5. Disable installation of applications from unknown sources
6. Enable Audit Logging
Doing this ensures that the device complies with the MDFPP requirements. Please refer to
the Admin Guide on how to configure these settings and features.
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
4
3.2 TOE Evaluated Platforms
Details regarding the evaluated configuration is provided in Section 8 below.
3.3 TOE Architecture
The TOE provides an API for mobile application use and provides users installing an
application the option to either approve or reject an application based upon the API access
that the application requires (or to grant applications access at runtime).
The TOE also provides users with the ability to protect Data-At-Rest with AES encryption,
including all user and mobile application data stored in the user’s data partition. The TOE
uses a key hierarchy that combines a Root Encryption Key (REK) with the user’s password to
provide protection to all user and application cryptographic keys stored in the TOE.
Finally, the TOE can interact with a Mobile Device Management (MDM) system (not part of
this evaluation) to allow enterprise control of the configuration and operation of the device so
as to ensure adherence to enterprise-wide policies (for example, restricting use of a corporate
provided device’s camera, forced configuration of maximum login attempts, pulling of audit
logs off the TOE, etc.) as well as policies governing enterprise applications and data. An
MDM is made up of two parts: the MDM agent and MDM server. The MDM Agent is
installed on the phone/mobile computer as an administrator with elevated permissions
(allowing it to change the relevant settings on the phone/device) while the MDM Server is
used to issue the commands to the MDM Agent. Neither portion of the MDM process is
considered part of the TOE, and therefore not being directly evaluated.
The TOE includes several different levels of execution including (from lowest to highest):
hardware, a Trusted Execution Environment, Android’s Linux kernel, and Android’s user
space, which provides APIs allowing applications to leverage the cryptographic functionality
of the device.
3.4 Physical Boundaries
The TOE’s physical boundary is the physical perimeter of its enclosure. The TOE runs the
Android operating system on a Qualcomm Snapdragon processor. The TOE does not include
the user applications that run on top of the operating system but does include controls that
limit application behavior. Further, the device provides support for downloadable MDM
agents to be installed to limit or permit the various functionality of the device. No built-in
MDM agent is pre-installed on the device.
The TOE communicates and interacts with 802.11-2012 Access Points and mobile data
networks to establish network connectivity, and through that connectivity interacts with
MDM servers that allow administrative control of the TOE.
4 Security Policy
This section summaries the security functionality of the TOE:
1. Security audit
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
5
2. Cryptographic support
3. User data protection
4. Identification and authentication
5. Security management
6. Protection of the TSF
7. TOE access
8. Trusted path/channels
4.1 Security audit
The TOE implements security and logcat logs that are both stored in circular memory buffers.
Logcat refers to log records traditionally viewable with the Android logcat command. In the
TOE, logcat records are considered user logs and are stored separately from the evaluated
security audit logs. An MDM agent can read and download the security logs, can retrieve the
logcat logs, and then handle them appropriately (potentially storing the logs to Flash or
transmitting their contents to the MDM server). These log methods meet the logging
requirements outlined by FAU_GEN.1 in MDFPPv3.3. Please see the Security audit section
for further information and specifics.
4.2 Cryptographic support
The TOE includes multiple cryptographic libraries with algorithms that have been shown to
be directly or indirectly conformant to CAVP certified algorithms for a wide range of
cryptographic functions including the following: asymmetric key generation and
establishment, symmetric key generation, encryption/decryption, cryptographic hashing and
keyed-hash message authentication. These functions are supported with suitable random bit
generation, key derivation, salt generation, initialization vector generation, secure key storage,
and key and protected data destruction. These primitive cryptographic functions may be used
to implement security protocols such as TLS, EAP-TLS, IPsec, and HTTPS and to encrypt the
media (including the generation and protection of data and key encryption keys) used by the
TOE. Many of these cryptographic functions are also accessible as services to applications
running on the TOE allowing application developers to ensure their application meets the
required criteria to remain compliant to MDFPP standards.
4.3 User data protection
The TOE controls access to system services by hosted applications, including protection of
the Trust Anchor Database. Additionally, the TOE protects user and other sensitive data using
File-Based Encryption (FBE) so that even if a device is physically lost, the data remains
protected. The TOE’s evaluated configuration supports Android Enterprise profiles to provide
additional separation between application and application data belonging to the Enterprise
profile. Please see the Admin Guide for additional details regarding how to set up and use
Enterprise profiles.
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
6
4.4 Identification and authentication
The TOE supports a number of features related to identification and authentication. From a
user perspective, except for FCC mandated functions, such as making phone calls to an
emergency number, and non-sensitive functions, such as choosing the keyboard input method
or taking screen shots, a password (e.g., Password Authentication Factor) must be correctly
entered to unlock the TOE. Also, even when unlocked, the TOE requires the user to re-enter
the password to change the password.
Passwords are obscured when entered so they cannot be read from the TOE's display. The rate
at which passwords are entered is metered and the number of failures is limited to a
configurable number. When the failure limit is exceeded, the TOE will perform a wipe of all
protected data. Passwords can be constructed using upper and lower cases characters,
numbers, and special characters. Password lengths must be between 4 and 16 characters.
The TOE can also serve as an 802.1X supplicant and can both use and validate X.509v3
certificates for EAP-TLS, TLS, and HTTPS exchanges.
4.5 Security management
The TOE provides all the interfaces necessary to manage the security functions identified
throughout this Security Target as well as other functions commonly found in mobile devices.
Many of the available functions are available to users of the TOE while many are restricted to
administrators operating through a Mobile Device Management solution, once the TOE has
been enrolled.
4.6 Protection of the TSF
The TOE implements a number of features to protect itself to ensure the reliability and
integrity of its security features. It protects particularly sensitive data such as cryptographic
keys so that they are not accessible or exportable through the use of the application
processor’s hardware. The TOE disallows all read access to the Root Encryption Key and
retains all keys derived from the REK within its Trusted Execution Environment (TEE).
Application software can only use keys derived from the REK by reference and receive the
result.
The TOE also provides its own timing mechanism to ensure that reliable time information is
available (e.g., for log accountability). It enforces read, write, and execute memory page
protections, uses address space layout randomization, and stack-based buffer overflow
protections to minimize the potential to exploit application flaws. It also protects itself from
modification by applications as well as to isolate the address spaces of applications from one
another to protect those applications.
The TOE includes functions to perform self-tests and software/firmware integrity checking so
that it might detect when it is failing or may be corrupt. If any self-tests fail, the TOE will not
go into an operational mode. It also includes mechanisms (i.e., verification of the digital
signature of each new image) so that the TOE itself can be updated while ensuring that the
updates will not introduce malicious or other unexpected changes in the TOE. Digital
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
7
signature checking also extends to verifying applications prior to their installation as all
applications must have signatures (even if self-signed).
4.7 TOE access
The TOE can be locked, obscuring its display, by the user or after a configured interval of
inactivity. The TOE also has the capability to display an administrator specified advisory
message or banner when the user unlocks the TOE for the first time after reboot.
The TOE is also able to attempt to connect to wireless networks as configured.
4.8 Trusted path/channels
The TOE supports the use of IEEE 802.11-2012, 802.1X, EAP-TLS and TLS, HTTPS to
secure communications channels between itself and other trusted network devices.
5 Assumptions & Clarification of Scope
Assumptions
The Security Problem Definition, including the assumptions, may be found in the following
documents:
• Mobile Device Fundamentals, Version 3.3, 12 September 2022
• collaborative PP-Module for Biometric enrolment and verification - for unlocking the
device, Version 1.1, 12 September 2022
• PP-Module for Bluetooth, Version 1.0, 15 April 2021
• PP-Module for WLAN Clients, Version 1.0, 31 March 2022
• Functional Package for Transport Layer Security (TLS), Version 1.1, 12 February
2019
That information has not been reproduced here. The PP-Set should be consulted if there is
interest in that material.
The scope of this evaluation was limited to the functionality and assurances covered in the
PP-Set as described for this TOE in the Security Target and in Section 1 of this document.
Other functionality included in the product was not assessed as part of this evaluation. All
other functionality provided by the devices should be assessed separately, and no further
conclusions about their effectiveness can be derived from this evaluation.
Note that this TOE stores audit logs in volatile memory, so when the device is powered off,
all audit logs are lost. In particular, the shutdown audit record, one required by the PP-Set, is
generated but erased almost immediately.
Clarification of scope
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
8
All evaluations (and all products) have limitations, as well as potential misconceptions that
need clarification. The following are some of the more important limitations and clarifications
of this evaluation.
• As with any evaluation, this evaluation only shows that the evaluated configuration
meets the security claims made with a certain level of assurance (the assurance
activities specified in the PP-Set and performed by the evaluation team).
• This evaluation covers only the specific device models and software as identified in
this document, and not any earlier or later versions released or in process.
• Apart from the Admin Guide, additional customer documentation for the specific
Mobile Device models was not included in the scope of the evaluation and therefore
should not to be relied upon when configuring or operating the device as evaluated.
• This evaluation did not specifically search for, nor attempt to exploit, vulnerabilities
that were not “obvious” or vulnerabilities to objectives not claimed in the ST. The
CEM defines an “obvious” vulnerability as one that is easily exploited with a
minimum of understanding of the TOE, technical sophistication and resources.
• The functionality evaluated is scoped exclusively to the security functional
requirements specified in the PP-Set and applicable Technical Decisions. Any
additional security related functional capabilities of the TOE were not covered by this
evaluation.
6 Documentation
The following documents were available with the TOE for evaluation:
• Motorola Mobility LLC Mobile Devices on Android 14 Administrator Guidance
Documentation, Version 0.2 June 3, 2025
Any additional customer documentation provided with the product, or that is available online
was not included in the scope of the evaluation and therefore should not be relied upon when
configuring or operating the device as evaluated. This includes web links in the evaluated
Administrator Guidance.
To use the product in the evaluated configuration, the product must be configured as specified
in the Guidance Documentation listed above.
7 IT Product Testing
This section describes the testing efforts of the developer and the Evaluation Team. It is
derived from information contained in the proprietary Detailed Test Report for Motorola
Mobility LLC Mobile Devices on Android 14, Version 0.2 June 3, 2025 (DTR), as
summarized in Section 3.4 of the Assurance Activity Report (AAR).
7.1 Developer Testing
No evidence of developer testing is required in the assurance activities for this product.
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
9
7.2 Evaluation Team Independent Testing
The evaluation team verified the product according to a Common Criteria Certification
document and ran the tests specified in the PP-Set, including the tests associated with optional
requirements. Section 1.1 of the AAR lists the tested devices, provides a list of test tools, and
has diagrams of the test environment.
8 Evaluated Configuration
This evaluation includes the following models and versions, when configured in accordance
with the documentation identified in Section 6 of this report.
Product Model Number CPU Arch Kernel Android
OS
version
Security Patch
Level
Motorola Edge
2024
XT2405-1
XT2405V
XT2307-1
XT2307-2
XT2307-3
Qualcomm
Snapdragon 7s Gen 2
(SM7435)
ARMv8 5.10 Android
14
May 2025
9 Results of the Evaluation
The results of the CCTL’s performance of the assurance requirements are generally described
in this section and are presented in detail in the proprietary ETR. The reader of this document
can assume that all assurance activities and work units received a passing verdict.
A verdict for an assurance component is determined by the resulting verdicts assigned to the
corresponding evaluator action elements. The evaluation was conducted based upon CC
version 3.1 rev 5 and CEM version 3.1 rev 5. The evaluation determined the Motorola
Mobility LLC Mobile Devices on Android 14 TOE to be Part 2 extended compliant, and to
meet the SARs contained in the PP-Set.
9.1 Evaluation of the Security Target (ASE)
The evaluation team applied each ASE CEM work unit. The ST evaluation ensured the ST
contains a description of the environment in terms of policies and assumptions, a statement of
security requirements claimed to be met by the Motorola Mobility LLC Mobile Devices on
Android 14 products that are consistent with the Common Criteria, and product security
function descriptions that support the requirements.
The validators reviewed the work of the evaluation team and found that the evaluation team
provided sufficient evidence and justification to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the
evaluation team was justified.
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
10
9.2 Evaluation of the Development (ADV)
The evaluation team applied each ADV CEM work unit. The evaluation team assessed the
design documentation and found it adequate to aid in understanding how the TSF provides the
security functions. The design documentation consists of a functional specification contained
in the Security Target and Guidance documents. Additionally, the evaluator performed the
assurance activities specified in the PP-Set related to the examination of the information
contained in the TSS.
The validators reviewed the work of the evaluation team and found that the evaluation team
provided sufficient evidence and justification to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the
evaluation team was justified.
9.3 Evaluation of the Guidance Documents (AGD)
The evaluation team applied each AGD CEM work unit. The evaluation team ensured the
adequacy of the user guidance in describing how to use the operational TOE. Additionally,
the evaluation team ensured the adequacy of the administrator guidance in describing how to
securely administer the TOE. All of the guides were assessed during the design and testing
phases of the evaluation to ensure they were complete.
The validators reviewed the work of the evaluation team and found that the evaluation team
provided sufficient evidence and justification to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the
evaluation team was justified.
9.4 Evaluation of the Life Cycle Support Activities (ALC)
The evaluation team applied each ALC CEM work unit. The evaluation team found that the
TOE components were consistently identified, and that bug fix information is available to the
TOE administrators.
The validators reviewed the work of the evaluation team and found that the evaluation team
provided sufficient evidence and justification to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the
evaluation team was justified.
9.5 Evaluation of the Test Documentation and the Test Activity (ATE)
The evaluation team applied each ATE CEM work unit. The evaluation team ran the set of
tests specified by the assurance activities in the PP-Set and recorded the results in a Test
Report, summarized in the AAR.
The validators reviewed the work of the evaluation team and found that the evaluation team
provided sufficient evidence and justification to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the
evaluation team was justified.
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
11
9.6 Vulnerability Assessment Activity (VAN)
The evaluation team applied each AVA CEM work unit. The vulnerability analysis is in the
Detailed Test Report (DTR) prepared by the evaluator. The vulnerability analysis includes a
public search for vulnerabilities. The public search for vulnerabilities did not uncover any
residual vulnerability.
On 2 June 2025 the evaluator searched the National Vulnerability Database
(https://web.nvd.nist.gov/view/vuln/search) and Vulnerability Notes Database
(http://www.kb.cert.org/vuls/) with the following search terms: “Motorola”, “Motorola
Mobility LLC”, “Android”, “Android 14”, “Motorola Mobility LLC Technologies
Corporation”, “Qualcomm Snapdragon 7”, “Qualcomm SM7435”, “Motorola Edge 2024”,
“BoringSSL”, “QTI Crypto Engine Core”, “QTI Inline Crypto Engine”, “Beryllium”,
“Android Locksettings service KBKDF”.
The validators reviewed the work of the evaluation team and found that the evaluation team
provided sufficient evidence and justification to confirm that the evaluation was conducted in
accordance with the requirements of the CEM, and that the conclusion reached by the
evaluation team was justified.
9.7 Summary of Evaluation Results
The evaluation team’s assessment of the evaluation evidence demonstrates that the claims in
the ST are met. Additionally, the evaluation team’s testing demonstrated the accuracy of the
claims in the ST.
The validation team’s assessment of the evidence provided by the evaluation team is that it
demonstrates that the evaluation team followed the procedures defined in the CEM, and
correctly verified that the product meets the claims in the ST.
10 Validator Comments/Recommendations
All validator comments and recommendations are adequately addressed in the Assumptions
and Clarification of Scope section.
11 Annexes
Not applicable
12 Security Target
The Security Target is identified as: Motorola Mobility LLC Mobile Devices on Android 14
Security Target, Version 0.4, June 3, 2025.
13 Glossary
The following definitions are used throughout this document:
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
12
• Common Criteria Testing Laboratory (CCTL). An IT security evaluation facility
accredited by the National Voluntary Laboratory Accreditation Program (NVLAP) and
approved by the CCEVS Validation Body to conduct Common Criteria-based evaluations.
• Conformance. The ability to demonstrate in an unambiguous way that a given
implementation is correct with respect to the formal model.
• Evaluation. The assessment of an IT product against the Common Criteria using the
Common Criteria Evaluation Methodology to determine whether or not the claims made
are justified; or the assessment of a protection profile against the Common Criteria using
the Common Evaluation Methodology to determine if the Profile is complete, consistent,
technically sound and hence suitable for use as a statement of requirements for one or
more TOEs that may be evaluated.
• Evaluation Evidence. Any tangible resource (information) required from the sponsor or
developer by the evaluator to perform one or more evaluation activities.
• Feature. Part of a product that is either included with the product or can be ordered
separately.
• Target of Evaluation (TOE). A group of IT products configured as an IT system, or an
IT product, and associated documentation that is the subject of a security evaluation under
the CC.
• Validation. The process carried out by the CCEVS Validation Body leading to the issue
of a Common Criteria certificate.
• Validation Body. A governmental organization responsible for carrying out validation
and for overseeing the day-to-day operation of the NIAP Common Criteria Evaluation and
Validation Scheme.
14 Bibliography
The Validation Team used the following documents to produce this Validation Report:
[1] Common Criteria for Information Technology Security Evaluation: Part 1:
Introduction and General Model, Version 3.1, Revision 5, April 2017.
[2] Common Criteria for Information Technology Security Evaluation Part 2: Security
functional components, Version 3.1, Revision 5, April 2017.
[3] Common Criteria for Information Technology Security Evaluation Part 3: Security
assurance components, Version 3.1 Revision 5, April 2017.
[4] Mobile Device Fundamentals, Version 3.3, 12 September 2022.
[5] collaborative PP-Module for Biometric enrolment and verification - for unlocking the
device, Version 1.1, 12 September 2022.
[6] PP-Module for Bluetooth, Version 1.0, 15 April 2021.
[7] PP-Module for WLAN Clients, Version 1.0, 31 March 2022.
Motorola Mobility LLC Validation Report Version 1.0 June 6, 2025
Mobile Devices on Android 14
13
[8] Functional Package for Transport Layer Security (TLS), Version 1.1, 12 February
2019.
[9] Motorola Mobility LLC Mobile Devices on Android 14 Security Target, Version 0.4,
June 3, 2025 (ST).
[10] Assurance Activity Report for Motorola Mobility LLC Mobile Devices on Android
14, Version 0.2 June 3, 2025 (AAR).
[11] Detailed Test Report for Motorola Mobility LLC Mobile Devices on Android 14,
Version 0.2 June 3, 2025 (DTR).
[12] Evaluation Technical Report for Motorola Mobility LLC Mobile Devices on Android
14, Version 0.2 June 3, 2025 (ETR).