TruPoint
Book a discovery call
Book a discovery call
Discipline three · TruCompliance™

Show an auditor exactly where you stand.

TruCompliance collects evidence as the service runs, on systems we built and operate in Canada. When a client, an insurer or a regulator asks, the answer is already assembled.

Advisor and client reviewing evidence
Who asks
Your insurerAt renewal, in writing, with consequences.
Your enterprise clientsVendor reviews before they sign or renew.
Your regulatorPIPEDA, and sector rules on top of it.
What it delivers

Compliance is a reporting problem wearing a security costume.

The controls are usually achievable. What breaks is the ability to demonstrate they were running on a particular Tuesday eight months ago. That is a data collection problem, and it is solvable.

01

What frameworks does this map to?

SOC 2 and ISO 27001 structures, cyber-insurance questionnaires, and PIPEDA obligations. The evidence is the same; the mapping differs.

02

Do we need to be certified?

Not always. Many businesses need to be demonstrably in control without holding a certificate. Readiness has value on its own.

03

What is in TruPortal?

Control status, access reviews, backup test results, incident records and policy versions. It is what you hand to an auditor.

04

Who writes the policies?

We provide the structure and draft against how your business actually works. You approve them, and they are reviewed on a schedule rather than at renewal.

The platforms behind it

The systems that prove your compliance are systems we built and run in Canada.

Three platforms, operated by us in our own Canadian facilities. They are part of TruCompliance, not products you buy separately.

SIEM

Security event collection and correlation. When an endpoint is wiped, the record of what happened on it is already somewhere else.

ISMS platform

Policies, controls, risk register and review cycles in one place, mapped to the frameworks you are measured against.

TruPortal

Where you and your auditor look. Control status, evidence, access reviews and test results, current rather than compiled.

These platforms run on TruCloud™ infrastructure. They are branded and sold under TruCompliance, not as TruCloud products.

Evidence as a by-product, not a project.

The difference between continuous compliance and an annual scramble is when the evidence is collected.

The usual way
1An audit date is set
2Somebody chases screenshots
3Policies are written to match what happened
4Gaps are found late, under time pressure
5The evidence is stale the week after
With TruCompliance
1Controls are configured and monitored
2Evidence is collected as the service runs
3Policies live in the ISMS platform and are reviewed on a cycle
4Gaps surface the week they appear
5TruPortal is current on any day you open it
Our own position
SOC 2Our private clouds run in Type 2 audited data centres, which shortens your vendor review.
ISO 27001In progress for TruPoint. We will tell you where, not imply it is finished.
CanadaWhere the SIEM, the ISMS platform and TruPortal run.

Every business we assess has controls it cannot prove and evidence it cannot find. Both are fixable, and neither is a reflection on the team.

Watch the overviewTruCompliance, an overview (plays the video)1:30 · Play

Find out what you could prove today.

A gap assessment produces a written list: what is in place, what is missing, and what each item takes to close. You keep it regardless of what happens next.

Get a gap assessment
RelatedCyber insurance readiness →Canadian data residency →Guides and checklists →Latest readingVirtual CISO: Bridging the Cybersecurity Leadership Gap for Small and Mid-Sized BusinessesNovember 2026 · 4 min readBuilding an Ironclad Evidence Trail: Proving Compliance for Cyber Insurance and Regulatory ScrutinySeptember 2026 · 5 min readWhat does cyber insurance require from a small Canadian business?August 2026 · 8 min readAll “Compliance and insurance” articles →