Audit and evidence
Data access log
The Autessa data access log records every READ, DECRYPT, CREATE, UPDATE and DELETE of protected data in your AutessaDB tables: when it happened, who it was for, the key, tool, agent or app it went through, the source IP and the request path. Entries sit on a tamper-evident hash chain, and every read of the log says whether the chain verified intact.
The problem
What problem does it solve?
When a regulator, a customer or your own incident review asks who looked at a record, “we don’t log reads” is the wrong answer. And a log that can be quietly edited is not evidence.
How it works
- 1
Open the Access Log
In AutessaDB, choose a table, or read it from the CLI.
- 2
Filter
By table, row, date range and action.
- 3
Open an entry
See the access event, subject, actor, on behalf of, request path and payload summary.
- 4
Trust the chain
Each read reports chainVerified. The page shows Chain verified, or Chain integrity issue.
Every option
Data access log: settings and options
| Setting | What it does |
|---|---|
| Actions | READ, DECRYPT, CREATE, UPDATE, DELETE. |
| Actor | The kind of actor (a user or an API key), its id and the user’s email. |
| Attribution | A one-line summary such as “via hr_data in Homebase, for Ana Diaz, using key HR data (owner Sam Lee)”. |
| Context | Source IP when captured, the endpoint path, and a canonical payload summary used in the chain. |
| Paging | 0-based pages, 25 per page by default, up to 100. |
Permissions
Who can do what?
| Who | What they can do |
|---|---|
| People with access to a table’s log | Read it in the app or the CLI. |
| Your company’s audit configuration | Decides whether the log is customer-visible; otherwise entries are withheld. |
FOR DEVELOPERS
What to know
- The log is returned only when your company’s audit configuration makes it customer-visible. The page says “Access logging is not enabled for your organization” otherwise; contact your administrator to enable it.
Connections
How Data access log connects to the rest of Autessa
Reports, policies and security questionnaires are on the Autessa Trust Center.
FAQ
Data access log: questions
Does Autessa log reads, or only changes?
Both. READ and DECRYPT are logged alongside CREATE, UPDATE and DELETE.
How do I know the log has not been altered?
Entries are hash-chained, and every read of the log reports whether the chain verified intact.
Can I tell which app or API key a read came through?
Yes. Each entry names the person it was for and the key (with its owner), tool, agent and app it went through.
Get started with Data access log
Autessa 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.
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