The Target of Evaluation (TOE) is Google Pixel Devices on Android 15. The TOE is a mobile device to support enterprises and individual users alike.
\r\nGoogle manufacturers some of the phones in multiple variants, differing in size (the designations vary, from the “base” device not having any, and other models having something like “a” or “Pro”) or build materials (entry and premium). The only differences between variants of a given device are build materials, screen type and size, battery capacity, cameras, RAM and Flash storage. The Pro phones are normally physically larger and have larger screen sizes, battery capacity and possibly RAM, while the “a” phones may have a smaller screen or different build materials. Storage options vary with each release and may be selectable by the customer of the device at purchase.
\r\nThe 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 5G/4G LTE/3G/2G mobile data networks). 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.
\r\nThe 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
","evaluation_configuration":"The evaluated configuration consists of the following devices:
Google Product | Model # | SoC | Kernel |
Pixel 9 Pro XL | GZC4K, GQ57S, GGX8B | Google Tensor G4 | 6.1 |
Pixel 9 Pro | GEC77, GWVK6, GR83Y | Google Tensor G4 | 6.1 |
Pixel 9 | GUR25, G1B60, G2YBB | Google Tensor G4 | 6.1 |
Pixel 9 Pro Fold | GGH2X, GC15S | Google Tensor G4 | 6.1 |
Pixel 9a | GXQ96, GTF7P, G3Y12 | Google Tensor G4 | 6.1 |
Pixel 8 Pro | G1NMW, GC3VE | Google Tensor G3 | 6.1 |
Pixel 8 | GKWS6, G9BQD | Google Tensor G3 | 6.1 |
Pixel 8a | G5760D, G6GPR, G8HHN | Google Tensor G3 | 6.1 |
Pixel Tablet | GTU8P | Google Tensor G2 | 6.1 |
Pixel Fold | G9FPL, G0B96 | Google Tensor G2 | 6.1 |
Pixel 7 Pro | GVU6C, G03Z5, GQML3 | Google Tensor G2 | 6.1 |
Pixel 7 | GE2AE, GFE4J, GP4BC | Google Tensor G2 | 6.1 |
Pixel 7a | GWKK3, GHL1X, G82U8, G0DZQ | Google Tensor G2 | 6.1 |
Pixel 6 Pro | GF5KQ, G8V0U, GLU0G | Google Tensor | 6.1 |
Pixel 6 | GR1YH, GB7N6, G9S9B | Google Tensor | 6.1 |
Pixel 6a | GX7AS, GB62Z, G1AZG, GB17L | Google Tensor | 6.1 |
The evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) requirements and guidance. The evaluation demonstrated that the TOE meets the security requirements contained in the Security Target. The criteria against which the TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 5, April 2017. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Evaluation Methodology, Version 3.1, Revision 5, April 2017. The product, when delivered and configured as identified in the Google Pixel Phones on Android 15 Administrator Guidance Documentation, Version 1.0, April 4, 2025 document, satisfies all of the security functional requirements stated in the Google Pixel Devices on Android 15 - Security Target, Version 1.0, April 4, 2025. The project underwent CCEVS Validator review. The evaluation was completed in April 2025. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11545-2025) prepared by CCEVS
","environmental_strengths":"The logical boundaries of the Google Pixel Devices on Android 15 are realized in the security functions that it implements. Each of these security functions is summarized below.
\r\n\r\n
Security audit:
\r\nThe TOE implements the SecurityLog and logcat that are stored in circular memory buffers. An MDM agent can read/fetch the logs (both the SecurityLog and logcat) and then handle appropriately (potentially storing the log to Flash or transmitting its contents to the MDM server). These log methods meet the logging requirements outlined by FAU_GEN.1 in PP_MDF_V3.3.
\r\nCryptographic support:
\r\nThe TOE includes multiple cryptographic libraries with 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 are used to implement security protocols such as TLS, EAP-TLS, 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 PP_MDF_V3.3 standards.
\r\nUser data protection:
\r\nThe 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 encryption 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 applications 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.
\r\nIdentification and authentication:
\r\nThe TOE supports several features related to identification and authentication. From a user perspective, except for FCC mandated (making phone calls to an emergency number) or non-sensitive functions (e.g., choosing the keyboard input method or taking screen shots), a password (i.e., Password Authentication Factor) must be correctly entered to unlock the TOE. Also, even when unlocked, the TOE requires the user re-enter the password to change the password. Passwords are obscured when entered so they cannot be read from the TOE's display and the frequency of entering passwords is limited and when a configured number of failures occurs, the TOE will be wiped to protect its contents. Passwords can be constructed using upper and lower cases characters, numbers, and special characters and passwords up to 16 characters are supported. The TOE can also be configured to utilize a biometric authentication factor (fingerprints), to unlock the device (this only works after the password has been entered after the device powers on).
\r\nThe TOE can also serve as an 802.1X supplicant and can both use and validate X.509v3 certificates for EAP-TLS, TLS, and HTTPS exchange.
\r\nSecurity management:
\r\nThe TOE provides all the interfaces necessary to manage the security functions identified throughout the ST 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 an MDM solution once the TOE has been enrolled. Once the TOE has been enrolled and then un-enrolled, it will remove Enterprise applications and remove MDM policies.
\r\nProtection of the TSF:
\r\nThe 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 using the application processor’s hardware. The TOE disallows all read access to the Root Encryption Key (REK) 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 TEE is a Separate Execution Environment (SEE), running outside the Android operating system on the device.
\r\nThe 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 isolates the address spaces of applications from one another to protect those applications.
\r\nThe 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 signature checking also extends to verifying applications prior to their installation as all applications must have signatures (even if self-signed).
\r\nTOE access:
\r\nThe 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 (using the TOE’s MDM API) advisory message (banner) when the user unlocks the TOE for the first use after reboot.
\r\nThe TOE is also able to attempt to connect to wireless networks as configured.
\r\nTrusted path/channels:
\r\nThe TOE supports the use of IEEE 802.11-2012, 802.1X, and EAP-TLS and TLS, HTTPS to secure communications channels between itself and other trusted network devices
","features":[{"id":2226,"feature_name":"Asymmetric Key Generation"},{"id":3006,"feature_name":"Auditing"},{"id":2256,"feature_name":"Biometrics"},{"id":2232,"feature_name":"Bluetooth"},{"id":2225,"feature_name":"Certificate Authentication"},{"id":2224,"feature_name":"Certificate Validation"},{"id":2228,"feature_name":"Cryptographic Hashing"},{"id":2227,"feature_name":"Cryptographic Key Establishment"},{"id":2230,"feature_name":"Cryptographic Signature Generation"},{"id":2231,"feature_name":"Cryptographic Signature Verification"},{"id":2220,"feature_name":"DRBG"},{"id":2221,"feature_name":"EAP-TLS"},{"id":2222,"feature_name":"HTTPS Client"},{"id":3007,"feature_name":"Key Destruction"},{"id":2229,"feature_name":"Keyed-hash message authentication"},{"id":2245,"feature_name":"MDM-Agent"},{"id":2219,"feature_name":"Mobile Device"},{"id":2223,"feature_name":"Multifactor Authentication"},{"id":2233,"feature_name":"TLS 1.2"},{"id":2234,"feature_name":"TLS Client"},{"id":2247,"feature_name":"Wi-Fi 6"},{"id":2246,"feature_name":"WLAN Client"},{"id":2251,"feature_name":"WPA2"},{"id":2248,"feature_name":"WPA3"}]}