808bits

Attivo Cryptographic Provider

FIPS 140-2 certificate #3010 · Attivo Networks Inc. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy. No assurance of the minimum strength of generated keys

Certificate

Certificate number3010
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorAttivo Networks Inc. · website
Software versions1.0

Module description

Attivo Cryptographic Provider 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.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4049
CVL878, 879, 1190
DRBG1213
DSA1095
ECDSA908
HMAC2644
KAS90
KASvendor affirmed
KBKDF99
KTSvendor affirmed
KTS
KTS
PBKDFvendor affirmed
RSA2084
SHA-39
SHS3339
Triple-DES2215

Allowed algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • Open JDK 1.8 on CentOS 6.5 Intel 64-bit on ESXi 5.5.0 running on an Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz system

Validation history

DateTypeLab
2017-09-06InitialADVANCED DATA SECURITY

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2017-09-06

Source documents