Procurement
Third-party risk management for testing vendors
2026-09-24
Third-party risk management (TPRM) programmes sort suppliers into tiers and apply more scrutiny to the higher tiers. The tiering questionnaire usually asks whether the supplier hosts data, runs a production service or touches customers. A testing vendor answers "no" to most of those questions and lands in a low tier.
That outcome misses how testing work is done. This post sets out where a QA vendor sits in a TPRM programme and what procurement should ask for at onboarding.
Why testing vendors carry more inherent risk than they appear to
Inherent risk comes from access. A testing team typically has:
- Source and test code access. Automation engineers work in your repositories and see unreleased features.
- Pipeline and environment credentials. Tests run in your build pipeline and against staging systems, sometimes with privileged accounts.
- Exposure to personal data. Test environments are often seeded from production. Even where they are not, logs, screenshots and support tickets can contain personal data.
- Knowledge of weaknesses. Testers find defects, including security defects, before anyone outside the company knows about them.
The 2023 US interagency guidance on third-party relationships says that not all relationships present the same level of risk, and that banking organisations should tailor oversight to the risk of each relationship. It also says that due diligence should be tailored to the specific activity the third party will perform. For a testing vendor, the activity is access to code, systems and data.
Rate the relationship on what the vendor will touch
Replace the generic tiering questions with specific ones:
- Which repositories, pipelines and environments will the vendor use?
- Will any tester have access to production, even read-only?
- Will testers see personal data, card data or health data, and in which environments?
- Where will the testers be located, and will any subcontractor be involved?
- How hard would it be to replace the vendor mid-release?
The answers set the tier. A vendor doing exploratory testing on a public marketing site is a different risk from one maintaining the regression suite for a payments service.
Onboarding requirements that match the risk
Security evidence. Ask for the ISO 27001 certificate with its number, scope and expiry, or a SOC 2 Type II report covering a recent period. Check the certificate with the issuing body. ISO/IEC 27036 and NIST SP 800-161 both treat supplier security as something the acquirer verifies and monitors, not something it assumes.
Data terms. If testers may process personal data on your behalf, the data processing terms need to be signed before they start. Default to synthetic or masked test data, and require written approval for any exception.
Subcontracting. Many testing vendors use freelancers or partner firms to cover peaks or niche skills. The interagency guidance lists subcontracting as a contract negotiation factor and notes the risk that comes from having no direct relationship with the subcontractor. Require disclosure and prior written consent.
Access management. Named accounts, least privilege, multi-factor authentication and removal of access within an agreed time when someone leaves the team.
Exit. The EBA outsourcing guidelines ask institutions to have a documented exit strategy for critical or important functions and to be able to exit without undue disruption. Even outside banking, agree at onboarding how test assets, documentation and knowledge will come back to you.
Regulated buyers
If you are an EU financial entity, a testing service may fall under the Digital Operational Resilience Act (DORA). Article 28 requires financial entities to assess risks and undertake due diligence before entering into a contractual arrangement for ICT services, and Article 30 lists the key contractual provisions, including where services are provided and data processed, and termination rights. Your risk or compliance team will know whether the testing service is in scope. Ask them before the RFP goes out, not after selection.
The EBA has published guidelines on third-party risk for non-ICT services which, once applicable, will repeal the 2019 outsourcing guidelines. Check with your compliance team which set applies to your arrangement and when.
Monitoring after onboarding
TPRM does not stop at signature. The interagency guidance describes a life cycle that continues through ongoing monitoring and termination. For a testing vendor, useful monitoring points include:
- a quarterly access review of every account the vendor holds;
- a check that the named team is still the team doing the work;
- renewal dates for certificates and assurance reports;
- any new subcontractor or change of location.
What this means for your selection
Use the due diligence checklist to record the access, evidence and data terms for each shortlisted vendor, and the contract clause builder for subcontracting, data processing and exit terms. The questionnaire includes questions on access and team location. For more detail, read the guides on the vendor security questionnaire, how to verify ISO 27001 and SOC 2, test data and GDPR and exit planning.
Questions buyers ask
- Should a QA vendor go through the same onboarding as a cloud provider?
- Not necessarily the same depth, but the same method. Rate the inherent risk from the access and data involved, then scale the due diligence to that rating. Guidance from US banking regulators says the scope of due diligence should match the level of risk and complexity of the relationship.
- Is a vendor's ISO 27001 certificate enough?
- It is evidence, not a conclusion. Check that the certificate is current, issued by an accredited body, and that its scope covers the sites and services that will work for you.
Sources
- Interagency Guidance on Third-Party Relationships: Risk Management (2023), US Federal Reserve, FDIC, OCC
- Regulation (EU) 2022/2554 (DORA), including Article 30 key contractual provisions, European Union
- ISO/IEC 27036-1:2021 Cybersecurity, Supplier relationships, Part 1: Overview and concepts, ISO/IEC
- NIST SP 800-161r1 Cybersecurity Supply Chain Risk Management Practices, NIST
- Final Report on the Guidelines on outsourcing arrangements (EBA/GL/2019/02), European Banking Authority
- Guidelines on third party risk management, European Banking Authority