A network engineer is configuring digital certificate authentication for Cisco Identity Services Engine (ISE) and enterprise network infrastructure. To ensure proper certificate deployment and validation, the engineer must correctly identify the operational function of each Public Key Infrastructure (PKI) element. Match each PKI component on the left to its corresponding primary function on the right.
- Certificate Signing Request (CSR)Contains an entity's public key and identity details sent to an issuing authority to generate a signed certificate.
- Root Certificate Authority (CA) CertificateServes as the trusted anchor installed on client devices to validate the authenticity of issued server certificates.
- Subject Alternative Name (SAN)Allows multiple domain names or IP addresses to be secured by a single X.509 digital certificate.
- Online Certificate Status Protocol (OCSP)Enables real-time verification of an individual certificate's revocation status without downloading full revocation lists.
Answer
Certificate Signing Request (CSR) matches the description of containing public key and identity details sent to an issuing authority; Root CA Certificate matches serving as the trusted anchor on client devices; Subject Alternative Name (SAN) matches allowing multiple domain names or IP addresses on a single certificate; Online Certificate Status Protocol (OCSP) matches enabling real-time verification of certificate revocation status.
Each PKI component plays a distinct role in digital certificate lifecycle management and authentication: CSRs initiate certificate issuance by bundling public keys and subject identity; Root CA certificates establish client-side trust anchors; SAN extensions allow single certificates to cover multiple FQDNs/IPs; and OCSP provides real-time revocation checks.
Step-by-Step Solution
Key Concept
Public Key Infrastructure (PKI) components and certificate validation mechanisms in network access control