AppsSecurity & Compliance

Security & Compliance · topic

Audit and evidence

Every read and change of protected data is logged on a verified hash chain, every run keeps its history, and evidence can be sealed write-once with signed hashes.

Know who did what in Autessa: a tamper-evident data access log, history for every tool and agent run, a write-once evidence vault and append-only tables.

Start free
AutessaDB · Access Logall actionsSample
Every read, change and decrypt of protected data: who, when and from where.CHAIN VERIFIED
14:02:11DECRYPThr_data · row 418for Ana Diaz, using key HR data (owner Sam Lee)
14:01:58READhr_data · 41 rowsvia hr_data in Homebase, for Ana Diaz
13:47:20UPDATEvendors · row 77Priya N. · 203.0.113.24
13:12:05DELETEleads · row 1290via agent Lead Cleaner, for Ben Ortiz
prev 9c41…e2 → this 3b07…5d · payloadCanonical hashed into the chain

How it fits together

How does audit and evidence work in Autessa?

Audit in Autessa answers “who did what, with which data, and can you prove it?” The data access log covers every read and change of protected data on a verified hash chain, execution history covers every run, and the evidence vault seals records write-once with signed hashes.

IN THIS AREA

  • Tamper-evident data access log
  • History for tools, agents, triggers, jobs and webhooks
  • Write-once evidence seals with verify
  • Append-only tables for ledgers

In this area

Every audit and evidence feature

01Data access logAutessa includes a tamper-evident data access log: every read, decrypt and change of protected table data, with the person, the key, tool or app it went through, the IP and a verified hash chain.→02Execution historyEvery tool execution, agent and manager conversation, trigger firing, scheduled job run and inbound webhook call is recorded with its inputs and outputs, and each run says where it came from.→03Evidence vaultThe Autessa evidence vault seals records into write-once storage with a SHA-256 hash for every item and a signed manifest, locks COMPLIANCE seals until their retention date, and logs every view in a chain of custody.→04Append-only tablesAn append-only AutessaDB table accepts new rows and reads but rejects every update and delete for every caller, and the setting can be turned on but never off.→

Other areas

The rest of Autessa Security & Compliance

FAQ

Audit and evidence: questions

Does Autessa log reads, or only changes?

Both. READ and DECRYPT are logged alongside CREATE, UPDATE and DELETE.

Can I see exactly what an agent sent to a tool?

Yes. Agent history includes full message and tool logs, and tool history includes decrypted inputs and outputs.

Can a sealed record be changed later?

No. Files are written to write-once storage. COMPLIANCE seals are locked until their retention date, and verify shows any difference.

Can an admin edit a row in an append-only table?

No. Updates and deletes are rejected for all callers.

Audit and evidence, built in

Every read and change of protected data is logged on a verified hash chain, every run keeps its history, and evidence can be sealed write-once with signed hashes.

Start free

Reports, policies and questionnaires live on the Autessa Trust Center.

100% customizable, code and all

Make Autessa Security & Compliance fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours