The cost to add a tenant audit export depends on the events included, filters, privacy rules, file size, evidence requirements, and who must approve or receive the result. Exporting a log safely is a separate workflow from viewing it.
Define the evidence and scope
List event types, actors, resources, date ranges, tenant boundary, filters, timestamps, outcomes, and correlation context. Explain what the export excludes and how the recipient interprets it.
Price access and redaction
Account for roles, approvals, sensitive fields, customer data, secrets, support access, and field-level redaction. Keep tenant boundaries enforced even when an administrator or integration requests a broad export.
Include generation and delivery controls
Estimate asynchronous jobs, progress, format, compression, signed links, expiry, notifications, retry, integrity evidence, and audit of the export itself. Large exports need a performance and queue plan.
The audit log retention checklist and data export expiration checklist cover source and file lifecycle.
Separate implementation from operations
Recurring work can include schema changes, redaction rules, retention, provider updates, export review, support reissues, and incident evidence. Ask who owns a request when the result contains unexpected or missing records.
Request an estimate with examples
Share event volume, users, roles, filters, formats, retention rules, integrations, and acceptance tests. Confirm whether migration, documentation, and staff training are included.
Audit exports exposing too much or not enough? Ask Vertinus to scope the evidence and access controls together.