Intrusion Detection and Prevention
Intrusion detection and prevention systems monitor network or host activity for signs of attack. Detection raises an alert; prevention also takes an action such as dropping traffic or ending a session.
itDefensive security and security operations | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Intrusion Detection and Prevention
An intrusion detection and prevention system, or IDPS, monitors events for signs of a security incident. It records what it observes, evaluates the evidence, and reports suspicious activity. An intrusion prevention system can also act on that decision. It might drop a packet, reset a connection, block an address, or change another security control.
The distinction is operational rather than cosmetic. A passive intrusion detection system receives a copy of traffic or host events. A mistake creates an alert that an analyst can dismiss. An inline intrusion prevention system sits in the traffic path. A mistake can interrupt a legitimate service. Prevention therefore requires stronger testing, narrower policies, and a defined failure strategy.
The core path is:
event source → sensor → normalization and state → detection logic → alert or prevention action → analyst
The event source supplies packets, wireless frames, flow records, logs, file changes, process activity, or other host events. A sensor collects and interprets that data. The analysis engine rebuilds useful context, such as a TCP stream or a sequence of login failures. Detection logic evaluates the normalized event. The system then records an alert or asks an enforcement point to act. A management console distributes policy and gives analysts a place to investigate results.
Four places to observe
NIST groups enterprise IDPS technologies into four classes. Each class sees a different part of an attack.
- Network-based IDPS inspects packets on wired network segments. It can observe many systems from one sensor, but it cannot see plaintext hidden inside encryption unless traffic is decrypted elsewhere.
- Wireless IDPS monitors wireless protocols and radio activity. It can identify unauthorized access points, unusual associations, and attacks specific to wireless networks.
- Network behavior analysis examines flows and traffic patterns. It is suited to changes in communication behavior, scans, denial-of-service patterns, and other activity that may not contain a known payload signature.
- Host-based IDPS runs on or monitors an individual system. It can inspect logs, files, processes, configuration, and system calls that a network sensor cannot see.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://csrc.nist.gov/pubs/sp/800/94/final
Supports
- IDPS purpose, components, detection methods, technology classes, deployment, operation, prevention actions, false positives, false negatives, and evasion
- Passive and inline distinctions, sensor placement, tuning, health monitoring, and complementary controls
- Quiz answers and the primary reference path
- https://nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800-94.pdf
Supports
- Detailed false-positive and false-negative tradeoffs
- Prevention through session termination, external control changes, blocking, and content modification
- https://csrc.nist.gov/glossary/term/intrusion_detection_system
Supports
- IDS definitions and network-based versus host-based vantage points
- Reference-link rationale
- https://docs.snort.org/start/inspection
Supports
- Packet capture, interface inspection, passive mode, inline mode, DAQ, and direct blocking
- https://docs.snort.org/rules/
Supports
- Rule headers, bodies, required option matching, actions, protocols, addresses, ports, and direction
- The claim that an alert establishes a rule match rather than successful compromise
- https://docs.suricata.io/en/suricata-8.0.3/ips/index.html
Supports
- Suricata inline IPS operation and deployment arrangements
- https://docs.suricata.io/en/suricata-7.0.15/rules/thresholding.html
Supports
- Alert threshold modes and the continued application of drop and reject actions to matching packets
- https://docs.suricata.io/en/suricata-8.0.0/output/eve/
Supports
- EVE alerts, anomalies, protocol records, flows, drops, and statistics
- https://www.ossec.net/docs/index.html
Supports
- Host-based log analysis, integrity checking, registry monitoring, rootkit detection, alerting, and active response
- OSSEC reference, awesome-link, and landscape placement
- https://github.com/sbilly/awesome-security
Supports
- Discovery of Security Onion, OSSEC, Wazuh, CrowdSec, and Fail2Ban for the IDS, IPS, host IDS, and host IPS ecosystem
- https://securityonionsolutions.com/software/
Supports
- Suricata signature detection, protocol metadata, packet capture, host visibility, hunting, and case management in a sensor grid
- Security Onion awesome-link and landscape rationale
- https://documentation.wazuh.com/current/getting-started/index.html
Supports
- Wazuh agent, server analysis, indexer, dashboard, and response architecture
- Wazuh awesome-link and landscape rationale
- https://docs.crowdsec.net/u/getting_started/intro/
Supports
- Log acquisition, parsing, behavior scenarios, decisions, and separate remediation components
- CrowdSec awesome-link rationale
- https://github.com/fail2ban/fail2ban
Supports
- Log-driven detection and firewall-rule enforcement after repeated failures
- Fail2Ban awesome-link rationale
- https://www.snort.org/
Supports
- Snort landscape identity, open-source engine, rule-driven IDS and IPS placement
- https://suricata.io/
Supports
- Suricata landscape identity as an open IDS, IPS, and network security monitoring engine
- https://secure.cisco.com/secure-firewall/v7.6/docs/intrusion-policy-73
Supports
- Snort inspection, network analysis policy, intrusion rules, alert and block actions, and inline deployment
- Cisco Secure Firewall landscape placement
- https://docs.paloaltonetworks.com/advanced-threat-prevention/getting-started/about-advanced-threat-prevention
Supports
- Firewall-integrated signatures and inline analysis for exploits, malware, and command-and-control traffic
- Palo Alto Networks landscape placement
- https://docs.fortinet.com/document/fortigate/7.2.10/administration-guide/565562
Supports
- FortiGate IPS signatures, protocol decoders, heuristics, threat intelligence, and inspection profiles
- Fortinet landscape placement
- https://www.checkpoint.com/quantum/intrusion-prevention-system-ips/
Supports
- Gateway protections, detect-only mode, recommended profiles, scope, prevention, and virtual patching
- Check Point landscape placement and virtual-patching quiz answer
- https://www.trendmicro.com/en/business/products/network/integrated-atp/next-gen-intrusion-prevention-system.html
Supports
- Dedicated inline inspection, enforcement, centralized management, and vulnerability-focused filters
- TippingPoint landscape placement
- https://www.trellix.com/products/network-security/
Supports
- Conventional IPS, behavioral analysis, sandboxing, and inline blocking
- Trellix landscape placement
- https://www.cerias.purdue.edu/about/history/coast_resources/idcontent/ids_bib.html
Supports
- April 1980 publication of James P. Anderson's Computer Security Threat Monitoring and Surveillance report
- https://faculty.nps.edu/dedennin/
Supports
- August 1985 IDES requirements and model report
- February 1987 publication details for An Intrusion-Detection Model
- https://doi.org/10.1109/TSE.1987.232894
Supports
- The 1987 audit-record, profile, statistical-model, and rule framework milestone
- https://docs.zeek.org/en/current/about/history.html
Supports
- Bro design in 1995, deployment in 1996, original paper publication, and project evolution
- https://secure.cisco.com/secure-firewall/v7.2/docs/snort-3-adoption
Supports
- Snort as a 1998 network sniffer, 1999 IDS, and 2004 inline IPS
- https://csrc.nist.gov/pubs/sp/800/31/final
Supports
- November 2001 IDS guidance and its enterprise integration scope
- https://suricata.io/timeline/
Supports
- First code in 2007 and OISF formation with Suricata 1.0 release in 2010
- https://zeek.org/2018/10/renaming-the-bro-project/
Supports
- October 2018 adoption of the Zeek name and continuity with the Bro project
