A digital signature proves two things: who sent something, and that it wasn't changed along the way. PKI, public key infrastructure, is the system that makes everyone's public keys trustworthy.
Here's how they fit together.
How a digital signature works
The sender hashes the message, then encrypts that hash with their private key. That's the signature.
The receiver decrypts the signature with the sender's public key and hashes the message themselves. If the two hashes match, the message is authentic and unchanged.
What signatures give you
- Integrity: the message wasn't changed
- Authentication: it came from the key owner
- Non-repudiation: the sender can't credibly deny sending it
Where PKI comes in
How do you know a public key really belongs to who it says? A certificate. A certificate ties a public key to an identity, and it's signed by a trusted certificate authority (CA). If you trust the CA, you can trust the certificate.
Revoked certificates
Sometimes a certificate has to be cancelled before it expires, like when a private key gets stolen. There are two main ways to check:
- CRL (certificate revocation list): a list of revoked certificates the CA publishes
- OCSP: a real-time check that asks if one specific certificate is still good
Cheat sheet
- Sign with your private key, verify with your public key
- Signatures give integrity, authentication, and non-repudiation
- A certificate ties a public key to an identity
- A CA signs certificates so they can be trusted
- CRL = revocation list, OCSP = real-time check
Common questions
Which key creates a digital signature?
The sender's private key.
What is non-repudiation?
Proof that the sender can't credibly deny sending something, which digital signatures provide.
What is the difference between CRL and OCSP?
A CRL is a published list of revoked certificates. OCSP checks one certificate's status in real time.
Studying for Security+?
Security+ Practice Test 701 has 1,100 practice questions with clear explanations, so you know why every answer is right.