The Target of Evaluation (TOE) is the Samsung Electronics Co., Ltd. Samsung Galaxy Note 5 & Galaxy Tab S2 with Exynos 5433 ARMv8 (64-bit) (Tab S2) & Exynos 7420 ARMv8 (64-bit) (Note 5).
The TOE is a mobile operating system based on Android 5.1.1 with modifications made to increase the level of security provided to end users and enterprises. The TOE is intended to be used as part of an enterprise messaging solution providing mobile staff with enterprise connectivity.
The TOE includes a Common Criteria mode (or “CC mode”) that an administrator can invoke through the use of an MDM or through a dedicated administrative application (see the Guidance for instructions to obtain the application). The TOE must be configured as follows in order for an administrator to transition the TOE to CC mode.
· Require a screen lock password (swipe, PIN, pattern, or facial recognition screen locks are not allowed).
· The maximum password failure retry policy should be less than or equal to ten.
· Device encryption must be enabled.
· Revocation checking must be enabled.
When CC mode has been enabled, the TOE behaves as follows.
· The TOE sets the system wide Android CC mode property to “Enabled”.
· The TOE performs FIPS 140-2 power-on self-tests.
· The TOE performs self-tests for the key management.
· The TOE performs secure boot integrity checking of the kernel and key system executables.
· The TOE prevents loading of custom firmware/kernels and requires all updates occur through FOTA (Samsung’s Firmware Over The Air firmware update method)
· The TOE uses CAVP approved cryptographic ciphers when joining and communicating with wireless networks.
· The TOE utilizes CAVP approved cryptographic ciphers for TLS.
· The TOE ensures FOTA updates utilize 2048-bit PKCS #1 RSA-PSS formatted signatures (with SHA-512 hashing).
The TOE includes a containerization capability, KNOX. This container 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 a KNOX container created (and to create a KNOX container, one must purchase an additional license). Thus, the evaluation includes several KNOX-specific claims that apply to a KNOX container when created.
The evaluated configuration consists of the following devices:
\r\n| \r\n Device Name \r\n | \r\n\r\n Base Model | \r\n\r\n Processor \r\n | \r\n\r\n Android | \r\n\r\n Kernel Version \r\n | \r\n\r\n Build Number \r\n | \r\n\r\n Carrier Models \r\n | \r\n
| \r\n Galaxy Tab S2 8” Wi-Fi \r\n | \r\n\r\n SM-T710 \r\n | \r\n\r\n Exynos 5433 \r\n | \r\n\r\n 5.1.1 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n LMY47X \r\n | \r\n\r\n None \r\n | \r\n
| \r\n Galaxy Tab S2 8” LTE (EU Open) \r\n | \r\n\r\n SM-T715 \r\n | \r\n\r\n Exynos 5433 \r\n | \r\n\r\n 5.1.1 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n LMY47X \r\n | \r\n\r\n None \r\n | \r\n
| \r\n Galaxy Tab S2 10” Wi-Fi \r\n | \r\n\r\n SM-T810 \r\n | \r\n\r\n Exynos 5433 \r\n | \r\n\r\n 5.1.1 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n LMY47X \r\n | \r\n\r\n None \r\n | \r\n
| \r\n Galaxy Tab S2 10” LTE (EU/AU Open) \r\n | \r\n\r\n SM-T815 \r\n | \r\n\r\n Exynos 5433 \r\n | \r\n\r\n 5.1.1 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n LMY47X \r\n | \r\n\r\n Y, None \r\n | \r\n
| \r\n Galaxy Tab S2 10” LTE (US Models) \r\n | \r\n\r\n SM-T817 \r\n | \r\n\r\n Exynos 5433 \r\n | \r\n\r\n 5.1.1 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n LMY47X \r\n | \r\n\r\n T, P, R4, V, A \r\n | \r\n
| \r\n Galaxy Note 5 \r\n | \r\n\r\n SM-N920 \r\n | \r\n\r\n Exynos 7420 \r\n | \r\n\r\n 5.1.1 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n LRX22G \r\n | \r\n\r\n I, F, T, P, R4, V, A \r\n | \r\n
The devices include a final letter or number at the end of the name that denotes that the device is for a specific carrier (for example, V = Verizon Wireless and A = AT&T, which were used during the evaluation). The following list of letters/numbers denotes the specific models which are covered by the evaluation:
\r\nV – Verizon Wireless,
\r\nP - Sprint,
\r\nR4 – US Cellular,
\r\nS – SK Telecom,
\r\nL – LG Uplus,
\r\nK - Olleh,
\r\nA – AT&T,
\r\nT – T-Mobile,
\r\nI - International
\r\nOnly models with one of these suffixes can be placed into the validated configuration.
\r\nThe security software version is MDF v2.0 Release 4.
","security_evaluation_summary":"\r\n\r\nThe evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the Samsung Galaxy Note 5 & Galaxy Tab S2 was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 4. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 rev 4. The product, when delivered and configured as identified in the Samsung Android 5 on Galaxy Devices Guidance Documentation, version 2.3, October 1, 2015 and Samsung Android 5 on Galaxy S6 & S6 Edge & Tab S2 Devices Guidance Documentation, version 2.2, October 1, 2015 documents, satisfies all of the security functional requirements stated in the Samsung Electronics Co., Ltd. Samsung Galaxy Note 5 & Galaxy Tab S2 (MDFPP20) Security Target, Version 0.4, October 8, 2015. The project underwent CCEVS Validator review. The evaluation was completed in October 2015. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID10683-2015) prepared by CCEVS.
","environmental_strengths":"\r\n\r\nThe logical boundaries of the Samsung Galaxy Note 5 & Galaxy Tab S2 TOE are realized in the security functions that it implements. Each of these security functions is summarized below.
Cryptographic Support - The TOE includes a cryptographic module with CAVP certified algorithms for a wide range of cryptographic functions including: 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, IPsec, and HTTPS and also to encrypt the media (including the generation and protection of data, right, and key encryption keys) used by the TOE. Many of these cryptographic functions are also accessible as services to applications running on the TOE.
User Data Protection - The TOE is designed to control access to system services by hosted applications, including protection of the Trust Anchor Database. Additionally, the TOE is design to protect user and other sensitive data using encryption so that even if a device is physically lost, the data remains protected. The functionality provided by a KNOX container enhances the security of user data by providing an additional layer of separation between apps and data while the device is in use.
Identification and Authentication - The 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 (i.e., Password Authentication Factor) must be correctly entered to unlock the TOE. Also, even when the TOE is unlocked the password must be re-entered 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 between 4 and 16 characters are supported. The TOE can also serve as an 802.1X supplicant and can use X509v3 and validate certificates for EAP-TLS, TLS and IPsec exchanges.
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. Once the TOE has been enrolled and then un-enrolled, it removes all MDM policies and disables CC mode.
TSF Protection - The TOE implements a number of features designed 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 is also designed to protect 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 of the 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.
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 advisory message (banner) when users unlock the TOE for use. The TOE is also able to attempt to connect to wireless networks as configured.
Trusted Path/Channels - The TOE supports the use of 802.11-2012, 802.1X, EAP-TLS, TLS and IPsec to secure communications channels between itself and other trusted network devices.