Cryptography protects confidentiality and integrity — the maths behind secure communication and trust.
PKI & the Certificate Trust Flow
How your browser decides to trust a website and encrypt the connection.
Tap or hover a part to learn more.
The trusted issuer.
A trusted third party (e.g. DigiCert, Let's Encrypt) that verifies identities and signs certificates. Browsers ship with a list of trusted root CAs.
Check your understanding
1. What makes a server certificate trustworthy?
2. Which mechanism checks whether a certificate has been revoked?
The building blocks
- Symmetric encryption (one shared key, fast — AES) vs asymmetric (public/private key pair — RSA/ECC) for key exchange and signatures.
- Hashing (SHA-256) produces a fixed fingerprint to verify integrity — it's one-way, not encryption.
- Digital signatures prove authenticity and integrity; certificates and PKI bind a public key to an identity via a trusted Certificate Authority.
- TLS combines all of this to secure the web (HTTPS).
This connects to IAM and Windows PKI, and is core to Security+.
