Connect your Document Repositories
Policies live in repositories — versioned, permissioned, sometimes stale. TruSecure's repository connector pulls policy documents and their state, so 'our policies are current' is tested against the actual document store.
What the connector pulls
| Source system | What TruSecure pulls | Feeds governance |
|---|---|---|
| Policy documents | Current versions, owners, approval state | Policy Assistant · source of truth |
| Review dates | Last review, next due, overdue flags | Control Library · ISO policy controls |
| Permissions | Who can read, who can approve | Evidence Automation · publication controls |
| Evidence attachments | Linked artifacts, integrity state | Audit Trail · evidence chain |
Evidence produced from Document Repositories data
One control test pulled from live Document Repositories state — not a manual export, not a screenshot, but a verified query result with provenance:
- Control tested
- Policies reviewed within their stated cycle
- Repo source
- SharePoint · policy library, 14 documents
- Test
- re-perform · document metadata vs review schedule
- Sample
- 14 policies · 12 current, 2 past review date by 41/63 days
- Result
- fail · 2 reviews scheduled with owners and dates
- Evidence
- Graph API query · timestamped 2026-08-22T08:47:36Z
- Export
- sealed · sha256:9c5b...3d7e
Setup and scope model
- Read-only, scoped permission
Connector requires read-only access to designated libraries and metadata. No write permissions, no ability to edit, move, or delete documents.
- Data filtered by entity
Libraries scoped to the entity context; group policy stores credit each entity's own document set.
- Continuous sync
Overdue reviews surface the day they become overdue — the policy register is a live view, not an annual audit artifact.
Commercial packaging
Document Repositories 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 Document Repositories 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.