Silver Peak Unity EdgeConnect EC-XS-FIPS, EC-M-P-FIPS, EC-XL-P-FIPS and EC-XL-P-NM-FIPS
Silver Peak Unity EdgeConnect EC-XS-FIPS, EC-M-P-FIPS, EC-XL-P-FIPS and EC-XL-P-NM-FIPS, from Silver Peak Systems, Inc., holds FIPS 140-2 certificate #4116 at overall level 2. 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.
Certificate
| Certificate number | 4116 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Silver Peak Systems, Inc. · website |
| Hardware versions | EC-XS-FIPS[1], EC-M-P-FIPS[2], EC-XL-P-FIPS[3] and EC-XL-P-NM-FIPS[3] with FIPS Kit 500329-001[1], 500330-001[2] or 500331-001[3] |
| Firmware versions | 8.1.9.7 |
Module description
Quoted from the NIST CMVP entry for this certificate.
Unity EdgeConnect appliances deliver predictable application performance over any combination of transport services. Orchestrated application-driven security policies enable direct internet breakout for trusted SaaS and web applications. Fully compatible with existing WAN infrastructure, EdgeConnect provides simplifies and enables the Thin Branch.
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms (7)
Allowed algorithms
Diffie-Hellman (CVL Cert. #C1204, key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #C1204 with CVL Cert. #C1204, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2021-12-27 | Initial | ADVANCED DATA SECURITY |
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: 2021-12-27