A systems engineer is implementing security controls for a enterprise API gateway that requires mutual TLS authentication. To optimize client connection speeds, the engineer wants to eliminate third-party real-time lookup latency during certificate revocation verification. Additionally, the engineer must request a new web server certificate following strict Public Key Infrastructure (PKI) enrollment best practices. Which of the following steps should the security engineer take to meet these requirements?
- Enable OCSP stapling on the server to provide clients with time-stamped, CA-signed certificate status responses during the initial handshake.Cevap
- BSubmit both the private key and the public key inside the Certificate Signing Request (CSR) file sent to the Certificate Authority for validation.
- Generate the key pair locally on the server hardware and send only the public key along with identification details inside the Certificate Signing Request (CSR).Cevap
- DEmbed symmetric encryption key certificates into the API gateway payload to accelerate asymmetric key exchange during connection establishment.
- EConfigure the web server to append digital signatures to standard HTTP GET request headers to guarantee connection integrity without encryption.
Cevap
The engineer should enable OCSP stapling on the server to provide cached revocation status responses during the TLS handshake, and generate the key pair locally to include only the public key in the Certificate Signing Request (CSR).
Enabling OCSP stapling offloads real-time revocation verification from the client to the server, significantly reducing handshake latency while keeping certificate status checks up to date. During certificate issuance, generating key pairs locally and submitting only the public key within the CSR maintains the strict secrecy of the server's private key.
Adım Adım Çözüm
Anahtar Kavram
Public Key Infrastructure (PKI) Certificate Enrollment and OCSP Stapling Mechanics
Tahmini Süre:1m 30s