Regulated Customer Contract Checker
Every country ยท Oceania

Australia

Outside the EEA. A customer here pulls on the regimes below by its sector; the rest are named and not quoted.

By customer sector

read on a SaaS subscription that names personal data
A bankCPS 230, CPS 234, ISO 27001, ISO 27701expected on a SaaS subscription with personal data: CPS 230 terms, security schedule, audit right, breach clock
An insurerCPS 230, CPS 234, ISO 27001, ISO 27701expected on a SaaS subscription with personal data: CPS 230 terms, security schedule, audit right, breach clock
A hospital or health systemISO 27001, ISO 27701expected on a SaaS subscription with personal data: security schedule, audit right, breach clock
A retailerISO 27001, ISO 27701expected on a SaaS subscription with personal data: security schedule, audit right, breach clock
A government departmentISO 27001, ISO 27701expected on a SaaS subscription with personal data: security schedule, audit right, breach clock
A technology companyISO 27001, ISO 27701expected on a SaaS subscription with personal data: security schedule, audit right, breach clock
Named, not quotedthe Australian Privacy Act and its notifiable data breaches scheme.

Codes the register reads for this country: AU, Australia, sydney, melbourne, brisbane, perth, adelaide, canberra, ballarat.

The clauses, quoted

24

Clause text from The Art of Service standards library at compliance.theartofservice.com, read against the published text of each standard and cited to its clause: our close statement of each clause, not the instrument verbatim. Where the UK text is covered only as a summary, the EU GDPR article of the same number is quoted and the page says so.

CPS 230 para 32 Notify APRA within 72 hours of a material operational risk incident

Clock: as soon as possible, and at the latest 72 hours from the time the entity becomes aware. Trigger: an operational risk incident the entity has determined is likely to cause a material financial impact, or to materially affect its ability to keep its critical operations running. An information security incident already notified to APRA under CPS 234 need not be notified aga...

Evidence an auditor accepts: APRA notification procedure stating the 72-hour clock, the materiality determination and the decision owner; Incident log fields recording awareness time, materiality determination time and APRA notification time; Copies of notifications lodged with APRA and acknowledgements
Where it usually falls short: Clock started from incident closure rather than from awareness
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 230 para 41 Notify APRA within 24 hours of a disruption outside tolerance

Clock: as soon as possible and no later than 24 hours after a critical operation is disrupted beyond its tolerance. The notification to APRA must describe the nature of the disruption, what action has been taken, the likely effect on business operations and the expected timeframe for getting back to normal operations.

Evidence an auditor accepts: APRA disruption notification procedure stating the 24-hour clock and the four required content items; Notification template covering nature, actions taken, likely impact and return timeframe; Copies of notifications lodged and timestamps of tolerance breach versus lodgement
Where it usually falls short: Notification waits until the disruption is resolved
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 230 para 49 Minimum material service provider classifications unless justified

Unless it can justify otherwise, the entity must at least treat providers of these services as material: for an ADI, mortgage brokerage, credit assessment, and funding and liquidity management; for an insurer, insurance brokerage, reinsurance, underwriting and claims management; for an RSE licensee, custodial services, fund administration, investment management, and arrangement...

Evidence an auditor accepts: Register showing providers of each prescribed service classified as material; Approved justification for any prescribed-service provider not classified as material; Mapping of core technology service providers
Where it usually falls short: Core technology services interpreted narrowly, leaving cloud providers out
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 230 para 53 Formal legally binding agreement for each material arrangement and its minimum terms

For every material arrangement the entity must hold a formal, legally binding agreement that at least: (a) defines the services and their service levels; (b) sets each party's rights, duties and expectations, including asset ownership, data ownership and control, dispute resolution, audit access, indemnity and liability; (c) lets the entity satisfy its legal and compliance obli...

Evidence an auditor accepts: Executed agreement for each material arrangement; Contract clause checklist mapping each agreement to items (a) to (g); Exemption record under para 57 or APRA notice under para 58 for any material arrangement without a compliant formal agreement
Where it usually falls short: Agreement lacks subcontractor notification or force majeure carve-outs
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 230 para 54 APRA access, on-site visit and non-impediment clauses

The formal agreement must also provide that (a) APRA can access documentation, data and other information about the service; (b) APRA may visit the provider on site; and (c) the provider undertakes not to obstruct APRA in performing its prudential regulator duties. Para 57 can exempt the arrangement (Attachment category provider on standardised terms or no formal agreement), an...

Evidence an auditor accepts: Clause references in each material agreement for APRA access, on-site visits and non-impediment; Contract review checklist confirming the three APRA clauses; Para 57 exemption record or para 58 APRA notice for any arrangement lacking them
Where it usually falls short: Cloud or SaaS terms accepted without APRA access rights and no exemption analysis
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 230 para 60 Notify APRA of critical-operation agreements (20 business days) and before material offshoring

Clocks: (a) as soon as possible and within 20 business days of signing, or materially changing, an agreement for a service the entity relies on to carry out a critical operation; and (b) before entering into any material offshoring arrangement, or when a significant change to such an arrangement is proposed, including where personnel or data used for the service will sit offsho...

Evidence an auditor accepts: APRA notification log with agreement execution or change dates and lodgement dates measured in business days; Pre-commencement offshoring notifications to APRA with lodgement before the arrangement start; Offshoring assessment identifying where service, data and personnel are located
Where it usually falls short: Offshoring notified after go-live
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 234 para 16 Assess the security capability of related and third parties

Where a related party or third party manages any of the entity's information assets, the entity assesses that party's information security capability, to a depth that matches the possible consequences of an incident touching those assets. A footnote makes this apply to every such party, not only those supplying outsourced material business activities covered by CPS 231 or SPS 2...

Evidence an auditor accepts: Inventory of related and third parties that manage information assets, with tiering by consequence; Completed security due-diligence questionnaires and assessment reports per party; Independent assurance reports reviewed (for example SOC 2 Type 2, ISO/IEC 27001 certificate and statement of applicability)
Where it usually falls short: Assessment limited to material outsourcing arrangements, missing SaaS and other parties that hold data
APRA CPS 234 Information Security in The Art of Service standards library
CPS 234 para 22 Evaluate the design of third-party controls

Where a related or third party manages the entity's information assets, the entity evaluates how that party's security controls protecting those assets are designed. A footnote confirms this reaches every such party, not only CPS 231 or SPS 231 material outsourcing.

Evidence an auditor accepts: Control design evaluation reports for each in-scope third or related party; Reviewed third-party assurance reports with the entity's own analysis of scope, exceptions and complementary user-entity controls; Contract rights to information, audit and assessment
Where it usually falls short: Accepting a certificate or report without reading its scope or exceptions
APRA CPS 234 Information Security in The Art of Service standards library
CPS 234 para 34 Internal audit assessment of third-party assurance

Internal audit has to assess the security control assurance a related or third party provides where both hold: (a) an incident affecting the assets could have a material financial or non-financial effect on the entity itself or on the interests of its depositors, policyholders, beneficiaries or other customers (the materiality limb); and (b) internal audit plans to rely on that...

Evidence an auditor accepts: Internal audit working papers assessing third-party assurance reports (scope, period, opinion, exceptions); List of third parties where internal audit relies on external assurance, with materiality rationale; Reliance methodology in the internal audit manual
Where it usually falls short: Internal audit accepts third-party reports without any evaluation
APRA CPS 234 Information Security in The Art of Service standards library
CPS 234 para 35 Notify APRA of material incidents within 72 hours

The entity must tell APRA promptly, and at the latest within 72 hours of becoming aware, of any information security incident that either (a) had, or could have had, a material financial or non-financial effect on the entity itself or on the interests of its depositors, policyholders, beneficiaries or other customers (the impact limb), or (b) has already been notified to anothe...

Evidence an auditor accepts: Notification procedure stating the 72-hour clock, who decides materiality and who submits to APRA; Materiality assessment criteria and completed assessments per incident; Copies of APRA notifications with timestamps of awareness and submission
Where it usually falls short: Clock started at confirmation of the incident instead of awareness
APRA CPS 234 Information Security in The Art of Service standards library
ISO 27001 A.5.19 Information security in supplier relationships

Define and apply processes to manage the security risk suppliers introduce.

Evidence an auditor accepts: Supplier risk assessment; Contractual security requirements; Supplier security monitoring
Where it usually falls short: Treating all suppliers as low risk
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.20 Addressing information security within supplier agreements

Establish and agree the relevant security requirements in each supplier contract.

Evidence an auditor accepts: Contract security clauses; Supplier risk assessment; Security incident reporting
Where it usually falls short: missing explicit security clauses
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.21 Managing information security in the ICT supply chain

Extend security requirements down the ICT products and services supply chain.

Evidence an auditor accepts: Supplier security requirements; Contractual security clauses; Supply chain risk assessments
Where it usually falls short: Treating supplier security as one-off check
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.23 Information security for use of cloud services

Govern acquisition, use, management and exit of cloud services against your security requirements.

Evidence an auditor accepts: Cloud service selection; Cloud contract management; Cloud security monitoring
Where it usually falls short: Relying solely on provider's security assurances
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.24 Information security incident management planning and preparation

Define incident roles, processes and readiness before an incident happens.

Evidence an auditor accepts: Incident response plan; Role assignment matrix; Training and awareness records
Where it usually falls short: roles are defined but not formally assigned or approved
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.31 Legal, statutory, regulatory and contractual requirements

Identify, document and keep current the legal and contractual obligations relevant to security, and your approach to meeting them.

Evidence an auditor accepts: Legal register; Contractual obligations; Regulatory filing records
Where it usually falls short: outdated legal register
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.34 Privacy and protection of personal identifiable information (PII)

Identify and meet privacy and PII-protection requirements from law, regulation and contract.

Evidence an auditor accepts: Privacy policy; Data inventory; Processing agreements
Where it usually falls short: Missing documented consent for all data subjects
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27701 A.2.2.2 Customer agreement

Where relevant, the contract to process personal data must address the organization's role in assisting the customer with the customer's own obligations, taking account of the nature of processing and the information available to it, covering as relevant privacy by design and by default, achieving security of processing, notifying breaches to a supervisory authority and to cust...

Evidence an auditor accepts: Customer contracts carrying the assistance provisions relevant to the engagement; Where the jurisdiction requires it, contract terms stating subject matter, duration, nature, purpose, data types and categories of individuals; Operational capability behind each assistance commitment, not the commitment alone
Where it usually falls short: Assistance promised in contract with no operational capability behind it, discovered only when the customer first asks
ISO/IEC 27701:2025 in The Art of Service standards library
ISO 27701 A.2.4.3 Return, transfer or disposal of PII

The organization must provide the ability to return, transfer or dispose of personal data securely and must make its policy available to the customer, managing the capability securely whether the outcome is return to the customer, transfer to another organization or controller, deletion, destruction, de-identification or archiving, providing the assurance the customer needs tha...

Evidence an auditor accepts: Documented return, transfer and disposal policy, made available to customers; Assurance evidence that erasure reaches backups, continuity copies and subcontractors; Stated post termination retention period before disposal, with its rationale
Where it usually falls short: Erasure certified for primary systems while backups retain the data for the full backup cycle, which the customer is not told
ISO/IEC 27701:2025 in The Art of Service standards library
ISO 27701 A.2.5.7 Disclosure of subcontractors used to process PII

The organization must disclose to the customer any use of subcontractors to process personal data before that use, with provisions included in the customer contract, disclosing that subcontracting is used and the names of the relevant subcontractors, the countries and international organizations to which they can transfer data, and the means by which they are obliged to meet or...

Evidence an auditor accepts: Current subcontractor list with names, the countries they can transfer to, and how their obligations are secured; Evidence of disclosure before use, not after; Contract provisions covering subcontractor disclosure
Where it usually falls short: Subcontractors disclosed only on request, with customers never told the information exists
ISO/IEC 27701:2025 in The Art of Service standards library
ISO 27701 A.2.5.8 Engagement of a subcontractor to process PII

The organization must engage a subcontractor to process personal data only according to the customer contract, obtaining written authorization from the customer before the subcontractor processes the data, whether through appropriate clauses in the customer contract or a specific one off agreement, holding a written contract with every such subcontractor that addresses implemen...

Evidence an auditor accepts: Written customer authorization for each subcontractor, whether general or specific; Written contract with every subcontractor carrying the processor control obligations; Justification for any processor control not required of a subcontractor
Where it usually falls short: Subcontractor engaged on the strength of a general authorization that does not in fact cover it
ISO/IEC 27701:2025 in The Art of Service standards library
ISO 27701 A.2.5.9 Change of subcontractor to process PII

Where it holds a general written authorization, the organization must inform the customer of any intended change involving the addition or replacement of a subcontractor that processes personal data, giving the customer the opportunity to object, and where it changes the subcontractor carrying out some or all of the processing, written authorization from the customer is require...

Evidence an auditor accepts: Change notification procedure with the notice period and the objection route; Records of notifications given and objections received, with outcomes; Evidence that new subcontractors did not begin processing before authorization
Where it usually falls short: Notification given at the point of change or after, so the objection right is theoretical
ISO/IEC 27701:2025 in The Art of Service standards library
ISO 27701 A.3.10 Addressing information security within supplier agreements

Agreements with suppliers shall specify whether PII is processed and the minimum technical and organizational measures the supplier must meet for the organization to meet its information security and PII protection obligations, shall clearly allocate responsibilities between the organization, its partners, suppliers and applicable third parties taking account of the type of PII...

Evidence an auditor accepts: Supplier agreements stating whether PII is processed and the minimum measures required; Responsibility allocation clauses by type of PII; Audit or assurance clause and the independent evidence obtained under it
Where it usually falls short: Supplier contracts silent on PII while the supplier processes it
ISO/IEC 27701:2025 in The Art of Service standards library
ISO 27701 A.3.12 Response to information security incidents

For a PII controller, an incident that involves PII shall trigger a review to determine whether a breach involving PII requiring a response has occurred, an event alone not necessarily triggering it; when a breach has occurred the response shall include the relevant notifications and records, jurisdictions defining when the supervisory authority and PII principals must be notif...

Evidence an auditor accepts: Breach determination records for incidents involving PII; Breach register carrying every field the standard names; Notifications made to authorities, PII principals or customers with timing against the legal limit
Where it usually falls short: Incidents closed as security events with no PII breach determination
ISO/IEC 27701:2025 in The Art of Service standards library

Read your customers in Australia

Paste the list; every agreement with a customer here is read against these regimes by its sector and its kind. Eight agreements free, no account.

Check my contract list