How to close the SOC 2 audit logging control in Vanta
If Vanta is showing your audit logging or monitoring control as failing, needing evidence, or not automated, here's the fastest way to close it: generate an evidence bundle from AuditRails and upload it as a document, plus how to wire it up as an automated Custom Test if you want it to stay current without manual uploads.
What Vanta checks for this control
Vanta's automated tests continuously evaluate synced data against a control's requirements and surface pass or fail status to your auditor without manual screenshots. For a logging or monitoring control tied to SOC 2 CC7.2, that means proof that system activity, logins, access changes, configuration changes, is actually being logged and retained, not just that a logging tool exists. Without a native Vanta integration streaming that data automatically, the control stays open until you attach evidence yourself.
The fastest path: upload an evidence bundle
This works today with no new integration required. AuditRails' evidence bundle is a zip containing a PDF summary, an NDJSON export of the underlying events, and a manifest with SHA-256 hashes, exactly the kind of document Vanta's manual evidence path accepts.
- 1
Generate a compliance report in AuditRails
From Compliance, Reports in your AuditRails dashboard, generate a SOC 2 report for the date range your auditor is reviewing.
- 2
Download the evidence bundle
Once the report is ready, download its evidence bundle: a zip with the PDF report, an NDJSON event export, and a manifest.json with SHA-256 hashes of each file plus the underlying hash-chain proof.
- 3
Add it as a document in Vanta
In Vanta, go to the relevant control, or the Documents page, choose to add a document, and upload the zip or its PDF summary. Vanta lets a single uploaded document map to multiple controls or frameworks at once.
- 4
Mark the control complete
Once the document is attached, mark the control as satisfied. Repeat each audit period, or move to the automated path below if you want this to stop being a manual step.
If you want it fully automated
Vanta has a self-serve Developer Console for building a private Custom Test: you push structured evidence to a custom-resource endpoint using Vanta's API, define pass or fail logic for that data, and attach the resulting test to a control like CC7.2. Since AuditRails exposes the same underlying event data via its API, a team comfortable with a short integration project can wire AuditRails' data into a Vanta Custom Test so the control updates automatically instead of relying on periodic manual uploads. AuditRails doesn't currently ship this as a pre-built connector; the manual path above is the quicker route to close the control today.
Frequently asked questions
Why is my audit logging control showing as failing in Vanta?
Usually because Vanta has no automated integration streaming your logging data and no evidence has been manually attached yet. Uploading an AuditRails evidence bundle as a document, or building a Vanta Custom Test against AuditRails' API, both resolve this.
Does AuditRails have an official Vanta integration?
Not a pre-built one today. The manual evidence-bundle upload works immediately with no integration; a Custom Test built against AuditRails' API is possible for teams who want the control to update automatically.
What's actually in the AuditRails evidence bundle?
A PDF summary report, an NDJSON export of the underlying log events for the date range, and a manifest.json containing SHA-256 hashes of each file plus the hash-chain proof for that period, so the bundle's own integrity is checkable independently of AuditRails.
How often do I need to re-upload evidence to Vanta?
As often as your audit period requires, typically each time your auditor samples a new date range. If that cadence gets tedious, that's the point at which building a Custom Test against AuditRails' API to automate it usually becomes worth the engineering time.