808bits

Silver Peak EdgeConnect

FIPS 140-2 certificate #4547 · Silver Peak Systems, Inc. · data as of 2026-08-28
Active. Sunset date 2026-09-21, 23 days away. This is the FIPS 140-2 sunset: after it, agencies may keep the module only in existing systems.
Caveat: When operated in FIPS mode

Certificate

Certificate number4547
StandardFIPS 140-2
Statusactive
Sunset date2026-09-21
Overall level1
Module typeFirmware
EmbodimentMulti-Chip Stand Alone
VendorSilver Peak Systems, Inc. · website
Firmware versionsECOS 8.1.9 and ECOS 9.1.0

Module description

Unity EdgeConnect appliances deliver predictable application performance and high availability over any combination of transport services. Orchestrated, application-driven security policies enable direct internet breakout for trusted SaaS, web, and applications, and secure connection to cloud hosted security services. EdgeConnect reduces complexity by enabling a single element, simplified "thin branch".

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AESA1957, A1958, C2122, C2163, C2209, C2214
CVLA1957, C2123, C2135, C2210, C2213
DRBGA1957, C2136, C2212
ECDSAA1957
ENT
HMACA1957, C2126, C2211
KAS
KAS-SSCA1957
KTS
RSAA1957, C2161, C2215
SHSA1957, C2121, C2208

Allowed algorithms

RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • EC-XS with Fedora Core 6 (2.6.38 Kernel) running on Intel Atom C3558 CPU (Denverton) with PAA
  • EC-XS with Fedora Core 6 (2.6.38 Kernel) running on Intel Atom C3558 CPU (Denverton) without PAA
  • EC-XS with Yocto 2.7.3 Warrior (4.19.87 Kernel) running on Intel Atom C3558 CPU (Denverton) with PAA
  • EC-XS with Yocto 2.7.3 Warrior (4.19.87 Kernel) running on Intel Atom C3558 CPU (Denverton) without PAA

Validation history

DateTypeLab
2023-07-09InitialAEGISOLVE, 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 active
  • Validation dates on record: 2023-07-09

Source documents