Port 500/udp: IKE / ISAKMP (IPsec Key Exchange)
Category: Network Infrastructure. Range: well-known. Status: iana registered.
What runs here
The port used by IKE (Internet Key Exchange, built on the ISAKMP framework) to negotiate and establish the Security Associations that IPsec VPNs use to authenticate peers and derive encryption keys: the control-plane handshake that happens before any encrypted ESP traffic flows. IANA also lists a TCP registration for the same service name, That covers a documented but far less common fallback: RFC 8229/9329 define encapsulating IKE and IPsec entirely inside a single TCP connection when UDP negotiation isn't possible.
Why it matters
IKE/IPsec endpoints are exactly the kind of internet-facing 'front door' that shows up in external attack-surface reviews. VPN gateways are a well-established initial-access vector, and a DFIR analyst investigating a network intrusion should always confirm whether the organization has a site-to-site or remote-access IPsec VPN and whether its gateway has been patched for known IKE-implementation vulnerabilities. Because IKE negotiates the very keys that make subsequent traffic opaque, this handshake is also one of the few places metadata (peer identities, proposed algorithms) is visible at all to network monitoring.
Where you see it
Legitimately: site-to-site VPN tunnels and remote-access VPN clients establishing or rekeying IPsec Security Associations with a known peer/gateway. Anomalously/maliciously: IKE negotiation attempts from unrecognized source IPs against an internet-facing VPN gateway, or repeated failed negotiations consistent with scanning/fingerprinting the IKE implementation and version.
Related ports
- 4500/udp: IPsec NAT-Traversal (NAT-T)
- 1701/udp: L2TP (Layer 2 Tunneling Protocol)
- 1723/tcp: PPTP (Point-to-Point Tunneling Protocol)
ATT&CK techniques
- T1133: External Remote Services