Audit Log

A tamper-proof record of every significant action taken in your Verabase account — who did what, when, and from where. Essential for compliance and troubleshooting.

Technical definition

An audit log is an append-only event store that records system events with actor identity, timestamp, action type, affected resource, before/after state, and source IP. Audit logs must be tamper-resistant (append-only, integrity-verified) and retained for a configurable period. They serve both security (detecting unauthorized access) and operational (debugging configuration changes) purposes.

How Verabase uses Audit Log

Verabase's audit log records every configuration change, login event, knowledge base modification, agent settings update, and data export. Logs are available in Settings → Security → Audit Log, with filters for actor, action type, and date range. Audit logs are retained for 1 year on Business plans and indefinitely on Enterprise plans. Logs include raw API payloads for complete forensic capability.

Why it matters for support teams

When something goes wrong — an AI agent starts giving wrong answers, a knowledge base article gets deleted, or a security incident occurs — the audit log tells you exactly what happened. For SOC 2 audits, auditors will ask for evidence that you track and review access logs. Without an audit log, you're flying blind.

Related terms

How Verabase Handles Self-Healing Knowledge

The standard industry approach relies on support agents manually flagging stale content and technical writers updating documentation weeks later. Verabase completely upends this model through an autonomous AI platform that identifies knowledge gaps the moment an AI agent encounters a question it cannot answer.

Rather than requiring manual intervention, our visual RAG engine drafts a proposed fix. It analyzes the context of the user's question, reviews your existing knowledge base for conflicts, and creates a clear, structured article or snippet. All you need to do is click 'Approve'. This ensures your AI agents continually get smarter over time without adding to your support team's workload.

Security First Architecture

Many legacy platforms bolt AI onto their existing infrastructure, creating potential data leaks between tenants or exposing sensitive internal documents to end-users. Verabase is built from the ground up with a Bring Your Own Key (BYOK) architecture, enterprise-grade access controls, and strict semantic boundaries. This means your private engineering documents never accidentally leak into customer-facing agent responses.