nsm-ids-triage

Triages Suricata IDS alerts from packet captures with detection posture validation and Zeek session corroboration.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill nsm-ids-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nsm-ids-triage
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/nsm-ids-triage
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill nsm-ids-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A Suricata sensor that loaded zero signatures reports zero alerts, which looks identical to a clean capture. This Skill prevents false 'all clear' conclusions by exposing the detector's posture (ARMED, INERT, or UNKNOWN) alongside every alert list, so analysts know whether the detector actually inspected the traffic.

Core Features & Use Cases

  • Posture-aware alert triage: Every nsm_alerts response carries suricata_posture and signature counts, so an empty alert list is never mistaken for a clean verdict when the ruleset was never loaded.
  • Severity-filtered alert review: Query alerts with min_severity=2 for human-priority findings, then pull the unfiltered list while respecting truncated pagination flags.
  • Session corroboration: Pivot from any alert to full Zeek session context via nsm-session-pivot, turning a signature match into an investigable incident.
  • Use Case: Given a .pcap from a CML or GNS3 lab capture, run nsm_status to check ruleset age, update rules if needed, then triage alerts and pivot to sessions to determine whether known-bad traffic is present.

Quick Start

Ask the agent to triage Suricata IDS alerts in a specific pcap file and report the detector posture, signature count, and severity-filtered findings.

Frequently Asked Questions about nsm-ids-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage Suricata IDS alerts from a pcap file?

Run nsm_status to verify Docker and ruleset state, update rules with nsm_update_rules if none are loaded, then call nsm_alerts with min_severity=2 for priority findings and again unfiltered for the full picture. Pivot to sessions with nsm-session-pivot for context.

Why does Suricata report zero alerts on my capture?

Stock Suricata loads zero signatures, so zero alerts means the detector was off, not that traffic is clean. Check the suricata_posture field: INERT means no signatures were loaded and you must run nsm_update_rules before drawing conclusions.

Can this skill capture live network traffic or block threats?

No. The skill is strictly read-only and analyzes pcap or pcapng files already on disk. It cannot sniff interfaces, block traffic, or modify sensor configuration, and such actions must not be offered.

What does a Suricata invalid checksum alert mean?

A SURICATA TCPv4 invalid checksum alert usually indicates NIC checksum offloading in the capture, not an attack. It also signals Zeek would discard those packets, so cross-check the affected flows with nsm-session-pivot.

How does ruleset age affect IDS alert accuracy?

A stale ruleset cannot alert on signatures published after it was fetched. nsm_status reports ruleset_age_days, and the triage summary should quote it so findings reflect the detector's actual coverage window.