Intrusion Prevention System
Also called IPS, NIPS.
An inline sensor that detects and actively blocks malicious traffic.
What it is
A monitoring system placed inline in the traffic path that, beyond detecting threats, can drop or reset malicious connections in real time. It combines detection with active enforcement.
Why it matters
Because an IPS can block as well as alert, its logs show both what was attempted and what was stopped, and its drop actions are themselves evidence when reconstructing an attacker's blocked attempts.
In practice
Confirming from IPS logs that a scanning burst was actively reset at the perimeter before any session completed.
What to look for
- Blocked sessions and the rules that fired.
- False positives breaking real traffic.
- Rules in detect only mode by mistake.
Common mistake
Turning on blocking for every rule. Test rules first, or you will block legitimate business traffic.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Palo Alto Networks NGFW Commercial
A next generation firewall that enforces policy by application and user and logs each session.
-
Cloudflare WAF Commercial
Filters web traffic at the edge before it reaches the application.
-
Suricata Open source
Can run inline as an IPS to block traffic that matches its rules. Our notes.
-
Snort Open source
A long standing open source IDS and IPS with a large public rule set.
Read next
- Intrusion Detection System: A sensor that watches traffic and alerts on malicious activity.
- Deep Packet Inspection: Inspecting a packet's payload, past the headers, to identify content.
- DNS Sinkhole: Redirecting malicious domain lookups to a controlled server.