Skip to main content
Yes AI - AI Solutions Australia
Referral service for compliance-driven security reviews

Security Compliance Audits: Working Out What Applies and Who Assesses It

Yes AI does not perform security compliance audits or readiness reviews. That work needs specialist professional indemnity and cyber insurance, which the firm doing it should carry. We introduce businesses to an independent specialist security firm that scopes the review, contracts with them directly and holds its own insurance.

This page sets out, in general terms, the frameworks Australian businesses most often meet: APRA CPS 234, ISO/IEC 27001, PCI DSS, the Privacy Act 1988 and its Notifiable Data Breaches scheme. It explains who each one applies to, who is allowed to assess or certify against it, and what to ask a firm before signing. It is general information. It is not legal advice and not security advice about your business.

What the Introduction Includes

1 introduction
To a firm suited to the framework you face
Made by email or a short call, with the context you have approved
4 checks
Made before we introduce a firm
Its own insurance, qualified staff, a sample report up front and a direct contract with you
1 direct relationship
You contract with the firm
The firm scopes, quotes, invoices and takes responsibility for its work
0 compliance sign-off
Given by Yes AI
We do not assess, certify, attest or give legal or security opinions

Four Questions to Settle Before a Compliance Review

A compliance review can miss the point if the business commissions the wrong one, or the right one from the wrong kind of assessor.

Which obligation actually applies to you

Each framework has its own reach. CPS 234 binds APRA-regulated entities. PCI DSS applies where card data is stored, processed or transmitted, or where your systems can affect its security. The Privacy Act covers organisations above a turnover threshold and some smaller businesses regardless of turnover. ISO/IEC 27001 certification is a choice for most businesses, though a customer, a contract or an industry can require it. Being clear on which applies, and why, comes before any audit. A lawyer can confirm legal obligations, and the firm can confirm what an assessment needs to show.

Audit, assessment and certification are different

A gap assessment tells you how far you are from a framework. An audit tests whether controls are in place and working. Certification, where it exists, is a formal decision by a body entitled to issue it. ISO/IEC 27001 certificates are issued by certification bodies after their own audits, and PCI DSS has its own validation routes. Ask any firm which of these it is offering, because the outputs are not interchangeable.

Independence rules limit who can do what

Some frameworks separate the people who help you prepare from the people who judge the result. A certification body, for example, must not offer management system consultancy under the international standard that governs certification bodies. That is healthy, and it means you may deal with more than one organisation. A good firm will tell you plainly which role it is playing and where its role ends.

Evidence has to outlast the audit

Compliance frameworks expect controls to operate over time, not only on the day of an assessment. Policies, access reviews, training records, incident logs and test results need to be kept so the next assessment can see them. Ask the firm what evidence it expects to see and how far back, so you are not reconstructing a year of records the week before.

The Frameworks Australian Businesses Most Often Meet

A short, general description of each, with who it applies to. Check the regulator’s or standards body’s current publications for the detail, and take legal advice on your own position.

APRA-regulated entities only

APRA CPS 234 Information Security

CPS 234 is a prudential standard from the Australian Prudential Regulation Authority. It applies to APRA-regulated entities, such as authorised deposit-taking institutions, insurers and superannuation trustees, and requires them to maintain information security matched to their threats, test their controls and notify APRA of material incidents within set timeframes. It does not apply directly to other businesses. Suppliers to regulated entities often meet it indirectly, because a regulated entity must assess the information security capability of third parties that manage its information assets.

Usually a choice, sometimes required

ISO/IEC 27001

ISO/IEC 27001 is an international standard for an information security management system: the policies, risk assessment, controls and review cycle an organisation uses to manage information security. Certification is a choice for most organisations, though some customers, contracts and industries require it. A certificate is issued by a certification body after its audit, which usually runs in two stages and is followed by periodic surveillance audits and recertification. Preparation and internal audits can be done by a separate consulting firm.

Where card data is handled

PCI DSS

The Payment Card Industry Data Security Standard is maintained by the PCI Security Standards Council. It applies to entities that store, process or transmit payment card data, or whose systems can affect the security of that data. How a business validates compliance, by self-assessment questionnaire or an assessor’s report, is set by its acquiring bank and the card brands. Using a payment provider’s hosted payment page can reduce the scope of what you must show, but it does not remove all obligations.

APP entities

Privacy Act 1988 and the APPs

The Australian Privacy Principles apply to Australian Government agencies and to organisations with annual turnover above $3 million, as well as some smaller businesses regardless of turnover, such as private health service providers and businesses that trade in personal information. Australian Privacy Principle 11 requires reasonable steps to protect personal information from misuse, interference, loss and unauthorised access, modification or disclosure. What counts as reasonable depends on the circumstances, which is where a security review and legal advice meet.

Breach assessment and notice

Notifiable Data Breaches scheme

Under the Notifiable Data Breaches scheme, run by the Office of the Australian Information Commissioner, entities covered by the Privacy Act must notify affected individuals and the OAIC of an eligible data breach: unauthorised access to, unauthorised disclosure of, or loss of personal information that is likely to result in serious harm to someone, where remedial action has not prevented that likely harm. Where a breach is suspected, the entity must carry out a reasonable and prompt assessment and take reasonable steps to complete it within 30 days. Small businesses that hold tax file number information are covered by the scheme for breaches involving that information. Check the OAIC’s current guidance.

Whatever you signed

Contract and customer requirements

Some businesses meet security compliance requirements through contracts rather than law: a customer’s supplier security questionnaire, a clause requiring an annual independent review, or a tender asking for a named framework. These requirements are only as clear as the wording. Before commissioning a review, give the firm the exact clause or questionnaire, so the scope answers what the customer asked rather than a general idea of compliance.

Compliance Situations That Lead to an Introduction

TaskTraditionalThrough a Yes AI introductionNotes
A bank or insurer client sends a security questionnaireAnswer it from memory and hope it is acceptedIntroduced to a firm that reviews your answers and evidenceThe questionnaire may reflect the client’s own CPS 234 obligations for third parties.
An enterprise tender asks for ISO/IEC 27001Buy a policy template packFirm introduced to assess readiness and plan the pathCertification still comes from a certification body. Ask how long its audit process takes.
Your acquirer asks for PCI DSS validationPick a questionnaire type and tick through itIntroduction to a firm that can confirm scope and validation routeScope depends on how card data flows, which the firm maps before anything is signed.
Turnover is about to pass $3 millionAssume nothing changes until something goes wrongFirm introduced for a security review alongside legal adviceYour lawyer confirms Privacy Act coverage. The firm reviews the security side.
A health practice holding patient recordsRely on the practice software vendorIntroduction to a firm that reviews the practice’s own setupPrivate health service providers are generally covered by the Privacy Act regardless of turnover.
An ISO/IEC 27001 surveillance audit is comingGather a year of evidence in a weekFirm introduced for an internal audit beforehandAsk the firm how it keeps the internal audit independent of the certification body and of whoever built the controls.
A contract requires an annual independent reviewAsk the IT provider to write a letterAn independent firm reports against the stated clauseIndependence usually matters to the customer, so check what the clause requires.
The board wants a gap analysis against a frameworkRead the standard and self-assessFirm introduced to run a structured gap assessmentA gap assessment is not certification, and the report should say so.

Where Compliance Reviews Go Wrong

Commissioning the wrong framework

Businesses sometimes buy an ISO/IEC 27001 readiness project when the actual requirement was a customer questionnaire, or a general audit when the acquirer wanted PCI DSS validation. Start from the document that created the requirement: the contract clause, the regulator’s letter or the tender schedule. The firm can then scope against that.

Expecting one organisation to prepare and certify

Independence rules mean the firm that helps you build an ISO/IEC 27001 management system is normally not the body that certifies it. A firm offering both for the same system should explain how that fits the rules. Expect to deal with a consulting firm and a certification body as separate parties.

Assuming outsourcing moves the obligation

Using a cloud provider, a payment gateway or a managed IT provider changes how controls are delivered, but it does not generally transfer your legal or contractual obligations by itself. Your lawyer can confirm where your obligations sit. A review normally looks at what each supplier does on your behalf and what you remain responsible for. Contracts and supplier assurance reports are part of the evidence.

Treating compliance as the whole of security

A framework sets a minimum that a regulator, standard or customer will accept. Meeting it is worthwhile, but frameworks are written for many organisations at once. A firm may point out risks that a framework does not mention. Whether to act on them is your decision, made with the firm’s advice.

Treating a security review as legal advice

A security firm can tell you how your controls compare with a framework. It cannot tell you whether you are legally required to notify a breach, or what a contract clause means. Those are questions for a lawyer. Keep the two sets of advice separate, and make sure each adviser knows what the other has been asked.

Leaving evidence until the assessment

Frameworks expect controls to work over time. Access reviews that were never recorded, training without attendance records and incident logs that were never kept are hard to prove later. Ask the firm at the start what evidence it will want and from what period.

What Yes AI Does Next to the Introduction

A warm introduction

We introduce you to an independent specialist security firm by email or a short call, passing on only what you agree to share, such as the framework involved, the deadline and the systems in scope.

Our checks on the firm

We look for a firm that holds its own professional indemnity and cyber insurance, has staff with recognised security qualifications, shows you a sample report before you commit and contracts with you directly.

A systems register you own

Our systems audits list your accounts, admins, licences, domains, phone numbers and SaaS tools. Shared with the firm if you choose, the list saves it discovery time. The register does not assess security or compliance.

Referral fees stated up front

If we receive a referral fee from the firm, we tell you before the introduction, and it never changes what you pay the firm. Our AI, automation, Microsoft 365, phone and integration work for you carries on unchanged.

How the Introduction Works

Five steps. The compliance review, its findings and any sign-off are between you and the firm.

Book a call and bring the requirement

The contract clause, regulator correspondence, acquirer request, tender schedule or questionnaire that started this. The initial consultation is free for businesses with 20 or more full-time staff, otherwise $200 including GST.

Agree the background we may share

You choose what the firm hears from us, for example the framework, the deadline, how many sites and staff, and whether to pass on the systems register from one of our audits.

Warm introduction

We connect you with the firm by email or a short three-way call. If a referral fee applies, you hear about it from us before this step.

The firm scopes and contracts with you

The firm confirms which framework and role it is taking on, whether gap assessment, internal audit or validation support, and sends its own quote and terms directly to you.

Review and report

The firm does the review and reports to you. Legal questions go to your lawyer and certification decisions sit with the certification body where one is involved.

FAQ

Do you do the security work yourselves?

No. Compliance reviews need professional indemnity and cyber insurance written for security work, and the independent firm we introduce carries that insurance while we do not. Yes AI does not perform, supervise, resell, white-label or subcontract security reviews, and gives no security opinions, compliance sign-off or warranties.

Does APRA CPS 234 apply to my business?

Directly, only if your business is an APRA-regulated entity, such as a bank or other authorised deposit-taking institution, an insurer or a superannuation trustee. Most other businesses meet CPS 234 indirectly as suppliers, because regulated entities must assess the information security capability of third parties that manage their information assets. That is why suppliers to banks and insurers receive detailed questionnaires. If you are unsure whether you are regulated, check with APRA or your lawyer.

Can you get us ISO/IEC 27001 certified?

No. Certification is issued by a certification body after its own audit, and Yes AI is neither a certification body nor a security firm. A specialist firm we introduce can assess your readiness and help you prepare, if that is the role you engage it for. The certification audit is then carried out by a separate certification body that you choose.

Do we need to worry about PCI DSS if a payment provider handles cards?

Usually yes, though often with a smaller scope. PCI DSS applies to entities that store, process or transmit card data or whose systems can affect its security. Sending customers to a provider’s hosted payment page can reduce the scope of what you need to show, but your acquiring bank decides how you validate compliance. A firm can map how card data actually moves through your business before you choose a validation route.

Does the Privacy Act apply to small businesses?

Generally the Australian Privacy Principles apply to organisations with annual turnover above $3 million, and the OAIC’s small business checklist asks whether turnover has been above that in any financial year since 2002. Some smaller businesses are covered regardless, including private health service providers and businesses that trade in personal information. Privacy law in Australia was amended in 2024, and some of those changes start later. The OAIC publishes guidance on who is covered. Whether it applies to you is a legal question for your lawyer.

Is this legal advice, and how is Yes AI paid?

Nothing on this page or in the introduction is legal advice or security advice. Booking uses our normal call booking: free for businesses with 20 or more full-time staff, otherwise $200 including GST. The firm quotes and invoices you directly and we publish no security prices. If we receive a referral fee from the firm, we tell you before the introduction, and it never changes what you pay the firm.

Who should not use this introduction?

If you think personal information may already have been accessed or lost, or an incident is still under way, do not wait for an introduction. Contact your cyber insurer’s incident line if you have cover, speak to your lawyer about any notification duty, and report through cyber.gov.au, where the Australian Signals Directorate’s Australian Cyber Security Centre lists the Australian Cyber Security Hotline, 1300 CYBER1. The OAIC website explains how to notify a data breach.

Facing a Compliance Requirement? Ask for an Introduction

Book a call and bring the clause, letter or questionnaire. We introduce you to an independent specialist firm that carries its own insurance, and it scopes the review with you directly.

All discussions held in confidence. Australian-based consultants.

Interactive controls are loading. Phone and email links are available.