TLS & Certificates

TLS (Transport Layer Security) is a cryptographic protocol used to secure network communication between clients and servers.

HTTPS is HTTP sent over TLS, which encrypts traffic and authenticates the server.

TLS protects data in transit from eavesdropping, tampering, and impersonation.

A certificate is a digital document that binds an identity to a public key.

A public key can be shared openly and is used to verify signatures or encrypt data.

A private key is kept secret and is used to decrypt or sign data.

Asymmetric cryptography uses a pair of keys: a public key and a private key.

Symmetric cryptography uses one shared secret key for both encryption and decryption.

Asymmetric encryption is slower and used for trust and key exchange. Symmetric encryption is faster and used for bulk data encryption.

TLS uses asymmetric cryptography to establish trust and exchange a session key, then symmetric cryptography for data transfer.

The TLS handshake is the process by which a client and server agree on encryption settings and establish a secure connection.

A server certificate proves the identity of the server and contains the public key used in the TLS handshake.

A certificate authority (CA) is a trusted entity that issues digital certificates.

A root CA is a trusted top-level certificate authority used as the foundation of trust in a certificate chain.

A certificate chain is the sequence of certificates from the server certificate up to a trusted root CA.

An intermediate certificate sits between the server certificate and the root certificate and helps distribute trust.

They reduce the risk of root key compromise and improve operational flexibility.

Certificate validation checks whether the certificate is trusted, not expired, and valid for the requested hostname.

Hostname validation confirms that the certificate is valid for the server name the client is trying to reach.

A SAN (Subject Alternative Name) certificate includes multiple valid hostnames for a single certificate.

A wildcard certificate can cover multiple subdomains under one domain, such as *.example.com.

A self-signed certificate is signed by itself instead of by a trusted certificate authority.

Because clients cannot trust them unless explicitly configured to do so.

A trust store is the set of certificates a system trusts as CAs.

A keystore is a container for private keys and certificates used by applications or services.

A truststore stores trusted CA certificates used to validate remote certificates.

PKI (Public Key Infrastructure) is the entire framework for issuing, managing, and validating digital certificates.

A certificate subject is the identity information encoded in the certificate, such as common name or organization.

The common name is a field in a certificate that traditionally identifies the certificate owner or hostname.

The issuer is the entity that signed the certificate, usually a CA.

A digital signature proves that data was signed by a private key and has not been modified.

A hash is a one-way function that produces a fixed-size digest of data for integrity checks.

Hashes help verify data integrity and support digital signatures.

A certificate expires at a predefined date, after which it should no longer be trusted.

Certificate renewal is the process of replacing an expiring certificate with a new one.

Certificate revocation invalidates a certificate before its expiration, often because it was compromised or no longer valid.

CRL (Certificate Revocation List) is a list of certificates that have been revoked by a CA.

OCSP (Online Certificate Status Protocol) allows clients to query a CA about the real-time revocation status of a certificate.

OCSP stapling allows the server to provide revocation status during the TLS handshake to reduce latency and improve privacy.

It happens when the certificate cannot be validated to a trusted root, or the chain is incomplete or expired.

Certificate pinning binds a client to a specific certificate or public key to reduce MITM risk.

A certificate mismatch happens when the hostname in the URL does not match the names in the certificate.

Authentication in TLS means verifying the identity of the server (and sometimes the client) using certificates.

Confidentiality means the contents of the communication are encrypted and not readable by attackers.

Integrity ensures that the message was not changed in transit.

A MITM (Man-in-the-Middle) attack intercepts traffic and pretends to be the intended endpoint.

It verifies the server identity and encrypts the channel so traffic cannot be read or altered without detection.

A TLS session is a negotiated secure connection between two endpoints.

A cipher suite defines the key exchange, encryption algorithm, and message authentication method used in TLS.

A cipher is an algorithm used to encrypt and decrypt data.

The record layer handles the encryption, fragmentation, and transmission of TLS data.

TLS alerts communicate warnings and errors during a TLS session.

It indicates a problem during the handshake, such as incompatible algorithms or rejected certificate validation.

X.509 is the standard format used for digital certificates, especially in TLS and PKI.

PEM is a text-based certificate format using ASCII-armored base64 content.

DER is a binary encoding for certificates and keys.

PKCS#12 is a common binary format for storing certificates and private keys, often used in Windows environments.

OpenSSL is a widely used toolkit for working with TLS, certificates, keys, and certificate authorities.

keytool is the Java tool used for generating and managing Java keystores and certificates.

The default HTTPS port is 443.

Port 8443 is a common alternative HTTPS port used by applications or reverse proxies.

Certificate issuance is the process by which a CA creates and signs a certificate.

Certificate enrollment is the process by which an entity requests and receives a certificate.

A CSR (Certificate Signing Request) is a request sent to a CA containing the public key and identity information.

Private key generation creates a secret key pair used for authentication or encryption.

Key strength refers to the cryptographic difficulty of breaking a key, such as 2048-bit or 4096-bit RSA.

RSA is an asymmetric algorithm widely used for key exchange and signatures.

ECDSA is an elliptic-curve-based digital signature algorithm commonly used in modern TLS.

Ed25519 is a modern, efficient signature algorithm widely used for SSH and some TLS applications.

ECDHE is an ephemeral Diffie-Hellman key exchange used in modern TLS to provide forward secrecy.

DH (Diffie-Hellman) is a key exchange algorithm that allows two parties to derive a shared secret without transmitting it.

Forward secrecy ensures past session keys remain protected even if a long-term key is later compromised.

An ephemeral key is generated for a single session and discarded afterward.

TLS version negotiation allows client and server to agree on the highest mutually supported protocol version.

Secure renegotiation prevents insecure or unsafe renegotiation of TLS sessions.

ALPN (Application-Layer Protocol Negotiation) negotiates protocols such as HTTP/1.1 or HTTP/2 during the TLS handshake.

SNI (Server Name Indication) allows the client to indicate which hostname it is connecting to during TLS setup.

SANs allow one certificate to cover multiple hostnames, which is common in modern deployments.

A SAN extension lists alternative names such as DNS names, IP addresses, or URIs.

A CA bundle is a group of trusted root and intermediate certificates used by clients or servers.

Clients need the chain to establish trust from the server certificate to a known root CA.

A trust anchor is a trusted root certificate or key used as the starting point for validating a certificate path.

A leaf certificate is the end-entity certificate presented by the server or client.

A private key passphrase encrypts the key file so it cannot be used without the passphrase.

A key pair is a public key and matching private key.

A certificate fingerprint is a hash of the certificate used for quick verification and comparison.

Certificate transparency makes public certificates visible in a public log to detect misissuance or tampering.

A CT log is a public log of issued certificates used in certificate transparency systems.

It helps detect spoofed or malicious certificates and improves public trust.

HSTS (HTTP Strict Transport Security) tells browsers to only connect to a site over HTTPS.

A downgrade attack tries to force clients to use an older or weaker protocol version.

Modern TLS implementations prevent insecure fallback and enforce secure protocols.

It may pin a public key or certificate hash to a trusted application configuration to prevent MITM attacks.

TOFU accepts the first observed certificate as trusted and warns on future changes.

Because it is vulnerable to malicious server impersonation on the first connection unless manually verified.

A certificate policy specifies how certificates are issued, validated, and used in a given environment.

A certificate profile defines the fields, extensions, and constraints for a certificate issuance process.

A key algorithm defines how a key pair is generated and used, such as RSA, ECDSA, or Ed25519.

Entropy is randomness used in key generation and cryptographic security.

Poor randomness can make keys predictable and drastically reduce security.

TLS 1.3 removed many legacy algorithms, simplified the handshake, and improved security and performance.

It is faster, simpler, and stronger than earlier TLS versions.

TLS 1.0 is an older protocol version with known weaknesses and limited modern support.

TLS 1.1 is also deprecated and should not be used in modern deployments.

TLS 1.2 is widely supported and still common but is being phased out in favor of TLS 1.3.

TLS 1.3 is the modern version with reduced handshake complexity and stronger defaults.

The client sends supported versions and parameters, the server selects them, and a series of key exchanges establishes secure session keys.

It reduces handshake round trips and removes many legacy cryptographic modes.

Zero-RTT allows the client to send early application data in a resumed connection without a full handshake.

It may replay data if not carefully handled, which is why it is limited in practice.

In TLS 1.3, the record layer is simplified and uses authenticated encryption with associated data.

AEAD (Authenticated Encryption with Associated Data) provides confidentiality and integrity simultaneously.

ChaCha20-Poly1305 is a modern AEAD cipher often used in TLS 1.3 for performance.

AES-GCM is a common AEAD cipher in modern TLS implementations.

The TLS key schedule derives session keys from the handshake secrets.

The master secret is the shared secret used to derive session keys in older TLS versions.

Resumption secret allows quick resumption of a TLS session without a full handshake.

Session resumption reuses an earlier TLS session instead of repeating the full handshake.

Ticket resumption allows the server to store session state and issue a ticket to the client.

PSK (Pre-Shared Key) is a shared secret used in some secure sessions, especially in TLS and related protocols.

The process includes generating a new CSR, obtaining a new certificate, deploying it, and removing the old one.

The lifecycle includes issuance, validation, renewal, revocation, and expiration.

Certificate automation is the process of issuing, deploying, and renewing certificates without manual intervention.

Because certificates expire and manual renewal is error-prone.

ACME (Automatic Certificate Management Environment) is a protocol used by certificate authorities to automate TLS certificate issuance and renewal.

Let’s Encrypt is a free, widely used CA that provides automated TLS certificate issuance via ACME.

A CSR generation tool creates the material that is sent to a CA for certificate issuance.

Certificate ordering refers to the sequence of certificates in a chain from leaf to root for correct validation.

Common formats include PKCS#1, PKCS#8, and PEM/DER encodings.

Key wrapping protects encryption keys when stored or transported.

A certificate bundle contains multiple certificates used together, usually leaf + intermediates.

It is the method by which clients know which CAs to trust, typically through OS/browser trust stores.

A root program is the set of trusted roots included in a platform or browser.

It is the set of policies and procedures for managing trust, issuance, and revocation across a PKI.

It defines requirements for validation, identity proofing, and issuance.

The key usage extension defines how a certificate’s public key may be used, such as signing or encryption.

Extended Key Usage (EKU) further constrains the purpose of the certificate, such as server auth or client auth.

Basic Constraints restrict whether a certificate is a CA and the maximum path length.

A CA constraint defines whether a certificate can sign other certificates.

They define how the certificate is intended to be used and how it should be validated.

The subject DN is the distinguished name identifying the entity that owns the certificate.

The issuer DN identifies the CA that signed the certificate.

A certificate serial number uniquely identifies the certificate issued by a CA.

The validity period is the time range when the certificate is considered valid.

A CA compromise means the CA’s private key or issuance process is compromised, which can lead to widespread trust loss.

Because certificates issued by a compromised CA may be trusted by clients globally.

Key escrow stores private keys with a trusted third party so they can be recovered in emergencies.

Because it increases the risk of unauthorized key access.

An HSM is a secure device used to generate, store, and protect cryptographic keys.

Key rotation is the process of replacing old keys with new ones to reduce exposure and support security hygiene.

It is the deployment of new certs and keys while preserving service uptime and smooth fallover.

It involves identifying compromised certs, revoking them, replacing them, and assessing exposure.

Chain of trust is the sequence by which trust is established from a leaf certificate to a root certificate.

Certificate caching avoids repeated and expensive certificate validation operations.

Session reuse allows a client to reconnect without doing a full handshake if the server supports resumption.

DANE binds DNS records to TLS certificates for stronger certificate verification.

DNSSEC secures DNS records and can be used alongside certificate validation for stronger identity proofing.

mTLS provides mutual identity verification by requiring both sides to present valid certificates.

It gives strong identity assurance and protects internal traffic from unauthorized access.

They often include short lifetimes, strong algorithms, HSM-backed keys, and rotation automation.

Static keys are long-lived; ephemeral keys are created for a single message or session.

It allows two parties to derive a shared secret without exposing it in transit.

It proves possession of a private key and binds that key to an identity.

It determines whether a certificate has been revoked before it is accepted.

It is the time taken by the service to answer revocation status checks and affects connection performance.

Freshness means the certificate is not expired and has valid issuance and revocation status.

Common causes include expired certs, hostname mismatch, missing intermediate chain, or untrusted roots.

It occurs when certificates are delivered in the wrong order, causing chain validation to fail.

Cookies over HTTPS with secure and HttpOnly flags reduce risk of interception or JavaScript access.

A TLS intercept proxy decrypts and re-encrypts traffic, often used in enterprise inspection environments.

They create a trust boundary and can break certificate validation unless properly managed.

A malicious certificate may be injected by an intercepting proxy or hostile network actor.

Encryption without trust does not guarantee you are talking to the intended server.

Browsers trust a predefined set of CAs and enforce certificate validation rules before accepting a site as secure.

A certificate may be issued to a single subdomain or a set of subdomains with SANs or wildcard coverage.

It occurs when the cert is valid but for a different hostname than the client is connecting to.

Client certificate authentication uses a certificate presented by the client to prove identity to the server.

Mutual TLS means both parties authenticate each other using certificates.

It is used to authenticate internal services or trusted clients with certificates instead of username/password.

It allows secure service-to-service communication in clusters and internal networks without per-request credentials.

PKCS#11 defines an API for cryptographic hardware tokens and HSM interaction.

It means the private key is securely stored and used by hardware, reducing compromise risk.

ECDSA is often more performant and smaller in key size; RSA is widely supported but bigger and slower for some workloads.

They provide strong security with shorter keys and efficient operations.

Future quantum computers may break widely used public-key systems like RSA and ECC, so post-quantum algorithms are being explored.

Hybrid schemes combine classical and post-quantum algorithms to provide transitional security.

It means a CT log may not include certain certificates for policy or operational reasons, which can affect trust.

An OID (Object Identifier) identifies a certificate policy and helps classify usage or compliance requirements.

X.509 v3 extensions add features such as SANs, key usage, EKU, and constraints.

It is the process of constructing the chain from the leaf certificate to a trust anchor, which can fail if intermediates are missing.

Path validation confirms the chain is valid, not expired, not revoked, and rooted in trusted trust anchors.

Because they need to verify the requestor controls the domain before issuing the certificate.

DNS validation confirms domain control by creating a DNS record that the CA checks.

HTTP validation confirms domain control by creating a token in a known HTTP endpoint.

TLS validation confirms domain control by establishing a TLS connection and receiving a challenge.

A challenge token is a random value a ACME or validation service checks to confirm control over a domain.

It includes CRL, OCSP, or newer mechanisms to check whether certificates are still valid before acceptance.

If revocation checks fail or are unavailable, clients may accept certificates that should no longer be trusted.

Preloading is the process of including a certificate or CA in a browser or operating system trust store to reduce validation friction.

TLS is not just encryption; it is the combination of secure algorithms, strong key management, certificate validation, and trust infrastructure that makes secure communication possible at internet scale.