Cryptography & PKI Language

Symmetric encryption (AES) uses one shared secret key for both encrypting and decrypting — fast, but both parties must already have the same key. Asymmetric encryption (RSA, ECC) uses a mathematically linked key pair: a public key (shared freely, used to encrypt or verify) and a private key (kept secret, used to decrypt or sign). Real systems combine both in "hybrid encryption" — asymmetric operations exchange a symmetric session key, then AES encrypts the actual data efficiently.

Core terms: ClientHello/ServerHello (the opening negotiation), cipher suite (the chosen combination of algorithms), Certificate/CertificateVerify (proving server identity), session key (the derived symmetric key for this connection), and forward secrecy (ephemeral keys that protect past traffic even if the long-term key is later compromised). Being able to narrate these steps in plain English is a common requirement in security engineering interviews and incident write-ups.

A "chain of trust" links a website's certificate (the leaf) up through one or more intermediate Certificate Authorities to a root CA that is pre-installed and trusted by browsers and operating systems. Each certificate in the chain is signed by the one above it — the root CA's certificate is self-signed and forms the anchor of trust. Browsers reject connections if any link in this chain cannot be verified.

"Deprecated" is the professional English term for "still technically functional, but no longer recommended and being phased out because a safer alternative exists." MD5 and SHA-1 are deprecated for security purposes specifically because practical collision attacks were demonstrated against them — attackers can construct two different inputs producing the same hash. SHA-256 and SHA-3 are the current recommended replacements.

A JWT (JSON Web Token) is header.payload.signature, all base64url-encoded — NOT encrypted. Anyone can decode and read the header and payload; the signature only guarantees the token hasn't been tampered with and was issued by someone holding the signing key. This distinction — "signed" vs. "encrypted" — is a common source of confusion and a frequent English vocabulary trap for developers new to authentication.

In practice the terms overlap, but "renewal" typically refers to extending an existing certificate's validity (sometimes with the same key), while "rotation" implies actively replacing the certificate (and often the key pair) on a schedule, usually via automation like cert-manager with an ACME-compatible CA. Modern best practice favours short-lived certificates with automated rotation over long-lived ones that are manually renewed.

Signing proves authenticity and integrity — "this message came from the holder of this private key and hasn't been altered" — using a private key to sign and a public key to verify. Encrypting provides confidentiality — "only the holder of the matching private key can read this" — using a public key to encrypt and a private key to decrypt. The two operations use keys in opposite directions and solve different problems.

Useful phrasing for a post-mortem: "The certificate for api.example.com expired at 03:00 UTC because the automated renewal job failed silently three days earlier, and no alert was configured for certificates approaching their renewal window. Remediation: add expiry monitoring with a 14-day alert threshold, and add a renewal-failure alert to the automation pipeline." Precise, blameless, and action-oriented language is expected in incident communication.

Know the four main grant types (Authorization Code + PKCE, Client Credentials, Device Flow, and the deprecated Implicit grant) and be able to say which client type each fits: browser/mobile apps use Authorization Code + PKCE; service-to-service calls use Client Credentials; limited-input devices use Device Flow. Also know access token vs. refresh token, and scopes (the specific permissions a token grants).

An HSM is a dedicated, tamper-resistant hardware device that generates and stores private keys so they can never be extracted in plaintext — all cryptographic operations happen inside the device itself. HSMs are used to protect the most sensitive keys, such as a root Certificate Authority's private key, often requiring a formal "key ceremony" with multiple authorised custodians present (a "quorum") to perform sensitive operations.

Short lifetimes limit the "blast radius" if a key or token is ever stolen — a leaked JWT valid for 15 minutes is far less damaging than one valid for a week, and a 90-day TLS certificate forces teams to build reliable renewal automation rather than relying on a "set once, forget for years" approach that tends to fail silently. This principle — favouring automated, frequent rotation over long validity periods — runs through TLS certificates, access tokens, and API keys alike.