Suricata eve.json Alerts: Trace an Nmap Scan to the Rule
Replay a bounded scan with one explicit Suricata rule. Follow EVE alerts to packets, compare an empty-rule run, and explain a benign alert.
Replay a bounded scan with one explicit Suricata rule. Follow EVE alerts to packets, compare an empty-rule run, and explain a benign alert.
Build a known capture, process it with Zeek, and follow connection UIDs through DNS and HTTP results. Check the records against the packets.
Query one signed answer over four transports, test certificate identity and DoH paths, then carry a DNSSEC-bogus answer over verified TLS.
Change one digit in a signed parent DS, follow delv to the failed child key check, and tell a bogus chain from an unsigned delegation.
A trusted server can still reject its client. Reproduce three client-certificate failures, compare both sides of TLS, and verify recovery.
Keep the destination fixed while changing SNI, the expected hostname, and the chain. Verify each fault with strict OpenSSL checks.
Small requests pass while a 64 KiB upload stalls at a 1280-byte link. Restore Packet Too Big feedback and see how a cached PMTU hides the fault.
A captured SYN can still fail source validation before local delivery. Compare strict and loose checks, then fix the route and keep strict mode.
Reproduce a missing route, stopped listener, loopback binding, and later firewall drop. Choose the next check from the packet’s last known point.
Keep one session open while changing SNAT. Compare original and reply tuples, reproduce stale no-translation state, and repair one flow.
Follow one SYN through an allow and a later deny. Use a scoped nft trace, rule handles, and captures on both sides of an isolated Linux router.
Two MACs can answer for one IP while ping still works. Capture the duplicate, repair it, and test a Linux proxy that answers ARP but not DAD.