808bits

VPN-1

FIPS 140-2 certificate #634 · Check Point Software Technologies Ltd. · data as of 2026-08-28
Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number634
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeFirmware
EmbodimentMulti-chip standalone
VendorCheck Point Software Technologies Ltd. · website
Firmware versionsNG with Application Intelligence R54

Module description

Check Point's VPN-1 version NG with Application Intelligence R54 is a tightly integrated software solution combining the FireWall-1 (FW-1) security suite with sophisticated Virtual Private Network (VPN) technologies and a hardened Secure Platform operating system (OS). The cornerstone of Check Point's Secure Virtual Network (SVN) architecture, VPN-1 meets the demanding requirements of Internet, intranet, and extranet VPNs by providing secure connectivity to corporate networks, remote and mobile users, branch offices, and business partners.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • EMI/EMC: Level 3
  • Design Assurance: Level 2
  • Tested: Dell Optiplex GX-1 running Secure Platform Operating System version NG with Application Intelligence R54

Approved algorithms

AlgorithmCAVP certificate
AES88
HMAC56
RNG30
RSA63
SHS325
Triple-DES333

Other algorithms

DES (Cert. #311); CAST 40 bit; CAST 128 bit; MD5; HMAC-MD5; Diffie-Hellman (key agreement, key establishment methodology provides between 70 and 97 bits of encryption strength; non-compliant); RSA (PKCS #1, key wrapping, key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2006-03-03InitialCYGNACOM SOLUTIONS INC
2008-05-02Update
2009-05-28Update

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: 2006-03-03, 2008-05-02, 2009-05-28

Source documents