808bits

Caymas Systems 318 Identity-Driven Access Gateway

FIPS 140-2 certificate #567 · Caymas Systems Inc. · data as of 2026-10-09

Caymas Systems 318 Identity-Driven Access Gateway, from Caymas Systems Inc., holds FIPS 140-2 certificate #567 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.

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 number567
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorCaymas Systems Inc.
Hardware versionsRev. 100-000001
Firmware versionsR2.6.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Caymas 318 and Caymas 525 are the world's first Identity-Driven Access Gateways, combining universal access, Identity-Based access control, integrated application security and federated policy enforcement. Caymas products are hardened, purpose-built appliances, with custom acceleration hardware allowing them to scale to thousands of users and multi-gigabit speeds in a single platform. With no per user or per feature pricing, Caymas gateways deliver radical price/performance for enterprises extending their information assets to internal and external users.

Security level exceptions

  • Roles, Services, and Authentication: Level 3

Approved algorithms (7)

AlgorithmCAVP certificates
AES231, 233, 234, 235
DSA129, 130, 131
HMAC43, 45
RNG71, 73, 74
RSA55, 56
SHS310, 312, 313, 314
Triple-DES321, 323, 325, 326

Other algorithms

DES (Certs. #301, #303 and #304); Diffie-Hellman (key agreement); MD5; HMAC-MD5; RC4

Validation history

DateTypeLab
2005-08-30InitialDOMUS

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: 2005-08-30

Source documents