FortiManager-1000D
FortiManager-1000D, from Fortinet, Inc., holds FIPS 140-2 certificate #2517 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 | 2517 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Fortinet, Inc. · website |
| Hardware versions | C1AA82-01AA-0000 with Tamper Evident Seal Kits: FIPS-SEAL-RED |
| Firmware versions | v5.2.4-build0738 150923 (GA) |
Module description
Quoted from the NIST CMVP entry for this certificate.
FortiManager Network Security Management Appliances were designed to provide security management for large enterprise organizations and service providers. They enable you to centrally manage any number of Fortinet devices, including FortiManager, FortiWiFi, and FortiCarrier™. FortiManager provides the high performance and scalability you need to efficiently apply policies and distribute content security/firmware updates, regardless of the size of your network.
Security level exceptions
- Cryptographic Module Ports and Interfaces: Level 3
- Roles, Services, and Authentication: Level 3
- Design Assurance: Level 3
- Mitigation of Other Attacks: N/A
Approved algorithms (7)
Other algorithms
Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 201 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength); DES; MD5; HMAC-MD5
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2016-01-05 | Initial | CGI Information Systems & Management Consultants Inc |
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: 2016-01-05