A third-party risk assessment evaluates the cyber security and operational risk a vendor or supplier introduces, based on the data and access they hold. Tier vendors by criticality, run a proportionate questionnaire covering governance, access, data handling and subcontractors, collect evidence such as ISO 27001 or SOC 2 reports, set contract clauses for security and audit rights, and reassess on a schedule with event based triggers.
Most breaches that make the news did not start inside the victim’s own network. They started with a supplier, a managed service provider, or a piece of software from a vendor nobody had properly assessed. A third-party risk assessment is how a business catches that exposure before it becomes a contract, not after.
What is a third-party risk assessment, and why does it matter?
A third-party risk assessment evaluates the cyber security, privacy and operational risk introduced by a vendor, supplier, contractor or partner. It asks what data or systems the third party can reach, how they protect that access, what happens if they are compromised, and whether the risk is acceptable given the relationship. It applies before a contract is signed and at intervals through the life of the relationship.
The reason it matters is simple. When a vendor is given access to an organisation’s data, network or customers, their weaknesses become its exposure. Attackers know this and increasingly target the supplier rather than the end target directly, because one compromised vendor can open the door to many of their customers at once. Supply chain attacks exploit exactly this pattern. Frameworks reflect the same logic, ISO 27001 Annex A requires managing information security in supplier relationships, and regulators increasingly expect organisations to demonstrate they understand and manage the risk their supply chain carries, not just their own systems.
What should a third-party risk assessment template include?
A usable template has a small number of moving parts, applied consistently:
- Risk tiering: classify each vendor by the data they access, the criticality of the service, and the level of integration, so assessment depth matches actual risk
- Governance questions: do they have a named security lead, a written information security policy, and a defined incident response process
- Access and data handling: what data or systems they can reach, how access is granted and revoked, whether data is encrypted in transit and at rest, and where it is stored or processed
- Subcontractors and fourth parties: who they in turn rely on, and whether that chain is disclosed and managed
- Incident history: any past breaches or significant incidents, and how they were handled and communicated
- Certifications and evidence: ISO 27001 certification, a SOC 2 report, a recent penetration test summary, or equivalent independent evidence rather than a vendor’s self-assessment alone
- Contract clauses: security obligations, breach notification timeframes, audit or assessment rights, and data return or deletion obligations at offboarding
- Reassessment schedule: a defined cadence and a list of events that trigger an early review
Keep the questionnaire proportionate. A critical vendor handling sensitive customer data deserves deep scrutiny and possibly a right to audit; a low risk vendor supplying office stationery does not need the same process, and forcing it through one slows procurement without reducing real risk.
How do we tier and assess vendors by risk?
Tiering comes first, because it decides how much effort every later step deserves. A common approach uses three or four tiers, critical, high, medium and low, driven mainly by two questions, what data can this vendor access, and how disruptive would losing this service be. A payroll provider or a cloud hosting partner falls in a higher tier than a graphic design contractor with no system access, even if both are similarly sized businesses.
Once tiered, assessment depth follows. Critical and high tier vendors should provide independent evidence, an ISO 27001 certificate, a SOC 2 report, or a recent penetration test summary, plus a completed questionnaire covering the areas above. Medium tier vendors might complete a shorter questionnaire without requiring formal certification. Low tier vendors can often be handled with a light touch check and standard contract terms. Whatever evidence comes back, review it rather than filing it, a stale certificate, an unanswered question, or a vague policy statement is a finding, not a formality to tick off.
How often should vendor risk be reviewed, and what triggers a reassessment?
Reassessment on a calendar alone misses risk that changes between review dates. Critical and high tier vendors are commonly reassessed annually. Lower tier vendors can go longer, every two to three years, or be handled through a lighter attestation process. Layer event based triggers on top of the calendar, a vendor discloses a breach, they change their subcontractors or hosting provider, their certification lapses or is not renewed, they start handling a new category of the organisation’s data, or the relationship expands in scope. Any of these should prompt an early look regardless of when the last review happened.
Build the whole process into the organisation’s broader risk management, not as a side activity. It belongs alongside the ISO 27001 risk register where an information security management system is in place, and it connects directly to incident response, because if a vendor is compromised the incident response plan should already know which vendors matter and what data they touch. Where an organisation wants help building or running a third-party risk programme, Cybernion’s advisory services can set up the template, the tiering model and the ongoing process.
Frequently asked questions
What is a third-party risk assessment?
A third-party risk assessment is the process of evaluating the cyber security, privacy and operational risk a vendor, supplier or partner introduces before engaging them and at intervals afterward. It looks at what data or access the third party has, how they protect it, their track record, and whether their controls match the risk of the relationship. The output feeds a go or no go decision, contract terms, and ongoing monitoring.
What should a third-party risk assessment template include?
A good template includes a risk tiering step based on data access and criticality, a standard questionnaire covering governance, access control, data handling, subcontractors, incident history and certifications, evidence collection such as audit reports or policies, a scoring or risk rating method, contract clauses covering security obligations and audit rights, and a reassessment schedule and trigger list. It should be proportionate, a low risk vendor does not need the same depth as a critical one.
How do we assess a vendor’s cyber security before signing a contract?
Start by tiering the vendor based on the data they will access and how critical the service is, then request evidence proportionate to that tier, a completed questionnaire, an independent certification such as ISO 27001 or SOC 2, or a recent penetration test summary for higher risk vendors. Review the evidence against the organisation’s minimum requirements, flag gaps, and negotiate contract clauses covering security obligations, breach notification timeframes and audit rights before signing.
How often should third-party risk assessments be reviewed?
Critical and high risk vendors are typically reassessed annually, with lower risk vendors reviewed every two to three years or on a lighter touch basis. Reassessment should also be triggered by events, a vendor reports a breach, their service or subcontractors change materially, their certification lapses, or they start handling a new category of data. A static risk register that is never revisited understates real exposure.
What frameworks guide third-party and supply chain risk management?
In Australia, the ASD publishes cyber supply chain risk management guidance describing how to identify, assess and manage risk from suppliers. ISO 27001 Annex A includes specific controls for supplier relationships and ICT supply chain security. NIST’s supply chain risk management guidance covers similar ground for organisations aligning to NIST frameworks. These sources agree on the same core discipline, know the suppliers, tier them by risk, and verify rather than assume their controls.
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.
Sources:
- Cyber supply chain risk management, Australian Signals Directorate, 2026
- ISO/IEC 27001:2022, International Organization for Standardization, 2022
- Supply Chain Risk Management practices for federal information systems and organisations (SP 800-161), NIST Computer Security Resource Center, 2022
Last updated: 30 August, 2026
