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

Automated client behavior

Syndu annotates all incoming traffic and extracts behavioral signals that help explain intent. This page defines the bot 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 patterns strongly suggest automation rather than a human-operated browser.
Read the definition → View live signal sections →

Definition

Canonical reference for bot behavior.
Catalog code
bot
Display name
Automated client behavior
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 clients whose request behavior is consistent with automated tooling (crawlers, scanners, scripted clients). Typical indicators include bursty request cadence, repetitive patterns, unusually broad traversal of endpoints in short windows, and other non-human navigation characteristics. This annotator is behavioral: it describes observed traffic dynamics and should not be treated as attribution of intent.

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 bot 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