UDP port 514 is classic syslog, where devices and servers send log messages to a central collector. Syslog over TLS uses TCP 6514. It should not be reachable from the public internet.
- Port
- 514
- Protocol
- UDP and TCP
- Service
- Syslog
- Expose to internet?
- No
- Also used by
- rsyslog, syslog-ng, network devices, SIEM collectors
Is port 514 safe to open?
Plain syslog has no authentication or encryption. Anyone who can reach the collector can inject fake log entries or flood it, and anyone on the path can read the logs. Logs often contain usernames, IP addresses and sometimes secrets.
How to secure Syslog
- Accept syslog only from known senders (rsyslog
$AllowedSenderor firewall rules). - Use TLS on TCP 6514 between sites.
- Never expose the collector to the internet.
- If the server does not collect logs, remove the
imudp/imtcpinput modules from rsyslog.
Check if port 514 is open
Linux: what is listening on this port
sudo ss -tulpn | grep ':514 'Windows (PowerShell): what is listening
Get-NetTCPConnection -LocalPort 514 -State Listen | Select-Object LocalAddress, OwningProcess, @{n='Process';e={(Get-Process -Id $_.OwningProcess).Name}}From another machine: is it reachable
nc -zv HOST 514
# or
nmap -p 514 HOST
# Windows
Test-NetConnection HOST -Port 514Restrict port 514 in the firewall
Replace 10.0.0.0/8 with the network or address that needs access. Docker publishes container ports through its own iptables rules, which bypass ufw; bind published ports to 127.0.0.1 (-p 127.0.0.1:514:514) instead of relying on the host firewall.
ufw: allow only your private network, deny everyone else
sudo ufw allow from 10.0.0.0/8 to any port 514 proto udp
sudo ufw deny 514/udpfirewalld: allow one source network only
sudo firewall-cmd --permanent --remove-port=514/udp
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="514" protocol="udp" accept'
sudo firewall-cmd --reloadiptables
sudo iptables -A INPUT -p udp --dport 514 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p udp --dport 514 -j DROPWindows Firewall (PowerShell, as Administrator)
New-NetFirewallRule -DisplayName "Block 514 from internet" -Direction Inbound -Protocol UDP -LocalPort 514 -RemoteAddress Internet -Action BlockMonitor port 514
Run a TCP port monitor against your public IP on port 514: here, a failed connection is the healthy result, so you know the firewall is still doing its job. On Linux, the Statance agent also reports every listening port on the server. TCP port monitoring.
Related ports
FAQ
What is port 514 used for?
UDP port 514 is classic syslog, where devices and servers send log messages to a central collector. Syslog over TLS uses TCP 6514. It is also used by rsyslog, syslog-ng, network devices, SIEM collectors.
Is it safe to open port 514?
Not to the public internet. Plain syslog has no authentication or encryption. Anyone who can reach the collector can inject fake log entries or flood it, and anyone on the path can read the logs. Logs often contain usernames, IP addresses and sometimes secrets.
Is port 514 TCP or UDP?
Syslog uses UDP and TCP on port 514.
How do I check if port 514 is open?
On the server, run sudo ss -tulpn | grep ':514 ' (Linux) or Get-NetTCPConnection -LocalPort 514 (Windows) to see what is listening. From another machine, run nc -zv HOST 514 or Test-NetConnection HOST -Port 514.
Know the moment a port stops answering.
TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.