What is Public Key Infrastructure (PKI)?

What is Public Key Infrastructure (PKI)?

• A. A framework of roles, policies, and procedures to manage digital certificates and public-key cryptography
• B. A hardware device for securing keys
• C. A cloud-based password manager
• D. A protocol for secure email

Answer: (A)

Public Key Infrastructure is the framework that makes public-key cryptography usable in a trusted, scalable way. It defines the people, roles, and rules needed to issue, manage, distribute, and revoke digital certificates that link identities to public keys. Key pieces include certificate authorities that issue certificates, registration authorities that verify who you are before a certificate is issued, and directories or databases that store and publish certificates. It also covers how certificates are trusted (trust anchors), how their validity is checked (CRLs or OCSP), and the policies and procedures that govern key management (certificate policies and certification practice statements). This structure underpins secure communications and authentication in many protocols, such as TLS for websites and S/MIME for email. The other options don’t fit PKI because they describe specific tools or protocols rather than the overarching system. A hardware device for securing keys refers to an HSM or smart card, not the framework itself. A cloud-based password manager stores and autofills credentials, which is about password management, not certificate-based public-key infrastructure. A protocol for secure email describes a method for encrypting email but does not capture the full system of issuing and managing certificates that PKI provides; PKI can support secure email, but it’s the infrastructure that enables that capability.

Public Key Infrastructure is the framework that makes public-key cryptography usable in a trusted, scalable way. It defines the people, roles, and rules needed to issue, manage, distribute, and revoke digital certificates that link identities to public keys. Key pieces include certificate authorities that issue certificates, registration authorities that verify who you are before a certificate is issued, and directories or databases that store and publish certificates. It also covers how certificates are trusted (trust anchors), how their validity is checked (CRLs or OCSP), and the policies and procedures that govern key management (certificate policies and certification practice statements). This structure underpins secure communications and authentication in many protocols, such as TLS for websites and S/MIME for email.

The other options don’t fit PKI because they describe specific tools or protocols rather than the overarching system. A hardware device for securing keys refers to an HSM or smart card, not the framework itself. A cloud-based password manager stores and autofills credentials, which is about password management, not certificate-based public-key infrastructure. A protocol for secure email describes a method for encrypting email but does not capture the full system of issuing and managing certificates that PKI provides; PKI can support secure email, but it’s the infrastructure that enables that capability.