DigitalOcean Referral Badge
cloud1
cloud2
cloud3
cloud4
cloud5
cloud6
← Back to catalog
code fwprobe

Firewall probing

Syndu annotates all incoming traffic and extracts behavioral signals that help explain intent. This page defines the fwprobe signal — what it means, how to interpret it, and how it will later connect to live evidence across IPs, subnets, organizations, ISPs, countries, and cities.

Signal gist Traffic behavior suggests probing of access controls and protected surfaces.
Read the definition → View live signal sections →

Definition

Canonical reference for fwprobe behavior.
Catalog code
fwprobe
Display name
Firewall probing
How to read this signal
This annotator represents a behavioral pattern, not a claim of identity. It’s designed to help you understand why certain traffic looks suspicious, automated, probing, or exploit-oriented — and to support consistent reporting across the Syndu system.
Explanation
Flags patterns consistent with probing or mapping your firewall/policy surface: repeated hits on restricted endpoints, testing for differences in responses (403 vs 404 vs redirects), and attempts to infer what is blocked or protected. This annotator is about interaction with defense boundaries rather than payload injection specifically. Interpret alongside Never-200-like patterns, scan velocity, and your allow/deny decisions.

Live sections

These panels will be wired to real metrics, enrichment context, and drill-down links.
Signal footprint over time
Rolling volume, bursts, first/last seen, and time-window slices (e.g. last hour/day/week). This will help separate chronic background noise from active campaigns.
Coming next: time series + burst markers
Top affected entities
Links to the entities where fwprobe is most present: IPs, subnets, organizations/ASNs, ISPs, and geographies — with “why” context.
Coming next: entity leaderboards + drill-down
Enrichment context
How enrichment affects interpretation: known crawlers, monitored ranges, trusted scanners, or policy exceptions. This is where “benign but noisy” gets separated from “unknown and risky.”
Coming next: enrichment flags + allowlist context