808bits

Network Security Platform Sensor NS7100, NS7200 and NS7300

FIPS 140-2 certificate #3576 · McAfee, LLC · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. 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 number3576
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorMcAfee, LLC · website
Hardware versionsP/Ns IPS-NS7100 Version 1.00, IPS-NS7200 Version 1.00 and IPS-NS7300 Version 1.00; FIPS Kit P/N IAC-FIPS-KT2
Firmware versions9.1.17.100

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
AESC409
CKGvendor affirmed
CVLC409, C410
DRBGC409
HMACC409
KTS
KTS
RSA2638, C409
SHS3960, C409

Allowed algorithms

EC Diffie-Hellman (CVL Cert. #C409 with CVL Cert. #C410, key agreement; key establishment methodology provides 128 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2019-12-04InitialAcumen Security
2020-03-23UpdateAcumen Security

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: 2019-12-04, 2020-03-23

Source documents