Key Match or Trusted Identity?

About this interactive

Public key cryptography gives you a key pair: a private key the owner keeps and a public key anyone can have. If the public key unlocks something, you know it was locked with the matching private key. That is useful, and the lesson is careful about how far it goes: it shows the two keys belong together, and nothing more. The reason is that anybody can generate a key pair, and anybody can create a digital certificate, the file that carries the public key along with details such as its expiration date. An attacker can put yourbank.com in a certificate they made five minutes ago, and their public key will unlock their data perfectly. A certificate on its own is not enough for authenticity. Public key infrastructure adds what is missing: a trusted third party. A certificate authority that both you and the server trust validates the certificate, so you know the public key inside really belongs to who the certificate names. Your browser does this every time it shows the lock icon and "Certificate is valid", and the certificate's details name the CA that issued it. One question sorts every card. Has anyone you trust vouched for the certificate? If not, all you know is that the keys match. If a certificate authority you and the server both trust has validated it, you know who is on the other end. Public key cryptography is a component of PKI, but PKI is the bigger thing because it includes that third party.

What you'll learn

Decide whether a situation only shows that a public key matches a private key, or shows who the sender is because a certificate authority both sides trust has validated the certificate
Recognize that anyone can generate a key pair and a digital certificate, so public key cryptography alone does not prove identity; public key infrastructure adds the trusted third party that does

Aligned to

NIST 800-53

SC-17 Public Key Infrastructure Certificates

SC-12 Cryptographic Key Establishment and Management

NIST NICE

K1239 Knowledge of certificate management principles and practices

K1203 Knowledge of Public Key Infrastructure (PKI) libraries

K0698 Knowledge of cryptographic key management principles and practices

S0657 Skill in implementing Public Key Infrastructure (PKI) encryption

Cisco CCST Cybersecurity

1.4 Explain encryption methods and applications

CompTIA Tech+

6.6 Explain common uses of encryption

Key terms

Public Key Infrastructure: A framework of hardware, software, policies, and standards used to create, manage, and distribute digital certificates.
Public Key Cryptography: A cryptographic system that uses a mathematically linked public and private key pair to encrypt data and verify identity.
Certificate Authority: A trusted entity that issues digital certificates used to verify the identity of individuals, organizations, or devices.
Digital Certificate: An electronic document that uses a digital signature to bind a public key with an identity.
Third-Party Trust: A trust model in which a mutually trusted third party, such as a certificate authority, vouches for and extends trust to other entities.
Public Key: A cryptographic key that can be shared openly and is used to encrypt data or verify digital signatures.
Private Key: A secret cryptographic key used in asymmetric encryption to decrypt data or create digital signatures.

Topics

Public Key Infrastructure Digital Certificates Authenticity Interactive Streak Sort

About TechKnowSurge

TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.

Explore free tools and programs →