808bits

Kasten Chase Cryptographic Engine

FIPS 140-2 certificate #486 · Kasten Chase Applied Research, Ltd. · data as of 2026-09-13

Kasten Chase Cryptographic Engine, from Kasten Chase Applied Research, Ltd., holds FIPS 140-2 certificate #486 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 number486
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeSoftware
EmbodimentMulti-chip standalone
VendorKasten Chase Applied Research, Ltd. · website
Software versions2.0

Module description

Quoted from the NIST CMVP entry for this certificate.

KCCE is an independent, executable cryptographic module that exists variously as a dynamic linked library (dll), a shared library and a driver. KCCE provides software designers with a comprehensive API that ensures secure cryptographic application development, for a wide range of operating systems, without undue complexity.

Security level exceptions

  • Roles, Services, and Authentication: Level 3

Approved algorithms (7)

AlgorithmCAVP certificates
AES163
ECDSAvendor affirmed
HMAC-SHA-1, HMAC-SHA-256, HMAC-SHA-384; HMAC- SHA-512vendor affirmed
RNG10
RSA12
SHS246
Triple-DES265

Other algorithms

MD5; HMAC-MD5; KEA, EC Diffie-Hellman (key agreement)

Tested configurations

  • AIX 5L for POWER V5.2 on a IBM p630-6C4 with a POWER4 CPU
  • Sun Trusted Solaris™ Version 8 4/01 on a SunBlade 100 with a 500 MHz UltraSPARC Iie
  • Windows 2000 Server with SP3 and Hotfix Q326886 on a 650 MHz Pentium III platform

Validation history

DateTypeLab
2004-12-10InitialEWA - Canada

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: 2004-12-10

Source documents