Protocol ExplorerGuidesPricing

Security and Access Protocols: TLS, IPsec and Wi-Fi

Security happens at several layers. A protected Wi-Fi link, authenticated access decision, encrypted tunnel and validated HTTPS server solve different problems.

Published · Updated

Curated learning paths from Protocol Explorer · Editorial approach and simulation limits

This hub groups lessons about link protection, peer authentication, encrypted transport and network access policy. The category is a learning path; it does not imply that one mechanism replaces another.

Choose the protection boundary before the protocol

Security protocols protect different things. TLS protects an application channel between peers that authenticate according to the negotiated certificates and policy. IPsec applies protection to selected IP traffic, often after IKEv2 negotiates Security Associations. WireGuard maps peer keys to allowed IP prefixes. WPA3 protects a wireless link, while RADIUS commonly carries authentication and authorization decisions between a network access device and an identity service. These roles can be combined; one does not replace all the others.

Start by naming the threat boundary: a browser-to-server connection, traffic between network gateways, a remote peer tunnel, a Wi-Fi association, or a user’s permission to join a network. Then ask which identity is checked, what traffic is protected, where keys are stored, and what a successful exchange actually proves. RADIUS acceptance may authorize access without encrypting every later packet; encryption may protect a channel without deciding what an authenticated user may do.

For learning, begin with TLS if you want to inspect certificates and protected application channels. Move to IPsec or WireGuard for network-layer tunnels, then WPA3 and RADIUS for access at the wireless edge. Read the implementation’s policy and deployment documentation alongside the packet sequence; protocol names alone do not establish that access controls are correct.

Explore protocols in this topic

  • Captive Portal

    How network provisioning, the CAPPORT API and enforcement support public Wi-Fi access.

  • DNSSEC

    How signatures and a chain of trust help validate DNS data.

  • HTTPS

    How TLS protects HTTP and how the client validates server identity.

  • IPsec

    How IP-layer policy, directional Security Associations and ESP protect traffic.

  • RADIUS

    How an access device requests authentication and authorization decisions.

  • SSH

    How transport keys, host identity, user authentication and channels fit together.

  • TLS

    How a handshake establishes traffic keys and protects application data.

  • Wi-Fi

    How wireless association and link security differ from IP access.

  • WireGuard

    How peer keys and allowed IP ranges form an encrypted IP tunnel.

  • WPA3

    How personal and enterprise Wi-Fi security modes protect a wireless link.

Match the protection to the trust boundary

WPA3 protects a wireless link; TLS protects a channel between TLS endpoints; IPsec and WireGuard protect selected IP traffic; RADIUS carries access decisions; DNSSEC validates signed DNS data. Choosing the right lesson starts by identifying which party or path needs protection.

Authentication, encryption and authorization are distinct

Encryption can protect bytes without deciding what an authenticated user may access. A valid server certificate can identify a TLS endpoint without making its content safe. A RADIUS Access-Accept can authorize a session without guaranteeing that routing or DNS works.

Read the standard and the deployment policy together

The lesson pages cite the primary protocol specifications and describe their limits. Continue with the captive portal discovery guide or compare the network protocol hub.

Keep learning across layers