Public Key Infrastructure (PKI) is what lets Windows services prove their identity and encrypt traffic — from LDAPS to internal web servers and code signing.
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 chain of trust
A Certificate Authority (CA) issues certificates. Clients trust a certificate because it chains up to a root CA they already trust. In a Windows domain, an enterprise CA (Active Directory Certificate Services) can auto-enrol certificates to domain-joined machines.
Validation and revocation
When presented with a certificate, a client checks it's in date, matches the name, chains to a trusted root, and hasn't been revoked (via CRL or OCSP). A single failed check breaks trust.
Why it matters
Certificates secure LDAPS, HTTPS and many authentication flows, and PKI is a heavily-tested Security+ topic. Understanding trust and revocation is essential for both support and security roles.
