How to fix: Certificate carries no embedded Certificate Transparency SCTs
The leaf certificate contains no embedded Signed Certificate Timestamp list extension. That extension is the most common way a certificate proves it was submitted to public Certificate Transparency logs.
Why it matters
Certificate Transparency is what makes a misissued certificate for your domain visible. A certificate that is never logged does not appear to any CT monitor, so a certificate issued for your name by a compromised or tricked CA can exist without anyone being able to notice it from the outside.
SCTs can also be delivered in the TLS handshake extension or inside a stapled OCSP response, so the absence of the embedded extension does not prove the certificate is unlogged. It does mean the most common and most portable delivery method is not in use, which in practice points to a private or internal CA that does not log at all. Either way, CT monitoring for your domains is worth having, because it catches misissuance by any public CA regardless of what your own certificate does.
How to fix it
- 1For a publicly trusted certificate, ask the CA to embed SCTs; every major public CA does so by default.
- 2Subscribe to a Certificate Transparency monitor for your domains so any newly logged certificate raises an alert.
- 3Publish a CAA record so only the CAs you intend can issue for the domain at all.
Code examples
Look for embedded SCTs
openssl s_client -connect example.com:443 </dev/null 2>/dev/null \
| openssl x509 -noout -text \
| grep -A3 -i "CT Precertificate SCTs"Restrict issuance with CAA
example.com. IN CAA 0 issue "letsencrypt.org"
example.com. IN CAA 0 issuewild ";"
example.com. IN CAA 0 iodef "mailto:[email protected]"References
Detected automatically by VulnRadar. The check id is tls-cert-no-embedded-sct, stable across every scan so you can filter or diff on it.
More tls checks
Questions
- How severe is Certificate carries no embedded Certificate Transparency SCTs?
- VulnRadar rates this info severity in the tls category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id tls-cert-no-embedded-sct, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Certificate carries no embedded Certificate Transparency SCTs map to?
- It maps to CWE-295. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.