An enterprise network administrator is configuring perimeter firewall rules to isolate an application subnet while enabling secure integration with centralized infrastructure services in the management zone. The application servers require three network communication capabilities:
1. Directory lookup services using StartTLS (explicit TLS negotiation over the standard directory port).
2. Centralized event logging using secure transport (Syslog over TLS according to RFC 5425).
3. Ticket-granting user authentication via Kerberos.
Which combination of transport protocols and destination port numbers must be permitted on the firewall to satisfy all three requirements?
- TCP 389 for LDAP StartTLS, TCP 6514 for Syslog over TLS, and TCP/UDP 88 for KerberosCevap
- BTCP 636 for LDAP StartTLS, UDP 6514 for Syslog over TLS, and TCP 88 for Kerberos
- CTCP 389 for LDAP StartTLS, UDP 514 for Syslog over TLS, and UDP 445 for Kerberos
- DTCP 636 for LDAP StartTLS, TCP 514 for Syslog over TLS, and TCP/UDP 389 for Kerberos
Cevap
TCP 389 for LDAP StartTLS, TCP 6514 for Syslog over TLS, and TCP/UDP 88 for Kerberos
The option specifying TCP 389 for LDAP StartTLS, TCP 6514 for Syslog over TLS, and TCP/UDP 88 for Kerberos is correct. StartTLS uses explicit TLS negotiation initiating over standard LDAP TCP port 389. Syslog over TLS (RFC 5425) is standardized to use TCP port 6514 for reliable encrypted log transmission. Kerberos authentication uses port 88 over both TCP and UDP.
Adım Adım Çözüm
Anahtar Kavram
Common Ports and Protocols