The TOE is a mobile device based on Android 12 with a built-in IPsec VPN client and modifications made to increase the level of security provided to end users and enterprises. The TOE is intended for use as part of an enterprise mobility solution providing mobile staff with enterprise connectivity.
\r\nThe TOE includes a Common Criteria mode (or “CC mode”) that an administrator can invoke using an MDM. The TOE must meet the following prerequisites in order for an administrator to transition the TOE to and remain in the CC configuration.
\r\n· Require a boot and device lock password (swipe, PIN, pattern, accessibility (direction), screen locks are not allowed). Acceptable biometrics vary with the device for the device lock.
\r\n· The maximum password failure retry policy should be less than or equal to 30.
\r\n· A screen lock password required to decrypt data on boot.
\r\n· Revocation checking must be enabled.
\r\n· Security and audit logging must be enabled.
\r\n· External storage must be encrypted.
\r\n· Developer debugging must be disabled.
\r\n· When CC mode has been enabled, the TOE behaves as follows:
\r\no The TOE sets the system wide Android CC mode property to be enabled.
\r\no The TOE prevents loading of custom firmware/kernels and requires all updates occur through FOTA.
\r\no The TOE utilizes ACVP/CAVP approved cryptographic ciphers for TLS.
\r\nThe TOE includes the ability to create separate profiles part of the Knox Platform. A profile provides a way to segment applications and data into two separate areas on the device, such as a personal area and a work area, each with its own separate apps, data and security policies. For this effort, the TOE was evaluated both without and with profiles created. Thus, the evaluation includes several Knox-specific claims that apply when these profiles are created.
\r\nThere are different models of the TOE, the Samsung Galaxy Devices on Android 12, and these models differ in their internal components (as described in the table below). All devices are A64 architecture.
","evaluation_configuration":"The logical boundaries of the Samsung Galaxy Devices on Android 12 - Fall 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 generates logs for a range of security relevant events. The TOE stores the logs locally so they can be accessed by an administrator or they can be exported to an MDM.
\r\nCryptographic support:
\r\nThe TOE includes multiple cryptographic libraries with ACVP 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, 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.
\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 functionality provided by work profiles and Knox Separated Apps enhance the security of user data by providing an additional layer of separation between different categories of apps and data while the device is in use. The TOE ensures that residual information is protected from potential reuse in accessible objects such as network packets.
\r\nIdentification and authentication:
\r\nThe TOE supports a number of features related to identification and authentication. From a user perspective, except for making phone calls to an emergency number, a password or Biometric Authentication Factor (BAF) must be correctly entered to unlock the TOE. In addition, even when the TOE is unlocked the password must be re-entered to change the password or re-enroll the biometric template. Passwords are obscured when entered so they cannot be read from the TOE's display, 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 case characters, numbers, and special characters and passwords between 4 and 16 characters are supported.
\r\nThe TOE can also serve as an 802.1X supplicant and can use X.509v3 and validate certificates for EAP-TLS, TLS and IPsec exchanges. The TOE can also act as a client or server in an authenticated Bluetooth pairing. In addition to storing X.509 certificates used for IPsec connections, the TOE can also securely store pre-shared keys for VPN connections.
\r\nSecurity management:
\r\nThe TOE provides all the interfaces necessary to manage the security functions (including the VPN client) 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. Once the TOE has been enrolled and then un-enrolled, it removes all MDM policies and disables CC mode.
\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. It 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.
\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 advisory message (banner) when users unlock the TOE for use.
\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 802.11-2012, 802.1X, EAP-TLS, TLS, HTTPS and IPsec to secure communications channels between itself and other trusted network devices.
","security_evaluation_summary":"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 Samsung Android 12 on Galaxy Devices Administrator Guide, Version 8.0.1, October 24, 2022 document, satisfies all of the security functional requirements stated in the Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 12 – Fall Security Target, Version 0.4, October 24, 2022. The project underwent CCEVS Validator review. The evaluation was completed in October 2022. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11307-2022) prepared by CCEVS.
","environmental_strengths":"The model numbers of the mobile devices used during evaluation testing are as follows:
\r\n| \r\n Device Name \r\n | \r\n\r\n Model Number \r\n | \r\n\r\n Chipset Vendor \r\n | \r\n\r\n SoC \r\n | \r\n\r\n Arch \r\n | \r\n\r\n Kernel \r\n | \r\n\r\n Build Number \r\n | \r\n
| \r\n Galaxy Z Flip4 \r\n | \r\n\r\n SM-F721 \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 8+ Gen 1 (SM8475) \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 5.10.81 \r\n | \r\n\r\n SP2A.220305.013 \r\n | \r\n
| \r\n Galaxy XCover6 Pro \r\n | \r\n\r\n SM-G736? \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 778G (SM7325) \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 5.4.147 \r\n | \r\n\r\n SP1A.210812.016 \r\n | \r\n
| \r\n Galaxy A53 5G \r\n | \r\n\r\n SM-A536 \r\n | \r\n\r\n Samsung \r\n | \r\n\r\n Exynos 1280 (S5E8825) \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 5.10.43 \r\n | \r\n\r\n SP1A.210812.016 \r\n | \r\n
| \r\n Galaxy A52 5G \r\n | \r\n\r\n SM-A526 \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 750G (SM7225) \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 4.19.152 \r\n | \r\n\r\n SP1A.210812.016 \r\n | \r\n
| \r\n Galaxy A71 5G \r\n | \r\n\r\n SM-A716 \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 765G (SM7250) \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 4.19.125 \r\n | \r\n\r\n SP1A.210812.016 \r\n | \r\n
| \r\n Galaxy Tab Active3 \r\n | \r\n\r\n SM-T575 \r\n | \r\n\r\n Samsung \r\n | \r\n\r\n Exynos 9810 \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 4.9.191 \r\n | \r\n\r\n SP1A.210812.016 \r\n | \r\n
\r\n
In addition to the evaluated devices:
\r\n| \r\n Evaluated Device \r\n | \r\n\r\n SoC \r\n | \r\n\r\n Equivalent Devices \r\n | \r\n\r\n Differences \r\n | \r\n
| \r\n Galaxy Z Flip4 \r\n | \r\n\r\n Snapdragon 8+ Gen 1 (SM8475) \r\n | \r\n\r\n Galaxy Z Fold4 5G \r\n | \r\n\r\n Z Fold4 > Z Flip4 in terms of display size \r\n | \r\n
| \r\n Galaxy Xcover6 Pro \r\n | \r\n\r\n Snapdragon 778G (SM7325) \r\n | \r\n\r\n Galaxy Tab Active4 Pro \r\n | \r\n\r\n Tab Active4 Pro is tablet and have bigger screen size \r\n | \r\n
| \r\n Galaxy A53 5G \r\n | \r\n\r\n Exynos 1280 (S5E8825) \r\n | \r\n\r\n N/A \r\n | \r\n\r\n |
| \r\n Galaxy A52 5G \r\n | \r\n\r\n Snapdragon 750G (SM7225) \r\n | \r\n\r\n Galaxy A42 5G \r\n | \r\n\r\n A52 5G > A42 5G screen resolution & RAM \r\n | \r\n
| \r\n Galaxy A71 5G \r\n | \r\n\r\n Snapdragon 765G (SM7250) \r\n | \r\n\r\n Galaxy A51 5G \r\n | \r\n\r\n A71 5G > A51 5G in terms of display size \r\n | \r\n
| \r\n Galaxy Tab Active3 \r\n | \r\n\r\n Exynos 9810 \r\n | \r\n\r\n N/A \r\n | \r\n\r\n \r\n | \r\n
\r\n
In general, the devices include a final letter or number at the end of the name that denotes that the device is for a specific carrier or region (for example, U = US Carrier build and F = International, which were used during the evaluation).
\r\nFor each device, there are specific models that are validated. This table lists the specific carrier models that have the validated configuration (covering both evaluated and equivalent devices).
\r\n| \r\n Device Name \r\n | \r\n\r\n Chipset Vendor \r\n | \r\n\r\n Chipset Name \r\n | \r\n\r\n Base Model Number \r\n | \r\n\r\n Carrier Models \r\n | \r\n
| \r\n Galaxy Z Flip4 \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 8+ Gen 1 (SM8475) \r\n | \r\n\r\n SM-F721 \r\n | \r\n\r\n W, B, C, N, U1, U, SC-54C*, SCG17*, \r\n | \r\n
| \r\n Galaxy Z Fold4 5G \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 8+ Gen 1 (SM8475) \r\n | \r\n\r\n SM-F936 \r\n | \r\n\r\n W, B, N, U1, U, SC-55C*, SCG16* \r\n | \r\n
| \r\n Galaxy XCover6 Pro \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 778G (SM7325) \r\n | \r\n\r\n SM-G736 \r\n | \r\n\r\n W, B, U1, U \r\n | \r\n
| \r\n Galaxy Tab Active4 Pro \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 778G (SM7325) \r\n | \r\n\r\n SM-T636 \r\n | \r\n\r\n B, N \r\n | \r\n
| \r\n SM-T638 \r\n | \r\n\r\n U \r\n | \r\n|||
| \r\n SM-T630 \r\n | \r\n\r\n None \r\n | \r\n|||
| \r\n Galaxy A53 5G \r\n | \r\n\r\n Samsung \r\n | \r\n\r\n Exynos 1280 (S5E8825) \r\n | \r\n\r\n SM-A536 \r\n | \r\n\r\n W, E, B, N, U1, V, U, SC-53C*, SCG15* \r\n | \r\n
| \r\n SM-S536 \r\n | \r\n\r\n DL \r\n | \r\n|||
| \r\n Galaxy A52 5G \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 750G (SM7225) \r\n | \r\n\r\n SM-A526 \r\n | \r\n\r\n W, B, U1, U, SC-53B \r\n | \r\n
| \r\n Galaxy A42 5G \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 750G (SM7225) \r\n | \r\n\r\n SM-A426 \r\n | \r\n\r\n B, N, U1, U \r\n | \r\n
| \r\n SM-S426 \r\n | \r\n\r\n DL \r\n | \r\n|||
| \r\n Galaxy A71 5G \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 765G (SM7250) \r\n | \r\n\r\n SM-A716 \r\n | \r\n\r\n U1, U, V \r\n | \r\n
| \r\n Galaxy A51 5G \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 765G (SM7250) \r\n | \r\n\r\n SM-A516 \r\n | \r\n\r\n V, SC54A*, SCG07*, \r\n | \r\n
| \r\n Galaxy Tab Active3 \r\n | \r\n\r\n Samsung \r\n | \r\n\r\n Exynos 9810 \r\n | \r\n\r\n SM-T577 \r\n | \r\n\r\n U \r\n | \r\n
| \r\n SM-T575 \r\n | \r\n\r\n N, None \r\n | \r\n|||
| \r\n SM-T570 \r\n | \r\n\r\n None \r\n | \r\n