A security engineer is troubleshooting intermittent connection timeouts and handshake failures reported by users accessing a high-security internal web application. Network logs indicate that client web browsers are attempting to query external Certificate Authority (CA) validation servers to verify the revocation status of the application's TLS certificate. However, client endpoints are on a strict zero-trust VLAN with no outbound internet access, causing the certificate status requests to block and eventually time out. Which of the following should the security engineer implement on the web server to resolve the validation failures while maintaining certificate status checking?
- Enable OCSP stapling on the web server so it periodically fetches and appends a time-stamped CA OCSP response during the TLS handshake.Answer
- BEmbed a Certificate Revocation List (CRL) distribution point directly into the Certificate Signing Request (CSR) before submitting it to the CA for signing.
- CConfigure HTTP Public Key Pinning (HPKP) using a pre-shared symmetric encryption key header to bypass CA validation entirely.
- DReplace the certificate with a digital signature using HMAC hashing to guarantee non-repudiation without requiring CA verification.
Answer
Enable OCSP stapling on the web server so it periodically fetches and appends a time-stamped CA OCSP response during the TLS handshake.
Enabling OCSP stapling resolves client-side outbound connectivity issues by offloading OCSP status checks to the web server. The web server periodically contacts the CA's OCSP responder, receives a digitally signed and timestamped status response, and appends ('staples') this proof directly into the TLS handshake (Server Hello). This allows restricted internal clients to verify certificate validity without direct access to external CA servers.
Step-by-Step Solution
Key Concept
OCSP Stapling (TLS Certificate Status Request Extension)