IT vendor management means knowing who supplies your technology, what they can touch, what you pay them and what happens when the relationship ends. For a business of 5 to 100 people, it comes down to one list, one tiering system, one contract checklist and one review each year. Most businesses we meet have the tools but not the list. This guide gives you the routine we would set up for you.
Key Takeaways
- Start with a vendor register: every supplier, what they access, who owns the relationship and when the contract ends.
- Sort vendors by risk. Your accountant’s cloud software needs more scrutiny than your stationery supplier’s portal.
- Put the shared responsibility split in writing: who patches, who backs up, who tells whom when something goes wrong.
- Review each important vendor once a year and again 3 to 6 months before renewal.
- Plan the exit on day one: data return, access removal and a final meeting.
Table of Contents
- What IT vendor management actually covers
- Why it matters more than it looks
- What most businesses get wrong
- Where the data and reality do not match
- Step 1: build the vendor register
- Step 2: sort vendors by risk
- Step 3: choose and contract with care
- Step 4: review on a rhythm
- Step 5: check access, not just paperwork
- Step 6: plan the exit before you need it
- Your IT provider is your highest-tier vendor
- Privacy law and your vendors
- What we recommend
- Getting help with the register and the review
- FAQ
- Sources
What IT vendor management actually covers
An IT vendor is any outside company that supplies technology or has access to your systems. That includes your internet provider, your phone system, your accounting software, your Microsoft 365 reseller, your website host, your printer lease company and your IT support provider. Vendor management is the habit of selecting, governing and offboarding them on purpose rather than by accident. One IT vendor management guide describes it as staying in control of cost, risk and access across the whole relationship.
The reader we have in mind is the owner or office manager who signed most of these arrangements one at a time over several years. There is no procurement team. This is not for a business with a dedicated vendor management office, and it is not about buying vendor management software. A spreadsheet is enough at your size.
Why it matters more than it looks
The number worth knowing comes from a Ponemon Institute survey of 238 Australian IT professionals. It found that 42% of Australian organisations had a breach or attack involving third-party network access in the previous 12 months. The same report put the average cost of restoring access after a breach in Australia at $116,000. That survey covers organisations of all sizes, so treat it as a direction rather than a forecast for your business.
The point for you is simple. Your vendors are an extension of your network. Outsourcing a task does not outsource the responsibility. The US cyber agency CISA says plainly that outsourcing does not absolve a business of risk-management responsibility, and the same logic applies under Australian privacy law, which we cover below.
What most businesses get wrong
We see this a lot, and the mistakes are usually ordinary ones.
There is no single list. Ask who has admin access to the website and you get three different answers. The person who set up the domain left two years ago. The renewal goes to a mailbox nobody reads.
Every vendor is treated the same. Either the business trusts all of them or it asks all of them for a 40-page questionnaire. Neither works. The first leaves gaps and the second never gets finished.
Contracts auto-renew unseen. A 12-month term rolls over because nobody diarised the notice window. The business pays for another year of a tool it replaced.
Access outlives the relationship. A contractor finishes a project and their sign-in stays active. Nobody removes it because nobody owns the task.
Nobody can say who is responsible for what. The backup vendor assumes the business is checking restores. The business assumes the vendor is. Neither is.
Where the data and reality do not match
The advice in most guides assumes a risk team, a procurement process and time. Small businesses have none of these. A Ponemon figure of 42% sounds like something that happens to large organisations with hundreds of suppliers, but the access path is often small: a remote-support tool left installed, a shared login for a vendor portal or an old integration that still has permission to read your files.
The second mismatch is about paperwork. Questionnaires and certificates tell you what a vendor says it does. They do not tell you what that vendor can currently reach in your environment. That second question is the one you can answer yourself, in an afternoon, by looking at your Microsoft 365 sign-in logs and the list of connected apps.
Step 1: build the vendor register
Open a spreadsheet. One row per vendor. Columns that earn their place:
- Vendor name and what they supply
- Business owner (the person at your company who manages them)
- What data or systems they can access
- Contract start date, term and notice period
- Annual cost
- Risk tier (see below)
- Last review date
To fill it in, do not rely on memory. Go through your accounts payable for the last 12 months, then your credit card statements, then the enterprise applications list in your Microsoft 365 admin centre. The card statements always turn up a tool someone signed up for and forgot. In our experience, a first register for a 30-person business usually surfaces a handful of subscriptions nobody can explain.
This register is also the foundation for answering a privacy question later: where does our customers’ personal information go? Our guide to the Privacy Act requirements for Queensland SMBs explains why that question matters.
Step 2: sort vendors by risk
You do not need a scoring model. Ask three plain questions of each vendor: can they see sensitive information, can they change your systems and would your business stop if they failed? Use the answers to place them in a tier.
AUSCERT, the Australian cyber emergency response team based at the University of Queensland, publishes a third-party risk toolkit that works the same way: light checks for low-risk vendors and heavier ones as the risk goes up. Here is how that looks adapted for a small business.
| Tier | Typical vendor | Checks that make sense |
|---|---|---|
| Low | Stationery supplier, event booking tool with no customer data | ABN search, a short security questionnaire, check they carry insurance |
| Medium | Accounting software, CRM, website host | Tailored questionnaire, review of the contract’s incident and data terms, yearly refresh of certificates |
| High | Your IT provider, backup provider, anyone with admin access or customer records | Full contract review, shared responsibility split in writing, exit plan, yearly review meeting |
The UK Information Commissioner’s Office takes the same approach, advising that businesses group suppliers by service type and assign risk profiles based on how sensitive the information is and how much disruption losing the supplier would cause.
What is not worth doing: sending a long questionnaire to a low-tier vendor. You will not read the answers and the vendor will not take it seriously.
Step 3: choose and contract with care
The Australian Cyber Security Centre (ACSC) gives sensible selection criteria in its guidelines for procurement and outsourcing. Pick vendors who show a commitment to the security of what they sell, who provide evidence when you ask and who agree to a shared responsibility model that defines supplier and customer duties.
That last item is the one we push hardest. A shared responsibility model is a short table in the contract that says who does what. For a Managed IT arrangement it looks like this:
- Who patches servers, laptops and phones
- Who owns multi-factor sign-in and Conditional Access policies (the Microsoft 365 rules that decide who can sign in from where)
- Who runs backups and who tests a restore
- Who trains staff and who handles phishing reports
- Who contacts whom when something goes wrong
CISA recommends exactly this kind of Shared Responsibility Model written into the agreement, with examples such as who patches and who trains staff.
What the contract should say
A review checklist from an Australian legal publisher says managed IT contracts should detail security monitoring, patching, multi-factor authentication support, backup frequency and retention, whether backup restores are tested and what the provider must do after an incident. We would add four checks from our own work:
- Data ownership. The contract should say your data is yours and you can get it out at any time. The NSW Government’s standard terms for cloud services say the buyer owns or controls its data and the vendor must allow access or extraction at any time. You are not a state government, but you can ask for the same principle.
- Breach notification. The same NSW terms require the vendor to notify the buyer of a security breach within 48 hours or sooner if the law requires. Pick a window and write it in. Vague wording such as “promptly” is hard to enforce.
- Exit help. The NSW terms also require up to three months of disengagement services at the end of the contract. Ask what your vendor will do to help you move away.
- Notice period. Find the date by which you must give notice and put it in your calendar with a reminder 90 days earlier.
One thing to skip: do not pay a lawyer to review a $30-a-month subscription. Spend that effort on the high-tier vendors.
Step 4: review on a rhythm
Once a vendor is signed, the job is routine. UNSW’s guide says the service owner should monitor each arrangement through periodic meetings, service level assessments and contract-compliance checks, with oversight in proportion to the size, complexity and risk of the arrangement. A university has a different scale from a 25-person Brisbane firm, but the principle holds.
Here is a rhythm that works for a small business:
- Low tier: check the register once a year. Cancel what nobody uses.
- Medium tier: annual check of the contract, the cost and the access list.
- High tier: a review meeting each year, plus a check 3 to 6 months before renewal so you have time to negotiate or switch.
In the high-tier review, bring real numbers. How many support requests did you raise? How many were repeats of the same problem? Did the monthly report match what your staff experienced? Has the cost per user changed? If a vendor cannot produce a report, that is your answer.
A structured meeting helps. A good weekly business review approach, with a fixed agenda and a decision at the end, translates well to vendor reviews: bring the figures, agree the actions and write down who owns each one.
Step 5: check access, not just paperwork
Once a quarter, spend 30 minutes on these checks in the Microsoft 365 admin centre:
- Review the list of guest users and delete anyone who no longer works with you.
- Review enterprise applications and remove integrations nobody recognises.
- Check that every account, including vendor accounts, uses multi-factor sign-in.
- Look for vendor accounts with global administrator rights. Most vendors need less.
This is where we see the biggest gap between paperwork and practice. A vendor can have a perfect security certificate and still have an admin account that was never reduced after a project finished. If you want help with this, our Microsoft 365 support and management service covers it.
Our cyber security risk assessment checklist gives more detail on the controls worth checking each quarter.
Step 6: plan the exit before you need it
Nobody enjoys planning a break-up on the first day, but this step is what separates a contract you control from one that controls you. AUSCERT’s toolkit says offboarding should include retrieving or verifying data deletion certificates, removing vendor integrations from production, confirming termination terms are met and updating the vendor register, then holding an offboarding meeting. For high-risk vendors it adds a written statement that data has been purged from systems and backups.
A hypothetical example to make this concrete: a 40-person professional services firm changes its backup provider. Before the cut-over date, the firm confirms the new backups are running and a test restore of a shared mailbox and one file server folder succeeds. Only then does it ask the old provider to remove its agent from every machine, disable its admin accounts and send a data deletion statement. The firm records the date in its register. That order matters: never cancel the old service until the new one has proved it can restore.
Your IT provider is your highest-tier vendor
Your IT provider usually holds the keys to everything: admin accounts, backups, firewalls and email. That makes it the vendor to scrutinise most closely and the one where a clear arrangement pays off most. CISA notes that ceding more responsibility to a managed service provider can improve cost-efficiency but also increases exposure, because you can lose visibility. The answer is not to avoid outsourcing. It is to keep visibility through reporting, defined access and a review rhythm.
Our guide to what Managed IT services are and how they work sets out what a good arrangement should include.
Privacy law and your vendors
If your vendors handle customer personal information, you remain responsible for it. The Privacy and Other Legislation Amendment Act 2024 (Cth) came into force on 10 December 2024, with most reforms in effect and automated decision-making transparency requirements starting on 11 December 2026. In practice, that means your vendor register should show which vendors hold personal information and where. Our data privacy tips for SMEs cover the practical steps. For legal advice on your own obligations, speak to a privacy lawyer.
What we recommend
We run Managed IT for Brisbane businesses of 5 to 100 people, and our honest view is that vendor management fails because nobody owns it, not because it is hard.
Pick one person to own the register. Give them an hour each quarter. Make your IT provider the vendor you review most closely, and ask for a written split of responsibilities: who patches, who backs up, who tests restores. Our Managed IT plans cover support, devices, Microsoft 365, backup and security under one agreement, which means fewer vendors to track and one place to look when something needs fixing.
We also think you should say no to complexity. If a tool costs less than a few hundred dollars a year and touches no customer data, a name in the register is enough. Spend your effort on the vendors with admin access and customer records.
We would rather you could answer “who can get into our systems and why” in two minutes than hold a thick binder of questionnaires.
IT Start
Getting help with the register and the review
We are based in Brisbane and work with businesses from the Sunshine Coast to the Gold Coast. If you would like a second set of eyes on your vendor list, our team can walk through your Microsoft 365 access, your backups and your IT contract with you. Our Managed IT plans bundle support, devices, Microsoft 365, backup and security, and our Business IT Support is $145 per hour ex GST for one-off projects such as a vendor handover or a cloud migration. See our cyber security services or ask for a free consultation through itstart.com.au.
FAQ
What is the difference between vendor management and supplier management in ITIL?
ITIL is a widely used framework for running IT services. It uses “supplier management” for the process of managing suppliers and their contracts, and the idea is the same as vendor management: choose, govern and review the outside companies you rely on. For a small business, the two terms mean the same routine, and you do not need to adopt ITIL to follow it.
How often should we review our IT vendors?
Review high-tier vendors such as your IT provider and backup provider at least once a year. Check the contract 3 to 6 months before it ends so you have room to negotiate or change. Medium and low-tier vendors can sit in an annual register check.
Do we need vendor management software?
Not at the size of business we work with. A shared spreadsheet with the columns above does the job. Software starts to earn its cost when you have hundreds of vendors and a team to manage them.
How do we manage vendor risk without a security team?
Sort vendors into tiers, check what each can access in Microsoft 365 every quarter and write the shared responsibility split into your high-tier contracts. The ACSC’s procurement guidance is a good reference for what to ask a vendor to show you.
What should happen when we stop using a vendor?
Remove their access, take out their integrations, get confirmation that your data has been deleted and update your register. Do this only after the replacement has been proven to work.
Sources
- The state of third-party access in cybersecurity, Ponemon Institute 2025 Australia Spotlight
- IT Vendor Management Guide
- Guidelines for procurement and outsourcing, ACSC
- Third-party risk and contract management toolkit, AUSCERT
- ICT Agreement for As-A-Service, NSW Government
- CISA Insights: Risk considerations for managed service provider customers
- Managed IT service contracts review checklist, Sprintlaw
- IT Contract and Vendor Management Guide, UNSW
- IT supplier relationships, ICO
- Cyber, Privacy and Technology Report Issue 11, Wotton Kearney
- Weekly business review

