Connect your Audit Tools
Audit tools hold findings and their remediation state — the closure evidence every framework asks for. TruSecure's audit connector pulls findings, schedules and remediation tracking, so closed means closed with evidence attached.
What the connector pulls
| Source system | What TruSecure pulls | Feeds governance |
|---|---|---|
| Audit findings | Findings, severity, affected controls | Risk Management · finding-driven entries |
| Remediation state | Actions, owners, due dates, closures | Evidence Automation · closure controls |
| Audit schedules | Planned and completed engagements | Governance workspace · audit-calendar view |
| Finding history | Recurrence, aging, past-due trends | Board Reporting · remediation metrics |
Evidence produced from Audit Tools data
One control test pulled from live Audit Tools state — not a manual export, not a screenshot, but a verified query result with provenance:
- Control tested
- Closed audit findings have closure evidence attached
- Audit source
- AuditBoard · 23 open findings YTD
- Test
- re-perform · closure records vs evidence links
- Sample
- 14 closed · 12 with evidence, 2 closed on assertion only
- Result
- fail · 2 reopened pending evidence, owners notified
- Evidence
- Audit API query · timestamped 2026-08-22T10:58:19Z
- Export
- sealed · sha256:7f1c...9e3b
Setup and scope model
- Read-only, scoped permission
Connector requires read-only access to findings and remediation records. No write permissions, no ability to close, reopen, or re-rate findings.
- Data filtered by entity
Engagements scoped to the entity context — your audits, your findings, your board's metrics.
- Continuous sync
Closure state refreshes with the audit tool; a finding reopened there reopens here.
Commercial packaging
Audit Tools connectors are part of the paid TruSecure Fabric subscription. The connector itself, the continuous sync, the evidence provenance tracking, and the mapping to NIS2, DORA, ISO 27001, SOC 2 and other frameworks are all included — no per-connector fees, no usage tiers. Pricing is scoped in the conversation, not a price list.
How integration works
A demo with your actual Audit Tools environment shown in preview mode — your data pulling into governance, feeding controls and evidence. Then a Resilience Sprint that configures the connector for production, scopes the entity context, and validates the first evidence pull. No self-serve checkout, no per-connector pricing.
TruSecure helps operationalize requirements and prepare evidence. Legal interpretation should be validated by qualified counsel.