SOC 2 Compliance: A Practical Guide

Posted on Oct 30, 2026 in IT policy

Team of business professionals working on laptops and tablets in a modern office environment

Image: fauxels via Pexels

If you’ve been in a meeting recently where someone mentioned “SOC 2” and you nodded along while quietly wondering what it actually means — you’re not alone. SOC 2 is one of those terms that sounds more complicated than it needs to be. Here’s a plain-English breakdown of what it is, who genuinely needs it, and how to approach it without it consuming your organisation whole.

What Is SOC 2?

SOC 2 (System and Organisation Controls 2) is an auditing framework developed by the American Institute of Certified Public Accountants (AICPA). It provides an independent assessment of how an organisation manages data security, availability, processing integrity, confidentiality, and privacy. The result is an attestation report — essentially a verified, third-party statement that your controls are what you say they are.

There are two types. A Type I report assesses whether your controls are designed appropriately at a point in time. A Type II report goes further — it evaluates whether those controls actually operated effectively over a defined period, typically six to twelve months. Type II carries significantly more weight.

Who Needs It — and Why It’s Becoming More Relevant

SOC 2 has historically been a voluntary framework, most common in SaaS and cloud services. But its relevance is growing. In September 2026, the U.S. Securities and Exchange Commission proposed sweeping updates to rules governing registered transfer agents, explicitly raising the question of whether independent assessments — including SOC 2 reports — should become a regulatory requirement for demonstrating cybersecurity and operational resilience. The comment period closed in early November 2026, and the outcome is being watched closely across the financial services sector internationally.

For New Zealand organisations, SOC 2 tends to come up in a few specific situations:

  • You supply services to enterprise or government clients overseas (particularly in the US or Australia) who ask for it during vendor due diligence
  • You hold sensitive client data — health records, legal files, financial information — and want a credible way to demonstrate your security posture
  • You’re growing and want to build trust with prospective clients at scale, without walking each one through your controls individually

How to Get There Without Losing Your Mind

The audit itself isn’t the hard part — the preparation is. Most organisations spend three to nine months getting ready before an auditor sets foot in the door. The key steps are:

  • Define your scope carefully. You don’t need to include every system. Narrow it to the services and infrastructure directly relevant to client data.
  • Document your controls. Auditors need evidence, not assertions. Policies, access logs, change management records, incident response procedures — all of it needs to exist and be current.
  • Close the gaps first. A readiness assessment before the formal audit helps you identify weaknesses without them appearing in the final report.
  • Choose the right auditor. They must be a licensed CPA firm. Quality and cost vary significantly — ask for references.

It’s also worth noting that SOC 2 and New Zealand’s own New Zealand Information Security Manual (NZISM) share significant common ground. If your organisation has already done serious work aligning to NZISM, you’re better placed for a SOC 2 audit than you might think.

If you’re unsure whether SOC 2 is the right fit for your organisation right now, our team is always happy to help you think it through.

Chris Drowley
General Manager, Resolve Technology

Outside the office, Chris runs a highly organised empire of model trains — where the schedules are always on time, unlike the real thing.

Leave a Reply