Cybernion
← Insights

United States

US Company Expanding to Australia: Cyber Compliance Guide

30 Aug 2026 · Updated 30 Aug 2026

A US company entering Australia meets a single national privacy law instead of the US patchwork, a specific security baseline in the Essential Eight, and a different government assurance path in IRAP rather than FedRAMP. The US control work carries across, but US certifications do not: FedRAMP, CMMC and SOC 2 are not accepted in place of Australian requirements. This guide sets out what actually applies and where to start.

Expanding into Australia is not a copy and paste of a US compliance program. The concepts are familiar, the instruments are different, and the biggest trap is assuming a US certification will be accepted here. This guide sets out what a US company will actually be asked for.

What cyber and privacy compliance does a US company need in Australia?

A US company operating in Australia faces obligations in three main areas: privacy, a security baseline, and, if it sells to government, a government assurance process. The specifics differ from the US even where the intent is the same.

For personal information, the Privacy Act and its Australian Privacy Principles apply, a single national law rather than the US mix of federal and state rules. For security, the ASD Essential Eight is the baseline that Australian government and many enterprises expect, often alongside ISO 27001 as the management system. If the company sells to Australian government, systems holding government information are assessed against the Information Security Manual through an IRAP assessment. And if it operates critical infrastructure, the Security of Critical Infrastructure Act may apply. The rest of this guide covers how each of these compares to what a US company already knows.

How does Australian privacy law compare to US privacy law?

The biggest structural difference is that Australia has one national privacy law, where the US has many. Instead of managing HIPAA for health, the CCPA for California, and a growing list of other state laws, a US company in Australia deals with the Privacy Act and its 13 Australian Privacy Principles, enforced by a single national regulator, the OAIC.

The coverage test is different too. The Privacy Act applies to most businesses with an annual turnover over 3 million dollars, plus specified others such as health service providers of any size. There is no CCPA style revenue or data volume threshold, and no HIPAA style covered entity model. The rights model differs as well: Australia focuses on how entities handle personal information rather than granting consumers a menu of transactional rights like the CCPA’s opt out of sale. One thing US companies should not underestimate is the penalty exposure. After the 2022 reforms, the maximum penalty for serious or repeated interferences with privacy reaches the greater of 50 million dollars, three times the benefit obtained, or 30% of adjusted turnover, which is in the same league as the largest US privacy penalties. The detailed comparisons are in CCPA vs the Australian Privacy Act and HIPAA vs Australian health privacy.

What does a US company need to sell to Australian government?

Selling to Australian government is where US and Australian requirements diverge most, and where US certifications are most often wrongly assumed to transfer. To sell to Australian government, a US company usually needs to meet the Essential Eight, commonly holds ISO 27001, and for systems holding government information, needs the system IRAP assessed against the Information Security Manual at the right classification.

US government credentials do not substitute for these. A FedRAMP authorization is not accepted for Australian government work, because Australia uses IRAP against the ISM, not FedRAMP. For defence, CMMC is not the Australian gate either, defence suppliers need Defence Industry Security Program membership, and the closer comparisons are in CMMC vs IRAP and FedRAMP vs IRAP within the IRAP guide. The good news is that the underlying controls overlap heavily: a system built to NIST 800-53 or 800-171 has done much of the technical work the ISM and Essential Eight require, as covered in NIST 800-171 vs the Essential Eight. So the technical investment carries across, but the Australian assessment still has to be done.

Does US compliance carry over to Australia?

Partly, and it is worth being precise about which parts. The controls carry over; the certifications do not. A US company arriving with a mature security program built for NIST, FedRAMP, HIPAA or SOC 2 has already implemented most of the technical controls Australian frameworks require, because they share the same foundations of access control, patching, multi-factor authentication and the like.

What does not carry over is the formal recognition. Australian government does not accept FedRAMP or CMMC in place of IRAP and DISP, and Australian privacy law is not satisfied by CCPA or HIPAA compliance. ISO 27001 and SOC 2, while useful and recognised as evidence of a security management system, do not by themselves meet Australian government requirements. The sensible way to think about it is that the US work gives a strong head start on the substance, while the Australian effort is mainly about re-evidencing that substance against Australian instruments and completing the Australian specific assessments. That reframing usually turns Australian compliance from a daunting fresh start into a manageable extension of what a company already has.

Where should a US company entering Australia start?

The first step is mapping what actually applies to the Australian operation: privacy under the Privacy Act, the Essential Eight as the security baseline, ISO 27001 where it is not already held, and IRAP where the plan is to sell to government. That scoping step prevents both under and over compliance.

Then reuse aggressively. Take the control work already done for the US frameworks, map it to the Essential Eight and, where relevant, the ISM, and identify the real gaps rather than rebuilding from scratch. Add the Australian specific pieces: the Privacy Act obligations, the Essential Eight maturity evidence, and the IRAP assessment where government work is involved. The single most valuable early move is to get local advice before assuming any US certification will be accepted, because that assumption is the most common and costly mistake US companies make entering the Australian market. Cybernion helps US companies through exactly this, the Australian side of the compliance picture, through IRAP assessment, Essential Eight and ISO 27001 advisory and assessment.

Frequently asked questions

What cyber and privacy compliance does a US company need in Australia?

A US company operating in Australia is typically subject to the Privacy Act and its Australian Privacy Principles for personal information, and is expected to meet the ASD Essential Eight as a security baseline, often alongside ISO 27001. If it sells to Australian government, systems holding government information are assessed against the Information Security Manual through IRAP. Critical infrastructure operators may also be caught by the Security of Critical Infrastructure Act.

Does US compliance like FedRAMP or SOC 2 carry over to Australia?

Not directly. FedRAMP authorization is not accepted for Australian government work, which uses IRAP assessment against the Information Security Manual instead. SOC 2 and ISO 27001 are recognised as evidence of a security management system and help, but do not by themselves satisfy Australian government requirements. The underlying controls carry across, so the technical work is not wasted, but the specific Australian assessments still have to be done.

How does Australian privacy law compare to US privacy law?

Australia has a single national privacy law, the Privacy Act, built on 13 principles and enforced by the OAIC, rather than the US patchwork of sector and state laws such as HIPAA and the CCPA. It applies to most businesses over 3 million dollars turnover, plus health providers of any size. Penalties are large after the 2022 reforms, reaching the greater of 50 million dollars, three times the benefit, or 30% of turnover.

What does a US company need to sell to Australian government?

To sell to Australian government, a US company usually needs to meet the ASD Essential Eight, often hold ISO 27001, and for systems holding government information, have the system IRAP assessed against the Information Security Manual at the right classification. Defence work also requires Defence Industry Security Program membership. FedRAMP and CMMC do not substitute for these, because Australia runs its own assessment regime.

Where should a US company entering Australia start?

Start by mapping what Australian obligations apply, privacy under the Privacy Act, the Essential Eight baseline, ISO 27001 if not already held, and IRAP if selling to government. Then reuse the control work already done for US frameworks such as NIST 800-53 or 800-171, which overlaps heavily, and add the Australian specific pieces. Engaging local expertise early avoids assuming US certifications will be accepted when they will not.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. Australian Privacy Principles, Office of the Australian Information Commissioner, 2026
  2. Essential Eight, Australian Signals Directorate, 2026
  3. Infosec Registered Assessors Program (IRAP), Australian Signals Directorate, 2026
  4. Security of Critical Infrastructure Act 2018, Federal Register of Legislation, 2026

Last updated: 30 August, 2026

Talk to us about your engagement

A scoped proposal within one business day.