OCSP Stapling and Must-Staple
What you'll learn: How servers can improve performance and privacy by delivering revocation status themselves, and how policies can enforce this practice.
The Problem with Traditional OCSP
When you learned about OCSP, you saw that clients contact the CA's OCSP responder directly to check certificate status. This creates two issues: latency (waiting for a third-party response slows connections) and privacy (the CA learns which sites you're visiting).
How OCSP Stapling Works
OCSP stapling shifts the responsibility from client to server. Here's the flow:
- The server periodically queries the OCSP responder and receives a signed, time-stamped response
- During the TLS handshake, the server "staples" (attaches) this OCSP response to its certificate
- The client receives both certificate and revocation status in one round-trip
Analogy: Instead of a bouncer calling security to verify every guest's ID (traditional OCSP), the bouncer shows a recent stamped approval from security headquarters that says "this venue is legitimate" (stapling).
Benefits of Stapling
- Performance: Eliminates separate OCSP queries
- Privacy: Client never contacts the CA directly
- Reliability: Works even if OCSP responder is temporarily down
Must-Staple Policy
The must-staple certificate extension tells clients: "Don't trust me unless the server includes an OCSP response." If a server with a must-staple certificate fails to staple, the connection must fail.
This prevents servers from exploiting soft-fail scenarios where missing OCSP responses are ignored (allowing potentially revoked certificates to work).
Key Takeaway: OCSP stapling moves revocation checking to servers for better performance and privacy, while must-staple enforces this behavior by rejecting connections without stapled responses.