The TOE is a VPN client that runs on a mobile operating system (the TOE platform) based on Android 7.0 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.
\r\nThe TOE platform 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 platform must meet the following prerequisites in order for an administrator to transition the TOE platform to CC mode.
\r\n· Require a screen lock password (swipe, PIN, pattern, or facial recognition screen locks are not allowed).
\r\n· The maximum password failure retry policy should be less than or equal to ten.
\r\n· Device encryption must be enabled or a screen lock password required to decrypt data on boot.
\r\n· Revocation checking must be enabled.
\r\n· External storage must be encrypted.
\r\n· Password recovery policy must not be enabled.
\r\n· Password history length must not be set.
\r\nWhen CC mode has been enabled, the TOE platform behaves as follows.
\r\n· The TOE platform sets the system wide Android CC mode property to “Enabled” if all the prerequisites have been met.
\r\n· The TOE platform performs power-on self-tests.
\r\n· The TOE platform performs secure boot integrity checking of the kernel and key system executables.
\r\n· The TOE platform prevents loading of custom firmware/kernels and requires all updates occur through FOTA (Samsung’s Firmware Over The Air firmware update method)
\r\n· The TOE platform uses CAVP approved cryptographic ciphers when joining and communicating with wireless networks.
\r\n· The TOE platform utilizes CAVP approved cryptographic ciphers for TLS.
\r\n· The TOE platform ensures FOTA updates utilize 2048-bit PKCS #1 RSA-PSS formatted signatures (with SHA-512 hashing).
\r\nThere are different models of the mobile phone into which Samsung embeds the TOE (the Samsung Galaxy Devices VPN Client on Android 7). These models differ physically and differ in their internal components (as described in the table below).
","evaluation_configuration":"\r\n\r\nThe evaluated configuration consists of the following devices:
\r\n| \r\n Device Name \r\n | \r\n\r\n Model | \r\n\r\n \r\n Chipset \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 Galaxy S8 (Qualcomm) \r\n | \r\n\r\n SM-G950 \r\n | \r\n\r\n MSM8998 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 4.4.16 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S8 (System LSI) \r\n | \r\n\r\n SM-G950 \r\n | \r\n\r\n Exynos 8895 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 4.4.13 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S8 + (Qualcomm) \r\n | \r\n\r\n SM-G955 \r\n | \r\n\r\n MSM8998 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 4.4.16 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S8 + (System LSI) \r\n | \r\n\r\n SM-G955 \r\n | \r\n\r\n Exynos 8895 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 4.4.13 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S8 Active \r\n | \r\n\r\n SM-G892 \r\n | \r\n\r\n MSM8998 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 4.4.16 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n \r\n Galaxy Tab S3 \r\n | \r\n\r\n SM-T820 \r\n | \r\n\r\n MSM8996 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.18.31 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n SM-T825 \r\n | \r\n\r\n MSM8996 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.18.31 \r\n | \r\n\r\n NRD90M \r\n | \r\n|
| \r\n SM-T827 \r\n | \r\n\r\n MSM8996 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.18.31 \r\n | \r\n\r\n NRD90M \r\n | \r\n|
| \r\n Galaxy S7 (Qualcomm) \r\n | \r\n\r\n SM-G930 \r\n | \r\n\r\n MSM8996 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.18.31 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S7 (System LSI) \r\n | \r\n\r\n SM-G930 \r\n | \r\n\r\n Exynos 8890 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.18.14 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S7 Edge (Qualcomm) \r\n | \r\n\r\n SM-G935 \r\n | \r\n\r\n MSM8996 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.18.31 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S7 Edge (System LSI) \r\n | \r\n\r\n SM-G935 \r\n | \r\n\r\n Exynos 8890 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.18.14 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S7 Active \r\n | \r\n\r\n SM-G891 \r\n | \r\n\r\n MSM8996 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.18.31 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S6 Edge+ \r\n | \r\n\r\n SM-G928 \r\n | \r\n\r\n Exynos 7420 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n NRD90M \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 7.0 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S6 \r\n | \r\n\r\n SM-G920 \r\n | \r\n\r\n Exynos 7420 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S6 Edge \r\n | \r\n\r\n SM-G925 \r\n | \r\n\r\n Exynos 7420 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n NRD90M \r\n | \r\n
| \r\n Galaxy S6 Active \r\n | \r\n\r\n SM-G890 \r\n | \r\n\r\n Exynos 7420 \r\n | \r\n\r\n 7.0 \r\n | \r\n\r\n 3.10.61 \r\n | \r\n\r\n NRD90M \r\n | \r\n
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 4, September 2012. 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 4, July 2012. The product, when delivered and configured as identified in the Samsung VPN Client on Galaxy Devices Guidance documentation, Version 3.0, February 27, 2017 document, satisfies all of the security functional requirements stated in the Samsung Electronics Co., Ltd. Samsung Galaxy Devices VPN Client on Android 7 (IVPNCPP14) Security Target, Version 1.1, March 29, 2017. The project underwent CCEVS Validator review. The evaluation was completed in June 2017. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID10813-2017) prepared by CCEVS.
","environmental_strengths":"\r\n\r\nThe logical boundaries of the Samsung Galaxy VPN Client on Android 7 (IVPNCPP14) are realized in the security functions that it implements. Each of these security functions is summarized below.
\r\nCryptographic Support - The IPsec implementation is the primary function of the TOE. IPSec is used by the TOE to protect communication between itself and a VPN Gateway over an unprotected network. With the exception of the IPsec implementation, the TOE relies upon its underlying platform (evaluated against the Protection Profile For Mobile Device Fundamentals) for the cryptographic services specified in this Security Target.
\r\nUser data protection - The TOE ensures that residual information is protected from potential reuse in accessible objects such as network packets.
\r\nIdentification and authentication - The TOE platform provides the ability to use, store, and protect X.509 certificates and pre-shared keys that are used for IPsec Virtual Private Network (VPN) connections.
\r\nSecurity management - The TOE provides all the interfaces necessary to manage the security functions identified throughout this Security Target. In particular, the IPsec VPN is fully configurable by a combination of functions provided directly by the TOE and those available to the associated VPN gateway.
\r\nProtection of the TSF - The TOE relies upon its underlying platform to perform self-tests that cover the TOE as well as the functions necessary to securely update the TOE.
\r\nTrusted path/channels - The TOE is a VPN client that uses IPsec to established secure channels to corresponding VPN gateways.
","features":[]}