Lenel OnGuard Communication Server
Lenel OnGuard Communication Server, from UTC Fire & Security Americas Corporation, Inc., holds FIPS 140-2 certificate #1086 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.
Caveat: When operated in FIPS mode with Windows Server 2003 Enhanced Cryptographic Provider (RSAENH) validated to FIPS 140-2 under Cert. #382 operating in FIPS mode and FIPS Key Generator validated to FIPS 140-2 under Cert. #1087
Certificate
| Certificate number | 1086 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | UTC Fire & Security Americas Corporation, Inc. · website |
| Software versions | 5.11.216 + Hot Fix 2.0.3 and 5.12.012 + Hot Fix 2.0.3 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Lenel OnGuard Communication Server module's primary purpose is to provide secure communications with external access control devices. The module is part of the Lenel advanced access control and alarm monitoring system. The Lenel advanced access control and alarm monitoring system is built on an open architecture platform, offers unlimited scalability, database segmentation, fault tolerance, and biometrics and smart card support. The Lenel advanced access control and alarm monitoring system 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 (4)
Other algorithms
RC2
Tested configurations
- Windows Server 2003 SP1 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2009-02-09 | Initial | UL Verification Services, Inc. |
| 2015-08-14 | Update | UL 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, 2015-08-14