The Target of Evaluation (TOE) is the Samsung SDS Co., LTD Samsung SDS CellWe EMM version 1.1.
\r\nThe EMM Suite consists of an EMM Server and Agent, where the Server provides centralized management of mobile devices and the Agent software (installed on each device) enforces the policies of the Server on each device.
\r\nSamsung SDS offers the EMM Server as a software installation for Java 1.7 and Tomcat 7.0 running on the Microsoft Windows Server 2008 R2 operating system through Windows Server 2012 R2. Once installed, the EMM Server allows administrators to configure policies for devices. Administrators connect securely to the EMM Server using a web browser (whether local to the Server itself or remote) and through the EMM Server’s web interface can enroll, audit, lock, unlock, manage, and set policies for enrolled mobile devices. The EMM Server includes the RSA Crypto-J 6.1 cryptographic module as part of its software, and the EMM Server’s Microsoft Windows platform includes SQL server 2008-2012 and an EJBCA certificate authority.
\r\nSamsung SDS provides the EMM Agent software for evaluated Samsung mobile devices (including the Galaxy S4, Note 3, S5, Note 4, and Galaxy Note Edge), and the Agent software, once installed and enrolled with the EMM Server, will apply and enforce administrator configured policies communicated through the EMM to the Agent software.
","evaluation_configuration":"The evaluated configuration consists of collection of server components (MDM server) and mobile device applications (MDM agent).
\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 SDS Co., LTD EMM Suite version 1.1 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. Gossamer Security Solutions determined that the evaluation assurance level (EAL) for the product is EAL 1. The product, when delivered and configured as identified in the Samsung SDS CellWe Enterprise Mobility Management Installation Guide, Version 1.1.0, March 2015 document, satisfies all of the security functional requirements stated in the Samsung SDS Co., LTD EMM Suite (MDMPP11) Security Target, Version 0.6, May 8, 2015. The project underwent CCEVS Validator review. The evaluation was completed in May 2015. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID10618-2015) prepared by CCEVS
","environmental_strengths":"The logical boundaries of the Samsung SDS Co., LTD Samsung SDS CellWe EMM Suite version 1.1 TOE are realized in the security functions that it implements. Each of these security functions is summarized below.
\r\nSecurity Audit - The EMM Server can generate and store audit records for security-relevant events as they occur. These events are stored and protected by the EMM Server and can be reviewed by an authorized Administrator. The EMM Server can be configured to export the audit records to an external SYSLOG server utilizing TLS for protection of the records on the network. The EMM Server also supports the ability to query information about MDM agents and export MDM configuration information.
\r\nThe EMM Agent includes the ability to the EMM Server to indicate (i.e., respond) when it has been enrolled and when it applies policies successfully. The EMM Server can be configured to alert an administrator based on its configuration. For example, it can be configured to alert he administrator when a policy update fails or an MDM Agent has been enrolled.
\r\nCryptographic Support - The EMM Server and EMM Agent both include and have access to cryptographic modules with FIPS 140-2 certified algorithms for a wide range of cryptographic functions including: asymmetric key generation and establishment, encryption/decryption, cryptographic hashing and keyed-hash message authentication. These functions are supported with suitable random bit generation, initialization vector generation, secure key storage, and key and protected data destruction.
\r\nThe primitive cryptographic functions are used to implement security communication protocols: TLS and HTTPS used for communication between the Server and Agent and between the Server and remote administrators.
\r\nIdentification and Authentication - The EMM Server authenticates mobile device users (MD users) and administrators prior to allowing those operators to perform any functions. This includes MD users enrolling their device with the EMM Server using the EMM Agent as well as an administrator logging on to manage the EMM Server configuration, MDM policies for mobile devices, etc.
\r\nIn addition, both the EMM Server and Agent utilize X.509 certificates, including certificate validation checking, in conjunction with TLS to secure communications between the EMM Server and EMM Agents as well as between the EMM Server and administrators using a web-based user interface for remote administrative access.
\r\nSecurity Management - The EMM Server is designed to two distinct user roles: administrator and mobile device user (MD user). The former interacts directly with the EMM Server through HTTPS (using a browser) while the latter is the user of a mobile device with the EMM Agent installed.
\r\nThe EMM Server provides all the function necessary to manage its own security functions as well as to manage mobile device policies that are sent to EMM Agents. In addition, the EMM Server ensures that security management functions are limited to authorized administrators while allowing MD users to perform only necessary functions such as enrolling with the EMM Server.
\r\nThe EMM Agents provide the functions necessary to securely communicate with and enroll with the EMM Server, apply policies received from the EMM Server, and report the results of applying policies.
\r\nTSF Protection - The EMM Server and Agent work together to ensure that all security related communication between those components is protected from disclosure and modification.
\r\nBoth the EMM Server and Agent include self-testing capabilities to ensure that they are functioning properly as well as to cryptographically verify that their executable images have not been corrupted.
\r\nThe EMM Server 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.
\r\nTOE Access - The MDM Server has the capability to display an advisory banner when users attempt to login in order to manage the TOE.
\r\nTrusted Path/Channels - The EMM Server uses TLS/HTTPS to secure communication channels between itself and remote administrators accessing the Server via a web-based user interface. It also uses TLS to secure communication channels between itself and mobile device users (MD users). In this latter case, the protected communication channel is established between the EMM Server and EMM Agent.
","features":[]}