The TOE is a mobile device designed to support enterprises and individual users alike. Based upon Android 7.0 with a Linux 3.18 kernel and improved by LG (for example, adding NIST approved cryptographic algorithms, strengthening X.509 certificate checking, bolstering keystore protection, and applying security patches) to meet the MDFPP requirements, the TOE provides wireless connectivity and provides an execution environment for mobile applications.
","evaluation_configuration":"\r\n\r\nThe evaluated configuration consists of the following devices:
\r\n| \r\n Product \r\n | \r\n\r\n Carrier \r\n | \r\n\r\n Security SW Version \r\n | \r\n\r\n OS version \r\n | \r\n\r\n Build number \r\n | \r\n\r\n WFA Cert# \r\n | \r\n
| \r\n LG G6 \r\n | \r\n\r\n AT&T \r\n | \r\n\r\n MDF v3.0 Release 1 \r\n | \r\n\r\n Android 7.0 \r\n | \r\n\r\n NRD90U \r\n | \r\n\r\n WFA69452 \r\n | \r\n
| \r\n LG G6 \r\n | \r\n\r\n Verizon \r\n | \r\n\r\n MDF v3.0 Release 1 \r\n | \r\n\r\n Android 7.0 \r\n | \r\n\r\n NRD90U \r\n | \r\n\r\n WFA69251 \r\n | \r\n
| \r\n LG G6 \r\n | \r\n\r\n Sprint \r\n | \r\n\r\n MDF v3.0 Release 1 \r\n | \r\n\r\n Android 7.0 \r\n | \r\n\r\n NRD90U \r\n | \r\n\r\n WFA69457 \r\n | \r\n
| \r\n LG G6 \r\n | \r\n\r\n T-Mobile \r\n | \r\n\r\n MDF v3.0 Release 1 \r\n | \r\n\r\n Android 7.0 \r\n | \r\n\r\n NRD90U \r\n | \r\n\r\n WFA69454 \r\n | \r\n
| \r\n LG G6 \r\n | \r\n\r\n Open, | \r\n\r\n MDF v3.0 Release 1 \r\n | \r\n\r\n Android 7.0 \r\n | \r\n\r\n NRD90U \r\n | \r\n\r\n WFA69455 \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. Gossamer Security Solutions determined that the evaluation assurance level (EAL) for the TOE is EAL 1. The product, when delivered and configured as identified in the LG LG Electronics Inc. LG Android 7 devices (G6) Guidance Documentation, Version 0.1, February 8, 2017 document, satisfies all of the security functional requirements stated in the LG G6 Smartphone (MDFPP30/WLANCEP10) Security Target, Version 0.3, February 28, 2017. The project underwent CCEVS Validator review. The evaluation was completed in May 2017. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID10791-2017) prepared by CCEVS.
","environmental_strengths":"\r\n\r\nThe logical boundaries of the LG G6 Smartphone are realized in the security functions that it implements. Each of these security functions is summarized below.
\r\nCryptographic support:
\r\nThe TOE includes cryptographic components (including its BoringSSL library, its Kernel Loadable Cryptographic module, and its Application Processor) 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 and HTTPS and also to encrypt Data-At-Rest (including the generation and protection of keys 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 is designed to control access to system services by hosted applications, including protection of the Trust Anchor Database. Additionally, the TOE is designed to protect user and other sensitive data using encryption so that even if a device is physically lost, the data remains protected. The TOE supports Android for Work profiles to provide additional separation between application and application data belonging to the Android for Work profile. Please see the Admin Guide for additional details regarding how to set up and use Android for Work profiles.
\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 (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 up to 16 characters are supported.
\r\nThe TOE can also serve as an 802.1X supplicant and can both use X.509v3 and validate certificates for EAP-TLS, TLS, and HTTPS exchanges.
\r\nSecurity management:
\r\nThe 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 will remove Enterprise applications, remove MDM policies, and disable CC mode.
\r\nProtection of the TSF:
\r\nThe 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.
\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 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 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 an MDM) 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 802.11-2012, 802.1X, and EAP-TLS to secure communications channels between itself and other trusted network devices.
","features":[]}