Module Name
Attivo Cryptographic Module
Validation Dates
07/07/2017
Caveat
When operated in FIPS mode
Security Level Exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Embodiment
Multi-Chip Stand Alone
Description
Attivo Cryptographic Module is a component of Attivo Networks’ products such as the Attivo Central Manager 200, BOTsink 3200, and BOTsink 5100. These products constitute the Attivo ThreatMatrix Deception and Response Platform which detects stolen credentials, ransomware, and targeted attacks within user networks, data centers, clouds, SCADA, and IoT environments by deceiving attackers into revealing themselves. The detections along with comprehensive attack analysis and actionable alerts empower accelerated incident response.
Tested Configuration(s)
- CentOS 6.5 on CentOS 6.5 – KVM running on an Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz system with PAA
- CentOS 6.5 on VMware ESXi 6.0.0 running on an Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz system with PAA
- Mac OS X El Capitan 10.11.3 running on an Intel Core i5 1.4GHz system with PAA
- Ubuntu 12.04 LTS on CentOS 6.5 – KVM running on an Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz system with PAA
- Ubuntu 12.04 LTS on VMware ESXi 6.0.0 running on an Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz system with PAA
- Windows 7 Professional 64-bit on CentOS 6.5 – KVM running on an Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz system with PAA (single-user mode)
- Windows 7 Professional 64-bit on VMware ESXi 6.0.0 running on an Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz system with PAA
- Windows Server 2008 SP2 (32 bit) on CentOS 6.5 – KVM running on and Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz system with PAA
- Windows Server 2008 SP2 32-bit on VMware ESXi 6.0.0 running on an Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz system with PAA
Allowed Algorithms
EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
