Connect your Backup and Disaster Recovery
Backups are a control that is only proven by restoration. TruSecure's backup connector pulls job outcomes and recovery-test results, so continuity evidence shows what was actually restored, when, and how long it took.
What the connector pulls
| Source system | What TruSecure pulls | Feeds governance |
|---|---|---|
| Backup jobs | Success, failure, duration, per system | Evidence Automation · backup-execution controls |
| Recovery tests | Restore exercises, scope, RTO achieved | Incident and Resilience Workflows · ISO 22301 alignment |
| Retention state | Copies, ages, immutability flags | Control Library · ransomware-resilience measures |
| Coverage map | Protected vs unprotected systems | Risk Management · continuity gaps |
Evidence produced from Backup and Disaster Recovery data
One control test pulled from live Backup and Disaster Recovery state — not a manual export, not a screenshot, but a verified query result with provenance:
- Control tested
- Critical systems restored in a test within RTO
- Backup source
- Veeam · 386 protected workloads
- Test
- re-perform · recovery-log review, Q3 exercise
- Sample
- 12 critical systems · 12 restored, 11 within RTO
- Result
- pass with exceptions · ERP restore at 1.4× RTO, documented
- Evidence
- Veeam API query · timestamped 2026-08-22T06:05:12Z
- Export
- sealed · sha256:f3b7...9e2a
Setup and scope model
- Read-only, scoped permission
Connector requires read-only access to job histories and restore logs. No write permissions, no ability to delete backups, alter retention, or trigger restores.
- Data filtered by entity
Jobs scoped to the entity's infrastructure. Group-shared backup estates keep each entity's continuity evidence separate.
- Continuous sync
Job outcomes land as they happen; a failed backup flags the control the morning after the job, not before the audit.
Commercial packaging
Backup and Disaster Recovery 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 Backup and Disaster Recovery 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.