The Target of Evaluation (TOE) is Enveil ZeroReveal™ Compute Fabric Client v2.5.4 and has been evaluated on the CentOS 8.1 on the Intel Core i7-10710U host platform. The TOE is the application software and required libraries only. The host platforms are not part of the evaluation. The TOE supports secure connectivity with several other IT environment devices as described in Table 1 IT Environments Components.
","evaluation_configuration":"The TOE has been evaluated on the following host platforms:
\r\n- CentOS 8.1 on Intel Core i7-10710U
\r\nNote: The TOE is the application software and required libraries only. The host platforms are not part of the evaluation.
\r\nThe TOE supports secure connectivity with several other IT environment devices as described below:
\r\n| \r\n Component \r\n | \r\n\r\n Required \r\n | \r\n\r\n Usage/Purpose Description \r\n | \r\n
| \r\n Enveil ZeroReveal® Compute Fabric Server \r\n | \r\n\r\n Yes \r\n | \r\n\r\n The TOE is a ZeroReveal® Compute Fabric Client, which communicates with a server to process data queries in a way that does not disclose the nature of the query to any observer. The TOE does not serve a useful function without the ZeroReveal® server. \r\n | \r\n
| \r\n Enveil ZeroReveal Compute Fabric Client platform \r\n | \r\n\r\n Yes \r\n | \r\n\r\n This is the platform on which the TOE is installed; the client application which communicates with the ZeroReveal server to process data queries in a way that does not disclose the nature of the query to any observer. \r\nThe Client workstation must include the Java Runtime as shown in Figure 1 and the CentOS 8.1 OS as defined above. \r\n | \r\n
| \r\n LDAP Server \r\n | \r\n\r\n Yes \r\n | \r\n\r\n LDAP is used for external authentication and identification of users. \r\n | \r\n
| \r\n User Workstation \r\n | \r\n\r\n Yes \r\n | \r\n\r\n The TOE executes on a user workstation which must support the REST APIs used to communicate with the TOE. \r\n | \r\n
Table 1 IT Environment Components
","security_evaluation_summary":"The 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 v2.5.4 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 ZeroReveal Compute Fabric Configuration Guide for Common Criteria v2.5.4, satisfies all of the security functional requirements stated in the Enveil ZeroReveal® Compute Fabric Client Security Target. The project underwent CCEVS Validator review. The evaluation was completed in May 2021. 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 [SWAPP] and [TLS-PKG].
\r\nThe TOE performs two kinds of cryptographic functions: those necessary to the operation of the TOEs homomorphic encrypted search function, and those necessary to the operation of the trusted path and trusted channels. Because the homomorphic encryption functionality is outside the scope of this evaluation, only those cryptographic functions necessary to support the trusted path and trusted channels are described below:
\r\n| \r\n Cryptographic Method \r\n | \r\n\r\n Use within the TOE \r\n | \r\n
| \r\n AES-GCM \r\n | \r\n\r\n TLS encryption \r\n | \r\n
| \r\n ECDSA \r\n | \r\n\r\n TLS key generation, signature generation and verification \r\n | \r\n
| \r\n RSA \r\n | \r\n\r\n TLS key generation, signature generation and verification \r\n | \r\n
| \r\n HMAC \r\n | \r\n\r\n Message integrity and authentication for TLS \r\n | \r\n
| \r\n AES-CCM \r\n | \r\n\r\n Storage of credentials \r\n | \r\n
| \r\n DRBG \r\n | \r\n\r\n Random bit generation for all cryptographic functions \r\n | \r\n
Table 2 TOE Provided Cryptography
\r\nEach of these cryptographic algorithms have been validated for conformance to the requirements specified in their respective standards, as identified below:
\r\n\r\n
| \r\n Algorithm \r\n | \r\n\r\n Standard \r\n | \r\n\r\n Mode/Keysize \r\n | \r\n\r\n CAVP Cert. # \r\n | \r\n
| \r\n HMAC_DRBG \r\n | \r\n\r\n NIST SP 800-90A \r\n | \r\n\r\n HMAC-SHA2-512 with 256 bits of entropy seeded by the platform DRBG \r\n | \r\n\r\n C1874 \r\n | \r\n
| \r\n ECDSA KeyGen \r\n\r\n ECDH Key Establishment \r\n\r\n ECDSA SigGen/SigVer \r\n | \r\n\r\n FIPS Pub 186-4, Appendix B.4 \r\n\r\n \r\n NIST SP 800-56Arev3 \r\n\r\n \r\n FIPS Pub 186-4, Section 5 \r\n | \r\n\r\n Curves P-256 and P-384 \r\n\r\n \r\n \r\n | \r\n\r\n C1874 \r\n | \r\n
| \r\n RSA KeyGen \r\n\r\n RSA SigGen/SigVer \r\n | \r\n\r\n FIPS Pub 186-4, Appendix B.3 \r\n\r\n \r\n FIPS Pub 186-4, Section 4 \r\n | \r\n\r\n 2048 bits \r\n | \r\n\r\n C1874 \r\n | \r\n
| \r\n AES-GCM \r\n | \r\n\r\n NIST SP 800-38D \r\n | \r\n\r\n 256 bits \r\n | \r\n\r\n C1874 \r\n | \r\n
| \r\n AES-CCM \r\n | \r\n\r\n NIST SP 800-38C \r\n | \r\n\r\n 256 bits \r\n | \r\n\r\n C1874 \r\n | \r\n
| \r\n SHA2-256 \r\n\r\n SHA2-384 \r\n\r\n SHA2-512 \r\n | \r\n\r\n FIPS Pub 180-4 \r\n | \r\n\r\n Digest size 256 bits \r\n\r\n Digest size 384 bits \r\n\r\n Digest size 512 bits \r\n | \r\n\r\n C1874 \r\n | \r\n
| \r\n HMAC-SHA2-256 \r\n\r\n HMAC-SHA2-384 \r\n\r\n HMAC-SHA-512 \r\n | \r\n\r\n FIPS Pub 198-1 \r\n\r\n | \r\n\r\n Key size 256 bits, block size 512 bits, digest size 256 bits \r\n\r\n Key size 384 bits, block size 1024 bits, digest size 384 bits \r\n\r\n Key size 512 bits, block size 1024 bits, digest size 512 bits \r\n | \r\n\r\n C1874 \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\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\nAn enterprise administrator manages the TOE via configuration files on each installation workstation or platform in the Operational Environment. There is no management GUI, CLI, or interface to manage the TOE over the network.
\r\nThe TOE does not include any predefined or default credentials and utilizes the platform recommended storage process for configured credentials in the TOE’s configuration files.
\r\nThe TOE does not collect or transmit Personally Identifiable Information (PII) over the network.
\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\nThe TOE communicates to the ZeroReveal® Compute Fabric Server via REST API over mutually authenticated TLS. The TOE communicates to the LDAP server via mutually authenticated TLS. Users communicate with the TOE through the REST API over HTTPS/TLS.
","features":[]}