Is SOC 2 mandatory in Australia?
No. No Australian Act, regulator standard or government policy requires a SOC 2 report. It becomes a requirement through your customers: a procurement team asks for it, a security questionnaire treats it as the fastest answer, or a contract makes it a condition of renewal. Once it is written into a contract, it is an obligation you must keep meeting, usually with a fresh report every year.
Regulation does push the request down the supply chain. APRA’s CPS 234 requires banks, insurers and super funds to assess the information security capability of third parties that manage their information assets, and most accept either a SOC 2 report or an ISO 27001 certificate as the core evidence. See ISO 27001 for fintechs and suppliers to banks for how that assessment works.
Why Australian companies get asked for SOC 2
SOC 2 comes from the American Institute of CPAs. It became the default security report for US software buyers, and it travelled with them. Australian companies typically get asked when they:
- sell software or services to US customers
- sell to global enterprises whose procurement teams use US vendor-risk processes
- are raising capital from US investors, or preparing for an acquisition
- are SaaS businesses whose customers trust them with sensitive data
Local buyers, especially government and regulated industries, are more likely to ask for ISO 27001. If you sell into both markets, you may need both. Our ISO 27001 vs SOC 2 comparison covers which to do first.
Who can audit an Australian company
A SOC 2 report can only be issued by a licensed CPA firm, because it is an attestation engagement under AICPA standards. There is no requirement for you to be a US company, and many CPA firms audit Australian companies remotely, with walkthroughs over video and evidence shared through a portal or compliance platform. You engage the CPA firm directly.
Three roles are easy to confuse:
| Role | What they do | Can they issue the report? |
|---|---|---|
| CPA firm | Examines your controls and issues the SOC 2 report | Yes |
| Readiness consultant | Assesses gaps, designs controls, prepares evidence and supports you through the audit | No |
| Compliance platform | Collects evidence, monitors controls and gives the auditor access | No |
Some platforms advertise “getting SOC 2” through partner audit firms. That can work well, but the report still comes from the CPA firm, and choosing a firm your customers recognise is worth the time. The AICPA has publicly warned that SOC services should be evaluated carefully by both service organisations and CPA firms, so a report that looks cheap and fast deserves scrutiny.
Questions to ask a CPA firm
- Will the report be issued under AICPA attestation standards and called a SOC 2 report, or under an Australian or international assurance standard?
- Have our target customers accepted this firm’s reports before?
- Can fieldwork run remotely, and in Australian business hours?
- Do you work directly in our compliance platform, or do you need evidence exported?
- What period and report date can you commit to, and how far ahead do we need to book?
- Who will be on the engagement, and do they know our cloud stack?
The Australian equivalent: ASAE 3150
ASAE 3150, Assurance Engagements on Controls, is the Australian standard for assurance reports on controls, issued by the Auditing and Assurance Standards Board (AUASB). Australian audit and assurance firms use it to report on controls such as security and system reliability, against criteria the engagement defines, which can include the Trust Services Criteria. Its sibling, ASAE 3402, covers controls at service organisations relevant to customers’ financial reporting, the local counterpart to SOC 1.
An ASAE 3150 report is credible, and some Australian buyers and regulators know it well. It isn’t a SOC 2 report, even when it uses the same criteria. If a customer has asked for SOC 2 by name, check with them before choosing it.
| SOC 2 | ASAE 3150 report | ISO 27001 | |
|---|---|---|---|
| Standard set by | AICPA (US) | AUASB (Australia) | ISO/IEC (international) |
| Issued by | Licensed CPA firm | Australian assurance practitioner | Accredited certification body |
| Output | Attestation report, shared under NDA | Assurance report, usually restricted | Certificate anyone can verify |
| Best recognised by | US buyers and US-parent enterprises | Some Australian enterprises and regulated buyers | Australian government, enterprise, Asia, Europe |
ISO 27001 is a certification of your whole information security management system and is the standard most Australian and international buyers recognise. It’s often the better first choice for companies selling mainly in Australia, Europe or Asia. See is ISO 27001 mandatory in Australia?
Realistic timelines for an Australian company
A first SOC 2 runs in four phases: readiness, remediation, the report period, and the CPA firm’s fieldwork. A Type 1 looks at control design on a single date; a Type 2 tests operation across an observation period, usually three to twelve months. Our SOC 2 Type 1 vs Type 2 guide covers period lengths, bridge letters and when to skip Type 1.
| Phase | Type 1 | Type 2 |
|---|---|---|
| Readiness and remediation | As long as your gaps take to close | The same |
| Observation period | None: a single date | Usually 3 to 12 months |
| CPA firm fieldwork and report | A few weeks | A few weeks after the period ends |
| Afterwards | Plan the move to Type 2 | The next period starts straight away |
Three Australian-specific points affect the calendar:
- Time zones. Fieldwork with a US-based firm means early-morning or evening walkthroughs. Agree working hours at engagement, and expect slower turnaround on evidence requests.
- Booking lead time. CPA firms schedule fieldwork in advance, and busy periods fill up. Book the firm once your readiness work has a firm end date, not after.
- Renewal timing. Pick a period end that suits your customers’ renewal cycle and your own busy months, such as the end of the Australian financial year, then keep it so reports run back to back.
Choosing the Trust Services Criteria
Security is always in scope. Availability, Confidentiality, Processing Integrity and Privacy are optional, and each one adds controls and testing. Add only what your customers and contracts care about; our SOC 2 page explains when each one fits. Note that the Privacy criterion is not an assessment against the Australian Privacy Act; it’s a separate set of criteria. If privacy law is your real concern, see Australian cyber and privacy law changes.
Scoping points that catch Australian companies
- Cloud providers. Most Australian SaaS runs on AWS, Azure or Google Cloud, often in Sydney or Melbourne regions. These are subservice organisations; reports usually carve them out and rely on their own SOC 2 reports, and you must show how you monitor them.
- Offshore teams. Developers or support staff overseas are in scope if they touch the system. Onboarding, device and access controls must cover them too.
- Essential Eight work. MFA, patching, backups and application control give you strong evidence for several common criteria, but SOC 2 doesn’t reference the Essential Eight. Map the controls; don’t assume the maturity level carries over.
- Data residency promises. If your contracts promise Australian hosting, your system description and controls should show it.
What drives the cost
- Report type and period. A Type 2 involves more testing than a Type 1, and a longer period means more samples.
- Criteria in scope. Each optional criterion adds controls and audit work.
- Your systems. The number of applications, cloud environments and infrastructure providers the auditor must cover.
- Readiness. How much needs designing, writing and fixing before the audit starts.
- The CPA firm. Fees vary widely by firm, and so does how well each is recognised by your customers.
- Tooling. A compliance platform is a separate subscription, but it often reduces the effort of keeping Type 2 evidence flowing.
The same drivers shape ISO 27001 budgets; our ISO 27001 cost guide explains how to think about them.
The criteria are being revised
Current SOC 2 examinations use the 2017 Trust Services Criteria with the AICPA’s 2022 revised points of focus. In October 2026 the AICPA released an exposure draft of revised criteria, including new points of focus on AI and emerging technology, with comments due by 15 January 2027. As proposed, the new criteria would apply to engagements beginning on or after 31 December 2027, with early adoption allowed. If you start now, plan on the 2017 criteria and expect a mapping exercise later; well-designed controls carry over.
Doing SOC 2 and ISO 27001 together
The two overlap heavily: access control, change management, incident response, supplier management, risk assessment and monitoring are central to both. Designing controls once and mapping them to both means the second framework costs a fraction of the first, and one evidence process serves both audits. The comparison guide explains how to sequence them.
Getting started
- Ask the customer which report type and criteria they need, and by when. Get it in writing.
- Define the system: the product, infrastructure, people and suppliers in scope.
- Run a readiness assessment against those criteria.
- Close the gaps and set up evidence collection.
- Choose a CPA firm and agree the report date or observation period.
Readiness, remediation and audit coordination are the part we take on for clients, with one certified security expert from first call to report. See our SOC 2 service or book a free 30-minute consultation.
