Threat prevention
Intrusion Prevention System (IPS)
Stop known exploits at the edge and in the cloud before they reach your systems.
An Intrusion Prevention System (IPS) inspects traffic for known attack patterns and blocks them in line. Nexapp IPS runs signature-based inspection with automatic updates on Nexapp edges and in the cloud, managed from one console with the rest of your security policy.
What it does
Unpatched servers, older branch systems and exposed services are easy targets. Attackers scan for known vulnerabilities and use published exploits soon after disclosure. Patching every system in every branch takes time you may not have. An Intrusion Prevention System buys that time. It inspects traffic against signatures of known attacks and drops matching traffic before it reaches the target. Because it sits in the traffic path, it also protects devices that cannot run security software of their own.
How it works in Nexapp
Signature-based inspection
Traffic is matched against signatures of known exploits and attack techniques, and matching flows are dropped.
Automatic updates
Signatures update automatically, so new protection reaches every edge without a manual push.
Edge and cloud
IPS runs on Nexapp edges as part of the Nexapp Controller security suite, and in the cloud for traffic that passes through Nexapp SSE.
Paired with IP reputation
InstaShield IP reputation blocking works alongside IPS to drop traffic from addresses known to be malicious.
Where teams use it
Legacy systems in branches
A cooperative bank shields older branch systems that cannot be patched quickly with IPS on the branch edge.
Between office IT and the plant
A manufacturer inspects traffic crossing from the corporate network towards plant systems to catch exploit attempts moving between them.
Data-centre services used by branches
Internal services that every branch reaches are protected by IPS on the path, reducing exposure while patches are tested.
Frequently asked questions
Where does IPS run?
On Nexapp edges, as part of the security suite managed from the Nexapp Controller, and in the cloud for traffic that goes through Nexapp SSE.
How are signatures kept current?
Signatures update automatically, and you manage IPS policy centrally rather than device by device.
Can IPS events go to our SIEM?
Yes. Edges send syslog to a remote collector, and security events can be forwarded by syslog, webhook or email.
Related capabilities
- Firewall-as-a-Service (FWaaS)One firewall policy for every branch and remote user, delivered from the cloud.
- Malware preventionCatch known malware at the gateway and test unknown files before anyone opens them.
- Extended Detection and Response (XDR)Turn network, SSE and endpoint alerts into a short list of incidents, each with a timeline.
- All capabilitiesEvery capability in the Nexapp SASE platform.
See Intrusion Prevention System (IPS) on your own sites.
24×7 NOC in Pune · 75,000+ devices deployed · 400+ enterprise and banking customers since 2014.