ACM 200
ACM 200, from Attivo Networks Inc., holds FIPS 140-2 certificate #4051 at overall level 2. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.
Certificate
| Certificate number | 4051 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Attivo Networks Inc. · website |
| Hardware versions | 200 |
| Firmware versions | 3.3 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The ACM is designed to manage several BOTsinks in a centralized manner. ACMs cannot be managed by other ACMs, and each BOTsink can be programmed to use one and only one ACM.
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms (7)
| Algorithm | CAVP certificates |
|---|---|
| AES | 4134, 4417 |
| CVL | 941, 1130, 1228, 1229, 1230 |
| DRBG | 1251, 1426 |
| HMAC | 2706, 2933 |
| RSA | 2250, 2405 |
| SHS | 3403, 3638 |
| Triple-DES | 2259, 2379 |
Allowed algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #941 with CVL Certs. #1228 and #1229, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2021-10-26 | Initial | ADVANCED 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: 2021-10-26