Evidence

# A log entry is a starting point

Logs help explain what a system did. For an outside review, you also need to understand where the record came from, whether it changed and what it leaves out.

9 April 2026 · 3 min read

Updated 28 October 2026

[← All articles](/blog)

[Keep the logs](#useful)[Ask how the record was made](#questions)[Add an independent integrity check](#seal)[Separate integrity from truth](#limits)[Make the next review easier](#handover)[Sources and further reading](#sources)

## Keep the logs

Application logs are useful. They help teams find errors, reconstruct requests and understand reported outcomes. Their value depends on what was captured, how it was protected and whether it answers the question being asked.

The problem starts when a log line is asked to prove more than it contains. An entry saying action approved is not, by itself, a record of exactly what was approved and what later ran.

## Ask how the record was made

Who wrote the entry? Could the same system or operator later edit it? Which events are omitted? Were the clocks reliable? Can another record support the account?

Access controls, protected storage and corroborating records all matter. A plain export may be useful evidence, but an auditor still needs its context. Giving the spreadsheet a PDF cover page does not change its ancestry.

## Add an independent integrity check

A sealed record adds a digital signature over specified content. A reviewer with the compatible verifier and trusted public-key material can check whether that signed content still verifies.

Change a signed value and the check should fail. That means changes to the signed content can be detected. It is not an assurance that a file cannot be edited, copied or deleted.

## Separate integrity from truth

A signature does not prove that the system recorded the right thing in the first place. It does not prove that every event was captured, that a source identity was genuine or that a decision was fair.

For supported workflows, records can also carry the approval scope and submitted action so the relevant relationship can be reviewed. That still depends on the connected control, identity setup and evidence profile. State those dependencies.

## Make the next review easier

Available for evaluation in Enterprise. Athena keeps records from connected controls and seals evidence for independent checking. Use that alongside ordinary logs, system records and the context the review needs. Coming to hosted Athena.

Try a handover to someone who did not configure the workflow. Can they find the action, understand the permission, repeat the integrity checks and identify missing coverage? If they can, the record is doing useful work. If they need a forty-minute explanation of why the missing fields are probably fine, improve the record.

## Sources and further reading

Originally published 9 April 2026. Rewritten on 28 October 2026.

[Independent verification guide](/blog/offline-verification)

[NIST FIPS 204](https://csrc.nist.gov/pubs/fips/204/final)

Keep exploring

[Explore Athena](/athena)[Trust and verification](/trust)[All articles](/blog)
