SBC Software Edition Session Border Controller
Certificate
| Certificate number | 3207 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Sonus Networks, Inc. · website |
| Software versions | R5.1.2 |
Module description
The Sonus SBC Software Edition Session Border Controller (SBC SWe) is a software-based, cloud-optimized SBC architected to enable and secure real-time communications in the cloud. Starting at 25 sessions, and scaling to tens of thousands per instance, the unique architecture of the SBC SWe allows customers to define where on the performance curve their network needs to reside. The SBC SWe uses a "microservices" design to separate signaling, media, and transcoding to optimize virtual network resources. It also supports on-demand auto-scaling, with a feedback loop using Key Performance Indicator
Security level exceptions
- Roles, Services, and Authentication: Level 2
- Physical Security: N/A
- Design Assurance: Level 2
- Mitigation of Other Attacks: N/A
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 4685, 4686 |
| CKG | vendor affirmed |
| CVL | 1327, 1380 |
| DRBG | 1588 |
| ECDSA | 1202 |
| HMAC | 3100, 3101 |
| RSA | 2556 |
| SHS | 3835, 3836 |
| Triple-DES | 2490, 2491 |
Allowed algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #1327, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)
Tested configurations
- HPE ProLiant DL380 Gen9 server with dual Intel Xeon processors running Sonus’s ConnexIP OS over a VMware ESXi 6.0 hypervisor
Validation history
| Date | Type | Lab |
|---|---|---|
| 2018-06-25 | Initial | EWA - Canada |
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: 2018-06-25