[Back to blog](https://zsoftly.ca/blog)
 [Company](https://zsoftly.ca/blog/category/company)

# How We Are Getting Ready for an Independent SOC 2 Audit

We built the technical controls and the evidence pipeline for SOC 2 with open source Wazuh and our own automation, before buying any compliance platform. Here is what that gave us and what is still ahead.

Ditah Kumbong

CTO and Founder

November 15, 2026

5 min read

Share

![Preparing for independent audit. Building evidence with Wazuh and automation, with ZCP branding on a blue grid background.](https://zsoftly.ca/images/blog/2026/how-we-are-getting-ready-for-an-independent-soc-2-audit.webp)

Anyone who trusts us with their workloads should ask a simple question: how do you prove your security controls work? A SOC 2 Type 2 report from an independent auditor is the usual answer. We are working toward one. This post explains how we started, why we started with evidence instead of software, and what is still ahead.

## Start with evidence, not a subscription

Compliance platforms such as Vanta and Drata are a common first purchase for a company starting SOC 2. They track policies, staff tasks and auditor requests, and they connect to the systems you already run. We remain responsible for log retention, server patching and checking whether every host is reporting.

A Type 2 report tests whether controls operated across a whole observation period, often six to twelve months. If the logs from month two are gone, no dashboard bought later brings them back. So we built the part that has to run every day first, with tools we already operate: [Wazuh](https://wazuh.com/), an open source security platform, plus our own Ansible automation. We have not bought a compliance platform. That decision is still open.

## What we built

- One source of technical evidence. Our servers and staff devices run the Wazuh agent. Alerts and inventory from both of our sites land in one reporting view.
- Twelve dashboards mapped to the Trust Services Criteria. They cover access, vulnerabilities, configuration, file integrity, malware, threat triage, agent coverage, change, attack origins and leaked secrets. Each one names the criteria it supports and lives in Git.
- A “How to read this” panel on every dashboard. It says what period the numbers cover, what one unit counts, what normal noise looks like and what to act on.
- A locked monthly evidence pack. On the first of each month a job renders 11 of our 12 dashboards to PDF. Secrets Exposure is not yet in the scheduled pack. Nine event views cover the previous month. Two vulnerability views show the state on the day of the run. The job hashes each file and protects its object version under a seven-year S3 compliance lock. Privileged storage administration outside the S3 API remains a separate control. The pack is emailed to our operations and security teams.
- Retention past the audit window. Alerts stay searchable for 12 months and sit in locked cold storage for 18 more, the split in US federal memo M-21-31. Our security engineer restores a snapshot every quarter to prove the copies work.
- Extra signals in the same place. CrowdSec bans, anomaly detection on alert volume and failed logins, and a nightly secret scan all feed Wazuh.

![Wazuh vulnerability triage dashboard. A How to read this panel explains that most findings are in old kernel packages. Totals are masked.](https://zsoftly.ca/images/blog/2026/soc2-wazuh-vulnerability-triage.webp)

The vulnerability triage dashboard. The panel at the top explains the numbers before anyone reads them. Totals are masked for publication.

## What that bought us

Evidence is already accumulating. The first monthly pack is stored and locked. Every month from here adds another frozen record. When an auditor samples from the window, the records will exist because they were collected on a schedule, not assembled the week before.

We found our own gaps early. Building the pipeline exposed gaps in our retention, coverage and scheduled checks. Our alert data was set to expire after 180 days, shorter than a typical observation window. Our vulnerability view covered only one of our two sites. A nightly scan stopped running and nothing complained. Each one is now fixed in code or tracked as a review step.

The numbers stopped scaring people. Raw security totals look like a crisis. When we split our vulnerability findings, 69 percent sat in old kernel packages that were installed but not running. Our monthly patching now removes them, and the dashboard says so up front.

We will know what we need from a platform. Whatever we decide to buy, if anything, will sit on top of evidence that already works. We can judge a tool by the gaps it closes instead of the demo it gives.

![Wazuh attack origins map showing where alerts from public addresses come from, with addresses and totals masked.](https://zsoftly.ca/images/blog/2026/soc2-wazuh-attack-origins-map.webp)

The attack origins map. Addresses, host names and totals are masked for publication.

## What is still ahead

Wazuh gathers technical evidence. A SOC 2 audit also asks for evidence that needs people and process: approved policies, staff acknowledgements, onboarding checks, training records, vendor reviews, a risk register and answers to the auditor’s requests.

We run that work as nine tracked workstreams with written scope and acceptance criteria. A control matrix in Git will list every control with its owner, evidence source, frequency and retention. Our runbooks, postmortems and patching records already exist. The formal policy set, training records, vendor inventory and risk register are still being written.

After that come a readiness assessment, the choice of an independent auditor and the dates of the observation window. We will share how it goes.

## Read the full white paper

We wrote up the whole build, with masked screenshots of all twelve dashboards, the criteria mapping, the retention design and seven lessons from production: [SOC 2 Readiness and Compliance Evidence with Wazuh](https://zsoftly.ca/resources/whitepapers/soc2-evidence-with-wazuh/). It is a free download with no form.

Get SOC 2 audit-ready before you buy a compliance platform. [Talk to our engineers](https://zsoftly.ca/contact). Your first hour with our engineers is free.

## Related articles

Company

September 11, 2026

### [Email Security Needs an Owner](https://zsoftly.ca/blog/email-security-needs-an-owner)

Email security needs ownership, validated senders, and regular review of the controls that protect your domain, people, and payments.

Company

September 7, 2026

### [Prepaid, Postpaid, and Manual Billing on ZCP](https://zsoftly.ca/blog/payment-modes-on-zcp-prepaid-postpaid-manual)

What Prepaid, Postpaid, and Manual billing mean on ZCP, how each one works day to day, and how to pick the right one at signup.

Company

September 3, 2026

### [An Open Letter to Canadian Colleges, Universities, and Tech Boot Camps: Teach Students to Build Cloud, Not Only Consume It](https://zsoftly.ca/blog/open-letter-canadian-colleges-universities-teach-cloud-building)

Canadian cloud education should pair commercial-platform training with open infrastructure, practical labs, and vendor-independent operating skills.
