Industries

Third-party risk by industry: a practitioner's map

The vendor lifecycle is the same in every sector. What changes is which rule puts a vendor in scope, what critical means, and which artifact an examiner expects to see. This page is the map of the industry guides and the regulations that already name those duties.

By the Rescana research team

A third-party risk program that works for a software company does not automatically work for a bank, a hospital, or a water utility. The lifecycle is shared: know the vendor, assess it, contract, monitor, and exit. The sector changes the trigger, the harm, and the artifact you have to be able to produce. NIST CSF 2.0, published 26 February 2024, says in its abstract that it offers outcomes any organization can use, regardless of sector, and that it does not prescribe how those outcomes are achieved. The sector rules below are the ones that name a vendor duty.

Why the sector changes the program

Three things move when the sector changes, and the lifecycle is not one of them. The trigger is what puts a vendor in scope: protected health information, cardholder data, nonpublic information, an ICT service supporting a financial entity, or remote access into an operational network. The harm is what a failure costs: a payment system, patient care, a physical process, or a tenant full of company data. The artifact is the thing an examiner asks to see: a business associate agreement, a written third-party policy, a register of ICT arrangements, or a supply-chain risk plan tied to a specific purchase. A questionnaire that ignores those three will look complete and still miss the duty that applies.

CISA recognizes 16 critical infrastructure sectors in the United States, including financial services, healthcare and public health, energy, and information technology. Software delivered as a service is not its own entry on that list. SaaS shows up inside the other sectors, which is why the SaaS guide below stacks on top of a sector rule rather than replacing it.

What this cluster covers

Third-party risk for SaaS

The distinct problem is the inventory and the tenant, not a single statute. Teams adopt applications outside procurement, each integration holds standing access into other systems, and a SOC 2 report describes the vendor's service rather than whether your tenant enforces MFA or which OAuth grants are still live. The page covers how to discover those vendors, tier them by data and privilege, and offboard the grants along with the subscription.

Third-party risk in critical infrastructure

Operators in energy, water, transport, and the other sectors CISA and NIS2 name inherit ordinary IT vendors plus operational-technology suppliers that are hard to replace, slow to patch, and often hold persistent remote access. NIS2 lists supply chain security, including security-related aspects of relationships with direct suppliers and service providers, among the minimum risk-management measures. The page maps that duty, together with NERC CIP-013 and CIRCIA, onto a program that can actually be run, and it is explicit about what an outside-in scan cannot see.

Third-party risk in financial services

A US banking organization works from the 2023 interagency guidance, which is supervisory guidance, plus the binding duties next to it: safety and soundness, the service-provider section of the Interagency Guidelines, the Bank Service Company Act, and the incident notification rule. An EU financial entity has DORA. The page maps the two side by side, from critical activities and the life cycle to the Register of Information, the Article 30 contract terms, and exit plans.

Third-party risk in healthcare

The business associate definition decides which vendors need an agreement, and many clinical suppliers are not business associates at all. The page covers the agreement as a gate, the breach notice clock, medical device and clinical suppliers, 42 CFR Part 2, and what the Change Healthcare incident showed about clearinghouse concentration.

Banks and other financial firms

For U.S. banking organizations the primary text is the Interagency Guidance on Third-Party Relationships (Federal Register, 9 June 2023), issued jointly by the Federal Reserve Board, the FDIC, and the OCC. The guidance organizes the relationship into five stages: planning, due diligence and third-party selection, contract negotiation, ongoing monitoring, and termination. It states that sound third-party risk management takes into account the level of risk, complexity, and size of the banking organization and the nature of the relationship. OCC Bulletin 2023-17 transmits that guidance. The bulletin uses "banks" for national banks, federal savings associations, covered savings associations, and federal branches and agencies of foreign banking organizations, and it says the guidance outlines the third-party risk management life cycle and that not all third-party relationships present the same level of risk or criticality. In September 2026 the agencies, joined by the NCUA, proposed replacement guidance; until it is finalized, the 2023 text is current.

EU financial entities have a separate, binding regime. Regulation (EU) 2022/2554 (DORA) applies from 17 January 2025, and Chapter V is titled Managing of ICT third-party risk. The register, the pre-contract assessment, and the contract clauses are broken down on DORA and third-party risk.

Two narrower U.S. rules sit alongside that guidance. Their scopes overlap with it and with each other, so one firm can be subject to more than one: a New York state-chartered bank, for example, is under the interagency guidance and 23 NYCRR 500.11 at the same time. 23 NYCRR 500.11 requires each DFS-covered entity to keep written policies and procedures for the security of information systems and nonpublic information that third-party service providers can access or hold, including due diligence on those providers. The FTC Safeguards Rule at 16 CFR 314.4(f) requires financial institutions within the Commission's jurisdiction (section 314.1) to select and retain service providers capable of maintaining appropriate safeguards, bind them by contract, and periodically assess them based on the risk they present. Banks are outside the FTC rule. Their GLBA counterpart is the Interagency Guidelines Establishing Information Security Standards (for national banks, 12 CFR part 30, appendix B), which include a service-provider oversight duty, and the 2023 interagency guidance sets the broader life cycle on top. The detail is on NYDFS Part 500 and the GLBA Safeguards Rule, and the full map of US and EU duties for banks is on third-party risk in financial services.

Healthcare

Healthcare vendor risk turns on one definition. Under 45 CFR 160.103, a business associate includes a person who, on behalf of a covered entity, creates, receives, maintains, or transmits protected health information for a regulated function, and the same definition reaches a subcontractor who does that work on behalf of the business associate. 45 CFR 164.504(e) then requires a contract that establishes the permitted and required uses and disclosures of that information. A billing service, or any other vendor processing clinical data on a covered entity's behalf, is in that category. The contract contents, the subcontractor chain, and the breach clock are on HIPAA and third-party risk. Clinical suppliers, device vendors, and clearinghouse concentration are on third-party risk in healthcare.

Card payments cut across sectors

A hospital, a retailer, and a bank can all have a vendor that stores, processes, or transmits cardholder data. The duty then comes from PCI DSS, published by the PCI Security Standards Council, rather than from the sector license alone. What the customer has to collect from that vendor is covered on PCI DSS and third-party risk.

How to pick the page that applies

Start from the vendor's access, then add the sector. If the exposure is an application teams connected without a procurement record, read the SaaS guide first, then the sector rule that matches the data. If the vendor can affect a physical process or holds remote access into operational technology, read the critical infrastructure guide. If the vendor touches protected health information, the business associate analysis applies whether or not the company calls itself a healthcare company. If the organization is a U.S. banking organization, read the 2023 interagency guidance for the shape of the program. If it is an EU financial entity, read DORA. A single vendor often needs more than one of these. The underlying work still starts with tiering so the depth of review matches the access.

Where tools fit

No platform satisfies a sector rule by itself. Workflow and GRC platforms such as OneTrust and ProcessUnity are built to hold the named artifacts: the contract, the policy, the register entry, the assessment record. Security-rating providers such as BitSight and SecurityScorecard add an outside-in view of internet-facing posture, which helps triage a large portfolio and cannot see a tenant's settings, a business associate's internal safeguards, or a segmented operational site. Rescana also works from the vendor's externally observable footprint, with the same limits; it validates vendor claims against live attack-surface signal and chases findings to closure under your approval. The sector page is still where you learn which artifact you have to be able to show an examiner.

Frequently asked questions

How does third-party risk management differ by industry?

The lifecycle does not change. The sector changes the trigger that puts a vendor in scope, the harm a failure causes, and the artifact an examiner expects. NIST CSF 2.0, published 26 February 2024, describes outcomes any organization can use and does not prescribe how to achieve them. A bank still has the 2023 interagency guidance or DORA. A vendor that handles protected health information still needs a business associate contract under 45 CFR 164.504(e). A critical infrastructure operator still has the supply-chain duty in NIS2 where that directive applies, and the sector guide covers the other regimes that sit alongside it.

Which industries have specific rules for third-party vendors?

CISA lists 16 U.S. critical infrastructure sectors, including financial services, healthcare and public health, energy, and information technology. The vendor duties are in the sector rules, not in that list: the 2023 interagency guidance for U.S. banking organizations, DORA for EU financial entities from 17 January 2025, 23 NYCRR 500.11 for New York DFS-covered entities, the FTC Safeguards Rule for financial institutions in the FTC's jurisdiction, HIPAA for vendors that handle protected health information, and NIS2's supply-chain measure for essential and important entities. PCI DSS, published by the PCI Security Standards Council, adds a card-data duty that can apply inside any of those sectors.

What third-party risk rules apply to banks?

U.S. banking organizations follow the Interagency Guidance on Third-Party Relationships, issued by the Federal Reserve, the FDIC, and the OCC and published in the Federal Register on 9 June 2023. It sets five stages: planning, due diligence and third-party selection, contract negotiation, ongoing monitoring, and termination, scaled to the risk, complexity, and size of the banking organization and the nature of the relationship. OCC Bulletin 2023-17 transmits that guidance to national banks, federal savings associations, covered savings associations, and federal branches and agencies of foreign banking organizations. EU financial entities follow DORA, Regulation (EU) 2022/2554, which applies from 17 January 2025 and devotes Chapter V to ICT third-party risk. In September 2026 the agencies, joined by the NCUA, proposed replacement guidance; until it is finalized, the 2023 text is current. The FTC Safeguards Rule is a different scope: section 314.1 limits it to financial institutions within the FTC's jurisdiction. Banks are outside it; their GLBA counterpart is the Interagency Guidelines Establishing Information Security Standards (12 CFR part 30, appendix B for national banks). Scopes can overlap: a New York state-chartered bank, for example, is under both the interagency guidance and 23 NYCRR 500.11.

When does a healthcare vendor need a business associate agreement?

When the vendor, on behalf of a covered entity, creates, receives, maintains, or transmits protected health information for a function regulated by HIPAA. That is the business associate definition at 45 CFR 160.103, and it also covers a subcontractor that does the same work for the business associate. 45 CFR 164.504(e) requires a contract that sets the permitted and required uses and disclosures of that information. A vendor with no access to protected health information is outside that definition.

How should a company manage third-party risk from SaaS applications?

Treat discovery as part of the program, because many applications are adopted outside procurement and do not appear on the vendor list. Tier them by the data and the access the integration holds, not by the size of the contract. A SOC 2 report covers the vendor's service, not the customer's tenant settings or live OAuth grants, so the assessment has to include those. Cancelling the subscription does not revoke a token, so offboarding has to include the integration. The same vendor may also be in scope for HIPAA, PCI DSS, or a financial-sector rule if the data it holds triggers one.

What third-party risk requirements apply to critical infrastructure operators?

It depends on the regime that covers the operator. NIS2 requires essential and important entities to address supply chain security, including relationships with direct suppliers and service providers. CISA's list of 16 sectors is the U.S. map of which industries count as critical infrastructure; it is not itself a vendor-contract rule. Operational-technology suppliers add a practical difference: they are hard to replace, patching depends on outage windows, and remote access is often the real perimeter. The critical infrastructure guide covers NIS2 alongside NERC CIP-013 and CIRCIA.