NIAP: Compliant Product
NIAP/CCEVS
  NIAP  »»  Product Compliant List  »»  Compliant Product  
Compliant Product - Samsung Galaxy Devices on Android 9

Certificate Date:  2019.08.02

Validation Report Number:  CCEVS-VR-VID10979-2019

Product Type:    Virtual Private Network
   Mobility

Conformance Claim:  Protection Profile Compliant

PP Identifier:    PP-Module for VPN Client Version 2.1
  Protection Profile for Mobile Device Fundamentals Version 3.1
  Extended Package for Wireless LAN Client Version 1.0

CC Testing Lab:  Gossamer Security Solutions

Maintenance Release:
CC Certificate [PDF] Security Target [PDF] * Validation Report [PDF]

Assurance Activity [PDF]

Administrative Guide [PDF]

VPN Client Administrative Guide [PDF]


* This is the Security Target (ST) associated with the latest Maintenance Release.  To view previous STs for this TOE, click here.

Product Description

The TOE is a mobile device based on Android 9.0 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.

The 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 CC configuration.

  • 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.
  • The maximum password failure retry policy should be less than or equal to 30.
  • A screen lock password required to decrypt data on boot.
  • Revocation checking must be enabled.
  • External storage must be encrypted.
  • Password (non-container) recovery policy and password history must not be enabled.
  • When CC mode has been enabled, the TOE behaves as follows:

o    The TOE sets the system wide Android CC mode property to be enabled.

o    The TOE prevents loading of custom firmware/kernels and requires all updates occur through FOTA.

o    The TOE utilizes CAVP approved cryptographic ciphers for TLS.

o    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 Workspace container, which is part of the Knox Platform. 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 Workspace container created. Thus, the evaluation includes several Knox-specific claims that apply to a Knox Workspace container when created.

There are different models of the TOE, the Samsung Galaxy Devices on Android 9, and these models differ in their internal components (as described in Evaluated Configuration section below).


Evaluated Configuration


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 9 on Galaxy Devices Administrator Guide, version 5.0, May 22, 2019 and the Samsung VPN Client on Galaxy Devices Administrator Guide, version 5.0, June 24, 2019 documents, satisfies all of the security functional requirements stated in the Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 9 (MDFPP31/WLANCEP10/VPNC21) Security Target, Version 0.4, June 24, 2019.  The project underwent CCEVS Validator review.  The evaluation was completed in July 2019.  Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID10979-2019) prepared by CCEVS.


Environmental Strengths

The logical boundaries of the Samsung Galaxy Devices on Android 9 are realized in the security functions that it implements. Each of these security functions is summarized below.

Security Audit:

The 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.

Cryptographic support:

The 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, 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.

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 encryption so that even if a device is physically lost, the data remains protected. The functionality provided by a Knox Workspace container enhances 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.

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 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.

The 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.

Security management:

The 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.

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. 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.

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 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 IEEE 802.11-2012, 802.1X, EAP-TLS, TLS, HTTPS and IPsec to secure communications channels between itself and other trusted network devices.

Evaluated Configuration:

The model numbers of the mobile devices used during evaluation testing are as follows:

Device Name

Model
Number

Chipset Vendor

CPU

Android
Version

Kernel Version

Build Number

Galaxy S10e

SM-G970F

Samsung

Exynos 9820

9

4.14.85

PPR1.180610.011

Galaxy S10+

SM-G975U

Qualcomm

SM8150

9

4.14.78

PPR1.180610.011

Galaxy S9+

SM-G965F

Samsung

Exynos 9810

9

4.9.59

PPR1.180610.011

Galaxy S9+

SM-G965U

Qualcomm

SDM845

9

4.9.112

PPR1.180610.011

Galaxy Note8

SM-N950F

Samsung

Exynos 8895

9

4.4.111

PPR1.180610.011

Galaxy Note8

SM-N950U

Qualcomm

MSM8998

9

4.4.153

PPR1.180610.011

Table 1 Evaluated Devices

In addition to the evaluated devices, the following device models are claimed as equivalent with a note about the differences between the evaluated device and the equivalent models.

Evaluated Device

CPU

Equivalent Devices

Differences

Galaxy S10e (Samsung)

Exynos 9820

Galaxy S10 (Samsung)

Galaxy S10+ (Samsung)

Galaxy S10 5G (Samsung)

·   S10 & S10+ have ultrasonic fingerprint sensor

·   S10 & S10+ have larger screen sizes

·   S10 5G has different cellular modem

Galaxy S10+ (Qualcomm)

SM8150

Galaxy S10e (Qualcomm)

Galaxy S10 (Qualcomm)

Galaxy S10 5G (Qualcomm)

Galaxy Fold (Qualcomm)

·   S10e & Fold has side image fingerprint sensor

·   S10 & S10e have smaller screen sizes

·   S10 5G has different cellular modem

·   Fold has 2 screens

Galaxy S9+ (Samsung)

Exynos 9810

Galaxy S9 (Samsung)

Galaxy Note9 (Samsung)

·   S9 has smaller screen

·   Note9 includes S Pen & functionality to take advantage of it for input (not security related)

Galaxy S9+ (Qualcomm)

SDM845

Galaxy S9 (Qualcomm)

Galaxy Note9 (Qualcomm)

·   S9 has smaller screen

·   Note9 includes S Pen & functionality to take advantage of it for input (not security related)

Galaxy Note8 (Samsung)

Exynos 8895

Galaxy S8 (Samsung)

Galaxy S8+ (Samsung)

·   S8 & S8+ do not include S Pen

·   S8 & S8+ are smaller

Galaxy Note8 (Qualcomm)

MSM8998

Galaxy S8 (Qualcomm)

Galaxy S8+ (Qualcomm)

Galaxy S8 Active (Qualcomm)

Galaxy Tab S4 (All)

·   S8, S8+ & S8 Active do not include S Pen

·   S8, S8+ & S8 Active are smaller

·   S8 Active has a IP68 & MIL-STD-810G certified body

·   Tab S4 is tablet form factor (no voice calling)

·   T835 & T837 have LTE

·   T830 models only have Wi-Fi

Table 2 Equivalent Devices

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). 

For each device there are specific models which are validated. This table lists the specific carrier models that have the validated configuration (covering both evaluated and equivalent devices).

Device Name

Chipset Vendor

Base Model
Number

Carrier Models

Galaxy S10 5G

Samsung

SM-G977

B, N

Galaxy S10 5G

Qualcomm

SM-G977

P, T, U

Galaxy S10+

Samsung

SM-G975

F, N

Galaxy S10+

Qualcomm

SM-G975

U, SC-04L*, SCV42*

Galaxy S10

Samsung

SM-G973

F, N

Galaxy S10

Qualcomm

SM-G973

U, SC-03L*, SCV41*

Galaxy S10e

Samsung

SM-G970

F, N

Galaxy S10e

Qualcomm

SM-G970

U

Galaxy Fold

Qualcomm

SM-F900

F, N, U, SC-06L*, SCV44*

Galaxy Note9

Samsung

SM-N960

F, N

Galaxy Note9

Qualcomm

SM-N960

U, SC-01L*, SCV40*

Galaxy Tab S4

Qualcomm

SM-T830

None

SM-T835

N, None

SM-T837

A, R4, P, V, T

Galaxy S9+

Samsung

SM-G965

F, N

Galaxy S9+

Qualcomm

SM-G965

U, SC-03K*, SCV39*

Galaxy S9

Samsung

SM-G960

F, N

Galaxy S9

Qualcomm

SM-G960

U, SC-02K*, SCV38*

Galaxy Note8

Samsung

SM-N950

F, N

Galaxy Note8

Qualcomm

SM-N950

U, SC-01K*, SCV37*

Galaxy S8+

Samsung

SM-G950

F, N

Galaxy S8+

Qualcomm

SM-G950

U

Galaxy S8

Samsung

SM-G955

F, N

Galaxy S8

Qualcomm

SM-G955

U

Galaxy S8 Active

Qualcomm

SM-G892

A, U

Table 3 Carrier Models

 

The carrier models marked by * are explicit model numbers for those carriers and do not follow the standard specified for other models.  Where Carrier Models specifies “None” that means a device without a suffix is also a device that can be placed into a validated configuration.


Vendor Information

Logo
Samsung Electronics Co., Ltd.
Henry Jong-Hyeon Lee c/o Brian Wood
973-440-9125
be.wood@samsung.com

www.samsung.com
Site Map              Contact Us              Home