Secure Firewall (Sidewinder) 1100E
Secure Firewall (Sidewinder) 1100E, from Secure Computing Corporation (Wholly owned subsidiary of McAfee, Inc.), holds FIPS 140-2 certificate #1108 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 | 1108 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Secure Computing Corporation (Wholly owned subsidiary of McAfee, Inc.) · website |
| Hardware versions | 1100 |
| Firmware versions | 7.0.1.01 |
Module description
Quoted from the NIST CMVP entry for this certificate.
Secure Firewall (Sidewinder) solutions provide unmatched protection for the enterprise in the most mission-critical and sensitive environments. Secure Computing's Secure Firewall (Sidewinder) appliances are created to meet the specific needs of organizations of all types and enable those organizations to reduce costs and mitigate the evolving risks that threaten today's networks and applications.
Approved algorithms (7)
| Algorithm | CAVP certificates |
|---|---|
| AES | 972, 973, 974 |
| DSA | 338, 339 |
| HMAC | 544, 545, 546 |
| RNG | 549, 550, 551 |
| RSA | 469, 470 |
| SHS | 941, 942, 943 |
| Triple-DES | 765, 766, 767 |
Other algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); Blowfish; RC2; RC4; MD5; DES
Validation history
| Date | Type | Lab |
|---|---|---|
| 2009-04-09 | Initial | DOMUS |
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: 2009-04-09