Custodia Registry · V02
Audit and integrity
35 minutes. · 10 slides
Lesson video coming soon. The player below contains a sample video, not this lesson. You can use the written lesson and slide guide now.
Work through the lesson
Use these explanations alongside the slide guide. Expand any section to read its full explanation.
Your task and authority
- Confirm your assigned duties
- Use the fictional training case
- Verify the result and its history
Learning outcome
Learner preserves evidence and avoids claiming an unkeyed CSV hash proves independent authenticity.
Read the full explanation
Our audience is director, admin, specifically authorized audit/integrity reviewers. Before the demonstration, confirm these prerequisites: C01, C02; fictional training record and approved account. The action-level access conditions are: audit.view; integrity.view/manage separately; record_export for per-record export. Check the actual account and record state. The goal is not simply to find a button: Learner preserves evidence and avoids claiming an unkeyed CSV hash proves independent authenticity.
Find the known action
- Filter to a known fictional action and compare its record history.
What to check
Use the fictional actor, time and record to narrow the trail. Compare central audit and record history in context. An audit entry records an event; interpreting it still requires the workflow facts.
Read the full explanation
Filter to a known fictional action and compare its record history. Use the fictional actor, time and record to narrow the trail. Compare central audit and record history in context. An audit entry records an event; interpreting it still requires the workflow facts. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.
Preserve the export
- Download Verifiable CSV export and preserve the original.
What to check
Choose Verifiable CSV export and keep the original unchanged. A normal report CSV is not interchangeable. The verifier expects the inputs provided by the supported export format.
Read the full explanation
Download Verifiable CSV export and preserve the original. Choose Verifiable CSV export and keep the original unchanged. A normal report CSV is not interchangeable. The verifier expects the inputs provided by the supported export format. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.
Technical verification
- Have the approved technical trainer validate it with the provided verifier.
What to check
The approved technical trainer runs the supplied verifier on the fixture. Record the input and result. Legacy exports lack required verification inputs and must not be silently treated as equivalent.
Read the full explanation
Have the approved technical trainer validate it with the provided verifier. The approved technical trainer runs the supplied verifier on the fixture. Record the input and result. Legacy exports lack required verification inputs and must not be silently treated as equivalent. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.
Altered-copy comparison
- Verify a labelled altered copy fails without changing the original.
What to check
First establish that the original fixture passes. Then test a clearly labelled altered copy while retaining the original. Explain the observed difference without editing evidence to force an expected result.
Read the full explanation
Verify a labelled altered copy fails without changing the original. First establish that the original fixture passes. Then test a clearly labelled altered copy while retaining the original. Explain the observed difference without editing evidence to force an expected result. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.
Meaning of integrity
- Explain hash consistency versus digital signatures and review any integrity warnings.
What to check
An unkeyed consistency hash is not independent proof of authorship. Optional signed daily seals are a different mechanism. Review integrity warnings in context and keep private keys out of training material.
Read the full explanation
Explain hash consistency versus digital signatures and review any integrity warnings. An unkeyed consistency hash is not independent proof of authorship. Optional signed daily seals are a different mechanism. Review integrity warnings in context and keep private keys out of training material. As we work through this example, identify the record or account involved and point out the evidence that confirms this step. If the expected control or result is missing, pause and explain the condition before continuing.
Exceptions and recovery
- Identify the blocked condition
- Preserve the relevant evidence
- Use the authorized next step
Important boundary
Use commands/verify-audit-export.php only with approved fixture files/runtime. Legacy exports lack required verification inputs. Optional daily RSA seals differ from CSV consistency hashes; never copy private keys.
Read the full explanation
Consider the exception before deciding to retry. Use commands/verify-audit-export.php only with approved fixture files/runtime. Legacy exports lack required verification inputs. Optional daily RSA seals differ from CSV consistency hashes; never copy private keys. Explain what you expected and what was actually shown. Keep the record identifier and sanitized error context, then refer the issue to the person responsible for that decision. A missing or blocked control is not a reason to borrow a more powerful account.
Guided practice
- Work within the assigned role
- Show the resulting state
- Explain one exception
Your exercise
Compare supplied valid and altered CSV verification results. Explain why a consistent CSV hash alone does not prove independent authenticity.
Read the full explanation
Now use the approved fictional example. Compare supplied valid and altered CSV verification results. Explain why a consistent CSV hash alone does not prove independent authenticity. Explain the identity, current state and intended action before acting. At the end, show the evidence of the result and name the next responsible person if the workflow cannot proceed. Destructive actions and live external sends are discussed using prepared examples.
Practice debrief
- Correct identity and authority
- Traceable result and history
- A justified next step
Expected answer
The original is preserved, the supported format and verifier result are identified, and consistency, signatures and truth of the underlying event are kept distinct.
Read the full explanation
The answer should establish the following: The original is preserved, the supported format and verifier result are identified, and consistency, signatures and truth of the underlying event are kept distinct. Walk through the evidence in the same order as the workflow. Explain the specific boundary discussed in this lesson. If a result could not be established, report it as unverified and identify what would be needed to complete the task.