808bits

Trellix Intrusion Prevention System Sensor NS7500

FIPS 140-3 certificate #5381 · Trellix · data as of 2026-08-28
Active. Sunset date 2031-07-07, 1773 days away.
Caveat: No assurance of minimum security of SSPs (e.g., keys, bit strings) that are externally loaded, or of SSPs established with externally loaded SSPs.

Certificate

Certificate number5381
StandardFIPS 140-3
Statusactive
Sunset date2031-07-07
Overall level1
Module typeHardware
EmbodimentMultiChipStand
VendorTrellix · website

Module description

The NS7500 is an Intrusion Prevention System (IPS) and Intrusion Detection System (IDS) designed for network protection against zero-day, DoS/DDoS, encrypted and SYN Flood attacks, and real-time prevention of threats like spyware, malware, VoIP vulnerabilities, phishing, botnets, network worms, Trojans, and peer-to-peer applications. The Trellix Intrusion Prevention system Sensors (Trellix IPS sensor) connect with the Trellix Intrusion Prevention System Manager Appliances (Trellix IPS Manager-may be referred to as Manager in this document). The Trellix IPS Manager is used to manage and push configuration data and policies to the Sensors. Communication between Manager and Sensors uses secure channels that protect the traffic from disclosure and modification. Authorized administrators may access the Trellix IPS Manager via a GUI (over HTTPS) or a CLI (via SSH or a serial console connection). Sensors may be accessed via CLI (via SSH or a serial console connection) for initial setup. Once initial setup is complete, all management occurs via the Manager.

Security level exceptions

  • Roles, services, and authentication: Level 2
  • Software/Firmware security: Level 2
  • Non-invasive security: N/A
  • Sensitive security parameter management: Level 2
  • Life-cycle assurance: Level 2
  • Mitigation of other attacks: N/A

Validation history

DateTypeLab
2026-07-08InitialAcumen 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 active
  • Validation dates on record: 2026-07-08

Source documents