A security administrator is setting up an automated deployment server that requires an enterprise-issued code-signing certificate from an internal Certificate Authority (CA). Which of the following procedures correctly follows Public Key Infrastructure (PKI) standards for generating and submitting a Certificate Signing Request (CSR)?
- Generate the public and private key pair locally on the deployment server, protect the private key on that server, and transmit only the CSR containing the public key to the CA for signing.Answer
- BGenerate the key pair and CSR directly on the Root CA server, then download both the signed certificate and the private key file to the deployment server over the network.
- CGenerate a single shared symmetric key on the deployment server, embed the symmetric key into the CSR payload, and transmit it to the CA for asymmetric validation.
- DGenerate an SHA-256 digest of the request file on the deployment server and submit only the hash value to the CA, relying on hashing alone to establish non-repudiation.
Answer
Generate the public and private key pair locally on the deployment server, protect the private key on that server, and transmit only the CSR containing the public key to the CA for signing.
In standard PKI workflows, the applicant system generates its own public/private key pair locally. The private key is securely retained, and only the public key along with identification data is packaged into the Certificate Signing Request (CSR) sent to the Certificate Authority. This prevents private key exposure during transmission.
Step-by-Step Solution
Key Concept
Public Key Infrastructure (PKI) Certificate Signing Request (CSR) Lifecycle Workflow