18 min read

RMM Security: What MSP Buyers Should Evaluate

RMM Security: What MSP Buyers Should Evaluate

Remote monitoring and management (RMM) software gives managed service providers centralized control over customer endpoints, including remote access, software deployment, patch management, and automation. These capabilities improve operational efficiency, but they also make the platform's security an important purchasing consideration.

An RMM platform may have the ability to execute privileged commands across hundreds or thousands of managed devices. A compromised administrator account, ineffective access restrictions, or exploitable platform vulnerability can therefore create risks that extend across multiple customer environments.

Meanwhile, MSPs face sustained customer scrutiny of their cybersecurity practices and growing responsibilities for managing third-party technology risks.

For MSPs evaluating RMM software in 2026, the decision increasingly involves more than comparing features and subscription costs. Buyers need to understand how vendors protect privileged access, isolate customer environments, respond to security incidents, and provide evidence supporting their security claims.

This article explains the factors influencing RMM security purchasing decisions, the protections MSPs should prioritize, and how to evaluate whether a vendor can meet their operational security requirements.

Why Security Is Becoming More Important in RMM Purchasing Decisions

Security is not a new requirement for remote management software. What has changed is the broader environment in which MSPs select, operate, and justify their technology choices.

Customer expectations, software supply chain risks, and the concentration of administrative capabilities all influence how MSPs should evaluate RMM vendors.

Customer Security Expectations Are Becoming More Established

MSPs are increasingly responsible for helping customers manage cybersecurity alongside traditional IT infrastructure.

The 2026 CyberSmart MSP Survey, involving 350 MSP leaders in the UK and Ireland, provides evidence of these changing responsibilities:

  • 70% reported increasing customer scrutiny of their cybersecurity capabilities, down from 77% in 2025.
  • More than two-thirds said customers expected them to manage both IT infrastructure and cybersecurity, up from 60% in 2025.
  • 61% reported being expected to help customers meet compliance requirements.

The decline from 77% to 70% does not indicate that security scrutiny has disappeared. Rather, the findings suggest that security expectations are becoming a more established part of customer relationships and vendor evaluations.

The survey does not directly measure changes in RMM purchasing priorities, and its findings should not be generalized to all MSPs worldwide. However, it helps explain why MSPs need stronger evidence of how their technology providers manage security.

Customers may expect their MSPs to explain how privileged access is controlled, how third-party vendors are assessed, and what safeguards protect managed environments.

Because RMM platforms provide powerful administrative capabilities, their security architecture is directly relevant to these responsibilities.

Centralized RMM Access Creates Concentrated Risk

RMM platforms consolidate several IT administration functions into one management system.

Technicians can monitor devices, deploy updates, execute scripts, transfer files, and establish remote connections without accessing each endpoint individually.

This centralization is one of the main reasons RMM software improves MSP efficiency. However, it also concentrates administrative capabilities.

An attacker who compromises an account with extensive permissions may potentially interact with devices across multiple customer environments.

The actual exposure depends on the account's permissions, available management functions, and the access boundaries separating customers.

For MSP buyers, this makes two questions especially important:

  1. How effectively does the platform prevent unauthorized administrative access?
  2. How much damage could a compromised account cause before access is restricted or revoked?

A secure purchasing decision considers both the likelihood of unauthorized access and the potential consequences.

Software Supply Chain Security Is Part of MSP Risk Management

MSPs depend on third-party technology providers for remote management, endpoint protection, backup, identity management, and other essential services.

These dependencies can expose MSPs and customers to incidents originating outside their own organizations.

The CyberSmart survey found that approximately two in five MSPs or their customers experienced a supplier-originated cybersecurity incident during the preceding year.

It also identified supplier assessments, contractual enforcement, and monitoring costs as challenges in managing third-party risk.

RMM vendors warrant particular scrutiny because their software may perform privileged operations directly on customer endpoints.

This does not mean every RMM provider represents the same level of risk. The exposure depends on product architecture, security controls, deployment configuration, and vendor practices.

It does mean that RMM security should be considered within an MSP's broader vendor risk management process.

For more context, see Level's article on MSP supply chain security.

How Security Incidents Have Influenced RMM Vendor Scrutiny

Security incidents involving legitimate remote management technology demonstrate why MSPs need to assess both product capabilities and vendor security practices.

Two distinct risks are particularly relevant: attackers misusing authorized management functions and attackers exploiting vulnerabilities in remote administration software.

Criminals Can Abuse Legitimate Remote Management Tools

In January 2023, the Cybersecurity and Infrastructure Security Agency (CISA), National Security Agency (NSA), and Multi-State Information Sharing and Analysis Center (MS-ISAC) issued a joint advisory about malicious use of RMM software.

The advisory described how cybercriminals misused legitimate remote access applications, including ScreenConnect and AnyDesk, during financially motivated attacks.

These tools can be abused for persistence and remote command execution when attackers obtain unauthorized access.

The underlying problem is not that remote management technology is inherently malicious. It is that legitimate administrative capabilities can be exploited when access is compromised.

This distinction affects RMM purchasing decisions.

MSPs should determine whether the platform can enforce strong authentication, restrict administrative privileges, record sensitive operations, and support prompt access revocation.

These protections help limit the opportunities for attackers to misuse legitimate management capabilities.

Platform Vulnerabilities Create Additional Exposure

Security risks can also originate from vulnerabilities within remote management software itself.

In February 2024, ConnectWise disclosed two serious vulnerabilities affecting ScreenConnect, a remote support and access product commonly used within IT management environments.

The vulnerabilities included:

  • CVE-2024-1709: A critical authentication bypass vulnerability with a CVSS v3.1 score of 10.0.
  • CVE-2024-1708: A path traversal vulnerability that could contribute to further compromise.

The issues affected ScreenConnect versions 23.9.7 and earlier. Security authorities subsequently reported active exploitation.

ConnectWise released fixes and remediation guidance, including instructions for affected self-hosted installations.

Source: ConnectWise ScreenConnect Security Bulletin

ScreenConnect is not a complete standalone RMM platform, but the incident remains relevant because remote access software can provide similarly privileged access to managed endpoints.

It also illustrates why vendors must be evaluated on more than preventive security features.

MSPs need to understand how vulnerabilities are identified, how quickly remediation becomes available, how customers are notified, and which responsibilities remain with the MSP.

The existence of a disclosed vulnerability does not automatically establish that a vendor has poor security practices. Its response, transparency, and remediation process are also important evidence.

Which RMM Security Requirements Should MSPs Prioritize?

MSPs should establish their security requirements before comparing RMM vendors.

This prevents purchasing decisions from becoming a contest over which platform advertises the longest list of features.

The most important requirements involve authentication, privileged access, remote management activities, and accountability.

Authentication and Identity Protection

Multifactor authentication (MFA) reduces reliance on passwords alone and helps protect technician accounts from unauthorized access.

However, supporting MFA is not the same as enforcing it.

MSPs should verify whether administrators can require MFA for all relevant accounts, including highly privileged users.

Single sign-on (SSO) may also be valuable when an MSP uses an existing identity provider to manage account policies and employee offboarding.

Relevant purchasing considerations include:

  • Organization-wide MFA enforcement.
  • Supported SSO providers and authentication methods.
  • Session expiration and management.
  • Account recovery procedures.
  • Immediate revocation of employee access.

The objective is to ensure that identity protection can be consistently administered across the MSP's workforce.

Role-Based Access and Customer Isolation

Role-based access control (RBAC) determines which actions a user is authorized to perform.

Customer and device-group restrictions determine where those permissions apply.

Both are important.

For example, a technician may legitimately require script execution permissions but should only be able to run scripts on devices assigned to that technician's customer accounts.

An RMM platform should support permissions that match actual operational responsibilities rather than forcing MSPs to grant broad access unnecessarily.

During evaluation, buyers should determine whether restricted users can view, modify, or administer devices outside their assigned customer scope.

Customer isolation is especially important because an MSP often manages multiple organizations through the same console.

Remote Access and Automation Security

Remote control, scripting, and automation can affect endpoint configurations and execute privileged operations.

MSPs should therefore evaluate how these capabilities are authorized and recorded.

Important considerations include remote session permissions, end-user approval options, restrictions on unattended access, script execution rights, and records of administrative actions.

Unattended remote access is not inherently insecure. It is often necessary for servers, maintenance windows, and systems without active users.

Its suitability depends on appropriate authentication, authorization, and monitoring.

Likewise, automation improves efficiency but should not automatically give every technician broad execution privileges.

For additional operational guidance, see Level's article on RMM security best practices.

Administrative Logging and Auditability

When suspicious activity occurs, MSPs need enough information to determine what happened.

Administrative activity records can help identify account access, remote sessions, script execution, permission changes, and other sensitive operations.

However, auditability depends on more than the existence of an activity log.

MSPs should evaluate which events are recorded, how long records remain available, whether they can be exported, and who can access or modify them.

Logging a remote session is also different from recording its visual contents.

The required level of visibility depends on the MSP's customer commitments and investigation requirements.

How MSPs Can Verify RMM Vendor Security Claims

Security features should be assessed using evidence rather than marketing descriptions alone.

A vendor may advertise MFA, RBAC, encrypted sessions, or independent security assessments without explaining whether those controls meet a particular MSP's operational requirements.

A practical evaluation asks three questions:

  1. What security capability does the vendor claim to provide?
  2. What documentation or independent evidence supports that claim?
  3. Can the MSP verify that the capability behaves as required?

The following comparison framework helps translate claims into purchasing evidence.

Vendor claim

Evidence to review

What to confirm

MFA is supported

Authentication documentation and settings

Whether it can be mandatory for all relevant users

RBAC is available

Role documentation and test accounts

Whether sensitive actions and customer access are restricted

Remote sessions are encrypted

Connection architecture documentation

How sessions are protected and authorized

Administrative actions are logged

Sample records and retention policies

Whether relevant events can be investigated

The platform is independently assessed

SOC 2 Type II report or other assurance documents

Scope, reporting period, exceptions, and relevant controls

Security vulnerabilities are managed

Disclosure process and security advisories

How issues are reported and remediated

Incident response is established

Incident response documentation

How customers are notified and supported

Classify Requirements Before Comparing Vendors

Not every security capability has the same purchasing importance.

A useful evaluation distinguishes four categories.

Requirement category

Meaning

Purchasing implication

Mandatory

A control the MSP must have to operate acceptably

Unmet requirements prevent approval unless a formally accepted alternative satisfies the underlying need

Conditional

A control required for certain customers or workflows

Must be satisfied before the platform is used in the affected environment

Preferred

A capability that improves security or administrative efficiency

Helps distinguish vendors that already meet mandatory requirements

Vendor assurance

Evidence supporting claims about the vendor's security practices

Requires review for relevance, scope, and adequacy

For example, an MSP may classify organization-wide MFA and customer-scoped permissions as mandatory.

End-user approval for remote sessions may be conditional if only certain customers require explicit consent.

Additional reporting capabilities may be preferred when existing logs already satisfy contractual and operational requirements.

An independent security assessment provides vendor assurance evidence, but its importance depends on the MSP's customer obligations and risk policy.

These categories should be determined by actual business and security requirements rather than treated as universal rankings.

Handle Security Gaps Before Making a Decision

When a vendor does not satisfy a requirement, the gap should be documented rather than ignored.

For each unresolved requirement, the MSP should identify:

  • The specific control or evidence that is missing.
  • Which customer environments or workflows are affected.
  • Whether an alternative control adequately addresses the requirement.
  • Who has authority to accept any remaining risk.
  • Whether the limitation affects purchasing approval.

An unmet mandatory requirement should not be offset simply because the vendor offers more automation features or a lower subscription price.

Preferred capabilities, however, can be compared after mandatory and conditional requirements have been satisfied.

This creates a consistent decision process without relying on arbitrary security scores.

Validate Security Controls During a Trial

Vendor documentation is useful, but an authorized product trial can verify whether important controls behave as described.

For example, an MSP can use designated test accounts and endpoints to confirm whether:

  • A restricted technician cannot access an unrelated customer's devices.
  • MFA enforcement applies to the intended accounts.
  • Remote control approval follows the configured policy.
  • Script execution permissions match assigned roles.
  • Administrative changes appear in activity records.
  • Revoked sessions or accounts lose their previous access.

These tests turn security claims into observable evidence.

They also help identify limitations before the platform is deployed across production customer environments.

Why Vendor Vulnerability Management and Incident Response Matter

No software vendor can guarantee that its platform will never contain vulnerabilities.

For MSP buyers, the more useful question is whether the vendor has credible processes for discovering, addressing, and communicating security problems.

Vulnerability Disclosure and Remediation

MSPs should understand whether an RMM vendor maintains a documented vulnerability disclosure process and provides actionable security advisories.

Important considerations include how vulnerabilities are reported, how remediation is prioritized, and what customers must do when security updates become available.

Cloud-hosted services may allow vendors to deploy certain fixes centrally.

Self-hosted deployments may require MSPs to perform updates directly.

Understanding these responsibilities before purchase helps prevent confusion during an actual security incident.

Containment and Recovery Capabilities

Preventive controls cannot eliminate every possibility of compromised credentials or unauthorized administrative activity.

A security evaluation should therefore examine what the platform allows an MSP to do when suspicious access is discovered.

Buyers should determine whether administrators can revoke compromised accounts, terminate active sessions, disable exposed credentials, restrict permissions, and preserve relevant evidence.

They should also understand what assistance the vendor can provide during containment and recovery.

Disabling a user account does not necessarily eliminate every possible access path, particularly when integrations or other credentials are involved.

The platform's capabilities and architecture influence how an incident can be contained.

Vendor Support and Infrastructure Access

MSPs should also understand the level of access that the RMM vendor's own personnel possess.

There is a meaningful distinction between administering the platform's infrastructure and being able to initiate privileged operations on customer endpoints.

Buyers should ask whether vendor support access requires customer authorization, whether it is temporary, and whether support activity can be reviewed.

These considerations help establish how much access the MSP is extending to an additional trusted technology provider.

How Security Affects RMM Cost and Operational Suitability

Security requirements can influence the total cost of operating RMM software.

A low subscription price may be less attractive when essential controls require additional licenses, separate integrations, or extensive manual administrative work.

For example, a platform with limited permission management may increase the effort required to manage technician access safely.

Insufficient audit reporting may also create additional work when responding to customer inquiries or investigating incidents.

MSPs should evaluate the cost of meeting security requirements, not simply the price of the base license.

This includes reviewing:

  • Whether essential protections are included in the quoted subscription.
  • The effort needed to maintain permissions and authentication policies.
  • Compatibility with existing identity and security systems.
  • The availability of audit records and vendor assurance documentation.
  • Customer-specific compliance or contractual requirements.

These factors affect the platform's operational suitability.

A product may be technically capable and competitively priced while still failing to meet the requirements of particular customers.

How Level Supports Security-Conscious RMM Purchasing

Level provides remote monitoring and management capabilities with security controls relevant to several common MSP purchasing requirements.

These include technician access restrictions, encrypted remote sessions, activity logging, and documented vendor security practices.

Restricting Access Across Customer Environments

A central purchasing concern for MSPs is preventing technicians from receiving unnecessary access to devices belonging to unrelated customers.

Level supports role-based permissions, write protections, and device-group restrictions.

These capabilities allow administrators to control which actions technicians can perform and which endpoints they can access.

Level also supports organization-wide two-factor authentication, inactivity timeouts, and IP-based access restrictions.

Level supports single sign-on through Microsoft Entra and Google Workspace, with additional identity providers supported through OpenID Connect (OIDC), including Okta. SSO is configured per user, so administrators must ensure the appropriate technicians are assigned to SSO authentication.

These controls help MSPs establish access policies that reflect technician responsibilities while retaining centralized management capabilities.

For buyers, the relevant benefit is the ability to enforce access boundaries rather than relying exclusively on internal procedures.

Governing Remote Control Sessions

Level uses encrypted remote connections, establishing peer-to-peer sessions when network conditions permit and an end-to-end encrypted relay when necessary.

The platform also allows organizations to configure end-user approval requirements for remote control sessions.

Approval behavior can be defined at the organization level and overridden for specific device groups.

When users are asked to approve a remote control session, administrators can configure what happens if no response is received.

Selecting Require approval prevents the session from proceeding without explicit consent.

Selecting Connect if the end user doesn't answer permits the session after the configured timeout.

These settings apply to remote control sessions rather than background management operations, which must be evaluated through their own access permissions.

For MSP buyers, this provides a way to align remote control behavior with different customer expectations.

See Level's remote control approval documentation.

Supporting Administrative Accountability

Level records administrative activity, including remote sessions, script execution, and configuration changes.

These records help MSPs determine which accounts performed specific actions and when those actions occurred.

The platform does not record video of remote control sessions, so buyers requiring visual session recordings should distinguish that requirement from activity logging.

MSPs should also confirm that the available event details and retention meet their investigation and contractual needs.

Evaluating Vendor Security Assurance

Level states that its employees do not have standing remote or administrative access to customer endpoints.

According to its published security architecture, infrastructure administration does not independently provide the ability to initiate remote control, shell, scripting, or file-management operations on managed devices.

Customer-authorized temporary support access is required before Level personnel can interact with devices through a customer account.

Level also maintains a SOC 2 Type II report available for review and documents its security development, vulnerability reporting, and incident response practices.

These assurances are relevant to MSP procurement, although buyers should review the actual documentation and evaluate its scope against their own requirements.

For additional information, see Level's security capabilities and security settings documentation.

MSPs comparing RMM vendors can also review Level's pricing to assess how its management capabilities and available security controls align with their purchasing requirements.

Building a Defensible RMM Purchasing Decision

A security-conscious RMM evaluation should produce a documented decision, not simply a completed feature checklist.

The process begins with identifying the administrative access the platform will require and the security obligations the MSP must meet.

From there, buyers should establish mandatory and conditional requirements, examine supporting vendor evidence, validate critical controls, and document unresolved limitations.

Once those requirements are satisfied, MSPs can compare operational efficiency, usability, automation capabilities, support, and total cost.

This approach helps prevent important security limitations from being overlooked during commercial negotiations.

It also gives MSPs a clearer basis for explaining their technology choices to customers and internal stakeholders.

The objective is not to eliminate every potential security risk. It is to select a platform whose capabilities, vendor practices, and operational limitations are understood and appropriately managed.

Final Thoughts

RMM security is an important purchasing consideration because remote management platforms can exercise extensive administrative control across customer environments.

MSPs also face established customer security expectations and the operational consequences of third-party technology risks.

Evaluating an RMM vendor therefore requires more than accepting advertised security features.

Buyers should verify access restrictions, remote management protections, administrative accountability, vulnerability response processes, and vendor assurance evidence.

A defensible purchasing decision identifies essential requirements, confirms that the selected platform satisfies them, and documents any remaining limitations.

By evaluating security alongside operational efficiency and cost, MSPs can choose RMM software that supports both effective IT management and responsible customer administration.

Frequently Asked Questions

1. Why is RMM security becoming an important MSP buying consideration?

RMM platforms can provide privileged administrative access across multiple customer environments. A compromised account or vulnerable platform can therefore create exposure beyond a single device. MSPs also face established expectations for cybersecurity oversight and third-party risk management, making platform security and vendor assurance important purchasing considerations.

2. What security features should MSPs prioritize when choosing RMM software?

MSPs should prioritize enforceable multifactor authentication, role-based permissions, customer or device-group access restrictions, encrypted remote connections, and administrative logging. Other important considerations include scripting permissions, session controls, API security, vulnerability management, and the ability to revoke compromised access.

3. Does a SOC 2 Type II report guarantee that an RMM vendor is secure?

No. A SOC 2 Type II report provides independent assurance about specified controls over a defined period. It does not guarantee that a product is free from vulnerabilities or that every security capability has been tested. MSPs should review the report's scope and findings alongside product documentation and technical validation.

4. How can MSPs verify an RMM vendor's security before purchasing?

MSPs can establish mandatory security requirements, request vendor documentation, review independent assurance reports, and validate critical controls during a product trial. Tests involving authentication enforcement, restricted technician access, remote approval behavior, activity logging, and access revocation can help determine whether a platform meets operational requirements.