Server Name Indication
A TLS extension where the client names the host it wants in the first handshake message, so one IP address can serve certificates for many domains.
SNI is a claim made by the client, so egress rules that trust it alone can be bypassed.
In more detail
Without it the server would have to pick a certificate before knowing which site the client wanted. The name is sent in cleartext, so firewalls can filter HTTPS by domain without decrypting it, although Encrypted Client Hello can hide it. Nothing checks the name against the destination address, so an allowed name paired with an attacker's IP still passes a name-only rule.
Related terms
- TLS — The encryption that protects data travelling over a network, the S in HTTPS.
- ClientHello — The first message a TLS client sends, listing the versions and ciphers it supports and extensions such as the server name.
- Encrypted Client Hello — A TLS extension that encrypts the sensitive parts of the ClientHello, including the real server name.
- AWS Network Firewall — A managed AWS firewall placed inside a VPC that filters traffic with stateless and stateful rule groups, including domain allow lists.
- server.addContext() — The Node.js TLS server method that registers a certificate and key for a host name, chosen automatically when a client asks for that name through SNI.
- multi-tenancy — One running system serving several separate customers, called tenants, while keeping each one's data and settings apart.
Taught in
- Security Landing Zones & Centralized Egress Inspection — Cloud Security & DevSecOps Engineering
- TLS & HTTPS Encryption: Certificates & SNI Contexts — Node.js Internals & Backend Services
- Reverse Proxies And Load Balancers — Linux Foundation Certified System Administrator (LFCS) Exam Prep
- Git For Admins: Who Changed That, And How To Undo It — Linux Foundation Certified System Administrator (LFCS) Exam Prep
- SSL Certificates: Create, Inspect And Verify A Chain — Linux Foundation Certified System Administrator (LFCS) Exam Prep