A ctlplne studio product
22 October 2026 · 3 min read

Proving a renewal happened

"Renewals are automated" is a claim. An auditor wants evidence, and evidence has a shape: a record of each step, an actor on each record, and a way to show nobody changed the record afterwards. Tickets do not have that shape. A system's own event log can.

Audit and ownershipRenewal automationSelf-hosting

The six questions

Strip any audit conversation about certificates down and it is six questions per certificate. Who requested it. Who approved it, if approval was required. What exactly was issued, by serial and fingerprint. Where it was deployed. When someone verified it was serving. And how you know the answers to the first five have not been altered since.

A chain of five audit records, each carrying the hash of the previous one, ending in a signed export anchored to the chain head requestedapprovedissueddeployedverified actor, time, tenantactor, time, tenantserial, fingerprinttarget, resultfingerprint seen h1h2h3h4 each record carries the hash of the one before it signed export records and chain head, signed change, drop, insert or reorder any record and every hash after it changes; verification names the first broken record.
The evidence is the state, not a report about the state.

What the record has to be

  • Complete. Every change to the system is an event, and the current inventory is a projection of those events, so there is no way for the record and the state to disagree.1
  • Attributed. Each event carries the authenticated actor and role, the time, and the tenant: who did what, when, under what authorization.1
  • Tamper-evident. Records are hash-linked. Altering, dropping, inserting or reordering any one changes its hash and every hash after it, and verification names the first broken record.1
  • Exportable and verifiable offline. A signed bundle of records plus the chain head, verifiable after a restart with a separately pinned key, so the auditor does not have to trust the running system to trust the evidence.1 In the commercial edition, with a timestamp authority enabled, each export also carries an RFC 3161 token over the chain head.2
  • Scoped. Every audit query is tenant-scoped, which for a service provider means a customer's evidence is theirs alone.1

The honest limit

A hash chain proves that a log is consistent with a point you signed earlier. It does not, by itself, prove nothing was rewritten in the gap between two signed points. The model is only as strong as the cadence of your anchors: export nightly, keep the exports in write-once storage, and verify against them.2 A vendor who claims continuous, unconditional immutability without telling you where the anchors are is selling you the word.

What the auditor gets

For a framework review, the commercial edition can render the same log as a signed evidence pack over an explicit 90-day window, evaluated per control rather than treating "some audit data exists" as proof of an unrelated one.3 What the pack cannot do is replace the operator's own responsibilities, and the documentation lists those separately rather than implying the software covers them.4

trstctl's audit subsystem is the design above: event-sourced state in an append-only log, an application-level hash chain, signed exports, an offline verification command, an optional timestamp and evidence packs across fifteen frameworks in the commercial edition, and a written trust model that says what it does and does not prove.1,2,3

Sources

  1. trstctl documentation, Compliance, "What the audit subsystem provides": completeness, attribution, tamper-evidence, signed offline-verifiable export, tenant isolation.
  2. trstctl documentation, Compliance, "The tamper-evidence trust model": the append-only log, the hash chain and anchors, the RFC 3161 token, and the need for scheduled exports to write-once storage; IETF, RFC 3161.
  3. trstctl documentation, Compliance, "Framework evidence packs".
  4. trstctl documentation, Compliance, "What the operator must still do" and "Framework mapping".