Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
An intrusion detection system (IDS) monitors network traffic or host activity for signs of attack and raises alerts; an intrusion prevention system (IPS) can also block it.

What Is an Intrusion Detection System (IDS)?
An intrusion detection system (IDS) is a security control that watches network traffic or activity on a host and raises an alert when it sees something that matches known attack patterns or deviates from normal behaviour. It is a detective control: it tells you something is happening, but on its own it does not stop it.
When the same engine sits inline and is allowed to drop malicious packets, it becomes an intrusion prevention system (IPS). Most commercial products today can operate in either mode, so the two are usually discussed together as IDS/IPS.
A network intrusion detection system (NIDS) inspects packets copied from a switch SPAN port or a network tap. It sees traffic between many systems at once—scans, exploit attempts, command-and-control beacons, and data leaving the network—without installing anything on endpoints.
A host-based intrusion detection system (HIDS) runs on an individual server or workstation. It watches log files, file integrity, registry changes, and process activity. OSSEC and its fork Wazuh are well-known open-source examples; modern EDR platforms have largely absorbed the HIDS role on endpoints, as covered in our note on EDR, MDR, XDR, and EPP.
The engine compares traffic against a library of rules describing known threats—a specific exploit payload, a malware user agent, or a pattern in a DNS query. Signatures are precise and easy to explain, but they cannot recognise attacks nobody has written a rule for yet. Rule sets such as Emerging Threats and the Snort community rules are updated daily.
The system learns a baseline of normal traffic and flags deviations: a workstation suddenly talking SMB to hundreds of hosts, or a server sending gigabytes to an unfamiliar country at night. This can catch novel attacks but tends to generate more false positives, especially in networks that change often.
Stateful protocol analysis checks whether traffic behaves as the relevant protocol specification says it should. Malformed HTTP requests, DNS tunnelling, and unexpected commands inside an industrial protocol are caught this way.
| IDS | IPS | |
|---|---|---|
| Position | Out of band, on a copy of traffic | Inline, traffic passes through it |
| Action | Alerts only | Alerts and blocks |
| Risk of disruption | None to traffic flow | False positives can block legitimate business traffic |
| Latency | No impact | Small added latency |
Many organisations run new rules in detect-only mode first, then move well-tested, high-confidence signatures into blocking mode. Next-generation firewalls commonly include an IPS engine.
Sensor placement decides what you can see. Common choices are just inside the internet edge, in front of the DMZ, between user and server segments, and at the boundary to sensitive zones such as cardholder data environments or OT networks. Monitoring east-west traffic matters because lateral movement never crosses the perimeter.
An untuned IDS produces thousands of alerts a day and is quickly ignored. Disable rules for software you do not run, suppress known-benign sources such as vulnerability scanners, and send alerts to your SIEM where they can be correlated with endpoint and identity data.
Most traffic is now encrypted with TLS 1.3, so a NIDS sees metadata—destinations, certificate details, JA3/JA4 fingerprints, timing—but not payloads, unless TLS inspection is deployed. Cloud workloads need virtual sensors or provider-native tools such as AWS Traffic Mirroring. And an IDS only creates value if someone triages its alerts around the clock.
From a compliance perspective, PCI DSS v4.0 requirement 11.5.1 explicitly calls for intrusion-detection or intrusion-prevention techniques, and the NIS Regulations expect operators of essential services to monitor for security events.
At Privia Security, we design, deploy, and tune sensors through our intrusion detection and prevention solutions.
Often the firewall’s built-in IPS covers north-south traffic at the internet edge, which is enough for smaller organisations. A separate IDS adds value for internal east-west monitoring, deep logging with tools such as Zeek, and independent visibility that does not depend on the firewall vendor. Larger or regulated organisations usually run both, feeding alerts into a central SIEM.
Not the content, unless you decrypt it first using TLS inspection on a proxy or firewall. Without decryption, a NIDS still analyses useful metadata: server names, certificate details, TLS fingerprints, connection timing, and traffic volumes. These signals are enough to detect many command-and-control channels and data exfiltration attempts. Endpoint agents complement this by seeing activity before encryption takes place.
Both are mature, free, and widely supported. Suricata was designed from the start for multi-threading and offers built-in protocol logging and file extraction, which suits high-throughput links. Snort 3 has closed much of the performance gap and benefits from Cisco Talos rules. The choice usually depends on your existing tooling, team experience, and which platform your SIEM integrates with best.
Begin by disabling rules for operating systems, applications, and protocols that you do not use. Add suppression for trusted sources such as vulnerability scanners and backup servers. Review the noisiest signatures weekly, and tune thresholds rather than turning rules off entirely. Correlating IDS alerts with endpoint and asset data in a SIEM also helps analysts quickly separate real attacks from harmless activity.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.