Third-party risk assessment
Third-party and vendor risk assessments you can defend
Know which vendors can hurt you, and what you are doing about each one.
BlueRadius provides third-party and vendor risk assessment services for mid-market companies: we find the vendors that hold your data or can reach your systems, rank them by the damage they could do, review the critical ones properly, and build a process your team can keep running.
Your vendors are part of your attack surface. A SaaS platform, an MSP with remote access or a payroll provider can expose you as badly as a breach of your own network, and regulators, auditors and customers now expect you to show how you manage that risk.
When companies ask for vendor risk assessments
- An exam or audit finding says vendor oversight is missing or undocumented.
- A SOC 2 or ISO 27001 audit is coming and the vendor management controls have no evidence behind them.
- A customer's security questionnaire asks how you assess your own vendors.
- A vendor was breached and nobody could say quickly what data it held or what access it had.
- The vendor list has grown past what one person can track, especially with new AI tools arriving every month.
How we run a third-party risk assessment
1. Build the inventory
We pull vendors from accounts payable, single sign-on, contracts and conversations with each department, because no single source has them all. Shadow IT and free tools turn up here more often than anyone expects.
2. Tier by risk
Each vendor is tiered by the data it holds, the access it has to your systems and how badly an outage would hurt the business. The tier sets how deep the review goes, so your effort goes to the vendors that matter.
3. Due diligence on critical vendors
We review SOC 2 reports, ISO 27001 certificates and penetration test summaries, and send a security questionnaire based on a recognized standard such as the SIG or the CSA CAIQ where the evidence falls short. For SOC 2 reports we check scope, period, exceptions, carved-out subservice organizations and the complementary user entity controls you are expected to run.
4. Fourth parties
Your vendors have vendors. We identify the subprocessors and hosting providers behind your critical vendors, so a breach two steps away does not come as a surprise.
5. Contract terms
We check that contracts with critical vendors cover breach notification timelines, security requirements, audit rights, data return and deletion, and subprocessor changes. Where they do not, we give your counsel specific language to ask for at renewal.
6. Decide, record and follow up
Each vendor gets a risk rating, a decision and an owner. Where a vendor falls short, we agree remediation with them or document the compensating controls and the risk acceptance, which is exactly the record examiners and auditors ask for.
Keeping the program running
A one-time review is out of date within months. We set up the parts that keep it current: an intake step so new vendors are assessed before contracts are signed, reassessment on a schedule set by tier, monitoring for vendor breaches and security changes between reviews, and an offboarding checklist so access and data are removed when a relationship ends.
Radius360, our platform, holds the vendor register, links each vendor to its evidence and its risks, and tracks reassessment dates. When a vendor appears in the news, our vendor breach playbook covers the first hours.
AI vendors need their own questions
AI tools receive sensitive data through prompts and file uploads, often sit on top of model providers you never contracted with, and increasingly take actions in your systems. We assess where data goes, whether it is retained or used for training, and what the tool is allowed to do. See the questions we ask AI vendors.
Built to satisfy the people who will check
Banks answer to the Interagency Guidance on Third-Party Relationships, and non-bank financial companies such as lenders and mortgage firms to the FTC's GLBA Safeguards Rule; see our financial services practice. Healthcare organizations need business associate agreements and vendor review under HIPAA. Companies pursuing SOC 2, ISO 27001 or PCI DSS need evidence for CC9.2, the Annex A supplier controls or requirement 12.8, and NYDFS-regulated firms need a third-party service provider policy under section 500.11. We build the program once and map it to each.
Vendor risk is one part of the wider picture. A cybersecurity risk assessment puts it alongside your other risks, and a virtual CISO can own the vendor program day to day. For the data behind why this matters, read our Third-Party Cyber Risk Report 2026.
Who we work with
- Banks, credit unions and financial services firms preparing for exams
- Healthcare organizations managing business associates
- SaaS and technology companies answering customer questionnaires and preparing for SOC 2
- Mid-market companies with hundreds of vendors and no one assigned to review them
Frequently asked questions
What is a third-party risk assessment?
A review of the security risk a vendor brings into your business: what data it holds, what systems it can reach, how well it protects them, and what would happen to you if it were breached or went offline. The result is a decision on each vendor (approve, approve with conditions, or reject) and a record of why.
Is a vendor risk assessment different from a third-party risk assessment?
In practice, no. "Vendor" usually means suppliers you pay, such as SaaS platforms, MSPs and contractors. "Third party" is broader and can include partners, affiliates and anyone else with access to your data or network. The assessment method is the same.
Do we have to assess every vendor?
No, and trying to is why most vendor programs stall. We tier vendors by the data they hold, the access they have and how much the business depends on them. Critical vendors get a full review, moderate ones a lighter one, and low-risk vendors little more than a contract check.
Isn't a SOC 2 report enough?
It is a strong starting point, not the end. We check that the report covers the services you actually use, that the period is recent (or there is a bridge letter covering the gap), whether the auditor noted exceptions, which subservice organizations were carved out, and which complementary user entity controls the vendor expects you to run. Those last ones are often missed, and they are your responsibility.
Which regulations require vendor risk management?
Many do. Banks follow the Interagency Guidance on Third-Party Relationships issued in June 2023. The FTC's GLBA Safeguards Rule requires non-bank financial companies to oversee their service providers, NYDFS Part 500 has a dedicated third-party service provider section (500.11), PCI DSS requirement 12.8 covers service providers that handle cardholder data, and HIPAA requires business associate agreements. SOC 2 (CC9.2) and ISO 27001 (the Annex A supplier controls) expect a documented vendor process as well.
How do you handle AI vendors?
With extra questions. AI tools often receive sensitive data through prompts and uploads, may use it for training, and increasingly act inside your systems. We ask where data goes, whether it is retained or used for training, which model providers sit behind the product, and what the tool can do on its own. Our list of AI vendor questions is a good preview.
How often should vendors be reassessed?
Critical vendors at least once a year, others on a longer cycle based on their tier, and any vendor immediately when something changes: a breach in the news, a new service, broader access, or an acquisition. Continuous monitoring fills the gaps between reviews.
Start with your vendor list
Send us whatever you have, even a spreadsheet export from accounts payable, and tell us what is driving the work: an exam, an audit, a customer questionnaire or a vendor breach. We will scope the assessment around it. Book a 30-minute call.