Module Name
Infoblox Trinzic Virtual DDI Appliance
Validation Dates
11/21/2018;02/28/2019;10/30/2019
Caveat
When operated in FIPS mode. When installed, initialized and configured as specified in Section 3.4 of the Security Policy
Security Level Exceptions
- Roles, Services, and Authentication: Level 2
- Design Assurance: Level 2
- Mitigation of Other Attacks: N/A
Embodiment
Multi-Chip Stand Alone
Description
Infoblox Trinzic Virtual DDI Appliances enable customers to deploy large, robust, manageable and cost-effective Infoblox Grids. This next-generation solution enables distributed delivery of core network services (including DNS, DHCP, IPAM, TFTP, and FTP) with the nonstop availability and real-time service management required for today's 24x7 advanced IP networks and applications.
Tested Configuration(s)
- NIOS 8.2.6 on VMWare ESXi 5.5 running on an HP ProLiant DL380 Gen9 with processor Intel Xeon E5-2680 with PAA
- NIOS 8.2.6 on VMWare ESXi 5.5 running on an HP ProLiant DL380 Gen9 with processor Intel Xeon E5-2680 without PAA
- NIOS 8.2.6 on VMWare ESXi 6.5 running on an HP ProLiant DL380 Gen9 with processor Intel Xeon E5-2680 with PAA
FIPS Algorithms
| AES |
Cert. #4805 |
| CKG |
vendor affirmed |
| CVL |
Certs. #1437 and #1438 |
| DRBG |
Cert. #1671 |
| DSA |
Cert. #1295 |
| ECDSA |
Cert. #1213 |
| HMAC |
Cert. #3215 |
| KTS |
AES Cert. #4805 and HMAC Cert. #3215; key establishment methodology provides 128 or 256 bits of encryption strength |
| RSA |
Cert. #2633 |
| SHS |
Cert. #3953 |
Allowed Algorithms
Diffie-Hellman (CVL Certs. #1437 and #1438, key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #1437 and #1438, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); HMAC-MD5; MD5; NDRNG; RSA (key wrapping; key establishment methodology provides between 112 bits and 150 bits of encryption strength)
Firmware Versions
NIOS 8.2.6
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
