FortcroftIntroductions to endpoint, network and security-operations tools

Firewalls and network security

What is Suricata? An introduction to the Open Information Security Foundation's network security tool

By the Fortcroft editorial team · Published · Updated

Suricata is a security tool that processes untrusted network data. It is documented by the Open Information Security Foundation (OISF) and offers IPS/inline modes as well as a firewall mode. Because it reads raw network traffic, its documentation puts considerable emphasis on how to run it with limited privileges.

Tool
Suricata
Made by
Open Information Security Foundation
Official site
suricata.io
Category
Firewalls and network security

Who makes Suricata

Suricata is documented by the Open Information Security Foundation, abbreviated OISF. The foundation also provides the package repositories referred to in the installation guidance, including the OISF COPR repo.

The official website, https://suricata.io/, is linked below this article and is the place to find the project's current documentation.

Official website: suricata.io

What Suricata is for

Suricata is used to handle network data that cannot be trusted. It acquires traffic from the network, and that acquisition requires elevated system privileges. It needs low-level read access to network traffic and, when it runs as an IPS, write access as well.

Its documented operating modes include IPS/inline modes and a firewall mode. In inline operation the tool sits in the traffic path rather than only observing it, which is why write access is part of the requirements. The documentation includes guides for setting up IPS/inline mode on Linux and on Windows.

Who Suricata is for

The vendor does not state a target audience, so this page does not assign one. The material that is documented is operational: it speaks to people who install, configure and harden a network inspection tool on a host.

In practice that means administrators who must decide how much privilege to grant a process that reads network traffic, and who need to understand how Suricata behaves under Linux, Windows, Docker and Podman.

Notable capabilities

The documented capabilities centre on how Suricata is deployed and how its privileges are contained. The points below come from the OISF documentation.

  • Privilege dropping: Suricata can switch to a non-root user after startup, which limits the impact of a vulnerability in Suricata itself. This is currently supported only on Linux.
  • Configurable run-as identity: the run-as user and group can be set in the configuration file or on the command line.
  • Startup as root: Suricata is typically started as root so that it can access network interfaces and set capabilities before it switches to the configured user.
  • Non-root tooling: suricata-update and suricatasc can be run without root or sudo once permissions are set up.
  • Packaged installs: Suricata RPMs are available from the OISF COPR repo and the EPEL repo, and they come with the non-root setup already configured.
  • IPS/inline guides: the documentation covers setting up inline mode on both Linux and Windows.
  • Container isolation: Docker and Podman containers can be used to isolate Suricata from the host. Such containers need the net_admin, net_raw and sys_nice capabilities.
  • Supply chain awareness: the documentation warns that supply chain attacks, particularly around rule distribution, could target Suricata installations.

How Suricata fits firewalls and network security

Within firewalls and network security, Suricata sits at the point where traffic is inspected and, in inline modes, acted upon. Its IPS/inline modes and firewall mode place it in the same practical territory as other network controls, and the documentation treats the network-facing process as something that must itself be secured.

That framing is useful when planning a wider defensive stack of endpoint protection, EDR, firewalls, SIEM and threat intelligence. Network inspection covers traffic that endpoint tools may not see, while the host running Suricata becomes a component to be hardened like any other. The guidance on privilege dropping, containers and rule distribution reflects that.

One limit is worth noting for container planning. Suricata does not work with rootless Podman, because it must start with root privileges.

Frequently asked questions

What is Suricata used for?

Suricata is a security tool that processes untrusted network data. It has IPS/inline modes and a firewall mode, and it needs low-level read access to network traffic, plus write access when run as an IPS.

Who develops Suricata?

Suricata is documented by the Open Information Security Foundation (OISF). The foundation also provides the COPR repository that offers Suricata RPMs.

Can Suricata run without root privileges?

Suricata is typically started as root so it can access network interfaces and set capabilities. It can then drop to a non-root user, which is currently supported only on Linux. The run-as user and group are set in the configuration file or on the command line.

Does Suricata work in Docker or Podman?

Docker and Podman containers can be used to isolate Suricata from the host, and they need the net_admin, net_raw and sys_nice capabilities. Rootless Podman does not work because Suricata must start with root privileges.

Does Suricata support IPS mode on Windows?

The documentation includes guides for setting up IPS/inline mode on both Linux and Windows.

Sources. This introduction is based on the vendor's official pages, checked on 21 November 2026 (Asia/Dhaka):

Fortcroft is independent and is not affiliated with Open Information Security Foundation. Product names belong to their owners. Features change; confirm details on the official website.