Port 514/udp: Syslog
Category: Remote Management & Administration. Range: well-known. Status: iana registered.
What runs here
The standard log-transport protocol: a device or host sends log messages (originally the loosely structured BSD format, later formalized by RFC 5424) to a central collector. RFC 5426 defines the plain UDP transport, which is connectionless, unauthenticated, and unencrypted by design.
Why it matters
Most centralized logging and SIEM pipelines run on syslog over UDP, which makes it essential telemetry and simultaneously a spoofable, lossy one: with no source authentication, forged log entries can be injected to pollute or mislead an investigation, and because delivery is fire-and-forget UDP, messages can silently drop under load. Worth keeping in mind whenever a device "should have" logged an event and the collector has no record of it.
Where you see it
Legitimately: firewalls, switches, and servers forwarding logs to a SIEM or a syslog-ng/rsyslog collector. Anomalously/maliciously: log injection/spoofing via a forged UDP source address, flooding a collector to induce message loss, or an attacker altering a device's configured syslog destination to blind or redirect its logging.
What to look for
| Signal | What it means |
|---|---|
| Source/identity mismatch | A syslog message whose source IP doesn't match the hostname or device identity claimed in the message body is a spoofing indicator. |
| Unexplained log-volume drop | A sudden drop in log volume from a device that's otherwise still reachable is worth investigating as either lost UDP traffic or deliberate log tampering. |
Related ports
- 6514/tcp: Syslog over TLS