Cellcrypt Android Mobile Client is a secure multimedia application for Android smartphones. It implements end-to-end encryption and authentication of voice, video, text messages and file attachments between two or more users of Cellcrypt Android Mobile Client and other compatible applications. The Cellcrypt system comprises a handset software application (Cellcrypt Android Mobile Client, i.e. the TOE) and the back-end support infrastructure (Cellcrypt Server). The TOE is the handset software application, Cellcrypt Android Mobile Client, on a specific hardware platform described in the Security Target and in the evaluated configuration below.
","evaluation_configuration":"The TOE runs on Android 14 and was tested on Samsung Galaxy S23. The evaluated configuration includes the following hardware platforms:
\r\n· Samsung Galaxy S23 running Android 14.0 on a Qualcomm Snapdragon 8 Gen2 processor with Processor Algorithm Accelerators (PAA).
\r\n· Samsung Galaxy S21 running Android 14.0 on a Qualcomm Snapdragon 888 processor with Processor Algorithm Accelerators (PAA).
","security_evaluation_summary":"The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme for the Protection Profile for Application Software, Version 1.4 with the Functional Package for Transport Layer Security (TLS), Version 2.0 and PP Module for Voice and Video over IP (VVoIP), version 1.0 applied. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 release 5. The product, when delivered and configured as identified in the guidance documentation, satisfies all the security functional requirements stated in the CellCrypt Android Mobile Client Security Target. The evaluation was completed in Decemeber 2025. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"Cryptographic Support
\r\nThe TOE implements cryptography to protect data in transit. For data in transit, the TOE implements TLS as a client. The TOE supports TLS connections both with and without mutual authentication. The TOE also implements SRTP to transmit voice and video data.
\r\nThe TOE implements all cryptography used for these functions using its own implementations of OpenSSL with NIST-approved algorithms. The TOE’s DRBG is seeded using entropy from the underlying OS platform.
\r\nFor data at rest, the TOE relies on its operational environment to control access to stored credential data.
\r\nCommunications
\r\nThe TOE transmits voice and video data using a constant bit rate vocoder.
\r\nUser Data Protection
\r\nThe TOE relies on platform provided credential storage mechanisms to protect sensitive data at rest.
\r\nThe TOE enforces the media transmission policies for controlling the transmission of voice and video data to a remote peer.
\r\nThe TOE relies on network connectivity and the credential repository provided by its host OS platform. All uses of network connectivity are user-initiated.
\r\nIdentification and Authentication
\r\nThe TOE supports X.509 certificate validation as part of establishing TLS connections. The TOE implements functionality to support various certificate validity checking methods, including the checking of certificate revocation status using OSCP. If the validity status of a certificate cannot be determined, the certificate will be rejected.
\r\nSecurity Management
\r\nThe TOE itself and the configuration settings it uses are stored in locations recommended by the platform vendor. The TOE is launched by the OS user and runs in the session context of that user; there is no interface for a non-administrator to act as an administrator through separate authentication. The TOE’s primary management function is to configure the ESC server parameters and set the parameters that are used for the TLS channel (ciphersuites) or the Voice and Video connection channels (vocoder codecs and SRTP parameters).
\r\nPrivacy
\r\nThe TOE does not transmit PII.
\r\nProtection of the TSF
\r\nThe TOE enforces various mechanisms to protect itself against unauthorized modification and use. The TOE implements address space layout randomization (ASLR), does not allocate any memory with both write and execute permissions, does not write user-modifiable files to directories that contain executable files, is compiled using stack overflow protection, and is compatible with the security features of its host OS platform.
\r\nThe TOE contains libraries and invokes system APIs that are well-known and explicitly identified.
\r\nThe TOE has a mechanism to determine its current software version. Software updates to the TOE are acquired through the application’s connection to the Controller in the operational environment and subsequently applied using the TOE platform. All updates are digitally signed to guarantee their authenticity and integrity.
\r\nTOE Access
\r\nThe TOE terminates voice and video connections after the configured inactivity time-period elapses.
\r\nTrusted Path/Channels
\r\nThe TOE encrypts sensitive data in transit between itself and its operational environment using TLS and SRTP. These interfaces are used to secure all data in transit between the TOE and its operational environment.
","features":[{"id":281,"feature_name":"Application Software"},{"id":298,"feature_name":"Certificate Authentication"},{"id":297,"feature_name":"Certificate Validation"},{"id":288,"feature_name":"Credential Storage"},{"id":293,"feature_name":"Cryptographic Key Establishment"},{"id":295,"feature_name":"Cryptographic Signature Generation"},{"id":296,"feature_name":"DRBG"},{"id":294,"feature_name":"Keyed-hash message authentication"},{"id":292,"feature_name":"PBKDF"},{"id":307,"feature_name":"TLS 1.2"},{"id":303,"feature_name":"TLS Client"},{"id":300,"feature_name":"VVoIP"}]}