The TOE is the Enveil ZeroReveal Compute Fabric Client (otherwise referred to as the ZeroReveal Client or the TOE) software application which communicates to one or more instances of the Enveil ZeroReveal Compute Fabric Client software application via REST API over mutually authenticated HTTPS over TLS.
\r\nThe TOE is a homomorphic encryption engine for database queries. In normal database operation, a query is submitted in plain text, and a plain text answer retrieved for the querier. While the communication between the querier and the database engine itself may be transmitted through a tunnel such as IPsec, TLS, or SSH, the contents of the query are always in plaintext. The ZeroReveal Compute Fabric Client takes an authenticated user’s database query and encrypts it using Enveil’s proprietary homomorphic encryption process. This encrypted query is passed via a mutually authenticated TLS trusted channel from ZeroReveal Client to ZeroReveal Server. The encrypted query is never decrypted during this process, which prevents ZeroReveal Server and its owners/administrators from being able to tell what the query was searching for and what items in the database (if any) matched the query. The output of this process is an encrypted response that is sent back to ZeroReveal Client. In this way, the database itself is not strictly aware of what the query was and no individual point in the chain between the user and the information know what was requested.
","evaluation_configuration":"The diagram below depicts a representative TOE deployment.
\r\n\r\n
Figure 1: Representative TOE Deployment
\r\n\r\n
The TOE has been evaluated on the following host platform:
\r\nThe following items are required for the operational environment.
\r\n\r\n
Table1: Hardware and Software Environmental Components
\r\n\r\n
The TOE is the ZeroReveal Compute Fabric Client software that includes the following libraries:
\r\n· Java JSSE Library v8
\r\n· Bouncy Castle FIPS Provider v1.0.2.3
\r\n· Bouncy Castle FIPS TLS Provider v1.0.12.3
\r\n· GMP Library v6.2.0
\r\n· SEAL Homomorphic Encryption Library v3.7.2.0
\r\nAdditionally, the TOE boundary includes configuration files that include key strings that must be completed to configure the TOE in the evaluated configuration. The configuration files are modified by administrators and are accessed using the local keyboard.
\r\nThe TOE’s operational environment requires the TOE platform to have:
\r\n· Rocky Linux 8.7 with SELinux OS installed and running and
\r\n· OpenJDK 8 JRE installed.
\r\nThe following diagram depicts the TOE and the Operational Environment of the ZeroReveal Compute Fabric Client Host.
\r\n\r\n
Figure 2: ZeroReveal Client Host
\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 Enveil ZeroReveal® Compute Fabric Client v4.6.3 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. Acumen Security determined that the evaluation assurance level (EAL) for the product is EAL 1. The product, when delivered configured as identified in the , Enveil ZeroReveal® Compute Fabric Configuration Guide for Common Criteria v3.1, Version 4.6.3.0 [AGD] satisfies all of the security functional requirements stated in the Enveil ZeroReveal® Compute Fabric Client v4.6.3 Security Target, v2.1. The project underwent CCEVS Validator review. The evaluation was completed in April 2024. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"The TOE provides the security functionality required by [AppPP] and [TLSPkg].
\r\n\r\nThe cryptographic services provided by the TOE are described below.
\r\nTable 2: Provided Cryptography
\r\nEach of these cryptographic algorithms have been validated for conformance to the requirements specified in their respective standards (refer to Table).
\r\nTable 3: CAVP Algorithm Testing
\r\n\r\n\r\n
The ZeroReveal Client network communication is restricted to user-initiated communication for authentication via LDAP directory, responses to API requests, and initiation of communications with the ZeroReveal Server.
\r\nIdentification and Authentication
\r\nThe ZeroReveal Client relies on X.509v3 certificate validation functions provided by the platform to authenticate the certificate(s) during the establishment of the TLS trusted channel. All trusted paths and channels are first authenticated using X.509v3 certificates.
\r\nIndividual users are authenticated to the TOE by X.509v3 certificate during TLS with mutual authentication trusted channel establishment and by authentication via LDAP server (the first shows that the user is authorized to communicate with the TOE at all, the second shows that the user is authorized to run queries using the TOE).
\r\n\r\nAdministrators manages the TOE via configuration files on each installation platform. The access interface and file editor used to modify the files is outside the scope of the TOE.
\r\nThe TOE does not include any predefined or default credentials and utilizes the platform recommended storage process for configuration files.
\r\nPrivacy
\r\nThe TOE does not collect or transmit Personally Identifiable Information (PII) over the network.
\r\nProtection of the TSF
\r\nThe TOE leverages platform provided package management for secure installation and updates. The TOE installation package includes only those third-party libraries necessary for its intended operation. The TOE utilizes compiler-provided anti-exploitation capabilities.
\r\nTrusted Path/Channels
\r\nThe TOE communicates to the ZeroReveal® Compute Fabric Server via REST API over mutually authenticated HTTPS over TLS. The TOE communicates to the LDAP server via mutually authenticated TLS. Users communicate with the TOE by running a REST API application and sending REST API commands over HTTPS over TLS or using a browser and communicating using HTTPS over TLS.
","features":[{"id":2210,"feature_name":"Certificate Authentication"},{"id":2211,"feature_name":"Certificate Validation"},{"id":2209,"feature_name":"Credential Storage"},{"id":2212,"feature_name":"DRBG"},{"id":2213,"feature_name":"DTLS 1.0"},{"id":2214,"feature_name":"DTLS Server with Mutual Authentication"},{"id":2215,"feature_name":"HTTPS Client"},{"id":2216,"feature_name":"HTTPS Server with Mutual Authentication"},{"id":2217,"feature_name":"PBKDF"},{"id":2218,"feature_name":"TLS 1.0"}]}