A enterprise healthcare organization is deploying an S/MIME solution for secure email communications. The compliance team mandates that encrypted emails must remain recoverable by security auditors if an employee leaves the company. However, the legal team requires that digitally signed emails strictly maintain legal non-repudiation. Which of the following public key infrastructure (PKI) key management configurations should the security team implement to satisfy both requirements?
- Escrow the private key designated for email decryption on a secure server, while keeping the digital signature private key under the user's sole control on the local system without escrow.Answer
- BEscrow the digital signature private key on the central Certificate Authority to ensure signature evidence can be audited and reconstructed by compliance officers.
- CInstruct the Certificate Authority to generate the private signature key during Certificate Signing Request (CSR) creation and publish it via the Certificate Revocation List (CRL).
- DImplement symmetric key escrow on the Registration Authority to manage both email body decryption and signature verification.
Answer
Escrow the private key designated for email decryption on a secure server, while keeping the digital signature private key under the user's sole control on the local system without escrow.
In enterprise PKI environments, separating encryption certificates from digital signature certificates is standard practice. The private key used for decrypting S/MIME emails can be safely escrowed so that the organization can recover encrypted files and emails if needed. Conversely, the private key used for digital signatures must remain under the exclusive control of the owner and never be escrowed, preserving strict legal non-repudiation.
Step-by-Step Solution
Key Concept
Dual Key Pair Management and Key Escrow vs Non-Repudiation in PKI
Estimated Time:1m 30s