Audit trail

Every meaningful action across the platform is written to an audit trail that is tamper-evident: each entry is chained by hash to the one before it, so any later change or deletion breaks the chain and can be detected.

What is recorded

Sign-ins and the authentication method used, connection changes, findings triage, risk exceptions and who approved them, remediation requests, approvals and results, report generation, API calls, and configuration changes. Each entry carries the actor, the time, the tenant and the before/after where relevant.

Why it cannot be edited

The chain is enforced in the database. Even an administrator cannot quietly alter history: re-writing an entry would change its hash and break every entry after it. Verified-outcomes and evidence packs record a fingerprint into this chain, so an auditor can confirm a report has not been changed since it was produced.

Search and filter

Open the audit trail (CloudVision360: Admin → Audit log; ITOps360: Insights → Audit trail; AgentVision360: Admin → Settings → Audit trail; BackupVision360: Reports → Audit trail) and filter by actor, action type, resource, outcome or date range. This is the fastest way to answer “who changed this, and when”.

Export and forward

Export a filtered view to CSV, or forward audit events to your SIEM — Splunk or Microsoft Sentinel — so they live alongside the rest of your security logging. ITOps360 and AgentVision360 keep their own hash-chained trails with the same guarantees.