An intrusion detection system (IDS) monitors network traffic or systems for attack patterns and reports hits; an intrusion prevention system (IPS) sits inline in the data path and blocks detected attacks directly. Both work with signatures of known attacks, complemented by protocol and anomaly analysis.
Today IDS/IPS rarely appear as standalone products: their functions live in next-generation firewalls, FWaaS platforms and cloud security services — centrally supplied with current signatures.
IDS or IPS — detect or prevent?
The difference lies in position and consequence: an IDS observes passively (at a mirror port, say) and alerts — it cannot prevent anything, but cannot break anything either. An IPS stands in the data path and stops attacks in real time — in return, every false positive becomes an operational problem because legitimate traffic gets stuck.
In practice you therefore often start in detection mode, measure false alarms, refine rules — and then switch to blocking selectively. Modern platforms allow this per rule and risk class.
Where IDS/IPS act today
- As a module in NGFW and FWaaS: signatures and protocol analysis in the central data path.
- At the network edge: virtual patching of known exploits before systems are updated.
- In the data center: detection of lateral attacks between segments.
- As a sensor building block for NDR and SIEM analysis.