FireEye AX, CM, EX, FX, HX, NX, and VX Series are network devices comprised of hardware and software. The virtual devices as defined in Table 1 [ST] are considered virtual network devices as defined in Case 1 of NDcPP 2.2e running on general purpose hardware and virtualization system which are outside of the TOE. In the virtual case, the TOE boundary represents the virtual network device only. The hardware appliances are physical devices comprised of the TOE firmware running on bare metal, where the TOE boundary is inclusive of hardware and software. The Trellix Appliances runs on a pre-installed, hardened TRFE(Trellix FireEye) operating system(TRFEOS) and comes pre-loaded with the TRFEOS software. TRFEOS runs on all platforms with version 10.0.4 Please see Section 1.3 [ST] for additional details on the TOE models.
\r\nThe FireEye Malware Analysis (AX) series is a group of forensic analysis platforms that give security analysts hands-on control over powerful auto-configured test environments to safely execute and inspect advanced malware, zero-day and advanced persistent threat (APT) attacks embedded in Web pages, email attachments and files.
\r\nFireEye Central Management (CM) series consolidates the administration, reporting and data sharing of the FireEye products in one easy-to-deploy, network-based solution.
\r\nThe FireEye Email Security (EX) Series Appliances are network devices that secure against advanced email attacks by using signature-less technology to analyze email attachments and quarantine malicious emails.
\r\nThe FireEye Threat Prevention (FX) platform protects data assets against attacks originating in a wide range of file types. Web mail, online file transfer tools, the cloud, and portable file storage devices can introduce malware that can then spread to file shares and content repositories.
\r\nThe FireEye Endpoint Security (HX) Appliances are network devices providing organizations with the ability to continuously monitor endpoints for advanced malware and indicators of compromise.
\r\nFireEye Network Security (NX) is an effective cyber threat protection solution that helps organizations minimize the risk of costly breaches by accurately detecting and immediately stopping advanced, targeted and other evasive attacks hiding in Internet traffic.
\r\nThe FireEye Network Threat Prevention Platform (VX) identifies and blocks zero-day Web exploits, droppers (binaries), and multi-protocol callbacks to help organizations scale their advanced threat defenses across a range of deployments, from the multi-gigabit headquarters down to remote, branch, and mobile offices. FireEye Network with Intrusion Prevention System (IPS) technology further optimizes spend, substantially reduces false positives, and enables compliance while driving security across known and unknown threats.
\r\n\r\n
Note: Each model of the TOE shares an identical codebase employing all NDcPP required functionality. Breach detection, email analysis, endpoint monitoring, IPS, malware analysis, and threat prevention features are not evaluated as part of the Common Criteria certification and are excluded from the evaluated configuration.
","evaluation_configuration":"The following environmental components are required to operate the TOE in the evaluated configuration. The TOE evaluated configuration consists of any of the AX, CM, EX, FX, HX, NX, and VX series appliances listed above. The TOE also supports secure connectivity with several other IT environment devices as listed in the table below (Table 1). The virtual appliances are tested on a Dell PowerEdge R830 with VMware vSphere ESXi 7.0 and Intel(R) Xeon(R) CPU E5-4620 v4(Broadwell). Figure 1 [ST] provides a visual depiction of an example of a typical TOE deployment.
\r\nTable 1 – Required IT Environmental Components
\r\n| \r\n Components \r\n | \r\n\r\n Required \r\n | \r\n\r\n Usage/Purpose Description for TOE performance \r\n | \r\n
| \r\n Virtual Hardware \r\n | \r\n\r\n Yes (for virtual appliances) \r\n | \r\n\r\n Virtual hardware provided by VMware vSphere ESXi 7.0 and Intel Xeon E5-4620 v4 (Broadwell). \r\n | \r\n
| \r\n Management Workstation with Web Browser and SSH Client \r\n | \r\n\r\n Yes \r\n | \r\n\r\n This includes any IT Environment Management workstation with a Web Browser and an SSH client installed that is used by the TOE administrator to support TOE administration through HTTPS and SSH protected channels. Any SSH client that supports SSHv2 may be used. Any web browser that supports TLS 1.2 may be used. \r\n | \r\n
| \r\n Audit server \r\n | \r\n\r\n Yes \r\n | \r\n\r\n The syslog audit server is used for remote storage of audit records that have been generated by and transmitted from the TOE. The syslog server must support communications using TLS 1.2. \r\n | \r\n
| \r\n NTP Server \r\n | \r\n\r\n Yes \r\n | \r\n\r\n NTP server supporting SHA-1 integrity verification. \r\n | \r\n
\r\n
Note: VX series models doesn’t support Web UI Feature.
\r\n\r\n
Physical Boundaries:
\r\nEach instance of the TOE is a hardware and software solution implemented in one of the security appliance models listed in Table 1. The TOE guidance documentation that is considered to be part of the TOE can be found listed in the FireEye Common Criteria Addendum document and is downloadable from the FireEye website.
\r\nThe network on which the TOE resides is considered part of the environment. The software is pre-installed and is comprised of only the software versions identified above. In addition, software updates are downloadable from the FireEye website. A login ID and password is required to download the software update.
\r\nAn instance of the TOE consists of a physical or virtual appliance instance of one of the models listed in Table 1.
\r\nTable 1 – TOE Physical Boundary Components
\r\n| \r\n Model \r\n | \r\n\r\n CPU \r\n | \r\n\r\n Network Interfaces \r\n | \r\n\r\n Storage \r\n | \r\n\r\n Dimensions \r\n | \r\n\r\n Firmware \r\n | \r\n
| \r\n Physical Models \r\n | \r\n|||||
| \r\n AX5600 \r\n | \r\n\r\n Intel Xeon E-2334 (Rocket Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 2 x 4TB disk / 4 TB virtual disk RAID 1 \r\n | \r\n\r\n 1 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n CM4600 \r\n | \r\n\r\n Intel Xeon E-2334 (Rocket Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 4x 4TB disk / 8TB virtual disk RAID 10 \r\n | \r\n\r\n 1 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n CM7600 \r\n | \r\n\r\n Intel Xeon Silver 4314 (Ice Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 4x 4TB disk / 8TB virtual disk RAID 10 \r\n | \r\n\r\n 2 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n CM9600 \r\n | \r\n\r\n Intel Xeon Silver 4316 (Ice Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 4x 10TB disk / 20TB virtual disk RAID 10 \r\n | \r\n\r\n 2 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n EX3600 \r\n | \r\n\r\n Intel Xeon E-2334 (Rocket Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 4x 4TB disk / 8TB virtual disk RAID 10 \r\n | \r\n\r\n 1 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n EX5600 \r\n | \r\n\r\n Intel Xeon Silver 4314 (Ice Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 4x 4TB disk / 8TB virtual disk RAID 10 \r\n | \r\n\r\n 2 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n EX8600 \r\n | \r\n\r\n Intel Xeon Silver 4316 (Ice Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 4x 4TB disk / 8TB virtual disk RAID 10 \r\n | \r\n\r\n 2 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n FX6600 \r\n | \r\n\r\n Intel Xeon Silver 4316 (Ice Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 4x 4TB disk / 8TB virtual disk RAID 10 \r\n | \r\n\r\n 2 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n HX4600 \r\n | \r\n\r\n Intel Xeon E-2378 (Rocket Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 4x 4TB disk / 8TB virtual disk RAID 10 \r\n | \r\n\r\n 1 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX2600 \r\n | \r\n\r\n Intel Xeon E-2334 (Rocket Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 2 x 4TB disk / 4 TB virtual disk RAID 1 \r\n | \r\n\r\n 1 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX3600 \r\n | \r\n\r\n Intel Xeon E-2378 (Rocket Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 2 x 4TB disk / 4 TB virtual disk RAID 1 \r\n | \r\n\r\n 1 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX4600 \r\n | \r\n\r\n Intel Xeon Silver 4314 (Ice Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 2 x 4TB disk / 4 TB virtual disk RAID 1 \r\n | \r\n\r\n 2 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX5600 \r\n | \r\n\r\n Intel Xeon Silver 4314 (Ice Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 2 x 4TB disk / 4 TB virtual disk RAID 1 \r\n | \r\n\r\n 2 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n 2x 10G BaseT \r\n | \r\n|||||
| \r\n NX6600 \r\n | \r\n\r\n Intel Xeon Gold 6330 (Ice Lake) \r\n | \r\n\r\n 2x 10G BaseT \r\n | \r\n\r\n 2 x 10TB disk / 10TB virtual disk RAID 1 \r\n | \r\n\r\n 2 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n 2x SFP \r\n | \r\n|||||
| \r\n NX8600 \r\n | \r\n\r\n Intel Xeon Platinum 8380 (Ice Lake) \r\n | \r\n\r\n 2x 10G BaseT \r\n | \r\n\r\n 2 x 10TB disk / 10TB virtual disk RAID 1 \r\n | \r\n\r\n 2 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n 2x SFP \r\n | \r\n|||||
| \r\n 2x 100G QSFP \r\n | \r\n|||||
| \r\n VX5600 \r\n | \r\n\r\n Intel Xeon E-2334 (Rocket Lake) \r\n | \r\n\r\n 2x 1GigE BaseT \r\n | \r\n\r\n 2 x 4TB disk / 4 TB virtual disk RAID 1 \r\n | \r\n\r\n 1 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n VX12600 \r\n | \r\n\r\n Intel Xeon Gold 6330 (Ice Lake) \r\n | \r\n\r\n 2x 10G BaseT \r\n | \r\n\r\n 4x 4TB disk / 8TB virtual disk RAID 10 \r\n | \r\n\r\n 2 RU \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n Virtual Models \r\n | \r\n|||||
| \r\n CM7500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n CM1500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n CM2500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n EX5500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n FX2500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n HX4502V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n HX4600V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX1500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX2500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX2550V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX4500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX6500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX7500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX8500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
| \r\n NX10500V \r\n | \r\n\r\n ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4 (Broadwell) \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n NA \r\n | \r\n\r\n TRFEOS 10.0 \r\n | \r\n
The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the FireEye AX, CM, EX, FX, HX, NX, and VX Series Appliances was evaluated is 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 and configured as identified in the Common Criteria Administrator Guidance, satisfies all of the security functional requirements stated in the FireEye AX, CM, EX, FX, HX, NX, and VX Series Appliances Security Target. The project underwent CCEVS Validator review. The evaluation was completed in October/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 functions required by the Collaborative Protection Profile for Network Devices, hereafter referred to as NDcPP v2.2e or NDcPP.
\r\nThe TOE keeps local and remote audit records of security relevant events. The TOE internally maintains the date and time which can be set manually or using authenticated NTP.
\r\nThe TOE provides cryptographic support for the services described in Table 2. The related CAVP validation details are provided in Table 3
\r\nTable 2 TOE provided cryptography
\r\n| \r\n Cryptographic Method \r\n | \r\n\r\n Use within the TOE \r\n | \r\n
| \r\n TLS Establishment \r\n | \r\n\r\n Used to establish initial TLS session \r\n | \r\n
| \r\n SSH Establishment \r\n | \r\n\r\n Used to establish initial SSH session \r\n | \r\n
| \r\n ECDSA Signature Services \r\n | \r\n\r\n Used in TLS session establishment \r\n | \r\n
| \r\n RSA Signature Services \r\n | \r\n\r\n Used in TLS session establishment \r\nUsed in SSH session establishment \r\nUsed in secure software update \r\n | \r\n
| \r\n Random Bit Generation \r\n | \r\n\r\n Used in TLS session establishment \r\nUsed in SSH session establishment \r\n | \r\n
| \r\n Hashing \r\n | \r\n\r\n Used in secure software update \r\nUsed in NTP integrity \r\n | \r\n
| \r\n HMAC \r\n | \r\n\r\n Used to provide TLS traffic integrity verification \r\nUsed to provide SSH traffic integrity verification \r\n | \r\n
| \r\n AES \r\n | \r\n\r\n Used to encrypt TLS traffic \r\nUsed to encrypt SSH traffic \r\n | \r\n
The TOE utilizes Trellix OpenSSL FIPS Object Module cryptographic library.
\r\nFor all cryptographic operations performed by the TOE, the cryptographic algorithms have been validated as identified in the table below.
\r\n\r\n
Table 3 CAVP Algorithm Testing References
\r\n| \r\n Functions \r\n | \r\n\r\n Algorithms \r\n | \r\n\r\n Mode Supported \r\n | \r\n\r\n CAVP Certs. \r\n | \r\n\r\n Name \r\n | \r\n\r\n OE \r\n | \r\n
| \r\n Data Encryption \r\n | \r\n\r\n AES-CBC, \r\nAES-CTR, \r\nAES-GCM \r\n | \r\n\r\n CBC, CTR, GCM (128, 256) \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n\r\n TRFEOS 10.0 on Intel(R) Xeon (R) E-2334 (Rocket Lake) \r\n\r\n TRFEOS 10.0 on Intel(R) Xeon (R) Gold 6330 (Ice Lake) \r\nTRFEOS 10.0 running on ESXi Hypervisor v7.0 on Intel(R) Xeon(R) CPU E5-4620 v4(Broadwell) \r\n | \r\n
| \r\n Hash \r\n | \r\n\r\n SHS \r\n(Cryptographic hashing) \r\n\r\n | \r\n\r\n SHA-1, SHA-256, SHA-384, SHA-512 \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n|
| \r\n Random Number Generator \r\n | \r\n\r\n Counter DRBG \r\nHMAC DRBG \r\n | \r\n\r\n CTR_DRBG (AES-256), Hash DRBG(SHA-512) \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n|
| \r\n Key Generation \r\n | \r\n\r\n RSA KeyGen (FIPS186-4) \r\n | \r\n\r\n Mode: n(2048,3072), n = 2048,3072 SHA(256) \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n|
| \r\n ECDSA KeyGen (FIPS186-4) \r\nECDSA KeyVer (FIPS186-4) \r\n | \r\n\r\n P-256, P-384, P-521 \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n||
| \r\n\r\n | \r\n\r\n (L,N): (2048,256) \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n||
| \r\n Safe Primes Key Generation \r\n | \r\n\r\n modp-2048(DH-14) \r\nmodp-4096(DH-16) \r\nmodp-8192(DH-18) \r\n | \r\n\r\n NA \r\n | \r\n\r\n No NIST CAVP, CCTL has performed all assurance/evaluation activities. \r\n | \r\n||
| \r\n Key Establishment \r\n | \r\n\r\n KAS ECC SSC Sp800-56Ar3 \r\n(Domain Parameter Generation) \r\n | \r\n\r\n P-256, P-384, P-521 \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n|
| \r\n KAS-FFC-SSC Sp800-56Ar3 \r\n(Domain Parameter Generation) \r\n | \r\n\r\n MODP-2048 \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n||
| \r\n KAS-FFC-SSC Sp800-56Ar3 \r\n(Domain Parameter Generation) \r\n | \r\n\r\n modp-2048(DH-14) \r\nmodp-4096(DH-16) \r\nmodp-8192(DH-18) \r\n | \r\n\r\n NA \r\n | \r\n\r\n No NIST CAVP, CCTL has performed all assurance/evaluation activities. \r\n | \r\n||
| \r\n Digital Signature services \r\n | \r\n\r\n ECDSA SigGen (FIPS186-4) \r\nECDSA SigVer (FIPS186-4) \r\n | \r\n\r\n P-256, P-384, P-521 \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n|
| \r\n RSA SigGen (FIPS186-4) \r\nRSA SigVer (FIPS186-4) \r\n | \r\n\r\n Mode: n(2048, 3072), n = 2048,3072 SHA(256) \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n||
| \r\n Keyed Hash \r\n | \r\n\r\n HMAC-SHA-1, HMAC-SHA-256, HMAC-SHA-384, HMAC-SHA-512 \r\n | \r\n\r\n Mode: SHA-1, SHA-256, SHA-384, SHA-512 \r\n | \r\n\r\n A2624 \r\n | \r\n\r\n Trellix OpenSSL FIPS Object Module \r\n | \r\n
\r\n
The Trellix OpenSSL FIPS Object Module provides cryptographic operations related to entropy.
\r\nThe TOE authenticates administrative users using a username/password combination. The TOE does not allow access to any administrative functions prior to successful authentication. The TOE validates and authenticates TLS clients and servers using X.509 certificates for all claimed certificate uses.
\r\nThe TOE supports passwords consisting of alphanumeric and special characters and enforces minimum password lengths. The TSF supports authentication based on certificates. Certificates are used to authenticate trusted channels, not administrators. The TOE only allows users to view the login warning banner prior to authentication. Remote administrators are locked out after a configurable number of unsuccessful authentication attempts.
\r\nThe TOE enables secure local and remote management of its security functions, including:
\r\nCollectively these roles comprise the “Security Administrator”
\r\nThe TOE ensures the authenticity and integrity of software updates through digital signatures and requires administrative intervention prior to the software updates being installed.
\r\nThe TOE can be configured to display a warning and consent banner when an administrator attempts to establish an interactive session over the CLI (local or remote) or remote web UI (Only VX series models doesn’t support Web UI Feature). The TOE also enforces a configurable inactivity timeout for remote administrative sessions.
\r\nThe TOE protects the integrity and confidentiality of communications as follows:
\r\n