Skip to content

Third party risk management (TPRM): the complete guide for Australian organisations

In Short: Third party risk management is about understanding and controlling the risks suppliers introduce to your systems, data and operations. Outsourcing a service does not outsource accountability. A practical TPRM programme identifies your suppliers, prioritises them by risk, validates evidence rather than relying on questionnaires alone, and tracks remediation throughout the relationship. This guide explains Australian regulatory requirements, how assessments work and how to clear a growing vendor backlog. 

Contents

What is third party risk management?
Why is third party risk so high right now?
What do Australian regulations require for third party risk?
Why do third party risk assessment backlogs build up?
How does a third party risk assessment work?
How often should you assess third parties?
What risks do questionnaires miss?
How do you build a stronger TPRM program?
Should you build in-house or outsource?
Third party risk management FAQs
How Avocado helps with third party risk 

What is third party risk management?

Third party risk management (TPRM) is the ongoing process of identifying, assessing and controlling the risks that come from suppliers, SaaS providers, managed service providers and other partners who access your systems or handle your data. It covers cyber, privacy, operational, financial and compliance risk across the full vendor lifecycle, from procurement to offboarding.

Your organisation is only as secure as the weakest supplier connected to it. Every new application, integration and outsourced service extends your attack surface beyond the perimeter you control, and regulators are clear that outsourcing a service does not outsource accountability.

As Tony Rabottini, GM Cyber and Operational Resilience at Avocado, puts it: "Just because your third party is compromised, doesn't mean you're not responsible."

This guide covers why third party risk has become a board-level issue in Australia, what the regulations now require, how a third party risk assessment works, and how to clear a growing backlog of unassessed vendors.

Why is third party risk so high right now?

Third party risk is rising because breaches are getting larger, and many of the biggest now start at a supplier rather than inside the victim organisation. The figures below are the latest available as of November 2026.

Indicator Latest figure Source
Data breach notifications, 2025 calendar year 1,205, the highest since the scheme began in 2018 and up 8% on 2024 OAIC via IDM
Notifications, January to June 2026 667, broadly flat on the prior period OAIC
Breaches affecting more than 1 million people 11 in H1 2026, up from 4 in the prior period Cyber Daily
Organisations hit through a supplier or vendor 57% of those surveyed MinterEllison Perspectives on Cyber Risk 2026, via Insurance Business
Incidents ASD's ACSC responded to, 2025-26 More than 1,500, up 36% over five years ASD
Australians concerned about data breaches 82%, up from 74% in 2023 OAIC ACAPS 2026 via IDM

What recent incidents show

The Qantas breach is the clearest Australian example. In mid-2025, attackers used a phone-based social engineering attack on an overseas contact centre run by a third party, then accessed the customer servicing platform it used. Around 5.7 million customer records were affected.

The OAIC's review found the provider was required to hold ISO 27001, yet a default platform setting still let any end user connect a third-party application. A certificate on file did not stop the breach. Earlier incidents such as MediSecure (2024) and the MOVEit compromise point to the same lesson: point-in-time assurance is not the same as control.

ASD's Annual Cyber Threat Report 2025-26, released in October 2026, notes that more interconnected systems and suppliers make a single compromise far more complex to contain. It again lists supply chain management, including choosing products that are secure by design, among the key actions for Australian organisations.

What do Australian regulations require for third party risk?

Australian regulation now makes third party risk an explicit obligation for critical infrastructure, financial services and anyone handling personal information. Outsourcing a service never transfers accountability for it.

Regulation Who it applies to What it means for third parties
APRA CPS 230 Operational Risk Management Banks, insurers and super funds In force from 1 July 2025. Entities must keep a register of material service providers, manage fourth party risk where a critical operation depends on it, and have compliant contracts in place. Transition for older contracts ended on the earlier of renewal or 1 July 2026.
APRA CPS 234 Information Security APRA-regulated entities Entities must assess the information security capability of any third party that manages their information assets, in line with the potential impact of a breach.
SOCI Act and CIRMP rules Responsible entities for critical infrastructure assets, including energy, water, health, transport, data storage and financial market infrastructure Supply chain is one of four hazard areas a critical infrastructure risk management program must cover, with an annual board-approved report.
Privacy Act 1988 (APP 11) Organisations covered by the Privacy Act You must take reasonable steps, including technical and organisational measures, to protect personal information, including data held or processed by suppliers. Breaches at a supplier still trigger your notification duty.
Proposed Privacy Act tranche 2 Organisations covered by the Privacy Act The exposure draft released on 31 August 2026 proposes a fair and reasonable test, controller and processor roles, and a 72-hour breach notification window. It is still a draft, with no start date yet.
ASD and AICD board guidance Boards and directors Cyber Security Priorities for Boards 2025-26 names cyber supply chain controls as one of four priorities and asks whether suppliers are categorised by criticality and risk.

Government is not exempt. A March 2026 Queensland Audit Office report, Managing third-party cyber security risks, set out a checklist that starts with a simple question: have you identified your full supply chain, including who has access to your systems?

This guide is general information, not legal advice. Check your specific obligations with your legal or compliance team.

Why do third party risk assessment backlogs build up?

Backlogs build when the number of vendors grows faster than the team that assesses them. Even in the Commonwealth, 70% of entities performed supply chain risk assessments for IT in 2025, down from 74% in 2024, so the gap is widening, not closing.

The most common causes we see:

  • Resource constraints. Skilled cyber GRC people are scarce. Teams stretched thin rush assessments, burn out, or quietly narrow the scope to a short list of "critical" suppliers.
  • SaaS and AI sprawl. Business units can buy low-cost, high-risk subscriptions and AI tools on a credit card, bypassing procurement and IT entirely.
  • Inconsistent methods. Different assessors apply different standards, so risks are rated unevenly and gaps go unnoticed.
  • Procurement without security. IT and security are often brought in after the contract is signed, when leverage to fix gaps has gone.
  • Checkbox culture. Generic questionnaires and filed certificates create a sense of assurance without testing whether controls actually work.
  • A changing threat landscape. Social engineering of suppliers, compromised software updates and stolen credentials evolve faster than annual review cycles.
  • Regulatory deadlines. CPS 230 contract uplifts, SOCI reporting and privacy reform add assessment demand on top of business-as-usual procurement.

If several of these sound familiar, the answer is usually a combination of better triage, consistent standards and extra capacity, covered below.

How does a third party risk assessment work?

A third party risk assessment gathers evidence from a supplier, tests it against your security and business requirements, rates each gap, and ends with a report and remediation plan. Once a supplier responds, Avocado typically turns an assessment around in about one week.

  1. Inventory and intake. Identify the vendor, the service, what data and systems it touches, and who owns the relationship internally.
  2. Inherent risk triage. Rate the vendor before any controls are considered, based on data sensitivity, system access, criticality to operations and regulatory scope. This sets the assessment depth and tier.
  3. Questionnaire and evidence request. Send a questionnaire proportionate to the tier and request evidence such as ISO 27001 certification and Statement of Applicability, SOC 2 Type II reports, penetration test results, Essential Eight maturity and incident history.
  4. Assessment and validation. Review the evidence rather than accept it at face value. Check scope, dates, exceptions in audit reports and whether controls cover the actual service you are buying.
  5. Gap rating. Evaluate each gap for control effectiveness and assign a risk rating against your risk appetite.
  6. Report and recommendations. Produce an executive summary and detailed findings, with clear recommendations for the business owner, procurement and security.
  7. Remediation and treatment. Agree fixes with the supplier, add contract clauses, design compensating controls, or formally accept residual risk. Record it all in a risk register.
  8. Ongoing monitoring and reassessment. Track the vendor between reviews, reassess on a schedule set by its tier, and reassess at contract renewal or after a material change or incident.

When evidence is thin, go further: penetration testing of the supplier's service, an independent audit, or architecture review of how the vendor connects to your environment.

How often should you assess third parties?

Assess medium and high risk third parties at least annually and at every contract renewal, with your highest-risk vendors monitored monthly. A tiered model lets you spend effort where the risk is, instead of applying one heavy questionnaire to everyone.

Avocado recommends building tiers with both IT and executive management, weighing business value and security risk together. This keeps every dollar spent tied to business goals without weakening your security posture.

Tier Typical vendors Assessment depth Review frequency
Tier 1: critical Core technology, managed service providers, vendors holding sensitive data or supporting critical operations (CPS 230 material service providers) Full assessment with evidence validation, contract security clauses, exit plan Monthly monitoring, full reassessment annually and at renewal
Tier 2: high or medium SaaS with business data, integrations with system access Standard questionnaire plus evidence review Annually and at renewal
Tier 3: low No data or system access, easily replaced Short-form questionnaire or attestation At onboarding and on material change

Reassess any vendor straight away after a breach involving them, a merger or ownership change, a new data type or integration, or a change in where data is stored.

What risks do questionnaires miss?

Questionnaires show what a supplier says it does, not how its software, integrations and own suppliers behave in your environment. Four areas need attention beyond the standard assessment.

Software supply chain

Modern software is assembled from open-source libraries, APIs and third-party components, so one vulnerable dependency flows into every application that uses it. SolarWinds Orion showed how a single compromised update can reach thousands of downstream organisations.

The answer is DevSecOps: building security into the delivery pipeline so teams can be fast, safe and secure at once. Key controls include:

  • Automated security scanning and software composition analysis in the CI/CD pipeline.
  • A software bill of materials (SBOM) for critical applications, and asking suppliers for theirs.
  • Policy-as-code, so security rules are versioned, tested and enforced automatically.
  • Protection against malicious code insertion, stolen application secrets and dependency chain attacks.

SaaS integrations and identities

Every integration creates an identity, often a service account, API key or OAuth token that nobody reviews. The Qantas incident turned on a platform setting that let users authorise a connected app. Treat non-human identities with the same rigour as people: least privilege, credential vaulting, rotation and monitoring of privileged access.

AI vendors and AI inside existing vendors

Many suppliers now embed AI features or send your data to their own model providers. ASD has published guidance on AI and machine learning supply chain risks, and proposed privacy reforms would bring model fine-tuning on personal data into scope. Ask every vendor:

  • Which AI features process our data, and can we turn them off?
  • Is our data used to train or fine-tune models, and whose?
  • Which model providers sit behind the service, and where is data processed?

Fourth parties

Your suppliers' suppliers carry your risk too. CPS 230 already requires APRA-regulated entities to manage fourth parties that material service providers rely on for critical operations. Ask Tier 1 vendors for their key subcontractors and how they assess them, and map concentration risk where several vendors depend on the same cloud or platform provider.

How do you build a stronger TPRM program?

A strong program puts security into procurement from day one, applies one consistent standard, and has enough capacity to keep the backlog at zero. These steps get you there.

  1. Bring security into procurement. No new vendor, SaaS subscription or AI tool is approved without a risk triage. Set a spending or data threshold that triggers review, so low-cost tools are not a blind spot.
  2. Build a complete inventory. You cannot assess what you cannot see. Combine procurement records, finance data, SSO logs and network data to find shadow IT.
  3. Standardise the method. One risk framework, one rating scale and tiered questionnaires, so results are comparable across business units.
  4. Write security into contracts. Include breach notification timeframes, right to audit, data location, subcontractor disclosure, minimum controls and exit provisions. CPS 230 sets a useful baseline even outside financial services.
  5. Use GRC technology. A platform such as MyRISK automates workflows, evidence collection and the risk register, freeing assessors for analysis.
  6. Monitor continuously. Add security ratings, breach alerts and threat intelligence for Tier 1 vendors between formal reviews.
  7. Plan for supplier incidents. Include third party breaches in your incident response plan and exercises, with named contacts at each critical vendor.
  8. Report to the board. Give directors a regular view of vendor risk by tier, overdue assessments and accepted residual risks.
  9. Train your people. Keep procurement, business owners and assessors current on emerging threats and what good evidence looks like.

Should you build in-house or outsource?

Most organisations do both: keep governance and risk decisions in-house, and outsource assessment volume. Outsourcing makes sense when you have a backlog, peaks around regulatory deadlines, or cannot justify a full-time cyber GRC team.

Approach Best when Watch out for
In-house team Steady, predictable vendor volume and budget for specialist staff Hiring lead times, key-person risk, backlogs during peaks
Burst capability (outsourced) Clearing a backlog fast or meeting a deadline such as a CPS 230 contract uplift Needs a clear framework to assess against
Managed service (outsourced) Ongoing high volume at a predictable fixed cost Keep risk acceptance decisions with your own executives

Third party risk management FAQs

What is the difference between TPRM and vendor risk management?

Vendor risk management usually covers suppliers you pay. TPRM is broader, covering any outside party with access to your systems or data, including partners, contractors, resellers and fourth parties.

When do I need a third party risk assessment?

You need one whenever you buy new software or IT services, renew a contract, go through a merger or acquisition, enter a government contract, or a supplier has a material change or incident. Digital transformation programs and complex supply chains also call for one.

Who needs a TPRM program?

Any organisation that shares data or system access with suppliers. It is essential for critical infrastructure sectors under SOCI (energy, water, health, financial services, transport, communications, data storage and more), APRA-regulated entities under CPS 230, and government agencies managing vendors across a cluster or department.

Is an ISO 27001 or SOC 2 report enough?

No. These reports are valuable evidence, but they may not cover the service you buy, can be up to a year old, and do not show how the vendor is configured in your environment. The Qantas breach occurred even though the provider was required to hold ISO 27001.

What evidence should I ask suppliers for?

Ask for ISO 27001 certification with its Statement of Applicability, SOC 2 Type II reports, recent penetration test results, Essential Eight maturity, incident history, subcontractor lists and, for software, an SBOM.

How long does a third party risk assessment take?

Once a supplier responds, Avocado typically completes an assessment in about one week. Supplier response time is usually the biggest variable, so clear requests and follow-up matter.

Are all TPRM assessments the same?

No. Many are generic checkbox exercises that drag on for months. A good assessment validates evidence, rates each gap for control effectiveness, and ends with clear, prioritised recommendations.

Is it cost-effective to outsource TPRM?

Often, yes. Outsourcing clears a backlog without hiring full-time GRC staff, and lets your team focus on strategic priorities and remediation. Avocado offers high-volume burst capability or a fixed-cost managed service.

What happens after a third party risk assessment?

Close the gaps the assessment found, record residual risks in a risk register, and add contract terms where needed. Next steps can include designing compensating controls, penetration testing the supplier, or an external audit if evidence was weak.

How Avocado helps with third party risk

Avocado's third party risk management services combine experienced consultants with GRC technology to clear backlogs quickly and keep them clear. We are Australian owned and operated since 2004, with assessments delivered by Australian-based reviewers.

  • Certified experts. Our consultants hold CRISC, CISM, ISO 27001 and QSA certifications, with experience across ASX-listed companies, government, health, education, retail and financial services.
  • Fast turnaround. Assessments typically take about one week once a supplier responds.
  • Flexible capacity. High-volume burst capability for backlogs and deadlines, or a managed service at a fixed cost.
  • Deeper than a questionnaire. Company and financial due diligence, service quality, cyber security, SOC 2 and ISO review, and contract review.
  • Full lifecycle support. Security architects to design compensating controls, penetration testing, external audit support, and MyRISK to manage outcomes.

We helped an ASX-listed global retailer manage all third party risk and security assessments as it moved from bricks and mortar to a full omni-channel model. Read the case study.

Unmanaged third party risk can undermine even a strong cyber security program. Talk to our team about your third party risk management.

Related content