808bits

Lenel OnGuard FIPS Key Generator

FIPS 140-2 certificate #1087 · UTC Fire & Security Americas Corporation, Inc. · 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 with [(Windows 7 Enhanced Cryptographic Provider (RSAENH) validated to FIPS 140-2 under Cert. #1330 operating in FIPS mode), (Windows Server 2008 R2 Enhanced Cryptographic Provider (RSAENH) validated to FIPS 140-2 under Cert. #1337 operating in FIPS mode) or (Windows Server 2003 Enhanced Cryptographic Provider (RSAENH) validated to FIPS 140-2 under Cert. #382 operating in FIPS mode)]

Certificate

Certificate number1087
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorUTC Fire & Security Americas Corporation, Inc. · website
Software versions2.1

Module description

The Lenel OnGuard FIPS Key Generator module's primary purpose is to provide a cryptographically secure means for generating 128-bit AES keys to be used as Master Keys within Lenel's Communication Server module. The FIPS Key Generator module is part of the Lenel advanced access control and alarm monitoring system which is built on an open architecture platform, offers unlimited scalability, database segmentation, fault tolerance, biometrics and smart card support, is fully customizable, and can be seamlessly integrated into the OnGuard total security solution.

Security level exceptions

  • EMI/EMC: Level 3
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AES327, 1650
RNG149, 882

Tested configurations

  • Windows 7
  • Windows Server 2003 SP1
  • Windows Server 2008 (single-user mode)

Validation history

DateTypeLab
2009-02-09InitialUL Verification Services, Inc.
2012-03-14UpdateUL Verification Services, Inc.
2015-08-14UpdateUL 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-02-09, 2012-03-14, 2015-08-14

Source documents