Home  /  Insights  /  ISO 27001 for managed service providers (MSPs)
Insights

ISO 27001 for managed service providers (MSPs)

An MSP holds the keys to many businesses at once. That makes you an attractive target, and it’s why your clients’ security teams, regulators and auditors now ask what you do to protect that access. Here’s why the questions come, how to scope an MSP ISMS and which controls get the hardest look.

Cyber Veda

Quick answer: MSPs get asked for ISO 27001 because they hold privileged access to many client environments, so one compromise can spread to all of them. APRA-regulated clients must manage material service providers under CPS 230 and assess third parties under CPS 234, and critical infrastructure clients must manage supply chain hazards. An MSP ISMS is scoped to your service delivery, people and management tooling, and auditors focus on privileged access, segregation between clients, logging, change control, backups and incident notification.

Why MSPs get asked

To do your job, you need broad, privileged access to your clients’ systems. ASD puts the problem plainly: because MSPs have trusted and privileged access, they can act as a gateway into their clients, and the compromise of a single MSP can affect many organisations. ASD reported MSP compromises in 2017 and saw attackers keep targeting MSPs and, through them, their customers.

In May 2022 ASD’s ACSC joined the cyber security agencies of the UK, Canada, New Zealand and the US in a joint advisory warning of increasing malicious activity aimed at MSPs. It set out baseline measures for MSPs and told customers to make sure their contracts require their MSP to implement them. That advisory, and ASD’s own Questions to ask managed service providers, is where many of the questions in your clients’ due diligence come from: do you implement the Essential Eight, how do you administer systems remotely, what do you log, how do you test for vulnerabilities and how will you respond to an incident.

An ISO 27001 certificate and Statement of Applicability answer most of those questions at once. See how to answer security questionnaires faster.

Regulated clients: APRA and critical infrastructure

CPS 230 and CPS 234

Banks, insurers and super funds must assess the information security capability of third parties that manage their information assets under CPS 234. Since 1 July 2025 they must also meet CPS 230 Operational Risk Management, which requires them to manage the risks of using service providers and keep a register of material service providers. Providers of core technology services are treated as material unless the entity can justify otherwise, so an MSP running a regulated client’s IT is usually in that group.

For you, that means contract terms covering audit access, notification of your own material subcontractors and APRA’s right to access documentation and visit, alongside the CPS 234 assessment. Our guide to CPS 234 vs ISO 27001 explains both standards and where ISO 27001 falls short of them.

Critical infrastructure

Responsible entities under the Security of Critical Infrastructure Act must run a risk management program that identifies and minimises supply chain hazards, and comply with a recognised cyber security framework such as ISO 27001 or the Essential Eight. For electricity, gas, liquid fuel, water, freight, broadcasting, domain name system and energy market operator assets, the enhanced rules that commenced in June 2026 add specific requirements on credential compromise and lateral movement hazards, which describe exactly how an MSP compromise spreads. These entities also have 12 or 72 hours to report a cyber incident to ASD, depending on its impact, so they need to hear from you quickly. Expect tighter access conditions and short notification windows in their contracts.

Government clients bring their own frameworks; see ISO 27001 for government suppliers.

Scoping an MSP ISMS

Scope is where MSP projects most often go wrong. Clients read the scope on your certificate, so it must clearly cover the managed services they buy, and the systems that make those services work.

AreaUsually in scopeNotes
Service deliveryService desk, network operations, security operations, projects that touch client systemsThe scope statement should name the managed services, not only an office address
Management toolingRMM, PSA, documentation and password vaults, backup platforms, EDR and SIEM consolesEach one is a path into every client it manages
IdentityYour identity provider, admin accounts, privileged access tooling, delegated access into client tenanciesAccounts you hold in client environments are yours to control
Client environmentsYour access to them and the actions you takeThe client’s own environment stays in its scope, not yours
PeopleTechnicians, engineers, contractors and offshore staff with client accessScreening and offboarding are tested hard
SuppliersRMM and PSA vendors, cloud platforms, distributors, subcontracted techniciansManaged as dependencies; you assess them, you don’t audit them

Clause 4.3 requires you to consider interfaces and dependencies with what’s outside scope. For an MSP the key interface is the client boundary. ASD advises MSPs to identify which client systems they administer and how, and to keep that record current; the joint advisory asks for contracts that say what the client is and isn’t buying. A responsibility matrix for each service tier does both jobs, and it’s the first thing a good auditor asks to see. For how scope drives effort, see what drives the cost.

The controls under most scrutiny

All 93 Annex A controls must be considered, but for an MSP these carry the risk. Titles follow ISO/IEC 27002:2022; see Annex A controls explained.

Area and controlsWhat auditors and clients look for
Privileged access: 5.15 to 5.18, 8.2, 8.5MFA on every account that can reach a client environment, treated as privileged; separate admin accounts; least privilege and time-limited elevation; no admin credentials reused across clients; access removed promptly when staff leave or a contract ends
Segregation between clients: 8.22, 8.3Clients separated from each other and from your internal network; administration from secure jump hosts; high-security clients not co-hosted or co-managed with higher-risk ones
Suppliers and subprocessors: 5.19 to 5.23A list of the tools and subcontractors your services depend on, security assessed before adoption, contract terms that match what you promise clients, and clients told about material subcontractors
Logging and monitoring: 8.15, 8.16Logs of your activity in client environments and of your delivery infrastructure, protected from tampering, retained to a defined period, reviewed, and visible to clients as agreed
Change management: 8.32Changes and scripts pushed to many clients at once approved, tested and staged, with a way back
Backup: 8.13Your own data and client data backed up as contracted, with offline or isolated copies and restore tests that prove they work
Incident management: 5.24 to 5.28Contracted notification to clients, including when your own systems are compromised, and a plan that meets each client’s deadline
People: 6.1, 6.6Screening proportionate to client access, including clearance levels where a client requires them, and confidentiality terms

Vulnerability management (8.8) and configuration management (8.9) matter too, for your own estate and for the platforms you manage. As always, auditors sample records: access reviews, change tickets, restore tests, incident notifications. A control that exists only in a policy becomes a nonconformity.

Your management tools are the crown jewels

An RMM platform that can run scripts on every client endpoint is the single most powerful system you operate. Attackers have used compromised remote management tools to push ransomware to many businesses at once. Treat the RMM, PSA and credential vault as your highest-risk assets in the risk assessment: phishing-resistant MFA where you can get it, restricted and reviewed admin roles, alerting on unusual script activity, patching the platform itself quickly and a tested plan for operating if it is unavailable or untrustworthy.

Essential Eight for MSPs

ASD advises MSPs to implement a cyber security standard internally, such as the Essential Eight, and promote it in the systems they manage for customers. Clients ask about the Essential Eight in two different senses, and you need to answer both:

  • Your own environment. What maturity level have you reached across the eight strategies, and how was it assessed? Restricting administrative privileges and MFA matter most here, given what your accounts can reach.
  • The services you deliver. When a client asks you to bring their environment to a maturity level, your contract and responsibility matrix must say which strategies you are responsible for.

Expect a third question soon. In October 2026 the ASD published ASD Essentials, the evolution of the Essential Eight, and it states that outsourcing does not transfer accountability: clients need current evidence that you deliver the outcomes you own, domain by domain. See Essential Eight to ASD Essentials.

There is no Essential Eight certificate; it is a maturity assessment. ISO 27001 gives you the place to manage it as an objective. See Essential Eight vs ISO 27001 and our Essential Eight assessments.

SOC 2 or ISO 27001?

ISO 27001 ends in a certificate from an accredited certification body and is the usual ask from Australian, Asian and government clients. SOC 2 ends in an attestation report from a CPA firm. A Type 2 report describes your system and tests your controls over a period, which some clients’ auditors prefer when they rely on your controls. US clients mostly expect SOC 2. Start with the one tied to your biggest clients and reuse the work. See ISO 27001 vs SOC 2 and SOC 2 in Australia.

Common mistakes

  • Scoping the office, not the service. A scope that leaves out the RMM, the SOC tooling or offshore technicians won’t survive Stage 1, and clients will notice.
  • Shared admin accounts. One login used by the whole team across many clients fails access control, accountability and the advisory’s guidance on credential reuse in one go.
  • No client boundary. Without a responsibility matrix, auditors can’t tell what you control, and clients assume you control everything.
  • Incident plans that only cover client incidents. The scenario clients care about most is your own compromise. Plan and rehearse telling them.
  • Forgetting your own suppliers. Your RMM vendor and subcontractors are part of your clients’ supply chain too.
  • Segregation of duties in a small team. Where the same engineers build and run everything, show compensating controls: peer review of changes, logged and reviewed privileged sessions. See ISO 27001 for small businesses.

Next step

If you are building the ISMS yourselves, follow how to implement ISO 27001 and plan the internal audit early. ISO 27001 requires internal audits to be objective and impartial; your own staff can do it if they aren’t auditing their own work, but in most MSPs the same engineers built the tooling and processes. That’s why many bring in an independent internal auditor. Drawing a defensible scope and client boundary around shared tooling and dozens of client tenancies is the part we take on for clients. See how our ISO 27001 service works, or book a free 30-minute consultation and tell us what your clients are asking for.

FAQ

Common questions

Do managed service providers need ISO 27001?

No law requires it. Clients do. Because an MSP holds privileged access to many client environments at once, banks, insurers, super funds, critical infrastructure operators and government buyers want independent proof that the access is controlled. ISO 27001 is the most common answer in Australia and Asia-Pacific.

Does our ISO 27001 certificate cover our clients’ environments?

No. It covers your ISMS: your people, tools and the way you access and manage client systems. Each client remains responsible for its own environment. A clear responsibility matrix for each service shows the client, and the auditor, where your side ends.

Are we a material service provider under APRA CPS 230?

Your APRA-regulated client decides. Under CPS 230, providers the entity relies on for a critical operation, or that expose it to material operational risk, are material, and providers of core technology services are treated as material unless the entity can justify otherwise. If you run a client’s core IT, assume you are and expect the contract terms that follow.

Should an MSP do ISO 27001 or SOC 2?

Do the one your clients ask for. Australian, Asian and government clients mostly ask for ISO 27001; US clients mostly ask for SOC 2 Type 2. The controls overlap heavily, so the second costs far less effort than the first. See ISO 27001 vs SOC 2.

How long should an MSP keep logs?

The 2022 joint advisory on MSP threats, co-authored by ASD’s ACSC, recommends that all organisations store their most important logs for at least six months, because incidents can take months to detect. Client contracts and regulated clients may require longer. Set the period in your logging policy and make sure your tooling actually retains it.

Talk to someone who has taken companies like yours to audit.

Book a free 30-minute consultation. Tell us what is driving the need, and leave with a realistic timeline and the first three things to do.