The TOE is the HYCU, Inc. HYCU for Enterprise Clouds. HYCU for Enterprise Clouds provides application-consistent and virtualization-native data protection, data migration and disaster recovery. HYCU for Enterprise Clouds allows administrators to protect and manage clusters of a virtualized infrastructure with one integrated interface.
\r\nHYCU for Enterprise Clouds is a TOE that is installed as a virtual machine. The deployed virtual machine is accessed via a web GUI.
","evaluation_configuration":"The TOE is HYCU for Enterprise Clouds virtual appliance and management access, LDAP/S, SMTP and DNS. The NTP, storage, and hypervisor are not included in TOE.
\r\nThe following environmental components are required to operate the TOE in the evaluated configuration:
\r\nThe following product functionality is not included in the CC evaluation:
\r\n· Linux and Windows based targets (NFS/CIFS)
\r\n· Cloud-based targets (Google, Amazon, Azure)
\r\n· iSCSI targets
\r\n· File-level recovery
\r\n· Reporting
\r\n· Nutanix File Server Backup
\r\n· VMware Virtual Machine Backup and Physical Machine Backup
\r\n· Virtual Machine Backup for Nutanix (AHV and ESXi)
\r\n· Application Awareness and Backup (Microsoft Active Directory, Exchange, SQL Server, Oracle Database)
\r\n· SSH
\r\n· Mutually authenticated TLS
\r\n· Encrypted backups
\r\n· S3 Compatible Targets
\r\n· NTP time synchronization
\r\n· Web GUI certificate authentication
","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 HYCU for Enterprise Clouds 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 Common Criteria Guide, HYCU for Enterprise Clouds Administrative Guide, December 2023, satisfies all of the security functional requirements stated in the HYCU for Enterprise Clouds Security Target, Version 0.2.9, January 2024. The project underwent CCEVS Validator review. The evaluation was completed in January 2024. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CEVS-VR-VID11409-2024) prepared by CCEVS.
","environmental_strengths":"The logical boundaries of the TOE are realized in the security functions it implements. Each of these security functions is summarized below.
\r\n\r\n
Security Audit
\r\nThe HYCU for Enterprise Clouds provides extensive auditing capabilities. The TOE generates a comprehensive set of audit logs that identify specific TOE operations. For each event, the TOE records the date and time of each event, the type of event, the subject identity, and the outcome of the event. Auditable events include:
\r\n· failure on invoking cryptographic functionality such as establishment, termination and failure of cryptographic session establishments and connections
\r\n· modifications to the group of users that are part of the Authorized Administrator roles
\r\n· all use of the user identification mechanism
\r\n· any use of the authentication mechanism
\r\n· administrator lockout due to excessive authentication failures
\r\n· any change in the configuration of the TOE
\r\n· changes to time
\r\n· initiation of TOE update
\r\n· indication of completion of TSF self-test
\r\n· maximum sessions being exceeded
\r\n· termination of a remote or local session
\r\n· attempts to unlock a termination session
\r\n· initiation and termination of a trusted channel
\r\n· failure of the trusted channel functions
\r\n· initiation and termination of a trusted path
\r\n· failure of the trusted channel path
\r\n\r\n
The TOE is configured to transmit its audit messages to an external audit server. Communication with the audit server is protected using TLS and the TOE can determine when communication with the audit server fails. If that should occur, the TOE will store all audit records locally and when the connection to the remote audit server is restored, all stored audit records will be transmitted to the remote audit server.
\r\nThe audit logs can be viewed on the TOE. The records include the date/time the event occurred, the event/type of event, the user associated with the event, and additional information of the event and its success and/or failure. The TOE does not have an interface to modify audit records.
\r\n\r\n
Cryptographic Support
\r\nThe TOE utilizes TLS (via HTTPS, SMTP/S and LDAPS) to securely communicate, both with external services (audit server, authentication server, mail server) and external clients (HTTPS for GUI administration). Both RSA and ECDSA keys are supported. Cryptographic support is restricted to the approved set of algorithms using a combination of system-wide policies and application-specific configuration. Random bit generation is served by underlying OS facilities (/dev/random).
\r\n\r\n
Identification and Authentication
\r\nThe TOE allows the Administrator to securely login to the management interface using a username and password. Usernames and passwords can be managed within the TOE or delegated to an external authentication server (AD/LDAPS). A lockout period protects against repeated authentication failures. The TOE can be configured with a custom login banner.
\r\nThe private key and certificate for the TLS server can be imported or generated on the TOE. The TOE can issue a certificate signing request to be signed by an external certificate authority and then imported for use by the TLS server.
\r\nTrusted roots can be imported to establish trust with external servers. The TOE validates certificates of external servers – invalid or untrusted certificates result in rejected communication attempts. Online Certificate Status Protocol can be used to manage revocation.
\r\n\r\n
Security Management
\r\nThe TOE is managed remotely via a web user interface. Some functionality requires local console access. Roles and groups (tenants) can be defined and the roles can be assigned to users. TOE management is scoped within a built-in “Infrastructure group”. The TOE restricts configuration of security-related functions to the Administrator role of the Infrastructure group.
\r\nThe Administrator is able to perform the following security-related functions:
\r\n· start and stop services
\r\n· update the TOE
\r\n· modify the behavior of the transmission of audit data to an external IT entity
\r\n· manage the cryptographic keys
\r\n· configure the cryptographic functionality
\r\n· set the time which is used for time-stamps
\r\n· manage the TOE's trust store and designate X509.v3 certificates as trust anchors
\r\n· import X.509v3 certificates to the TOE's trust store
\r\n· configure the session inactivity time before session termination or locking
\r\n· ability to configure the authentication failure parameters for FIA_AFL.1
\r\n· ability to configure access banner
\r\n· ability to update the TOE, and to verify the updates using hash comparison capability prior to installing those updates
\r\n· ability to administer the TOE locally and remotely
\r\n\r\n
Protection of the TSF
\r\nPasswords of TOE-managed users are stored in a non-reversible encoding in the internal database.
\r\nPrivate keys and passwords for external services are stored in an encrypted form within the TOE database. Password input is obscured by default (password reveal is optional).
\r\nThe administrator can set the local TOE time using the console.
\r\nThe TOE performs power-on self-tests to verify the integrity of the primary application server and supporting components. Self-tests can be performed on-demand.
\r\nThe TOE has an update mechanism. Before performing updates, the administrator should manually validate the update image using the published hash available via HTTPS.
\r\n\r\n
TOE Access
\r\nIdle sessions are terminated by the TOE after a configurable period of inactivity. In the web user interface, a short time before the inactivity period expires, a dialog is shown to notify of an impending session termination. The TOE lets the user sign out of their session on demand using a dedicated sign-out button (for web user interface) or the user can terminate the current shell (for the console).
\r\nThe TOE can be configured with a custom login banner, for both the web user interface and the console.
\r\n\r\n
Trusted Path/Channels
\r\nThe TOE uses TLS to securely communicate with the following authorized IT entities:
\r\n· authentication server (Active Directory via LDAP/S)
\r\n· mail server (via SMTP/S)
\r\n· audit server (via HTTPS webhooks)
\r\nAdministrator access to the web user interface is protected using TLS (via HTTPS).
","features":[]}