FireSphere 14600
FireSphere 14600, from iboss, Inc., holds FIPS 140-2 certificate #2755 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
Certificate
| Certificate number | 2755 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | iboss, Inc. · website |
| Hardware versions | FireSphere 14600_FIPS |
| Firmware versions | 8.2.0.10 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The iboss FireSphere 14600 and 7960 are part of the iboss Secure Web Gateway Platform, which protects enterprise organizations against today’s evasive and complex threats including unknown malware, zero-day attacks and advanced persistent threats (APTS). iboss technology delivers post-infection defense with Network Anomaly Detection and Automatic Infection Containment to reduce data loss, and provides comprehensive reporting via the Incident Response Center, which correlates threat information from threat feeds and millions of endpoints to deliver actionable intelligence in real time.
Security level exceptions
- Roles, Services, and Authentication: Level 3
- Mitigation of Other Attacks: N/A
Approved algorithms (7)
| Algorithm | CAVP certificates |
|---|---|
| AES | 3562, 3902 |
| CVL | 607, 757 |
| DRBG | 1118 |
| HMAC | 2269, 2532 |
| KTS | |
| RSA | 1831, 1987 |
| SHS | 2931, 3215 |
Other algorithms
MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2016-09-26 | Initial | 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: 2016-09-26