OCSP Stapling
What is OCSP Stapling?
A method for checking the revocation status of digital certificates that improves performance by having the server include the certificate status in the TLS handshake.
Frameworks that govern ocsp stapling
What the standards actually require on ocsp stapling
Requirements naming ocsp stapling across 2 standards, quoted from the control text.
Conforming TLSv1.2 implementations support the extensions the profile selects: renegotiation indication (RFC 5746), signalling of client-supported CA certificates through the Trusted CA extension, signalling of supported signature algorithms, stapling of OCSP...
iec-62351-power-systems-communication-security::3:7.5 · Part 3, 7.5: TLSv1.2 extensions (renegotiation indication, trusted CA, signature algorithms, OCSP stapling, server name indication, encrypt-then-MAC) →Implement cryptography + protocol security + PKI per O-RAN WG11 Security Requirements covering TLS + SSH + IPsec + certificate lifecycle.
ORANWG11-3 · Cryptography, TLS, SSH, IPsec, and PKI Lifecycle Management →Questions people ask about ocsp stapling
What is OCSP Stapling?
Why is OCSP Stapling important for compliance?
Which compliance frameworks address OCSP Stapling?
Where can I learn more about OCSP Stapling?
See how OCSP Stapling applies across compliance frameworks
Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.