- SOC 2 Readiness
- 24/7 incident line
- 24/7 security operations team
Third-Party Access Review Checklist
Vendors, MSPs and contractors often hold the keys to your environment. Check whether you know who has access, to what, and whether you could see it being misused.
20 checks across 6 areas. Your answers stay in your browser.
Overall Progress
0 of 20 controls in place
Prefer to talk it through? Talk to a vCISO
More self-assessments
Check the controls insurers ask about before your next application or renewal.
For municipalities with small IT teams protecting critical public services.
Could you recover from a ransomware attack? Check backups, identity, detection and response.
Why vendor access deserves its own review
Most organizations review employee accounts on a schedule, but vendor access grows quietly. An MSP gets a domain admin account during onboarding, a software supplier installs a remote support agent, a contractor is given a VPN login for a two week project. Each grant made sense at the time. A year later, few people can say which of them are still active, who uses them, or whether anyone would notice if one was used at 3 a.m. from another country.
This checklist is for IT leaders, risk owners and procurement teams who want a clear picture of that exposure. It is deliberately practical: every item is something you can verify by looking at a system, a log or a contract, rather than a statement of intent.
It covers six areas: knowing which vendors have access, controlling how they sign in, limiting the network paths they use, watching what they do, writing the right terms into agreements, and removing access when the relationship ends. Together they answer the three questions a board or auditor will ask about third parties: who has access, is it appropriate, and would we know if it was abused.
How to use the Third-Party Access Review checklist
Pull the real list first
Before ticking anything, export vendor accounts from your identity provider, VPN, remote access tools and cloud consoles. Compare that against the vendor list procurement holds. The differences are usually the most useful finding.Answer per vendor, then overall
For your highest-risk vendors (those with administrative or always-on access), walk through each item for that vendor alone. Only tick an item overall if it holds for all of them.Ask for proof, not policy
A policy that says vendors use MFA is not the same as a sign-in log showing it. Tick an item only where you could show the evidence to an auditor today.Turn gaps into owners and dates
Give each open item an internal owner and a target date, starting with the critical ones. Revisit the checklist at your next quarterly access review.
Gaps we see most often
Shared vendor logins
Forgotten remote support agents
Non-human access left off the list
No offboarding trigger
What to do with your result
A low score usually reflects missing visibility rather than missing technology. If you could not answer the inventory items confidently, treat the rest of your score with caution: you may be scoring the vendors you know about and missing the ones you do not.
A practical sequence is inventory, then MFA and named accounts, then removal of stale access, then monitoring and contract terms. Our team can run a third-party access review that reconciles accounts against contracts, tests how vendor connections reach your network and recommends what to tighten first.
Related resources
Third-Party Access Review Checklist: Frequently Asked Questions
Why focus on third-party access?
Vendors and MSPs often have privileged, always-on access across many customers, which makes them an attractive way in. Their access is also frequently less monitored than employee access.
Where should we start?
Build the inventory: every vendor, what they can reach and who owns the relationship internally. Then require MFA and named accounts for all of them.
How often should vendor access be reviewed?
At least quarterly, and immediately when a contract ends or vendor staff change. Vendors with administrative access are worth reviewing more often.
Is a vendor SOC 2 report enough assurance?
It helps, but it describes the vendor's own controls for the period and scope it covers. It does not tell you how their access into your environment is configured, so you still need to control and monitor that side yourself.
What if a critical vendor refuses to use MFA or named accounts?
Treat it as a risk decision for leadership. Compensating options include brokering their access through a gateway you control, enabling the account only for approved sessions, and recording those sessions. Raise the requirement at contract renewal.
Can GuardsArm help?
Yes. Our team runs third-party risk and security assessments, reviews how vendor access is granted and monitored, and helps you set the contract and offboarding processes that keep it under control.