Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

SOC 2, IRAP and ISO 27001: how to read the assurance report a hosting buyer is handed

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A SOC 2 report, an IRAP assessment and an ISO 27001 certificate are three different kinds of document. A SOC 2 report is a certified public accountant's (CPA's) written opinion on a provider's controls. An IRAP assessment is an independent assessment by an assessor endorsed by the Australian Signals Directorate (ASD). An ISO 27001 certificate is a statement from a certification body that a management system meets a standard. None of them says, on its face, that a provider is secure for your workload.

What each tells you depends on four things you can find in the document: who issued it, what period or date it covers, what services and sites it covers, and what is excluded or left to you. This guide shows where to find them. It does not cover data centre ratings, which are a separate topic.

Why it matters

A logo on a provider's website or a line in a proposal is easy to accept. The documents behind it are long, and the answer to 'does this cover the service I am buying?' is found in the scope, not in the title.

The AICPA, the body that sets the SOC 2 standard, says SOC reports "provide users with valuable information that is needed to assess and address the risks associated with outsourcing services" (AICPA & CIMA, SOC Suite of Services). The word to notice is "users". A report is a tool for the buyer's own risk assessment, and it needs reading, not filing.

SOC 2: Type 1 or Type 2, and which period

A SOC 2 report tests a provider's controls against the AICPA's Trust Services Criteria, which cover security, availability, processing integrity, confidentiality and privacy (AICPA, Trust Services Criteria; the criteria document itself sits behind a free account). Google Cloud explains the two report types plainly: "A SOC 2 Type I report covers the design of the service organization's controls at a specific point in time. A SOC 2 Type II report covers the design and operating effectiveness of the service organization's controls over a period of time" (Google Cloud, SOC 2).

The practical difference is this. A Type 1 report says controls were suitably designed on one date. A Type 2 report says they were designed and also operated, with the auditor's testing, across a stated period. For a buyer, Type 2 is the stronger evidence about how a provider actually runs, because it covers behaviour over time (our reading).

Next, check the period. AWS's published reports each cover a 12-month period: "Each report covers the previous 12 months" (AWS, SOC Compliance), and AWS says new reports are generally released about 9 to 10 weeks after the period ends. That means a report can be months old when you receive it. Google Cloud describes issuing monthly bridge letters, which are statements from management that cover the gap between the end of a report period and a later date. A bridge letter is the provider's own statement. It is not part of the auditor's testing (our reading of Google's description).

Ask: what dates does the report cover, and is there a bridge letter for the time since?

SOC 2: the scope and the system description

A SOC 2 report is about a described system, not about the provider as a whole. AWS says its SOC 2 report is "a description of the AWS controls environment and external audit of AWS controls", and that covered services and regions are listed separately (AWS, SOC Compliance). Google makes the same point in its own wording: customers may use the report to assess the risks from "the assessed Google Cloud and Google Workspace systems".

So before reading any finding, check:

  • Which services or platforms are in the described system. The service you are buying may not be among them.
  • Which Trust Services categories were selected. The AICPA's criteria list five categories. Microsoft notes that its Azure report is "relevant to trust services criteria for system security, availability, processing integrity, and confidentiality", which shows that categories vary between providers (Microsoft, SOC 2 Type 2). The AWS compliance guide says each organisation must pick the categories relevant to its services.
  • Which locations. Some reports list regions or sites; others do not.

SOC 2: carve-outs, controls expected of you, and exceptions

AICPA lists the topics a reader of a SOC 2 report should understand, including complementary user entity controls and "Inclusive versus carve-out methods of reporting on controls at subservice organizations" (AICPA & CIMA, SOC 2 Report Walkthrough). The AICPA pages we could read name these topics but do not define them. The explanations below are our understanding, and they should be checked against the report itself.

  • Complementary user entity controls (CUECs). AWS's SOC 2 compliance guide describes these as control activities that a provider expects its customers to carry out for the provider's controls to work, disclosed in the report, and not optional (AWS, SOC 2 Compliance Guide, July 2025). In practice they are your homework: for example, how you manage user access to your own accounts, or whether you back up your data. A buyer should read the CUEC list and ask who in their organisation performs each one.
  • Subservice organisations and carve-outs. Our understanding is that a provider often relies on another supplier, such as a data centre operator or a cloud platform. Under a carve-out approach, the report describes that supplier but leaves its controls outside the auditor's testing, so you rely on that supplier's own report. Under an inclusive approach, the supplier's controls are in scope. Check which approach the report uses, and then ask for the supplier's report if it is carved out.
  • Exceptions and the auditor's opinion. Our understanding is that a Type 2 report lists where a tested control did not operate as described, and that the opinion may be qualified. The AICPA lists "report opinion types" and "exceptions" among the topics of its walkthrough. Read the section listing test results and any management response, not just the opinion page.

SOC 2: how to obtain it, and the public summary

SOC 2 reports are usually shared under confidentiality. AWS says: "An NDA is required to review the AWS SOC 1 and SOC 2 reports." It also publishes a SOC 3 report, and says "The AWS SOC 3 report is a publicly available summary of the AWS SOC 2 report." A SOC 3 report is a short public version. It does not contain the detailed tests and exceptions that make the SOC 2 report useful (our reading).

Check who issued it. SOC reports are examinations by CPA firms. The AICPA page carries a notice that SOC services "should be thoroughly evaluated by service organizations and CPA firms". We read that notice only; we did not read the articles it refers to. Our recommendation: confirm the report names a CPA firm, a report date and a period.

The AICPA SOC page also lists "proposed 2027" exposure drafts of the Trust Services Criteria and description criteria, dated 26 October 2026. These are proposals. They may change what future reports look like, but they do not change the reports you receive now.

IRAP: what ASD says it is and is not

IRAP stands for the Infosec Registered Assessors Program. ASD describes it as giving Australian Government entities and major organisations "access to cyber security professionals who conduct high-quality, independent security assessment services" (ASD, IRAP). Assessors are endorsed by ASD, but ASD sets out the limits clearly:

  • "IRAP assessors do not accredit, endorse or register systems on our behalf."
  • "IRAP security assessments will generally not cover all security controls outlined in the Information Security Manual."
  • "Completion of an assessment doesn't mean the system is compliant with the tested security controls."
  • "It's vital to read and understand the security assessment reports or letters of completion to determine what a system has been tested against, and if it meets your needs."

The last line is the instruction for a buyer. An IRAP statement is not a pass mark. It is a record of what a system was tested against, and you decide if that matches your needs.

ASD's consumer guide adds that "Any entity can engage an IRAP Assessor, not just Australian government entities", that the engagement should have "a defined scope of work and expected deliverables", and that assessments have an expiry, with a reference to allowing time for reassessment "before the current assessment expires" (ASD, IRAP consumer guide, last reviewed 17 June 2026). The same guide says that for outsourced cloud service providers used by government, assessments must be done by an IRAP assessor. That requirement is about government use. It is not a rule for a commercial buyer, and an IRAP assessment is not something a commercial hosting buyer must demand.

So, for a provider offering IRAP evidence, ask: which services and which classification level were assessed, who the assessor was, the date and expiry of the assessment, and whether you can see the report or only a letter.

ISO/IEC 27001, briefly

ISO describes ISO/IEC 27001 as "the world's best-known standard for information security management systems (ISMS)" and says conformity means "an organization or business has put in place a system to manage risks related to the security of data owned or handled by the company" (ISO, ISO/IEC 27001:2022, archive copy captured 13 November 2026). It is a standard for a management system, meaning how an organisation runs its security. It is not a list of technical controls for the service you are buying.

ISO itself does not certify anyone: "ISO doesn't provide certification or conformity assessment" (ISO, Conformity assessment, archive copy captured 11 November 2026). A certificate comes from an outside certification body. For a buyer, the question is the certificate's scope statement: which organisation, which services, which sites and which dates. Our understanding is that a certificate only covers what its scope names, and that the scope is written by the certified organisation and checked by the certification body. Our understanding is also that a company holding a certificate keeps a document called a Statement of Applicability, which lists which of the standard's controls it applies, and that you can ask to see it.

What to choose and what to ask for

This section is our recommendation.

Question SOC 2 IRAP ISO 27001
Who issued it? A CPA firm An ASD-endorsed assessor A certification body
What does it cover? The described system and chosen categories The system, at the level and against the controls assessed The management system within the certificate scope
Date or period? Type 1: a date. Type 2: a period Assessment date and expiry Certificate dates
Where are the limits? Carve-outs, CUECs, exceptions The report states what was tested Scope statement
What do you do? Read the full report under NDA Read the report or letter Ask for the certificate and scope

Ask the provider for: the document itself, not a logo; the scope statement or system description; the date and period; the list of controls expected of you; and the supplier reports for any carved-out service. Then match the scope to the service you are buying.

Read-only checks

These checks read documents only. No commands are included.

  • Find the page that names the system or service covered and compare it with your contract.
  • Find the dates and note how old the report is today.
  • List every CUEC and write next to each the person at your business who does it.
  • List every carved-out supplier and ask for its report.
  • For IRAP, find the classification level, the assessor and the expiry.

A worked example (illustrative)

The following is invented. A firm is considering a hosted application. The provider sends a SOC 2 Type 2 report. The firm's IT manager reads past the opinion and finds three things. The period ended eight months ago. The described system covers the provider's shared platform but not the optional managed backup service the firm plans to buy. The report lists 14 complementary user entity controls, of which the firm currently does only nine.

The firm asks for a bridge letter, a written scope for the backup service and a plan for the remaining five controls. The report was useful because the firm read it as a list of gaps to close.

Risks and limits

  • We did not read the AICPA's paid guides, so our explanations of carve-outs, exceptions and opinion types are our understanding and should be checked against the report.
  • The AICPA criteria are under revision (proposed drafts only), and report formats may change.
  • We did not review other schemes such as ISAE 3402, SOC 1 or the Cloud Security Alliance's STAR programme.
  • This article uses AWS, Google and Microsoft pages as examples of what providers publish. It does not say anything about the reports of any particular hosting provider.
  • Assurance documents describe controls at a time. They do not prove a provider is secure now.

Next step

When a provider offers an assurance document, ask for the scope statement and the date of the document in writing, and then match both to the service you are buying. If you are reviewing a hosted service for your business, the Solutions for Businesses page is a starting point for that conversation; ask for the scope in writing.

Sources

All accessed 15 November 2026.

Learning notes

  • A SOC 2 report is an accountant's opinion; a certificate or an assessment is something else. Check who issued it.
  • Type 1 shows design on one date. Type 2 shows design and operation over a period.
  • The scope is the most important page: which services, which period, which exclusions.
  • Controls expected of you are part of the report. Read them as your own to-do list.
  • An IRAP assessment records what was tested. It is not a pass mark.