Small business cyber safety
Questions to Ask Your IT Provider Before You Trust Them with the Keys
You do not need to become the technician. You do need proof that the person with administrator access protects your email, files, backups and logins the way a careful owner would expect.
Start with one useful check this week. Write down who can administer your email, cloud storage, accounting software, domain name and staff devices. Include your IT provider, bookkeeper, website host and any “emergency” login they keep.
If you cannot name those people, or if several of them share one powerful password, you already have the first conversation to have. The aim is not suspicion. It is clarity.
Why this conversation matters
A managed service provider, or MSP, is any firm or contractor who looks after systems for you. That can be a national provider or one trusted technician. Australian Signals Directorate (ASD) guidance is plain: these providers often have privileged access to your systems, networks and data. That access is useful. It is also a risk if it is wider than the job, poorly monitored, or still active after the work ends.
ASD’s Australian Cyber Security Centre publishes questions organisations can ask an MSP, and separate advice on how to manage security when you engage one. You do not need to recite those documents. You do need answers you can understand.
Ask for evidence, not a slogan
A confident provider can explain, in ordinary language, how they protect themselves and you. ASD groups the useful questions around five themes. Use them as a script, then ask for a short written answer you can file with the contract.
- Better-practice cyber security. How do they protect their own systems? ASD still points providers to the Essential Eight as practical, prioritised mitigations. That is not a certificate you must buy. It is a way to ask whether they patch, restrict administration, use multi-factor authentication and take backups seriously.
- Secure administration. How do they sign in to your systems? Named staff accounts, multi-factor authentication, and no shared “admin” password is the standard to expect.
- Monitoring. How would they notice unusual sign-ins, a new forwarding rule on email, or a mass file download?
- Regular assessment. How do they find and fix weaknesses in the services they run for you?
- Incident response. Who do they call, how fast, and what do they tell you? ASD’s view is that incidents are a matter of when, not if. A calm plan reduces the damage.
A weak answer sounds like “we take security very seriously”. A useful answer names a control, who owns it, and how you would see it working.
Five owner questions that stay practical
If the official list feels too technical, ask these five. They cover the same ground in owner language.
- “Who in your team can reach our email and files, and how do they prove it is them?” You want named people, unique logins and multi-factor authentication. ASD’s small-business guidance is to turn MFA on, and to prefer stronger methods such as an authenticator app, passkeys or a hardware security key. SMS and email codes are better than nothing, and they are easier to intercept.
- “What can you do in our systems that we cannot see?” Hidden global administrator rights, unlogged remote tools, or a leftover “break-glass” account are common gaps. Ask them to list administrator roles and to remove any that are not needed for the current work.
- “If ransomware locked our files on Tuesday, what exactly happens on Wednesday?” You want to know where backups live, whether they are separate from the live system, who can restore them, and how recently a restore was tested. “The cloud is backed up” is not a restore plan.
- “How will we find out if something is wrong?” Ask who watches sign-in alerts, whether you receive them too, and how after-hours contact works. If only the provider sees the alerts, you are depending on their attention.
- “If you were compromised, how would that affect us?” Providers are attractive targets because one break can reach many customers. Ask how they separate customer environments, how quickly they would tell you, and whether they report incidents to ASD’s ACSC when appropriate.
What “good” looks like in writing
You do not need a 40-page security policy. A one-page note attached to the invoice or contract is enough if it covers:
- the services they run, and the administrator accounts they hold
- how MFA is enforced on those accounts
- how quickly they remove access when a staff member leaves—yours or theirs
- how updates are applied to the devices and software they manage
- where backups are stored and when a restore was last tested
- how they will contact a named person in your business during an incident
If they already follow ASD’s Essential Eight, they can say which strategies they apply to your environment and which they do not. ASD has said it is evolving Essential Eight into a broader Essentials Series. During that transition, existing Essential Eight guidance remains in effect. Treat any “we are Essential Eight compliant” claim as a starting point for examples, not as a finished answer.
A 20-minute review you can do yourself
Before or after the conversation, walk through your own side. ASD’s small-business how-to guides for Apple, Google and Microsoft start with the same fundamentals: strong unique passwords or a password manager, MFA, automatic updates, and backups.
- Open the admin page for business email. Confirm MFA is required, not optional, for every mailbox that can reset other systems.
- List people with administrator roles. Remove anyone who has left, including former providers.
- Check that staff do daily work in ordinary accounts, not in the administrator account.
- Confirm a recent backup exists for the files you could not afford to recreate, and that someone other than the provider knows how to ask for a restore.
- Write the after-hours number you would actually call. If you only have a generic helpdesk form, fix that while the business is calm.
None of that replaces a good provider. It stops you from outsourcing responsibility so completely that nobody is watching the watchers.
If the answers are vague
Do not start with a confrontation. Ask for the one-page note. Give a reasonable date. If the provider cannot explain MFA, backups or admin access in plain English, treat that as information. You may still keep them for desktop support while you move administrator rights for email and the domain name back under your control.
If you believe a business account has already been misused, pause, preserve what you can, and use official reporting paths. ASD’s ACSC can be reached on 1300 CYBER1 (1300 292 371). Cybercrime can also be reported through ReportCyber. Those services exist so you are not left guessing after a bad week.
Keep the relationship, raise the standard
Most small businesses need help. The useful standard is not “never use an IT provider”. It is: named access, MFA, monitored administration, tested backups, and a spoken plan for the day something goes wrong. That is a conversation a careful owner can lead.
If you want more practical Australian cyber-safety reading for a small team, browse the articles below or use Contact Us when you need a training conversation rather than a sales pitch.