Each administrative action is recorded with the person, the area it touched, what they did and when, so your team can reconstruct who did what at any point.
Audit
An audit trail you can prove, and access you can account for.
A verifiable activity log, checkpoints kept outside your deployment, and scheduled reviews of who still needs their access.
Audit log
An audit log whose integrity you can verify.
Every meaningful action in OneView is written to a chained log, and the integrity of the whole record is checked for you.
Search by person, area, or activity, then narrow by action, outcome (success, failure, or denied), and source, such as the browser, a service account, or the application itself.
Users with export permission can download the filtered log as a CSV, and every person can review their own activity from their account page.
Versioning and history
Every saved change becomes a version you can look back on.
Where a setting or rule shapes your compliance decisions, OneView keeps each change as its own version instead of overwriting the last one, so you can see what was in force at any point in time.
Branding
Every branding change is kept in a history, and an earlier version can be restored when you need it.
Recovery objectives
Every save is a new version with its rationale. Earlier versions are never edited, only superseded.
Business type ratings
Each published rating is a numbered version with its written reason, so you know which rating was in force and when.
Customer KYC workflows
Workflows are versioned per customer type and risk level, with a history of changes your team can review.
Transaction monitoring rules
Rule edits and status changes are recorded in each rule's own history, so a detection change can be traced.
Alert review standards
Changes to the review standard are kept as a history rather than overwritten.
External audit trail anchoring
Keep proof of your audit trail outside your own deployment.
A chained log protects against edits to single events. Anchoring adds an independent copy of the log's state, so even a consistent rewrite of the whole chain can be caught.
- 01
Signed checkpoints
Each checkpoint records the current head of your audit chain and is signed by your own installation. It is sent every day, or on demand with Anchor now.
- 02
A copy your administrators do not control
Send checkpoints to a secure web address you operate, or to an independent timestamping authority. A later rewrite of the log no longer matches what was recorded outside.
- 03
Test, verify, retry
Test a destination before relying on it, verify every stored checkpoint against the live log, and retry deliveries that failed. A failing destination never blocks logging.
- 04
A full history
See every checkpoint sent, when it was delivered, and what the destination answered, kept alongside the audit trail itself.
User access review
Check, at regular intervals, that access is still right.
Who has access should not be set once at onboarding and forgotten. Run a structured review on a schedule, get a reminder when due and keep the proof that you did.
- 01
Start a review
Starting a review collects a snapshot of every user's permissions and roles as they stand today. Later role changes do not alter the snapshot.
- 02
Decide on each person
As you review each person, OneView shows any conflicts in the permissions they hold, such as someone who can both raise a case and decide it, with a plain explanation of why that combination matters.
- 03
Close it with a record
A review closes once every person has a decision, and the full decision record stays behind it. Export it to CSV for your files or an auditor.
Set how often reviews should run, and a reminder appears when one is due. Reviewers cannot decide on their own access, unless they are the only eligible reviewer, and that is recorded in the review.
Start a conversation
Request a demoGive your auditors something they can verify.
See the audit log, external checkpoints, and access reviews working together with our team.