{"product_id":10621,"v_id":10621,"product_name":"LG Electronics, Inc. G3 Smartphone Lollipop OS","certification_status":"Certified","certification_date":"2015-03-30T00:00:00Z","tech_type":"Mobility","vendor_id":{"name":"LG Electronics, Inc.","website":"www.lge.com"},"vendor_poc":"Mitchell Park","vendor_phone":"408-657-6361","vendor_email":"mitchell.park@lge.com","assigned_lab":{"cctl_name":"Gossamer Security Solutions"},"product_description":"<p class=\"Body\">The Target of Evaluation (TOE) is the LG G3 Smartphone Lollipop OS with a Qualcomm Snapdragon 801 (MSM8974AC) processor.&nbsp;</p>\r\n<p>The TOE is a mobile device intended to support enterprises and individual users alike.&nbsp; Based upon Android 5.0 and improved by LG, the TOE provides wireless connectivity and provides an execution environment for mobile applications.</p>\r\n<p class=\"Body\">The TOE provides an Application Programming Interface (API) to mobile applications and provides users installing an application the option to either approve or reject an application based upon the API access that the application requires.&nbsp;</p>\r\n<p class=\"Body\">The TOE also provides users with the ability to protect data-at-rest with AES encryption, including all user and mobile application data stored in the user&rsquo;s data partition.&nbsp; The TOE affords protection to all user and application cryptographic keys stored in the TOE.&nbsp; Moreover, the TOE provides users the ability to AES encrypt data and files stored on an SD Card inserted into the device.</p>\r\n<p>Finally, the TOE can interact with Mobile Device Management (MDM) to allow enterprise control of the configuration and operation of the device to ensure adherence to enterprise-wide policies</p>","evaluation_configuration":"<p class=\"Body\">The evaluated configuration for the LG G3 Smartphone Lollipop OS contains 32GB of internal Flash storage, 3GB of memory with a Qualcomm Snapdragon 801 (MSM8974AC) processor, and the product comes in the following different carrier versions.</p>\r\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\r\n<tbody>\r\n<tr>\r\n<td width=\"102\" valign=\"top\">\r\n<p><strong>Product</strong></p>\r\n</td>\r\n<td width=\"76\" valign=\"top\">\r\n<p><strong>Carrier</strong></p>\r\n</td>\r\n<td width=\"180\" valign=\"top\">\r\n<p><strong>Security Software Version</strong></p>\r\n</td>\r\n<td width=\"113\" valign=\"top\">\r\n<p><strong>OS version</strong></p>\r\n</td>\r\n<td width=\"162\" valign=\"top\">\r\n<p><strong>&nbsp;Build   number</strong></p>\r\n</td>\r\n</tr>\r\n<tr>\r\n<td width=\"102\" valign=\"top\">\r\n<p>LG G3   D850</p>\r\n</td>\r\n<td width=\"76\">\r\n<p>AT&amp;T</p>\r\n</td>\r\n<td width=\"180\" valign=\"top\">\r\n<p>MDF v1.1   Release 3</p>\r\n</td>\r\n<td width=\"113\" valign=\"top\">\r\n<p>Android 5.0.1</p>\r\n</td>\r\n<td width=\"162\" valign=\"top\">\r\n<p>&nbsp;LRX21Y</p>\r\n</td>\r\n</tr>\r\n<tr>\r\n<td width=\"102\" valign=\"top\">\r\n<p>LG G3   VS985</p>\r\n</td>\r\n<td width=\"76\">\r\n<p>Verizon</p>\r\n</td>\r\n<td width=\"180\" valign=\"top\">\r\n<p>MDF v1.1   Release 3</p>\r\n</td>\r\n<td width=\"113\" valign=\"top\">\r\n<p>Android 5.0.1</p>\r\n</td>\r\n<td width=\"162\" valign=\"top\">\r\n<p>&nbsp;LRX21Y</p>\r\n</td>\r\n</tr>\r\n<tr>\r\n<td width=\"102\" valign=\"top\">\r\n<p>LG G3   LS990</p>\r\n</td>\r\n<td width=\"76\">\r\n<p>Sprint</p>\r\n</td>\r\n<td width=\"180\" valign=\"top\">\r\n<p>MDF v1.1   Release 3</p>\r\n</td>\r\n<td width=\"113\" valign=\"top\">\r\n<p>Android 5.0.1</p>\r\n</td>\r\n<td width=\"162\" valign=\"top\">\r\n<p>&nbsp;LRX21Y</p>\r\n</td>\r\n</tr>\r\n<tr>\r\n<td width=\"102\" valign=\"top\">\r\n<p>LG G3   D851</p>\r\n</td>\r\n<td width=\"76\">\r\n<p>T-Mobile</p>\r\n</td>\r\n<td width=\"180\" valign=\"top\">\r\n<p>MDF v1.1   Release 3</p>\r\n</td>\r\n<td width=\"113\" valign=\"top\">\r\n<p>Android 5.0.1</p>\r\n</td>\r\n<td width=\"162\" valign=\"top\">\r\n<p>&nbsp;LRX21Y</p>\r\n</td>\r\n</tr>\r\n</tbody>\r\n</table>","security_evaluation_summary":"<p>The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the LG G3 Smartphone was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 4.&nbsp; 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.&nbsp; Gossamer Security Solutions determined that the evaluation assurance level (EAL) for the product is EAL 1.&nbsp; The product, when delivered and configured as identified in the LG Electronics Inc. G3 Administrator Guidance, version 1.3, March 26, 2015&nbsp; document, satisfies all of the security functional requirements stated in the LG Electronics Inc. G3 Smartphone (MDFPP11) Security Target, Version 1.5, March 19, 2015.&nbsp; The project underwent CCEVS Validator review.&nbsp; The evaluation was completed in March 2015.&nbsp; Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID10615-2015) prepared by CCEVS.</p>","environmental_strengths":"<p>The logical boundaries of the LG G3 Smartphone Lollipop OS TOE are realized in the security functions that it implements. Each of these security functions is summarized below.</p>\r\n<p><strong>Cryptographic Support</strong> - The TOE includes cryptographic modules with FIPS-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.</p>\r\n<p><strong>User Data Protection</strong> - The TOE can control access to system services by hosted applications, including protection of the Trust Anchor Database. Additionally, the TOE can protect user and other data using encryption, so that even if a device is physically lost, the data remains protected.</p>\r\n<p class=\"Body\"><strong>Identification and Authentication</strong> - 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. 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. Passwords up to 16 characters in length are supported.</p>\r\n<p class=\"Body\">The TOE can also serve as an IEEE 802.1X supplicant and can use X509v3 certificates. It can validate certificates for EAP-TLS, TLS, and HTTPS exchanges.</p>\r\n<p><strong>Security Management</strong> - The TOE provides all the interfaces necessary to manage the security functions identified in the Security Target as well as other functions commonly found in mobile devices. Many of these functions are available to users of the TOE, while others 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 (Common Criteria) mode.</p>\r\n<p class=\"Body\"><strong>TSF Protection</strong> - The TOE implements a number of features to protect itself to ensure the reliability and integrity of its security features. It protects 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 (ASLR), and stack-based buffer overflow protections to minimize the potential to exploit application flaws. It can protect itself from modification by applications as well as isolate the address spaces of applications from one another to protect those applications.</p>\r\n<p class=\"Body\">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 because all applications must have signatures (even if self-signed).</p>\r\n<p class=\"Body\"><strong>TOE Access</strong> - The TOE can be locked thereby obscuring its display, either by the user or after a configurable 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. The TOE is also able to attempt to connect to wireless networks as configured.</p>\r\n<p><strong>Trusted Path/Channels</strong> - The TOE supports the use of IEEE 802.11-2012, IEEE 802.1X, and EAP-TLS to secure communications channels between itself and other trusted network devices.</p>","features":[]}