808bits

Odyssey Security Component User Mode and Odyssey Security Component Kernel Mode

FIPS 140-2 certificate #1207 · Pulse Secure, LLC. · data as of 2026-10-21

Odyssey Security Component User Mode and Odyssey Security Component Kernel Mode, from Pulse Secure, LLC., holds FIPS 140-2 certificate #1207 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number1207
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorPulse Secure, LLC. · website
Software versionsVersion 2.0 (Odyssey Security Component User Mode) and Version 2.0 (Odyssey Security Component Kernel Mode)

Module description

Quoted from the NIST CMVP entry for this certificate.

The Odyssey Security Component (OSC) is a general purpose cryptographic library. OSC / User Mode is a user mode binary module for the Windows operating system. OSC / Kernel Mode is a kernel-mode binary module for the Windows operating system.

Security level exceptions

  • Design Assurance: Level 2

Approved algorithms (7)

AlgorithmCAVP certificates
AES783, 784
DSA293
HMAC430
RNG451
RSA373
SHS787
Triple-DES679

Other algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • Microsoft Windows 2000 SP3 (single-user mode)
  • Microsoft Windows XP SP2

Validation history

DateTypeLab
2009-10-19InitialUL Verification Services, Inc.
2013-12-11Update
2015-02-13UpdateUL Verification Services, 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: 2009-10-19, 2013-12-11, 2015-02-13

Source documents