Most organisations now run critical services on suppliers they cannot see inside, and the third-party risk analyst is the person expected to tell the business which of those suppliers could hurt it. The role sits between security, procurement, legal and the business owners of each supplier, and it is one of the largest hiring pools in governance, risk and compliance, especially in financial services where regulators set explicit outsourcing and ICT third-party expectations. This guide covers what the work actually involves at each level, the skills and tools employers test for, realistic entry routes, which certifications help and how to progress into risk management, audit or supply chain security leadership. It is written for people aiming at their first TPRM job, analysts planning their next step and managers building a TPRM team. Broader career routes are in the Cybersecurity Careers Guide.
Key takeaways
- The job is judgement about suppliers, not questionnaire processing. Good analysts decide how much assurance a supplier needs, read the evidence critically and say clearly what risk remains and who owns it.
- Tiering drives everything. Inherent risk (data, access, criticality, concentration) decides the depth of due diligence; analysts who tier well save the business time and catch the suppliers that matter.
- Evidence reading is the core technical skill. Reading a SOC 2 Type 2 report, an ISO/IEC 27001 certificate scope, a penetration test summary and a security ratings report, and spotting what they do not cover, separates analysts from administrators.
- Regulation shapes the role in financial services. DORA in the EU and the PRA's SS2/21 in the UK set expectations on registers, materiality, contracts and exit plans, so FS employers look for people who can map work to those texts.
- Progression goes wide. Typical next steps are TPRM lead, cyber risk manager, IT auditor, supply chain security specialist or a security assurance role on the supplier side.
What the role does
NIST's NICE Framework (components v2.2.0, April 2025) has a Cybersecurity Supply Chain Risk Management work role, OG-WRL-017, in its Oversight and Governance category: building policy and processes for managing supply chain cyber risk and advising stakeholders on it. In industry the title varies: third-party risk analyst, vendor risk analyst, supplier assurance analyst, third-party security analyst or C-SCRM analyst. NIST SP 800-161 Rev. 1 (final, updated 1 November 2024) frames the underlying problem: products and services an organisation buys may contain malicious functionality, be counterfeit or carry weaknesses from poor development, and the risk grows when the buyer has little visibility into how the technology is built and delivered.
The working cycle follows the supplier lifecycle. NIST CSF 2.0 captures it in the Govern function: GV.SC-04 (suppliers are known and prioritised by criticality), GV.SC-06 (planning and due diligence before entering relationships) and GV.SC-07 (risks are understood, recorded, prioritised, assessed, responded to and monitored over the relationship). The process itself is covered in depth in the Third-Party Risk Management Guide; this page looks at it from the analyst's desk.
| Level | Typical titles | Main work | Usual background |
|---|---|---|---|
| Analyst | TPRM analyst, vendor risk analyst, supplier assurance analyst | Run intake and tiering, send and chase questionnaires, review evidence for low and medium tier suppliers, log findings and track remediation | Procurement, compliance, IT service, audit trainee, graduate |
| Senior analyst | Senior TPRM analyst, third-party security specialist | Assess critical suppliers, hold assessment calls, review SOC 2 exceptions and pen test results, agree remediation plans, advise on contract clauses | Two to four years in TPRM, audit or security operations |
| Lead or manager | TPRM lead, third-party risk manager | Own the framework, tiering model and risk appetite, report to risk committees, manage regulatory registers and concentration analysis | Senior analyst with stakeholder and reporting experience |
A typical assessment
- Intake: the business owner describes the service, the data shared, the access granted (user accounts, API keys, VPN, OAuth apps) and how critical the service is.
- Tiering: score inherent risk and set the assessment depth. See the Vendor Tiering and Inherent Risk Questionnaire Template.
- Evidence collection: request a questionnaire and existing attestations rather than starting from scratch. See the Security Questionnaires Guide.
- Review: check report scope, period, exceptions and complementary user entity controls; compare answers with evidence; note gaps.
- Risk decision: rate residual risk, agree remediation with dates, or escalate for formal risk acceptance by a named owner.
- Contract input: feed security requirements, notification clauses and audit rights into the contract. See the Third-Party Security Contract Clauses Template.
- Ongoing monitoring: reassess on a tier-based cycle, watch for incidents and material changes, and plan exit for critical services.
Core skills and tools
| Skill | What good looks like | How to practise |
|---|---|---|
| Reading assurance reports | Know the difference between SOC 2 Type 1 and Type 2, check the period and system description, read exceptions and complementary user entity controls, and confirm ISO/IEC 27001 certificate scope covers the service you buy | Read public SOC 3 reports and certificate scopes; see the How to Read a SOC 2 Report Guide |
| Control knowledge | Understand what MFA, encryption, logging, vulnerability management, backup and access review actually look like in practice, so answers can be challenged | Map questionnaire questions to NIST SP 800-53 or ISO/IEC 27001 Annex A controls |
| Risk rating | Separate inherent from residual risk, use the organisation's risk scale consistently, write a clear risk statement | Rewrite five vague findings as cause, event, impact and owner |
| Regulatory mapping | Know which suppliers count as critical or material under DORA, PRA SS2/21 or sector rules, and what the register must hold | Read the regulator texts and build a mapping for one service. See the DORA ICT Third-Party Risk and Register of Information Guide |
| Technical access review | Identify how a supplier connects: SSO, shared accounts, API keys, OAuth scopes, privileged remote access, and what monitoring exists | Inventory the integrations of one SaaS tool you use |
| Stakeholder handling | Get timely, honest answers from suppliers and explain findings to business owners without jargon | Practise a five-minute verbal summary of an assessment |
| Data handling | Use spreadsheets and the TPRM platform well: pivot by tier, overdue reviews and open findings | Build a small supplier register with tiers and review dates |
Tools you will meet: a TPRM or GRC platform for workflow and the register, standard questionnaires (industry questionnaires such as the Shared Assessments SIG or the Cloud Security Alliance CAIQ, or a custom set), security ratings services that score a supplier's external attack surface, contract management systems, and spreadsheets. Ratings and platforms are evaluated in the TPRM and Security Ratings Buyer's Guide. Treat ratings as a prompt for questions, not a verdict: they see only what is visible from the internet.
Where identity fits
Much third-party risk is access risk. Suppliers hold user accounts in your tenant, service accounts, API keys and OAuth grants into your SaaS estate, and these machine credentials often outlive the contract. Analysts who ask which non-human identities a supplier holds, how they are rotated and how quickly they are revoked at exit add real value. See the Third-Party Access Guide and the OWASP NHI Top 10 NHI3 Vulnerable Third-Party NHI Guide.
Routes into the role
- Procurement or vendor management: you already know contracts, renewals and supplier relationships; add control knowledge and evidence review.
- Compliance, operational risk or audit: strong on frameworks, evidence and risk statements; add security technical depth. See the Cybersecurity Auditor Career Guide.
- IT service desk, infrastructure or SOC: technical credibility that lets you challenge supplier answers; add risk language and regulation.
- Graduate and apprenticeship schemes: large banks, insurers and consultancies run GRC schemes where TPRM is a common first rotation.
- Supplier-side security assurance: people who answer questionnaires for a vendor learn exactly what good and weak evidence looks like, and can move to the buyer side.
What the market asks for: DSIT's Cyber security skills in the UK labour market 2026 found that across core cyber job postings in 2025 the most requested skills after general cyber security were auditing (22%), governance (20%), ISO/IEC 27001 (20%), risk management (19%) and risk analysis (16%), which is the TPRM skill set. The same report found 64% of postings asked for two to six years' experience and only 16% were open to people with under a year, so an adjacent role first is the usual path. Career changers should read the Career Change into Cyber Security Guide.
Pay: DSIT gives no TPRM-specific figure; it reports a mean advertised salary of £60,800 (median £58,050) across all core cyber roles in 2025, with 76% of postings giving no salary at all. Entry TPRM roles typically sit below that mean. The US Bureau of Labor Statistics reports a median of $129,180 (May 2025) for information security analysts, a broad occupation that is not specific to third-party risk.
Certifications that help
No single certification defines the role. Choose by background and target employer, and check each body's current outline, fees and experience rules before committing. The table is descriptive, not a ranking.
| Awarding body | Certification | Why it helps in TPRM | Typical stage |
|---|---|---|---|
| ISC2 | Certified in Cybersecurity (CC) | Security vocabulary for people coming from procurement or compliance | Entry |
| CompTIA | Security+ | Broad control knowledge to challenge supplier answers | Entry |
| Shared Assessments | CTPRP (Certified Third Party Risk Professional) | TPRM-specific programme content | Analyst |
| ISACA | CRISC | IT risk identification, assessment, response and reporting; domains are Corporate IT Governance, Risk Assessment, Risk Response and Reporting, and Technology and Security | Senior analyst to lead |
| ISACA | CISA | Audit method and evidence evaluation | Senior analyst, especially if moving towards audit |
| ISO/IEC 27001 Lead Auditor (various accredited training bodies) | Lead Auditor course and exam | Understanding certificate scope and audit depth | Analyst to senior |
| ISC2 | CISSP | Broad security management credibility | Lead and above |
As a cost example checked on 27 October 2026, ISACA lists the CRISC exam at US$575 for members and US$760 for non-members, plus a US$50 application processing fee after passing. See the CRISC Certification Guide, CISA Certification Guide and CISSP Certification Guide for exam details.
Progression
| Next role | What changes | Build this in TPRM | Read next |
|---|---|---|---|
| TPRM lead or manager | Own framework, appetite, committee reporting, team | Metrics, risk acceptance discipline, regulator engagement | Third-Party Risk Management Maturity Model |
| Cyber risk manager | Risk across the whole organisation, not only suppliers | Risk scenarios, quantification, reporting | Cybersecurity Risk Manager Career Guide |
| IT or security auditor | Independent assurance over internal controls | Evidence standards, sampling, report writing | Cybersecurity Auditor Career Guide |
| Supply chain security specialist | Software and hardware supply chain, SBOMs, provenance | Technical depth on build pipelines and components | NIST SP 800-161 Cyber Supply Chain Risk Management Guide |
| Operational resilience or concentration risk | Critical services, impact tolerances, exit and substitution | Mapping suppliers to important business services | Third-Party Concentration Risk Guide |
Choosing: if you like frameworks and evidence, audit or risk management; if you like the technical questions, supply chain security or third-party access; if you like running things, TPRM leadership. Large employers often allow rotation into the second line of defence or internal audit after two years.
Financial services context
The PRA's SS2/21 Outsourcing and third party risk management (first published March 2021, effective 31 March 2022; current version effective 31 December 2024, with a further version published 18 March 2026 that takes effect on 18 March 2027 following PS7/26 on operational incident and third-party reporting) complements UK operational resilience requirements and implements the EBA Outsourcing Guidelines. In the EU, DORA requires a register of information on ICT third-party arrangements. Analysts in FS need to know which version applies and when. See the DORA Critical ICT Third-Party Provider Oversight Guide.
Framework mapping
| Framework | Where TPRM work sits |
|---|---|
| NICE Framework v2.2.0 | OG-WRL-017 Cybersecurity Supply Chain Risk Management |
| NIST CSF 2.0 | GV.SC Cybersecurity Supply Chain Risk Management, including GV.SC-04, GV.SC-06 and GV.SC-07 |
| NIST SP 800-53 Rev. 5 | SR-3 Supply Chain Controls and Processes, SR-6 Supplier Assessments and Reviews, SA-9 External System Services |
| ISO/IEC 27001:2022 Annex A | 5.19 to 5.23 on supplier relationships, supplier agreements, the ICT supply chain, monitoring of supplier services and cloud services |
| CIS Controls v8.1 | Control 15 Service Provider Management |
| ISO/IEC 27036 | Information security for supplier relationships. See the ISO/IEC 27036 Supplier Relationships Guide |
Measuring your own performance
- Coverage: share of critical and high tier suppliers with a current assessment.
- Cycle time: days from intake to risk decision, by tier, without lowering review depth.
- Finding closure: share of supplier remediation items closed by the agreed date.
- Decision quality: share of your assessments that hold up when audit or an incident tests them.
- Register accuracy: suppliers found in finance or SSO logs that were missing from the register.
Common failure patterns
- Same questionnaire for every supplier: low-risk suppliers wait weeks while critical ones get the same shallow review.
- Accepting a certificate without reading scope: an ISO/IEC 27001 certificate or SOC 2 report that does not cover the service you buy is not evidence for it.
- Ignoring exceptions and user entity controls: SOC 2 exceptions and the controls the customer must operate are where real gaps sit.
- Point-in-time only: no monitoring between annual reviews, so incidents and ownership changes are missed.
- Forgetting machine access: supplier API keys and OAuth grants left active after offboarding.
Practitioner checklist
- Read the NICE OG-WRL-017 work role and three current TPRM job adverts in your target sector.
- Learn to read a SOC 2 Type 2 report end to end, including exceptions and complementary user entity controls.
- Learn NIST CSF 2.0 GV.SC and ISO/IEC 27001 Annex A 5.19 to 5.23 well enough to map a questionnaire to them.
- Build a sample tiering model and register with review dates.
- Write three model risk statements with cause, impact, owner and remediation date.
- If targeting financial services, read DORA register requirements and the current PRA SS2/21.
- Pick one certification that matches your background and next role.
- Always ask which accounts, API keys and OAuth grants a supplier will hold, and how they are removed at exit.
Standards and references
- NIST: NICE Framework current versions
- NIST: SP 800-161 Rev. 1, Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations
- NIST: Cybersecurity Framework 2.0
- Bank of England PRA: SS2/21 Outsourcing and third party risk management
- ISACA: CRISC certification
- DSIT: Cyber security skills in the UK labour market 2026
- US Bureau of Labor Statistics: Information Security Analysts
Related NHI Mgmt Group resources: Cybersecurity Careers Guide · Third-Party Risk Management Guide · How to Read a SOC 2 Report Guide · Cybersecurity Risk Manager Career Guide