Products in scope
Omnissa FedRAMP Certified systems incorporate FIPS 140-3 module implementation and usage validated annually by an approved FedRAMP 3PAO. As such, those modules are not included in the table below.
Workspace ONE UEM
Server
| Version | Bouncy Castle | OpenSSL | Platform provided |
| UEM Server (On-Prem) 2410 patch 20+ | Bouncy Castle (BC-FJA) 2.0.0 | WinCNG via .NET Core |
Hub
Workspace ONE UEM Hub versions, with the exception of Windows, are built against a common SDK, per platform, which provides OpenSSL encryption in FIPS mode.
| Version | Bouncy Castle | OpenSSL | Platform provided |
| Windows Hub | WinCNG via .NET Core | ||
| MacOS Hub 25.11+ | OpenSSL 3.4 with 3.0.9 FIPS module | Apple CoreCrypto | |
| iOS Hub 25.09+ | OpenSSL 3.4 with 3.0.9 FIPS module | ||
| Android Hub 26.02+ | OpenSSL 3.4 with 3.0.9 FIPS module |
Apps
Workspace ONE UEM mobile apps are built against a common SDK, per platform, which provides OpenSSL encryption in FIPS mode.
| Version | Bouncy Castle | OpenSSL | Platform provided |
| WS1 Web 25.08+ | OpenSSL 3.4 with 3.0.9 FIPS module | ||
| WS1 Content 25.08+ | OpenSSL 3.4 with 3.0.9 FIPS module | ||
| WS1 Intelligent Hub 26.02+ | OpenSSL 3.4 with 3.0.9 FIPS module |
Horizon
Connection Server
| Version | Bouncy Castle | OpenSSL | Platform provided |
| Horizon CS 2603 | Bouncy Castle (BC-FJA) 2.1.2 | OpenSSL 3.0.19 with 3.0.9 FIPS module | WinCNG via .NET Core |
| Horizon CS 2512 | Bouncy Castle (BC-FJA) 2.1.3 | OpenSSL 3.0.19 with 3.0.9 FIPS module | WinCNG via .NET Core |
| Horizon CS 2506 | Bouncy Castle (BC-FJA) 2.0.0 | OpenSSL 3.0.16 with 3.0.9 FIPS module | WinCNG via .NET Core |
Agent
Agent (Windows)
| Version | Bouncy Castle | OpenSSL | Platform provided |
| Horizon Windows Agent 2603 | Bouncy Castle (BC-FJA) 2.1.2 | OpenSSL 3.0.19 with 3.0.9 FIPS module | WinCNG via .NET Core |
| Horizon Windows Agent 2512 | Bouncy Castle (BC-FJA) 2.1.1 | OpenSSL 3.0.18 with 3.0.9 FIPS module | WinCNG via .NET Core |
| Horizon Windows Agent 2506 | Bouncy Castle (BC-FJA) 2.0.0 | OpenSSL 3.0.16 with 3.0.9 FIPS module | WinCNG via .NET Core |
Agent (Linux)
| Version | Bouncy Castle | OpenSSL | Platform provided |
| Horizon Linux Agent 2603 | Bouncy Castle (BC-FJA) 2.1.2 | OpenSSL 3.0.18 with 3.0.9 FIPS module | WinCNG via .NET Core |
| Horizon Linux Agent 2512 | Bouncy Castle (BC-FJA) 2.1.1 | OpenSSL 3.0.18 with 3.0.9 FIPS module | WinCNG via .NET Core |
| Horizon Linux Agent 2506 | Bouncy Castle (BC-FJA) 1.0.2.4 | OpenSSL 3.0.16 with 3.0.9 FIPS module | WinCNG via .NET Core |
Client
Client (Windows)
| Version | Bouncy Castle | OpenSSL | Platform provided |
| Horizon Windows Client 2603 | OpenSSL 3.0.19 with 3.0.9 FIPS module | WinCNG via .NET Core | |
| Horizon Windows Client 2512 | OpenSSL 3.0.18 with 3.0.9 FIPS module | WinCNG via .NET Core | |
| Horizon Windows Client 2506 | OpenSSL 3.0.19 with 3.0.9 FIPS module | WinCNG via .NET Core |
Client (Linux)
| Version | Bouncy Castle | OpenSSL | Platform provided |
| Horizon Linux Client 2603 | OpenSSL 3.0.19 with 3.0.9 FIPS module | ||
| Horizon Linux Client 2512 | OpenSSL 3.0.18 with 3.0.9 FIPS module | ||
| Horizon Linux Client 2506 | OpenSSL 3.0.16 with 3.0.9 FIPS module |
Client (Android)
| Version | Bouncy Castle | OpenSSL | Platform provided |
| Horizon Linux Client 2603 | OpenSSL 3.0.19 with 3.0.9 FIPS module | ||
| Horizon Linux Client 2512 | OpenSSL 3.0.18 with 3.0.9 FIPS module
| ||
| Horizon Linux Client 2506 | OpenSSL 3.0.18 with 3.0.9 FIPS module
|
Client (iOS/iPadOS)
| Version | Bouncy Castle | OpenSSL | Platform provided |
| Horizon iOS/iPadOS Client 2603 | OpenSSL 3.0.19 with 3.0.9 FIPS module | Apple CoreCrypto | |
| Horizon iOS/iPadOS Client 2512 | OpenSSL 3.0.18 with 3.0.9 FIPS module
| Apple CoreCrypto | |
| Horizon iOS/iPadOS Client 2506 | OpenSSL 3.0.16 with 3.0.9 FIPS module
| Apple CoreCrypto |
Client (macOS)
| Version | Bouncy Castle | OpenSSL | Platform provided |
| Horizon macOS Client 2603 | OpenSSL 3.0.19 with 3.0.9 FIPS module | Apple CoreCrypto | |
| Horizon macOS Client 2512 | OpenSSL 3.0.18 with 3.0.9 FIPS module
| Apple CoreCrypto | |
| Horizon macOS Client 2506 | OpenSSL 3.0.16 with 3.0.9 FIPS module
| Apple CoreCrypto |
Unified Access Gateway (UAG)
| Version | Bouncy Castle | OpenSSL | Platform provided |
| Unified Access Gateway 2603 | Bouncy Castle (BC-FJA) 2.1.2 | OpenSSL 3.0.19 with 3.0.9 FIPS module | |
| Unified Access Gateway 2512 | Bouncy Castle (BC-FJA) 2.1.2 | OpenSSL 3.0.18 with 3.0.9 FIPS module
|
Frequently asked questions about FIPS 140-3 at Omnissa
FIPS 140-3 includes different levels that apply to different technologies and different levels of security. Level 1 is the only level that applies to software solutions. The other levels broadly apply to chips and other hardware solutions. Level 1 FIPS requirements apply to cryptographic modules, and only cryptographic modules can be issued a FIPS certificate. Products that are not cryptographic modules can never be “FIPS validated”. “FIPS compliant” is often used to describe products that implement FIPS validated crypto modules either exclusively or in a “FIPS mode”. “FIPS Compliant” is not a term recognized by NIST. At Omnissa, we prefer to say that we implement FIPS validated cryptographic modules for all crypto operations that perform a security function, following all appropriate guidance from NIST.
This list is a continuous work in progress. As products implement and update their FIPS-validated modules, this list will be updated. If you require FIPS 140-3 for a product that is not listed here, please contact your Omnissa product team and/or open a support ticket.