Monkton IA Docs is a mobile app that is installed on the Apple iPhone and the Apple iPad. This app enables end users to securely download and view documents stored in a cloud/service provider.
\r\nMonkton IA Docs is Managed Configuration Enabled with MDM providers, allowing MDM providers to push configuration settings down to devices. This enables enterprises to manage apps on managed devices in a secure manner.
","evaluation_configuration":"\r\n\r\nThe TOE was evaluated on Apple’s iPhone 7 with iOS 10.3.2 (A10 Fusion with 64-bit architecture) and iPad Pro 10” with iOS 10.3.2 (A10X Fusion with 64-bit architecture).
\r\nTo use the product in the evaluated configuration, the product must be configured as specified in the Monkton IA Docs Reinforced by Rebar for iOS version 1.0.0 User Guide, version 1.0 and the Rebar Platform Administrative Guide, version 1.0.
","security_evaluation_summary":"\r\n\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 Monkton IA Docs Reinforced by Rebar for iOS, version 1.0, Built on Monkton’s Rebar Platform was evaluated are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 5. 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 5. The product, when delivered configured as identified in the Administrative Guidance, satisfies all of the security functional requirements stated in the Security Target. The project underwent CCEVS Validator review. The evaluation was completed in December 2017. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (CCEVS-VR-10825-2017) prepared by CCEVS.
","environmental_strengths":"\r\n\r\n\r\nThe TOE provides several functions for cryptographic support. The TOE, by virtue of being built on Rebar, implements DAR and DIT as a functional component. When HTTPS network connections are created, they are made over TLS 1.2 connections with the requisite cipher suites. The TOE uses OpenSSL 1.0.2L to provide its cryptographic support.
\r\nThe TOE, through Rebar, provides all requisite cryptographic functions for hashing, signing, HMAC, random number generation, and symmetric encryption.
\r\nTo protect the keys and data generated by the TOE, the TOE will aggressively and securely delete key data and files written to non-volatile memory. This leverages both platform implemented functions as well as functions integrated into Rebar.
\r\nUser Data Protection
\r\nThe TOE requests no hardware or software resources during the use of the application. The TOE requires network access but this is not a request that is prompted to the user.
\r\nIdentification and Authentication
\r\nThe TOE, through Rebar, implements X509 certificate validation for all server certificates presented for TLS 1.2 connections. Additionally, Rebar implements SSL Pinning, validating certificates based on SHA512 hashes of the certificates.
\r\nFor user authorization, the TOE leverages PBKDF2 with HMACSHA256 to validate user credentials based on a passcode. The conditioned key is used as the FEK for the RMD. The passcode can be configured by the administrator for complexity requirements.
\r\n\r\nThe TOE is, by default, configured to be secure whenever it is freshly installed on a device. The TOE, through Rebar, provides configuration settings available through the Managed App Configuration settings. Rebar implements a secure version of NSUserDefaults that ensures settings are stored in an AES256 encrypted database.
\r\n\r\nThe TOE leverages only approved iOS APIs and available libraries. The TOE includes several third-party libraries that provide specific functionality for the TOE. Each of these libraries leverage only approved iOS APIs.
\r\nThe TOE leverages the iOS update manager (App Store) or enterprise distribution mechanisms (MDM/Enterprise App Store) to update and install approved apps.
\r\nAll key material used within the TOE is protected and destroyed as part of the cryptographic support. The password conditioned FEK is never stored in non-volatile memory.
\r\n\r\nAll data in transit for the TOE is sent with TLS 1.2.
\r\nPrivacy
\r\nThe TOE does not transmit PII.
","features":[]}