MSP Insights··6 min read

How secure is your MSP? What clients can now ask you

ASD tells businesses to check an MSP's security before signing. Here are the questions clients can ask you, and the evidence to have ready.

By Pardeep Sharma

The short version: ASD publishes a guide that tells businesses how to check an MSP's security before and after they sign. That makes your own house a sales topic. Clients, insurers and tender buyers can ask how you protect the access you hold, and the MSP with dated answers wins the renewal. Start with four things: what you can reach in each client tenant, how your admin accounts are protected, who on your team has which access, and how you would tell a client if you were breached.

Why does an MSP's own security matter to clients?

An MSP holds administrator access to many client environments, so one compromise of the MSP can reach all of them. ASD's guide says as much when it tells businesses to control what each provider can access. A 2022 joint advisory that includes ASD's ACSC, titled Protecting Against Cyber Threats to Managed Service Providers and their Customers, was written because attackers target providers to reach their customers.

You are the supplier a client's security questionnaire now asks about. The supplier questionnaire post covers how to answer when you are the one sending answers. This post covers what is asked about you.

What does ASD tell your clients to ask?

ASD's guide, first published in 2018 and republished since, is built around steps a business can take. In plain English:

ASD stepWhat a client may ask you
Get security in the contractWhich security duties are in our agreement? Can you show you meet them?
Control MSP accessWhich of our systems can you reach, and how? Is the record current?
Protect against stolen credentialsIs multi-factor authentication on for every account you use here?
Keep visibility of MSP actionsCan we see what your staff did in our tenant?
Plan for an incidentHow and when would you tell us if you were compromised?

The guide also says the business should ask candidate MSPs for evidence of their ability to meet its security requirements, and that the contract should require the MSP to report incidents, including compromise of the MSP's own systems used to manage the client's data. ASD's supply chain guidance adds that audit provisions belong in contracts. Read the guide itself before you quote it to a client.

What evidence should you have ready?

Have five items, each with a date:

  1. An access list per client. The tenants, roles and tools your team can use. ASD advises that businesses keep this record up to date and treat access outside the MSP's scope as untrusted.
  2. Proof that MFA is enforced on every admin account, including break-glass accounts you keep for emergencies.
  3. A named list of staff with the access each person holds, and a note of when someone leaves and their access is removed.
  4. A log review habit. ASD advises storing logs centrally and having someone without MSP-level access review them. Decide who that is for your own tenant.
  5. An incident notice clause. How soon you tell a client, who you call, and what you share first.

If you're a small business

Ask your IT provider for the five items above. You do not need to understand each one. You need dated answers, not a promise. If they cannot show which of your systems they can reach, that is the first gap to close. For a short list of controls in plain English, see the Essential 8 MFA guide.

If you're an MSP

Treat this as a service line, not a chore. A short "MSP assurance pack" per client saves you hours at every renewal and every insurer questionnaire. Build it once for your business, then add one page per client listing what you can reach in that tenant. Keep it current, because an out-of-date list is worse than none. To price the pack as part of a package, see the compliance pricing guide.

One hard point. Do not claim a standard or certification you do not hold. Say what you do, show the date, and say what is still on your list to fix.

Worked example

This is a made-up example, not a real client.

A 15-person MSP looks after 22 clients. A law firm client sends a supplier form that asks which systems the MSP can access and whether MFA covers every admin login. The owner pulls her access list for the firm: three admin roles in Microsoft 365, one remote management agent, one backup console. She exports the MFA status for her own four technician accounts and one break-glass account and finds the break-glass account has no MFA. She fixes it that day, notes the date, and returns the form with a one-page access summary. The firm sees dated answers instead of a promise.

Where CYBERWHITE fits

The access list, staff list and incident clause are your own paperwork. CYBERWHITE does not produce them. It does help with the evidence your clients see about their own tenants. It scans a Microsoft 365 tenant, shows control by control where MFA and admin settings meet the Essential 8 and SMB1001, flags what needs review instead of showing a false green, and exports dated evidence. You can run the same scan on your own tenant to check your admin accounts before a client does. Controls outside Microsoft 365, such as staff training and backups, are recorded through attestation.

To see what a scan shows, book a free proof check. We scan one tenant with you. You can also read the Essential 8 compliance guide, try the cyber insurance calculator or see SMB1001 for MSPs.

Your checklist

  • Write down what your team can reach in each client tenant, with a date.
  • Check MFA on every admin and break-glass account you hold.
  • List staff by name with the access each has.
  • Remove access the day someone leaves, and record it.
  • Choose who reviews logs of your own admin activity.
  • Write an incident notice clause and agree it with clients.
  • Make one standard answer set, plus one page per client.
  • Re-date the pack every quarter.

Sources

  • Australian Signals Directorate, cyber.gov.au: How to manage your security when engaging a managed service provider
  • ASD's ACSC with international partners: Protecting Against Cyber Threats to Managed Service Providers and their Customers (2022 advisory)
  • Australian Signals Directorate, cyber.gov.au: Managing cyber supply chains

Keep reading: Supplier security questionnaire: answer it in a day and Cyber insurance questionnaire: an MSP walkthrough and MSP tool sprawl: how to answer "is this client compliant?"

Frequently asked questions

What does ASD tell businesses to check when they hire an MSP?
ASD's guide, How to manage your security when engaging a managed service provider, tells businesses to put security expectations in the contract, ask the MSP for evidence it can meet them, control and record what the MSP can access, and keep visibility of what the MSP does. Your clients can use it as a checklist for you.
Does the guide say MSP staff must use multi-factor authentication?
ASD advises combining a dedicated administration workstation with multi-factor authentication for sensitive MSP work. A 2022 joint advisory that includes ASD's ACSC also recommends enforcing MFA on MSP accounts that access a customer environment. Treat it as an expectation, not an option.
Is this a legal requirement for MSPs?
The ASD guide is guidance, not law. It still sets the standard a client or insurer can point to. Some clients will turn it into contract terms, so it is worth being ready before they ask.
What evidence should an MSP keep?
Keep a dated list of the systems you can reach in each client tenant, proof that MFA is enforced on your admin accounts, and a record of who in your team has which access. Add your incident notification terms. Date every item so you can show it was true on the day.
Can I use one questionnaire answer for every client?
Use one set of core answers about your own business, then add a short client-specific page showing what you can reach in that tenant. The core answers stay stable. The access list changes by client.