Rank the vendors your business can’t easily lose, verify the safeguards that matter, and plan how you’ll keep working or leave before a dependency becomes a disruption.

Key Takeaways:
- What is third-party risk management?
- Which vendors deserve the deepest review?
- What should happen if a critical vendor fails?
Which vendor could interrupt your ability to deliver, collect payment, or protect customer information, even if your own systems were working?
An engineering firm’s drawings are due today. The team’s ready, but the client portal is down. The latest files are inside it.
The firm checked the subscription price before signing. Nobody asked whether the team could retrieve its drawings during an outage.
“Build Trusted Relationships” is an Attentus core value. For this firm, that starts with asking the vendor a specific question before the next deadline: “If the portal goes down, how do we get our files?”
Third-party risk management helps you work out which vendor relationships deserve closer attention, what you need to verify, and what you’ll do if a supplier lets you down.
What’s my action item? Pick one customer deadline this week. Write down which vendor could make you miss it and what you’d lose access to.
Bring Attentus the name of the vendor your next deadline depends on. Let’s work through how you’d deliver if it went offline.
What Is Third-Party Risk Management?
Third-party risk management identifies, assesses, and manages risks created by outside organizations your business relies on for software, cloud, consultancy, support, payment processing, and other services.
It all starts with a short record answering these essential questions:
- Who are our vendors and what business activity do they support?
- Who owns the relationships internally, and who reviews technical or compliance concerns?
- What data does each vendor handle, which systems can they access, and what permissions do they have?
- What stops if any of your vendors’ services fail? Is there a usable alternative?
- How critical is this vendor? What evidence supports its claims, and who’s following up on any gaps?
- When are the renewal or exit dates, when is the next review, and who owns the fallback plan?
What’s my action item? Open your vendor list. For each supplier with access to sensitive files, record who owns the relationship and what the supplier can reach.
Which Vendors Deserve the Deepest Review?
Resist the urge to compare vendors purely on cost. A service with a small invoice doesn’t always bring small exposure. The opposite is equally true.
As a rule of thumb, prioritize deep reviews for vendors who:
- Could seriously hurt your business if their service failed.
- Handle your sensitive business and customer data.
- Have the most system and data access.
- Would be hard to replace.
These are the most critical. Check if they have relevant safeguards.
They aren’t the only ones to review, though.
You should ideally have three review tiers:
| Review tier | Which vendors belong here? | What to check? |
| Critical | Vendors whose failure could stop important work, disrupt a customer commitment, expose sensitive data, or prove difficult to replace. | Relevant security evidence, recovery capability, access controls, dependencies, and a tested fallback or exit plan. |
| Elevated | Vendors whose failure would disrupt a team or process, but whose impact could be easily contained. | Key safeguards, unresolved gaps, responsibilities, and whether a usable workaround exists. |
| Routine | Vendors whose failure would have limited impact and whose services are easy to replace. | Basic supplier verification, appropriate terms, and changes that might require a closer review. |
If two vendors look equally critical, compare the first customer commitment each outage would break. Explore how Attentus’s I.T. consultants can help you set review priorities.
What’s my action item? Rank your client portal and one low-impact subscription using the table above. Give the deeper review to the one that could stop a delivery.
What Evidence Should You Request?
Ask for evidence that matches the promise you’re relying on. If a vendor says it can restore your files, ask when it last tested that process and what the test showed.
For example:
- If a vendor handles sensitive information, ask who can access it, who reviews permissions, and how quickly access is removed when someone leaves.
- If an outage could interrupt your work, ask which other services the vendor needs to recover and whether they were included in its last test.
- If you’re worried about being locked in, ask what data you can export, how long retrieval takes, and whether the exported files will be usable elsewhere.
Review evidence for scope, date, exceptions, and responsibility. An assurance report or certificate can be helpful here, but check whether it covers the actual service you use.
These recommendations align with NIST SP 1326 guidance, which calls for thorough validation and encourages assessing resilience and sub-tier dependencies.
If a vendor’s report leaves you unsure who can reach your customer data, explore Attentus’s cybersecurity services for help reviewing that access.
What’s my action item? Replace “Do you test recovery?” with “What did your last test restore, and how long did it take?” Name the person who’ll review the answer.
Who Decides Whether the Remaining Risk Is Acceptable?
Another Attentus core value is “Be the Answer.” When a vendor review turns up a gap, one person in your business should own the decision and let the affected team know what’ll happen next.
Procurement can clarify terms, I.T. can assess technical evidence, and legal or compliance can review obligations. Give each question to someone who can answer it.
Can you proceed with a safeguard, limit access while the vendor makes a fix, or choose another provider? If you accept the risk, record who’s authorized to make that call.
Write down what could happen, who’ll act, and when the fix or exception comes up for review.
Have the right reviewers check the terms for access, notifications, recovery, and data export. If the vendor won’t negotiate, assess your alternatives before accepting the risk.
What’s my action item? Take one open vendor issue to the person who can accept the risk or require a fix. Record the decision, owner, and due date.
When Should a Vendor Be Reviewed Again?
Review critical vendors on a schedule and when something changes. A new subcontractor, broader data access, repeated outages, or an upcoming renewal can all warrant another look.
Each review doesn’t need to start from scratch. Check what has changed, whether agreed fixes were completed, and whether your fallback still works.
What’s my action item? Choose one change that should trigger a fresh review, such as broader access to customer files. Record who’ll reopen the review when it happens.
Could Two Vendors Depend on the Same Weak Point?
Always remember that vendors have suppliers of their own, and any of them can affect your service, too. That’s known as fourth-party risk.
Also consider supplier concentration risk. Two vendors may share a hosting, identity, or payment service. An outage there could take both your main service and its backup offline.
So what should you do about it?
Start with one critical vendor. Ask which outside service it relies on, then find out whether your backup relies on that same service.
What’s my action item? Ask your primary vendor and your backup which sign-in service they use. If it’s the same one, test how you’d get in during an outage.
What Should Happen If a Critical Vendor Fails?
Use your existing response plan. The vendor’s contact can confirm what’s down. The person who owns the relationship on your side should decide when to switch routes and tell the team.
If compromise or unsafe access is suspected, have the authorized technical responder assess containment under the plan. Protect necessary records and coordinate required notifications with the appropriate advisers.
If the engineering firm’s backup route works, its project lead can send the drawings. If it fails, that same lead calls the client, explains what’s delayed, and agrees on the next update.
What’s my action item? Have the person covering the next deadline try the backup route with a sample deliverable. Record where they get stuck and who’ll fix it.
Can You Leave Without Losing Data or Access?
Sometimes the right decision is to leave a supplier. Maybe the service no longer meets your needs, the risks are too difficult to manage, or perhaps you’ve found a better alternative.
Whatever the reason, the move shouldn’t disrupt your business.
Before leaving a critical vendor, export a representative set of files. Check how long retrieval takes, whether anything’s missing, and whether your team can open the files elsewhere.
When the time comes, sequence migration, verification, and access removal so the transition doesn’t create its own outage. Confirm agreed deletion or retention handling and revoke obsolete vendor accounts, tokens, and permissions.
What’s my action item? Export a sample project and open it outside the vendor’s platform. Note any files, formats, or permissions you’d need before switching.
Frequently Asked Questions About Third-Party Risk Management for SMBs
1. What is third-party risk management?
It’s a repeatable way to understand and manage the risk created by outside organizations your business depends on, from selection through ongoing use and exit.
2. Which vendors deserve the deepest review?
Prioritize vendors whose failure, access, or data exposure could seriously affect the business, especially when replacement is difficult. Review depth should reflect that exposure, not contract value alone.
3. What should happen if a critical vendor fails?
Activate the designated owner and existing response/continuity plan, verify what’s affected, and use the approved workaround when its trigger is met. Assess security concerns separately and communicate confirmed facts.
4. Does a completed questionnaire mean the vendor is safe?
No. Responses need relevant evidence, interpretation, and follow-up. Record the decision and any gaps. Review them again when the service, access, or risk changes.
Trust Needs Clear Expectations and Follow-Through
Before the next deadline, the engineering firm and its vendor can run a simple test: retrieve a current drawing while the usual portal is unavailable.
That’s how the firm builds trust with its vendor. Both sides see what worked, agree on any fix, and know who’ll call the client if a delivery is at risk.
Keep the test result with the vendor record so the next project lead can find it when a deadline’s approaching.
What’s my action item? Before your next renewal meeting, send the vendor your biggest open question. Agree on who’ll resolve it, by when, and what evidence will close it.
Prioritize Your Critical Vendors
Start with the supplier that would put your next delivery or payment run at risk.
Contact Attentus to review your most critical vendor. Bring its latest recovery report and your renewal date so we can help you decide what to verify before you sign.