FortiGate-200A/200A-HD, 300A/300A-HD and 500A/500A-HD
FortiGate-200A/200A-HD, 300A/300A-HD and 500A/500A-HD, from Fortinet, Inc., holds FIPS 140-2 certificate #807 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 | 807 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Fortinet, Inc. · website |
| Hardware versions | FortiGate-200A/200A-HD, FortiGate 300A/300A-HD, and FortiGate 500A/500A-HD |
| Firmware versions | FortiOS 3.00, build 8317, 061121 |
Module description
Quoted from the NIST CMVP entry for this certificate.
FortiGate Multi-Threat Security Solutions are dedicated, hardware-based devices that deliver complete content protection against blended threats at the network perimeter or within the internal network.
Security level exceptions
- Cryptographic Module Ports and Interfaces: Level 3
- Roles, Services, and Authentication: Level 3
- Cryptographic Key Management: Level 3
- Design Assurance: Level 3
Approved algorithms (6)
| Algorithm | CAVP certificates |
|---|---|
| AES | 471, 472, 475, 476 |
| HMAC | 228, 229, 232, 233 |
| RNG | 251 |
| RSA | 193 |
| SHS | 539, 540, 543, 544 |
| Triple-DES | 486, 487, 489, 490 |
Other algorithms
DES; 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 110 bits of encryption strength; non-compliant); MD5; HMAC-MD5
Validation history
| Date | Type | Lab |
|---|---|---|
| 2007-07-31 | Initial | DOMUS |
| 2008-02-21 | Update |
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: 2007-07-31, 2008-02-21