Port 754Kerberos Slave Propagation
Port 754 is used by Kerberos version 5 to propagate database updates from a primary KDC (Key Distribution Center) to secondary or slave KDCs. This replication ensures all KDCs maintain consistent authentication credentials across the Kerberos realm, which is crucial for maintaining a unified and secure authentication environment..
- transport
- tcp
- in transit
- cleartext
- assignment
- unofficial
- risk
- 2/10
- lookups
- 7,595
single transport
payload readable on path
used by convention
safe
rank 672 of 993 · top 68%
1 other service is registered on port 754. compare all 2 →
Technical Details
what runs on :754Overview:
Port 754 serves the Kerberos 5 slave propagation service. It facilitates the secure replication of the principal database from the master KDC to one or multiple slave KDCs. This is essential for high availability and load balancing in environments relying on Kerberos for authentication.
Database Replication:
Replication over this port involves transferring updates, such as new user credentials or key changes, from the primary server. It commonly uses secure protocols over TCP, sometimes layered on a secure channel, but the port itself is not inherently encrypted.
Operational Context:
Typically, the propagation occurs periodically or on demand to synchronize all KDCs. Slave servers listen on port 754 for incoming updates, ensuring the distributed nature of Kerberos-based authentication remains cohesive and reliable.
Security Information
exposure of :754risk score
2/ 10safe
routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.
security averages 3.8 across 216 ports — this one sits 1.8 below.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
tcp
every listening transport is another surface to filter at the edge
security overview
Common Vulnerabilities:
- Unauthorized Access: Without proper access controls, attackers may impersonate slave servers or intercept replication data.
- Man-in-the-Middle (MITM): Since encryption isn't enforced inherently, attackers could intercept or tamper with replication traffic.
- Data Integrity Issues: Tampered propagation updates may introduce malicious principals or alter authentication data.
Common Mitigations:
- Encrypt Replication: Use secure channels like IPsec or SSH tunnels for database propagation.
- Strict Authentication: Ensure mutual authentication between master and slave KDCs using strong keys and ACLs.
- Network Segmentation: Restrict access to port 754 within trusted internal networks or VPNs.
- Logging and Monitoring: Audit replication activities and monitor for unusual update events.
- Keep Software Updated: Apply security patches to Kerberos services to protect against known vulnerabilities.
Related Ports
the 8 most looked-up other ports in security — 216 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :8881 | Atlasz Secure Server | TCP | Web Services | caution | 67.6k |
| :443 | HTTPS | TCPtls | Web Services | caution | 65.9k |
| :8291 | Winbox MikroTik Admin | TCP | Security | caution | 62.9k |
| :3268 | Microsoft Global Catalog (GC) | TCPUDP | Security | caution | 54.6k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :3128 | Squid Proxy HTTP | TCP | Web Services | caution | 45.8k |
| :8080 | HTTP Alternate | TCPtls | Web Services | caution | 44.9k |
| :7000 | Vuze HTTPS Tracker | TCPtls | Security | caution | 28.9k |
risk mix of the 8 listed
- caution100%
3 of 8 encrypted