In insurance the audit trail is a regulatory expectation as much as an IT feature: the IDD, national conduct rules and every delegated authority agreement assume the MGA can show who bound a risk, who changed a rate, who approved a claim payment and who overrode a referral. DORA adds the expectation that access and changes to the systems themselves are logged.
A useful audit trail is structured (actor, action, entity, before/after, timestamp), exportable, and covers configuration as well as transactions.
On Soldek
Every event on Soldek — submissions, decisions, binds, endorsements, claims, invoices, product and rate changes, team and permission changes — is written to the tenant's activity log and is exportable at any time.
SecurityQuestions
- What should an insurance audit trail contain?
- At least: who (user), what (action and entity), when (timestamp), and the change (before and after values) for transactions and for configuration such as rates, rules and permissions; stored so that it cannot be edited and exportable for an auditor.