Certificate Transparency

Laurie, B., Langley, A., & Kasper, E. (2013). Certificate Transparency.

Type

Report

Intellectual base

Grey literature

Year

2013

DOI

10.17487/rfc6962

DOI registrant

RFC Editor

Link

https://www.rfc-editor.org/info/rfc6962/

Cited from

public_administration_policy

Cited by

3 citations across 3 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Certification
  • The structural remedy — certificate transparency logs that make every issued certificate publicly auditable — is a meta-layer watching the certifiers, the prime's recursive diagnosis applied as cure.

    This sourcePublic append-only (Merkle-tree) logs that make every issued certificate auditable — a meta-layer watching the certifiers against single-bad-CA failure.

    Supported in partVerified against the work's full text

    RFC 6962 describes public, append-only logs of issued certificates that let anyone audit CA activity; it frames this as mitigation, not a cure, and the 'recursive diagnosis' reading is the entry's own.

    “Certificate transparency aims to mitigate the problem of misissued certificates by providing publicly auditable, append-only, untrusted logs of all issued certificates.”

    Read by an automated reader; not a human review. How support was checked

Mechanisms

• Public-Key Certificate
  • The discipline that guards against this is Certificate Transparency — public, append-only logs of every issued certificate, so a subject can detect a rogue certificate for its own name even when no individual verifier could.

    This sourceSpecifies publicly auditable, append-only certificate logs that let domain owners detect misissuance.

• Transparency Log Monitoring
  • Certificate Transparency and the Sigstore Rekor signing log are the real-world instances of the append-only records this monitor watches.

    This sourceSpecifies Certificate Transparency logs as ever-growing append-only Merkle trees.

Verification

Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.

Does it back the claim? Read against the text for 1 of 3 citations: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.

Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Links previously used in the corpus

Before the registry existed this work was also linked 1 other way.

• https://doi.org/10.17487/RFC6962 ×2

Registry ID ref:85a1aa58505e · see in the full table