808bits

F-Secure Cryptographic Service Provider DLL

FIPS 140-1 certificate #199 · F-Secure Corporation · data as of 2026-10-21

F-Secure Cryptographic Service Provider DLL, from F-Secure Corporation, holds FIPS 140-1 certificate #199 at overall level 1. 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. Validation Sunsetting Policy - FIPS 140-1 Certificate. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and using FIPS Approved algorithms and processes as listed

Certificate

Certificate number199
StandardFIPS 140-1
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorF-Secure Corporation · website
Software versions1.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The F-Secure Cryptographic Service Provider is a FIPS 140-1 Level 1 compliant software module, implemented as a 32-bit Windows™ NT compatible DLL, which provides a variety of cryptographic services and can be dynamically linked into applications by software developers to get access to general-purpose cryptographic functionality.

Security level exceptions

  • EMI/EMC: Level 3
  • Operating System Security: Tested as meeting Level 1 with Microsoft Windows NT 4.0 SP6

Approved algorithms (4)

AlgorithmCAVP certificates
DSA50
RSAvendor affirmed
SHA-162
Triple-DES68

Other algorithms

DES (Cert. #129); RSA Encryption/Decryption; IDEA; Blowfish; CAST-128; Rijndael; Arcfour; MD5; RIPEMD-160; HMAC-SHA-1; HMAC-MD5; HMAC-RMD160; Diffie-Hellman (key agreement)

Validation history

DateTypeLab
2001-12-18InitialCYGNACOM SOLUTIONS INC
2003-07-31Update

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: 2001-12-18, 2003-07-31

Source documents