In certificate-based authentication, which entity issues digital certificates to bind public keys to identities?

In certificate-based authentication, which entity issues digital certificates to bind public keys to identities?

• A. Digital certificates
• B. Certificate Authority
• C. Public Key
• D. Trust Anchor

Answer: (B)

The main idea is that a Certificate Authority is the trusted issuer responsible for binding a public key to a real-world identity by issuing and signing digital certificates. The CA validates the subject’s identity, confirms control of the key, and then issues a certificate that ties that identity to the public key. This certificate carries the subject’s identity, the public key, and validity dates, and it’s signed with the CA’s private key. Others can verify this signature using the CA’s public key, which is distributed as a trusted root in systems, forming a chain of trust. Digital certificates themselves are the issued artifacts, not the issuer. The public key is the cryptographic key being bound, not the entity that binds it. The trust anchor is the trusted root used to verify the CA’s signature, not the issuer of the certificates.

The main idea is that a Certificate Authority is the trusted issuer responsible for binding a public key to a real-world identity by issuing and signing digital certificates. The CA validates the subject’s identity, confirms control of the key, and then issues a certificate that ties that identity to the public key. This certificate carries the subject’s identity, the public key, and validity dates, and it’s signed with the CA’s private key. Others can verify this signature using the CA’s public key, which is distributed as a trusted root in systems, forming a chain of trust.

Digital certificates themselves are the issued artifacts, not the issuer. The public key is the cryptographic key being bound, not the entity that binds it. The trust anchor is the trusted root used to verify the CA’s signature, not the issuer of the certificates.