808bits

Network Security Platform Sensor M-1250, M-1450, M-2750, M-2850, M-2950, M-3050, M-4050 and M-6050

FIPS 140-2 certificate #2555 · McAfee, Inc. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated with the tamper evident seals installed as indicated in the Security Policy

Certificate

Certificate number2555
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorMcAfee, Inc. · website
Hardware versionsP/Ns M-1250 Version 1.10, M-1450 Version 1.10, M-2750 Version 1.50, M-2850 Version 1.00, M-2950 Version 1.00, M-3050 Version 1.20, M-4050 Version 1.20 and M-6050 Version 1.40; FIPS Kit P/Ns IAC-FIPS-KT2 and IAC-FIPS-KT7
Firmware versions8.1.15.14

Module description

Network Security Platform products (formerly known as IntruShield) are Intrusion Prevention Systems (IPS) that protect network infrastructures and endpoints from intrusions such as zero-day, DoS, spyware, VoIP, botnet, malware, phishing, and encrypted attacks with highly accurate, enterprise-class risk-aware intrusion prevention. The Network Security Management system manages the sensor deployments and permits the customer to receive real-time network status updates and alerts, implement customized security policies and incident response plans, and perform forensic analysis of attacks.

Security level exceptions

  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES3155
CVL407, 598
DRBG648
HMAC1988
RSA1598, 1824
SHS2610, 2922

Other algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength); Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; RC4; DES; AES (non-compliant); HMAC (non-compliant); RSA (non-compliant); SHS (non-compliant); Triple-DES (non-compliant); SNMP KDF (non-compliant)

Tested configurations

  • N/A

Validation history

DateTypeLab
2016-02-09InitialUL Verification Services, Inc.
2016-05-03UpdateUL 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-02-09, 2016-05-03

Source documents