Learn · TrustedAIGov® Enterprise Knowledge Platform
Informational Fresh jira_story: GOV-311

Lesson 2 of 3 — External evidence anchoring

Cryptographic Trust & Anchoring · Source: Jira Story GOV-311 (8 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Anchor snapshots externally for tamper-evident timestamps.

Why it matters

External anchoring proves when evidence existed, independent of us.

Where this lives

Runs in the Customer AI Governance platform (components: shared). Snapshots are anchored via RFC-3161 timestamping or a transparency log. Learn teaches this read-only.

Workflow

  1. Given a posture snapshot
  2. When it is anchored
  3. Then it is anchored via RFC-3161 timestamping or a transparency log

Worked example

A regulator asks how you prove a snapshot existed on a date without trusting your servers. What does this story provide?

External anchoring (RFC-3161 or a transparency log) — an independent, tamper-evident timestamp.

Acceptance criteria (authoritative — GOV-311)

Given a posture snapshot, when it is anchored, then it is anchored via RFC-3161 timestamping or a transparency log.

Common pitfalls

  • Relying only on internal timestamps that we could alter.

Knowledge check

  • Scenario: A regulator asks how you prove a snapshot existed on a date without trusting your servers. What does this story provide?
  • Look for: External anchoring (RFC-3161 or a transparency log) — an independent, tamper-evident timestamp.

Key concepts

  • external anchoring
  • RFC-3161
  • transparency log

For the AI Tutor

  • Summary: Anchor snapshots externally for tamper-evident timestamps.
  • When to use: teaching or answering questions about "external evidence anchoring".
  • When NOT to use: the signing of the artefact (that is GOV-310).
  • Key concepts: external anchoring, RFC-3161, transparency log.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-311's acceptance criterion.

  • Module: LEARN-MOD-010 (Cryptographic Trust & Anchoring)
  • Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
  • Next: LEARN-LSN-053
← PreviousNext →