Most organisations assess the suppliers they pay, while the incidents that hurt them increasingly start at the suppliers those suppliers depend on. A SaaS vendor's hosting provider, a processor's sub-processor, an integration partner's own cloud account or a managed service provider's remote access tool are all outside your contracts and usually outside your view. Fourth-party risk is the exposure created by those indirect relationships, and nth-party risk extends it down the chain. This guide covers how to find fourth parties that matter, how to prioritise them, which contract terms reach them, how to monitor and respond, and what changes for identities and tokens held deep in the chain. It is for TPRM leads, procurement, privacy and security architects. It builds on the Third-Party Risk Management Guide and goes deeper than the shared-dependency section of the Third-Party Concentration Risk Guide.
Key takeaways
- You cannot assess every fourth party, and you should not try. Map fourth parties only behind your critical services and the suppliers that hold your data or credentials.
- Your leverage runs through your tier 1 contract. Notice of new subcontractors, the right to object, flow-down of security terms and supplier liability for subcontractors are the tools that reach the fourth party.
- Judge the supplier's oversight, not the subcontractor directly. The US interagency guidance of June 2023 frames it this way: assess how your supplier selects and oversees its subcontractors.
- Aggregation is the real fourth-party risk. When several critical suppliers share one hosting, identity or integration provider, a single failure hits all of them at once.
- Tokens travel down the chain. OAuth grants and API keys you issue to one supplier can end up stored in its provider's cloud, which is how a breach several steps away reaches your data.
What fourth-party and nth-party risk is
A third party is a supplier you contract with directly. A fourth party is a supplier to that third party that supports the service you receive, and an nth party is any supplier further down. You have no contract with them, no audit rights and often no notice when they change. The common forms are:
- Sub-processors: organisations processing personal data on your processor's behalf, which GDPR and UK GDPR Article 28 require to be authorised and bound by equivalent terms.
- Subcontracted services: outsourced support desks, development teams, data centres or managed security services used by your supplier.
- Platform dependencies: the cloud provider, identity provider, DNS, CDN or payment network your SaaS supplier runs on.
- Integration chains: an app you connect to your SaaS platform, which itself stores tokens in another provider's environment.
- Software components: open source and commercial components inside the products you buy. See the SBOM Guide.
The practical difference from third-party risk is visibility and leverage. You can assess a tier 1 supplier directly, but for fourth parties you rely on what the supplier discloses, what its assurance reports cover and what you can observe from outside, so the programme is built around disclosure obligations and evidence rather than direct assessment.
How fourth-party exposure reaches you
| Pathway | What happens | What you can usually see |
|---|---|---|
| Integration provider compromise | Attacker steals tokens your SaaS tenant granted to a connected app and uses them through the trusted app | Connected app inventory and OAuth consent logs in your own tenant |
| Supplier's cloud or code platform | Attacker reaches the supplier's source code or cloud account, then the secrets it stores for customers | Very little; only the supplier's disclosure |
| Support or service desk subcontractor | Outsourced agents are socially engineered or their accounts misused to reach customer environments | Help desk procedures you require; sign-in logs for supplier-initiated changes |
| Sub-processor data breach | Your personal data, held by a processor's sub-processor, is stolen | Sub-processor list; notification from the processor |
| Shared platform outage | A hosting, DNS or identity provider fails and several of your suppliers stop at once | Fourth-party disclosures, status pages, external fingerprinting |
| Compromised component or update | A component or update path deep in a product is compromised | SBOM and vendor advisories |
The Salesloft Drift breach shows the chain clearly. An intruder in Salesloft's GitHub account reached Drift's AWS environment, where OAuth tokens for customers' Salesforce integrations were stored, and used them to export Salesforce records in August 2025; Google Threat Intelligence Group said it was aware of over 700 potentially impacted organisations. For Salesforce customers, Drift was a third party, but the AWS environment and the GitHub foothold were steps further down.
Mapping beyond tier 1
Start from your critical business services and the suppliers that hold your data or credentials, then work down. Use several methods, because none is complete.
| Method | What it reveals | Reliability | Effort |
|---|---|---|---|
| Sub-processor lists | Named organisations processing personal data | High for personal data; silent on other services | Low |
| Assurance reports (for example SOC 2) | Subservice organisations and whether their controls are included or carved out of the report | Medium; carve-outs mean the fourth party was not tested | Low to medium |
| Questionnaire on critical subcontractors | Hosting, identity, support, development and security providers | Depends on supplier honesty and knowledge | Medium |
| Contractual notice obligations | Changes as they happen | High if enforced | Low after contracting |
| External technical discovery | Hosting, DNS, CDN and email providers visible from the internet | Good for infrastructure; nothing on people or processes | Medium |
| Your own tenant data | Connected apps, their publishers and the scopes they hold | High for integration chains | Low |
| SBOM and vendor advisories | Software components and their suppliers | Variable by vendor | Medium |
Record fourth parties as attributes of the supplier relationship in the supplier register: name, service supported, data or credentials it holds, location and source of the information. Re-check annually for critical suppliers and at renewal for others.
Prioritising which fourth parties matter
Score each identified fourth party on two dimensions and act on the top of the list.
- Criticality: does it support a critical service, hold your personal or confidential data, or hold credentials and tokens that can reach your environment?
- Aggregation: how many of your critical suppliers depend on it? Count them. A hosting or identity provider behind five critical suppliers is a concentration point even if each supplier looks resilient alone.
- Substitutability: could your supplier move off it, and how long would that take? Ask, and record the answer.
- Jurisdiction: where is the fourth party established and where does it process data? This drives transfer rules and regulatory access.
Fourth parties that score high on criticality and aggregation feed into concentration analysis and scenario testing. See the Third-Party Concentration Risk Guide and the Cloud Concentration Risk and Exit Strategy Guide.
Contract terms that reach the fourth party
You have no contract with a fourth party, so every control flows through the tier 1 agreement.
| Term | Purpose | Source that supports it |
|---|---|---|
| Prior authorisation and change notice for sub-processors, with a right to object | No new sub-processor without your knowledge | GDPR Article 28(2) and 28(3)(d), as explained by the ICO |
| Flow-down of equivalent obligations | Security and data protection terms reach the subcontractor | GDPR Article 28(4) |
| Supplier remains liable for subcontractors | Your claim stays against the party you contract with | GDPR Article 28(4); US interagency guidance subcontracting provisions |
| Notice of use or planned use of subcontractors, and the right to bar specific ones | Control over who supports critical activities | US interagency guidance on third-party relationships (2023) |
| Reporting on integral subcontractors' performance, audits and compliance | Evidence without direct audit rights | US interagency guidance (2023) |
| Termination without penalty for unauthorised subcontracting | An exit if the chain changes against the contract | US interagency guidance (2023) |
| Incident notice covering subcontractor incidents | Your clock starts when the fourth party is breached, not when the supplier decides it matters | Contract practice; GDPR Article 33(2) for processors |
EU financial entities should also check DORA's requirements on subcontracting of ICT services and on recording subcontractors in the register of information. See the DORA ICT Third-Party Risk and Register of Information Guide and the Third-Party Security Contract Clauses Template.
Where identity fits
Credentials are what make fourth-party compromise immediately usable. When you connect an app to a SaaS platform, the refresh token often lives in the app vendor's cloud, protected by that vendor's own access controls and its cloud provider. When you open a support case, diagnostic files may carry session tokens; in the Okta support system breach, customer HAR files with session tokens were taken from the support system.
- Know where your tokens live: for each connected app, record the publisher and where it says tokens are stored.
- Minimise what travels: grant the narrowest scopes, prefer short-lived tokens and restrict tokens by IP where the platform allows. See the SaaS and OAuth App Governance Guide.
- Sanitise what you share: strip tokens and secrets from support uploads and tickets.
- Plan to revoke in bulk: be able to revoke all tokens for one app across your tenant in minutes. See the OWASP NHI Top 10 NHI3 Vulnerable Third-Party NHI Guide.
Monitoring and responding to fourth-party events
- Subscribe to changes: sub-processor change notices, supplier trust pages and status pages for the fourth parties behind critical services.
- Watch threat intelligence by name: track fourth parties on your priority list in breach and leak monitoring, not just tier 1 suppliers.
- Ask fast when something breaks: when a widely used provider is breached, send a standard question to every tier 1 supplier that might use it: do you use it, for which service, and was our data or credential stored there?
- Act on your own side: revoke or rotate tokens held by the affected chain without waiting for confirmation, using the Third-Party Incident Response Playbook.
- Feed back into tiering: a fourth-party incident is a reassessment trigger for every supplier that depends on it.
Implementation roadmap
- Weeks 1 to 4, scope: list critical business services and the tier 1 suppliers behind them, plus every supplier that holds personal data, confidential data or credentials. This is usually a small fraction of the supplier base.
- Weeks 3 to 8, quick data: collect sub-processor lists, assurance reports and connected app inventories you already have rights to. Record the obvious platform dependencies from external discovery.
- Months 2 to 4, ask: send critical suppliers a short subcontractor questionnaire covering hosting, identity, support, development, security operations and where tokens or secrets they hold for you are stored.
- Months 3 to 6, analyse: compute aggregation, flag carve-outs and unknowns, and agree a short list of fourth parties that need scenario testing or contingency plans.
- At each renewal, contract: add notice, objection, flow-down, liability and subcontractor incident terms. Do not reopen every contract at once.
- Test: run a tabletop in which a widely used provider is breached and measure how long it takes to name affected services and revoke related tokens.
- Sustain: refresh critical supplier fourth-party data annually and on any trigger, such as an acquisition, a new sub-processor or an incident in the chain.
If the questionnaire stage stalls because suppliers will not disclose subcontractors, record the refusal as a risk factor in their tiering rather than abandoning the mapping.
Decision guidance
- Small organisations: collect sub-processor lists and the hosting provider for your five to ten most important suppliers, keep connected app inventories in your main SaaS platforms, and put sub-processor notice terms into new contracts.
- Large or regulated organisations: add fourth-party fields to the supplier register, compute aggregation across critical services, require subcontractor reporting from critical suppliers and test the top concentration points in scenario exercises.
- Questionnaire or discovery: questionnaires reveal people and process dependencies; discovery reveals infrastructure. Use both for critical suppliers; discovery alone for the long tail.
- Object or accept a new sub-processor: object where it adds a new jurisdiction, takes custody of credentials or data you consider sensitive, or increases aggregation on a provider you already rely on heavily.
Measuring it
| Metric | Why it matters |
|---|---|
| Critical suppliers with fourth parties recorded | Coverage of the mapping effort |
| Fourth parties supporting three or more critical services | Aggregation hotspots to test and plan for |
| Critical contracts with sub-processor notice and flow-down terms | Contractual reach into the chain |
| Connected apps with known token storage location and owner | Identity exposure through integration chains |
| Time to answer "are we exposed?" after a widely used provider is breached | Readiness of the mapping in a real event |
Framework mapping
| Framework | Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.SC-04, GV.SC-05, GV.SC-07 | Suppliers prioritised by criticality; requirements in contracts; supplier risks understood and monitored |
| NIST CSF 2.0 | ID.AM-04 | Inventories of services provided by suppliers |
| NIST SP 800-53 Rev. 5 | SR-3, SR-6, SA-9 | Supply chain controls and processes, supplier assessments, external system services |
| NIST SP 800-161 Rev. 1 | C-SCRM practices | Supply chain risk across tiers |
| ISO/IEC 27001:2022 Annex A | 5.19, 5.20, 5.21 | Supplier relationships, supplier agreements, managing security in the ICT supply chain |
| GDPR and UK GDPR | Article 28(2), 28(3)(d), 28(4) | Sub-processor authorisation, flow-down and liability |
Common failure patterns
- Stopping at the contract boundary: the supplier register lists only tier 1, so a breach at a widely used provider takes days to map to affected services.
- Accepting carve-outs unread: an assurance report excludes the hosting or support subcontractor, and nobody asks how that provider is assured.
- Ignoring sub-processor notices: change emails arrive and are filed, so objections are never raised within the window.
- Treating integrations as features: connected apps are approved by users or admins without anyone recording that they hold long-lived tokens in another vendor's cloud, as Drift's customers found.
- Counting suppliers, not dependencies: ten suppliers look diverse until it emerges that most run on the same identity or hosting provider.
- Trying to audit everyone: effort is spread across hundreds of fourth parties instead of the few that matter.
Practitioner checklist
- Identify fourth parties behind every critical service and every supplier holding your data or credentials.
- Add fourth-party fields to the supplier register and record the source of each entry.
- Collect sub-processor lists and subscribe to change notices; set an owner to review them.
- Read assurance reports for subservice carve-outs and follow up on critical ones.
- Count aggregation across critical suppliers and test the top concentration points.
- Put notice, objection, flow-down, liability and subcontractor incident terms in critical contracts.
- Inventory connected apps with publisher, scopes and token storage location.
- Prepare a standard "do you use this provider?" question and bulk token revocation steps for fourth-party incidents.
Standards and references
- NIST: Cybersecurity Framework 2.0
- NIST: SP 800-161 Rev. 1, Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations
- NIST: SP 800-53 Rev. 5
- Federal Register: Interagency Guidance on Third-Party Relationships, Risk Management
- ICO: What needs to be included in the contract
- NCSC: Principles of supply chain security
- EUR-Lex: Regulation (EU) 2022/2554 (DORA)
Related NHI Mgmt Group resources: Third-Party Concentration Risk Guide · Third-Party Risk Management Guide · NIST SP 800-161 Cyber Supply Chain Risk Management Guide · Vendor Offboarding and Termination Guide