Port 4500/udp: IPsec NAT-Traversal (NAT-T)
Category: Network Infrastructure. Range: registered. Status: iana registered.
What runs here
The port IKE/IPsec peers switch to when a NAT device is detected between them, encapsulating both the IKE negotiation and the resulting ESP-protected traffic inside UDP so it can survive NAT translation (plain ESP has no port number for NAT to rewrite, which otherwise breaks it). IANA lists both a TCP and UDP registration for 'ipsec-nat-t' on 4500, but the mechanism it names (UDP encapsulation to solve the NAT/ESP incompatibility) is inherently UDP-based per RFC 3948/RFC 7296.
Why it matters
Seeing 4500 alongside 500 is the normal signature of a remote-access or site-to-site IPsec VPN traversing NAT, which is the common case for most road-warrior and cloud-to-cloud VPN setups, so the same DFIR relevance as port 500 applies (VPN gateways as an initial-access surface), and an analyst should expect 4500 rather than raw ESP (IP protocol 50) whenever a NAT boundary is involved.
Where you see it
Legitimately: any IPsec VPN peer pair where one or both sides sit behind NAT, continuing negotiation and then carrying encapsulated ESP traffic over 4500 for the life of the tunnel. Anomalously/maliciously: unexpected 4500 traffic to/from a host that shouldn't be operating as a VPN endpoint, which can indicate an unauthorized tunnel or a compromised gateway being used to exfiltrate data inside what looks like routine VPN traffic.
Related ports
- 500/udp: IKE / ISAKMP (IPsec Key Exchange)
ATT&CK techniques
- T1133: External Remote Services