808bits

FortiSandbox-1000F/2000E/3000E

FIPS 140-2 certificate #4113 · Fortinet, Inc. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and installed, initialized and configured as specified in the FIPS 140-2 Compliant Operation Section of the Security Policy with the tamper evident seals and entropy token installed as indicated in the Security Policy. Authentication at level 3 is only applicable when identity-based authentication is enforced for the User role. No assurance of the minimum strength of generated keys

Certificate

Certificate number4113
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorFortinet, Inc. · website
Hardware versionsFortiSandbox-2000E (C1AG28), FortiSandbox-1000F (C1AH16) and FortiSandbox-3000E (C1AF74) with Tamper Evident Seal Kit: FIPS-SEAL-RED
Firmware versionsFortiSandbox 3.1, build 5166

Module description

The FortiSandbox-2000E, 1000F and 3000E are multiple chip, standalone cryptographic modules consisting of production grade components contained in a physically protected enclosure in accordance with FIPS 140-2 Level 2 requirements.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AESC1909, C1988, C1989
CVLC1988, C1989
DRBGC1986
HMACC1988, C1989
KTS
KTS
RSAC1988
SHSC1988, C1989

Allowed algorithms

Diffie-Hellman (CVL Certs. #C1988 and #C1989, key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #C1988, key agreement; key establishment methodology provides 128 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2021-12-20InitialLightship Security, 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: 2021-12-20

Source documents