Looking ahead to next year, major technology providers are adopting stronger, phishing-resistant authentication methods. Among them is Microsoft, which is phasing out its native SMS and
Managed Service Providers (MSPs) rely on centralized platforms to monitor, maintain and secure their clients’ systems. These tools help MSPs work efficiently, but their broad access also makes them high-value targets for cybercriminals. If attackers compromise a platform with broad administrative access, the potential impact can extend far beyond a single system or client environment.
The recent N-able N-central security incident clearly illustrates this risk.
What happened?
On November 9, 2026, a security researcher publicly disclosed over 30 alleged vulnerabilities within N-central, a Remote Monitoring and Management (RMM) platform used by thousands of MSPs and IT teams worldwide.
The list of vulnerabilities included credential disclosure, authentication bypasses, arbitrary file writes, privilege escalation and remote code execution. One of the most severe exploit chains allegedly allowed an unauthenticated attacker to create an administrator account, reset a password and execute commands on the N-central server.
N-able responded by taking its hosted N-central environments offline and advising customers operating on-premises N-central servers to temporarily take them offline. At the time, N-able said it had not observed active exploitation or unauthorized data access. The organization later released a security hotfix and reported scanning activity associated with the publicly released exploit code.
The incident was specific to N-central, and there is no indication that Passportal was compromised. However, the incident highlights the unique risk MSPs face: because these platforms can connect technicians to multiple client environments, vulnerabilities in one platform can create a potential path into many others.
Why centralized access creates concentrated risk
RMM platforms sit at the center of an MSP’s day-to-day operations, giving technicians broad, centralized access to monitor, maintain and troubleshoot client systems remotely. Through these platforms, technicians can deploy patches, install software, run scripts and respond to issues across countless client environments.
That level of access also means a vulnerability in the platform can create risk far beyond the platform itself. If an attacker gains control of an RMM platform, they may exploit its trusted connections and administrative capabilities to manipulate systems across multiple client environments. For providers serving dozens or hundreds of businesses, a single compromise could create a chain reaction across the systems it manages, especially if administrative accounts or technician credentials are exposed.
This is why MSPs should evaluate more than a vendor’s product capabilities. They should find out:
- What systems, devices and data can the platform access?
- Which passwords, API keys or other secrets are stored or used within it?
- How are privileged accounts protected and monitored?
- Can access be limited by role, user, client, task or time of day?
- Can access be immediately revoked if a technician’s role changes or an account is compromised?
- What safeguards limit the damage if the platform is breached or becomes unavailable?
- Which critical security functions depend on the platform, and what backup controls are in place?
RMM security and credential security are different layers
The N-central incident also raises an important question: should the same platform used to manage client systems also be responsible for protecting every credential that grants access to them?
RMM and identity security serve distinct purposes. An RMM platform helps technicians manage systems, while an identity security platform protects the passwords, privileged accounts and secrets used to access them. Keeping these functions separate can help limit the impact if one platform is compromised and give MSPs greater control over who can access what, when and why.
Keeper helps MSPs protect this layer through a purpose-built identity security platform. MSPs can securely store and share credentials, enforce Role-Based Access Controls (RBAC), apply Multi-Factor Authentication (MFA), manage privileged access and maintain visibility into how sensitive access is being used.
The goal is not to replace an RMM platform. RMM helps MSPs manage client systems, while Keeper helps protect the credentials and access used to manage those systems. Using both layers allows MSPs to maintain operational efficiency while adding an independent layer of protection for sensitive access.
A reminder for every MSP
The N-central incident reinforces the need for MSPs to take a closer look at how technicians access client systems and how those access points are protected. This includes reviewing which platforms enable privileged access, where related credentials are stored and whether access can be limited, monitored and quickly revoked.
MSPs should also consider how they would continue protecting client systems if a key management platform became unavailable or compromised.
Separating system management from access management can ultimately help reduce concentrated risk and limit the potential for a compromise of one platform to affect multiple client environments. This separation also gives MSPs greater control over how access is contained, reviewed and restored when a security incident occurs.
Protecting client environments requires more than securing the tools used to manage them. It requires protecting the identities and credentials that provide access to those systems in the first place.
Discover how KeeperMSP helps protect credentials, control privileged access and strengthen identity security across your client environments.