Skip to content

Suricata IDS

Network & host sensors. Network intrusion-detection alerts from a Suricata sensor.

Status: already running on your instance - nothing to connect

This is an on-box sensor, not an API integration. It runs on your dedicated instance, so there is no credential to create and no card to fill in. Tell us what you want it to watch and we enable and tune it for you - see Support.

Suricata does not use a vendor token. It is a network sensor that runs on infrastructure you control, so setup is about giving it traffic to watch rather than pasting a credential.

What SheerSight reads

SheerSight reads network intrusion-detection alerts from a Suricata sensor: signature matches on your traffic and hits against threat-intel indicators. That feed powers detections such as a high-severity IDS alert, a threat-intel indicator hit, and an alerts-per-host burst.

What you'll need

  • A place to give Suricata visibility into your traffic: a SPAN / mirror port or network tap on-premises, or cloud traffic mirroring (AWS Traffic Mirroring, Azure vTAP, or GCP Packet Mirroring).
  • Your dedicated instance enrolled.

How it connects

There is no API credential and nothing to paste. The Suricata sensor runs on your dedicated instance (or a sensor host you provide) and inspects the traffic you mirror to it. Rule content and threat intel are kept current for you.

To set it up:

  1. Tell us where the sensor should watch: the interface, mirror/tap, or cloud traffic-mirror target.
  2. We deploy and tune the Suricata sensor against that vantage point.
  3. Alerts begin flowing into the console.

Connect it in SheerSight

Nothing to connect. Suricata has no card fields, and it is not started through the connect flow. In Integrate -> Sources -> Suricata IDS you will see a note that the sensor runs on your dedicated instance. Contact us to enable it or to tune which interfaces and traffic it monitors.

Verify

  1. The Suricata source badge moves from not connected to live once the sensor is watching traffic.
  2. IDS alerts begin appearing, and matching detections start firing.

Troubleshooting

  • No alerts. Usually the sensor is not seeing traffic. Confirm the mirror / tap / traffic-mirror target is actually delivering packets to the sensor.
  • Too noisy or too quiet. Tell us and we tune the signatures and thresholds for your environment.

What SheerSight can and cannot do

Suricata observes traffic and raises alerts. It does not block, shape, or modify traffic in this deployment, and there is no credential into any of your systems. It only inspects mirrored traffic and reports.