24 min read

How Cybercriminals Abuse Legitimate RMM Tools for Remote Access

How Cybercriminals Abuse Legitimate RMM Tools for Remote Access

Remote monitoring and management (RMM) software allows IT teams to troubleshoot devices, execute commands, deploy updates, and manage endpoints without being physically present. These capabilities make RMM essential for managed service providers (MSPs) and internal IT departments. They also make legitimate remote management tools attractive to cybercriminals.

Rather than relying exclusively on custom malware, attackers can use commercially available remote access software to maintain control of compromised systems. The applications may be legitimate, digitally signed, and familiar to security teams. The problem is that the individuals operating them are not authorized.

This creates a difficult security challenge. Activities such as remote sessions, command execution, and file transfers can resemble routine administration even when they are part of an intrusion.

Understanding how cybercriminals abuse legitimate RMM tools, how to recognize suspicious activity, and which security controls reduce exposure is essential for organizations that depend on remote IT administration.

What Is RMM Tool Abuse?

RMM tool abuse occurs when a threat actor uses legitimate remote monitoring, management, or remote support software to gain, maintain, or expand unauthorized access to systems.

Unlike malware developed specifically for malicious access, these incidents involve software originally designed for legitimate administrative purposes.

An attacker might install an unauthorized RMM agent, persuade an employee to approve a remote support session, or compromise an existing management account.

Depending on the software and available privileges, the attacker may gain capabilities such as:

  • Establishing interactive remote desktop sessions.
  • Executing commands and administrative scripts.
  • Accessing files and transferring data.
  • Managing processes, services, and system settings.
  • Installing additional software.
  • Maintaining access through persistent management agents.

The MITRE ATT&CK framework documents malicious use of legitimate remote access software under technique T1219, Remote Access Tools.

RMM Software vs. Remote Support Tools

Although the terms sometimes overlap, not every remote access application is a full RMM platform.

RMM platforms typically combine persistent endpoint agents, device monitoring, remote administration, scripting, automation, and centralized management.

Remote support tools primarily facilitate interactive troubleshooting sessions, sometimes requiring users to launch an application or approve a connection.

Remote desktop technologies, such as RDP, provide interactive access to computers but do not necessarily include the broader monitoring and automation capabilities of an RMM platform.

Attackers can misuse all three categories. However, the methods used to establish access, maintain persistence, and evade detection can differ.

The central security issue is authorization, not whether the application was originally designed for legitimate use.

Why Cybercriminals Use Legitimate RMM Software

Established remote management products offer several advantages to attackers who obtain unauthorized access.

Legitimate Software Can Blend Into Normal IT Operations

Organizations routinely allow approved management applications to communicate with external services and perform administrative tasks.

Traditional security tools may recognize these applications as legitimate rather than malicious.

Modern endpoint detection and response (EDR) products can still identify suspicious behavior associated with approved software. However, determining whether an RMM session is malicious often requires information about the account, endpoint, timing, and actions involved.

For example, a remote management agent running on a workstation might be normal. A previously unseen agent appearing immediately after suspicious PowerShell activity deserves closer investigation.

Remote Management Offers Powerful Administrative Functions

Many RMM platforms provide more than screen sharing.

Features such as background command execution, software deployment, file management, and scripting allow technicians to administer devices efficiently.

Attackers who gain unauthorized control may use these same capabilities to conduct reconnaissance, establish persistence, or introduce additional tools.

The impact depends on the permissions available to the compromised account or agent. An RMM session does not automatically provide domain administrator access or unrestricted control of a network.

Nevertheless, management agents operating with elevated local privileges can significantly increase the consequences of unauthorized access.

Cloud Connectivity Can Simplify Remote Access

Modern remote management software commonly uses outbound encrypted connections to communicate with management infrastructure.

This allows technicians to access endpoints without exposing traditional inbound remote desktop services directly to the internet.

An attacker-controlled agent may use the same connectivity model.

Consequently, network defenses cannot rely exclusively on unusual ports or unfamiliar communication protocols to identify malicious remote access.

Persistent Agents Can Preserve Attacker Access

RMM agents are often designed to continue operating after a user logs out or the system restarts.

This supports unattended maintenance and continuous monitoring.

When an attacker deploys an unauthorized persistent agent, the same behavior may provide continued access after the original compromise.

How Cybercriminals Gain Access Through RMM Tools

RMM abuse does not follow a single intrusion pattern. The method of access determines both the potential impact and the appropriate defensive response.

1. Social Engineering and Fake Technical Support

An attacker impersonates an IT technician, help desk representative, or trusted software provider.

The victim receives a phone call, email, or message claiming that their computer requires urgent troubleshooting or security verification.

The attacker then persuades the user to launch a legitimate remote support application and authorize a connection.

Once the session begins, the attacker can interact with the system within the application's available permissions.

This method does not necessarily involve exploiting a technical vulnerability.

Microsoft documented this approach in its May 2024 investigation of Storm-1811.

The attackers impersonated technical support personnel and persuaded victims to use Microsoft Quick Assist. Subsequent activity included additional remote management tools and malware associated with Black Basta ransomware.

The incident illustrates how an unauthorized session can begin through an otherwise legitimate support workflow.

2. Installing an Unauthorized RMM Agent

An attacker who already controls an endpoint may deploy a legitimate remote management agent connected to an account under the attacker's control.

The initial compromise might involve phishing, stolen credentials, exploitation of a vulnerable service, or another intrusion method.

Once the new agent is operational, it creates a separate remote access channel.

This distinction is important: the RMM software may not be responsible for the initial compromise. It can instead become a mechanism for maintaining access.

Some remote support applications also offer portable executables that can run without conventional installation.

In January 2023, CISA, NSA, and MS-ISAC published a joint cybersecurity advisory warning that portable remote management software can enable access without administrative installation privileges.

The NSA's official announcement summarizes the advisory and its recommended defenses.

Consequently, monitoring installed applications alone is insufficient. Security teams must also examine executable activity, network connections, and persistence mechanisms.

3. Compromising an Existing RMM Account

Instead of introducing new software, an attacker may obtain control of an account used to operate an organization's approved RMM platform.

Potential attack methods include credential theft, phishing, stolen authentication sessions, and abuse of insufficiently protected administrative accounts.

The management agent may already be installed, properly enrolled, and operating normally.

Depending on the account's permissions, the attacker may be able to access multiple endpoints, execute scripts, or initiate remote sessions.

For MSPs, the impact can extend across customer environments when technician permissions are overly broad.

Unlike unauthorized agent deployment, this scenario may not produce a new software installation or suspicious executable.

Account activity, permission changes, session history, and endpoint behavior become critical investigation sources.

4. Exploiting Vulnerable Remote Management Infrastructure

Attackers may also exploit vulnerabilities in remote management software or supporting infrastructure.

A vulnerable self-hosted management server, exposed administration interface, or remote support service can become an entry point.

Once access is obtained, legitimate administration functions may be misused to expand the intrusion.

This differs from installing legitimate software for malicious purposes. It involves exploiting a security weakness to gain unauthorized access.

Keeping management infrastructure updated and limiting unnecessary exposure remain important safeguards.

Unauthorized Agents vs. Compromised RMM Accounts

These two scenarios can look similar from the perspective of an affected endpoint, but they require different investigation priorities.

Security consideration

Unauthorized RMM agent

Compromised RMM account

Primary access method

Attacker deploys or launches remote management software

Attacker controls an existing management identity or session

Software inventory

May reveal a new or unfamiliar application

May show only approved software

Common evidence

Process execution, new services, agent configuration, unusual network activity

Login records, active sessions, technician actions, permission changes

Potential scope

Endpoints where the unauthorized agent operates

Endpoints accessible to the compromised account

Initial containment

Restrict unauthorized connectivity and contain affected endpoints

Revoke unauthorized sessions and credentials, restrict compromised account access

Investigation priority

Determine how the software appeared and what it performed

Determine how the identity was compromised and which systems it accessed

An attacker may also combine these approaches, initially compromising an approved RMM account and subsequently deploying additional agents to preserve access.

Incident investigations should therefore consider whether multiple access methods are operating simultaneously.

What Cybercriminals Do After Establishing Remote Access

Once attackers establish unauthorized remote control, their actions depend on their objectives and available privileges.

System Reconnaissance

Attackers may inspect device information, user accounts, installed software, network connections, and accessible resources.

This information helps identify valuable targets and determine whether additional privileges are required.

Credential Theft and Privilege Escalation

Attackers may search for accessible credentials, sensitive files, or weaknesses that could support privilege escalation.

RMM software does not inherently bypass operating system permissions or authentication controls.

However, the privileges available through remote administration may provide opportunities for additional malicious activity.

Lateral Movement

Attackers may use a compromised endpoint or management account to reach additional devices.

This can involve legitimate administration protocols, stolen credentials, or permissions already available within the RMM platform.

For MSPs, poorly scoped permissions can increase the potential impact because a single management environment may connect to several customer networks.

Data Theft and Ransomware

Attackers may introduce additional software to collect information, transfer sensitive files, disable defenses, or deploy ransomware.

The RMM application acts as an access or execution mechanism. Other tools may perform data theft or encryption.

Real-World Examples of Legitimate RMM Tool Abuse

Several publicly documented incidents demonstrate how legitimate remote management applications fit into different attack scenarios.

CISA's 2023 Advisory: Legitimate Tools in Financial Fraud

In January 2023, CISA, NSA, and MS-ISAC issued a joint advisory describing malicious use of ScreenConnect and AnyDesk.

The campaign involved phishing messages that directed victims to legitimate remote management software used in refund scams.

The advisory also warned about broader risks involving persistence and command-and-control access.

The security lesson: Software legitimacy is not evidence of authorized use. Organizations need controls for identifying unapproved remote management applications, including portable executables.

Storm-1811: Exploiting User Trust in Technical Support

Microsoft's May 2024 investigation documented attackers using Quick Assist after impersonating technical support personnel.

Once victims granted access, the attackers introduced additional tools, including ScreenConnect and NetSupport Manager, during activity associated with Black Basta ransomware.

The original remote support session was established through social engineering rather than exploitation of Quick Assist itself.

The security lesson: Technical controls must be reinforced by trustworthy support verification procedures. Employees should be able to confirm that a remote access request genuinely originated from their IT team.

Storm-2570: Remote Management as Part of a Broader Intrusion

In September 2026, Microsoft documented Storm-2570 activity involving multiple legitimate remote management products.

Observed tools included Atera, MeshAgent, ScreenConnect, Splashtop, Remotely_Agent, and NinjaRMM.

Microsoft reported that the threat actor repeatedly used remote management utilities after initial access, including for persistence, command execution, and expanding control.

One distinctive technique involved renaming MeshAgent executables and services to resemble the compromised organization's naming conventions. For example, attackers incorporated organization-specific names into MeshAgent executable filenames, making the software appear more consistent with the victim's environment.

This demonstrates why unfamiliar or unexpectedly renamed management agents deserve investigation, even when the underlying executable is legitimate.

Other tools supported credential theft, network discovery, lateral movement, and data exfiltration before ransomware deployment.

The report described incidents involving different ransomware families, including Qilin, DragonForce, Anubis, and BERT.

The security lesson: Defenders should look for recurring attacker behavior rather than focusing exclusively on individual malware families or remote access products.

These incidents do not establish that the named RMM vendors were compromised or that their products contained exploited vulnerabilities.

They demonstrate how legitimate administrative software can be incorporated into malicious operations.

Why RMM Abuse Is Difficult to Detect

The central detection challenge is that malicious activity may resemble ordinary remote administration.

A technician and an attacker might both execute PowerShell commands, transfer files, restart services, or establish remote desktop sessions.

The difference often lies in authorization and the sequence of surrounding events.

Several factors complicate detection.

Approved applications may be trusted. Security controls often allow sanctioned remote management software because administrators depend on it.

Encrypted connections limit network visibility. Network tools may identify destinations, connection duration, and traffic volume without revealing every action inside an encrypted remote session.

Background management may not interrupt the user. Remote commands and file operations can occur without visibly taking control of the desktop.

Routine administrative activity creates noise. MSP technicians regularly run scripts, deploy software, and troubleshoot devices across many customers.

Multiple remote access utilities may be legitimate. Organizations sometimes operate an RMM platform alongside remote support products, security agents, and vendor-specific tools.

These conditions make simple application-name detections inadequate.

A stronger approach combines software authorization, process telemetry, identity monitoring, network activity, and management platform records.

Warning Signs of Unauthorized RMM Activity

Individual indicators do not automatically establish malicious intent, but combinations of events can justify investigation.

Warning sign

Why it deserves attention

An unfamiliar RMM agent appears

May indicate an unauthorized remote access channel

A portable support executable runs unexpectedly

May bypass installation-based inventory

A new management service appears after suspicious activity

Could indicate persistence

Remote sessions occur outside expected workflows

May indicate unauthorized access

A technician account suddenly accesses unfamiliar devices

Could suggest account compromise

Remote management processes launch unusual shells or scripts

May indicate malicious command execution

An unexpected second remote access product appears

Could provide an alternative access channel

Remote administration is followed by security-control changes

May indicate an attempt to weaken defenses

Suspicious file transfers follow remote sessions

Could indicate unauthorized data collection

These observations should be evaluated against change records, maintenance windows, technician assignments, and authorized management activity.

For example, an overnight remote session may be normal for an MSP supporting international clients.

An overnight session initiated by an unfamiliar account against a sensitive server, followed by unexpected credential-access activity, presents a substantially stronger reason for investigation.

A Practical Workflow for Detecting RMM Abuse

Security teams can improve detection by correlating multiple events rather than treating every remote access process as suspicious.

The MITRE ATT&CK detection strategy DET0496 provides a useful foundation for this approach.

It focuses on sequences involving remote access execution, persistence, outbound connectivity, and subsequent interactive activity.

Step 1: Identify Unexpected Remote Access Software

Begin with a maintained inventory of approved management and support applications.

Compare that inventory against endpoint process execution, installed applications, and newly created services.

Pay particular attention to unknown remote support executables, unexpected applications in user-writable directories, newly created management services, and unfamiliar agent configurations.

An unapproved application should trigger validation, not an automatic conclusion that an incident has occurred.

Step 2: Examine the Execution Context

Determine how the application started and which account executed it.

Relevant questions include:

  • Was it launched by an approved installer or management process?
  • Did it originate from a temporary or user-writable directory?
  • Was it executed shortly after suspicious email or browser activity?
  • Which user or service account initiated the process?
  • Is the execution consistent with an approved support request?

On Windows endpoints, Sysmon Event ID 1 can provide useful process creation details when appropriate logging is configured.

Step 3: Check for Persistence and Network Connections

Examine whether the application created a service, scheduled task, or other persistence mechanism.

Windows Service Control Manager Event ID 7045 can help identify newly installed services when the relevant system events are available.

Sysmon Event ID 3 can help correlate agent execution with external network communication.

These event sources are not universally available. Sysmon must be installed and configured to collect the relevant events, while Windows event logs must be retained and collected appropriately.

Persistent outbound traffic is not inherently suspicious for RMM software. The important question is whether the application and its connectivity are authorized.

Step 4: Correlate Subsequent Administrative Activity

Look for unexpected shell execution, account changes, security configuration modifications, network discovery, additional software deployment, and unusual file access.

A single administrative command may be legitimate.

A previously unknown RMM application followed by persistence, outbound connectivity, and unauthorized system changes provides a stronger investigative signal.

Step 5: Compare Findings With Authorized Activity

Check relevant help desk tickets, change records, technician assignments, and RMM session histories.

Determine whether the observed actions correspond to an approved administrative task.

Without this operational context, automated detection rules can generate unnecessary alerts and interrupt legitimate work.

Example: Investigating an Unexpected Remote Access Agent

Consider a workstation where endpoint monitoring identifies a previously unseen remote support executable.

The investigation reveals the following sequence:

  1. The application was launched from a user-writable directory.
  2. A new service appeared shortly afterward.
  3. The endpoint established a persistent outbound connection.
  4. The remote access process subsequently launched an administrative shell.
  5. No approved support ticket or authorized deployment explains the activity.

No single observation proves malicious intent.

Together, however, these events establish a credible reason to investigate possible unauthorized remote administration.

The security team can then contain the affected endpoint, preserve relevant evidence, identify the responsible account, and determine whether additional systems were accessed.

How to Investigate a Potentially Compromised RMM Account

Unauthorized agent detection is only part of the problem.

An attacker operating an approved RMM account may not introduce unfamiliar software. Existing endpoints and agents can appear normal while an unauthorized operator uses legitimate administrative permissions.

Investigations should therefore focus on identity activity, session behavior, and the scope of administrative actions.

Review Authentication and Session Activity

Examine available sign-in records for unusual access patterns.

Potential indicators include:

  • Sign-ins from unfamiliar locations or IP addresses.
  • Unexpected authentication methods or changes to MFA settings.
  • New sessions inconsistent with normal technician activity.
  • Simultaneous activity that does not match expected behavior.
  • Unexpected administrative account or permission changes.

Unusual geographic activity is not conclusive evidence of compromise. VPN usage, travel, and changes in working arrangements can produce legitimate variations.

Examine Device Access and Administrative Actions

Compare the account's recent activity with its assigned responsibilities.

Relevant questions include:

  • Did the account suddenly access unfamiliar customers or device groups?
  • Were remote sessions initiated without corresponding support requests?
  • Were scripts executed across an unusually large number of endpoints?
  • Did the account modify permissions or administrative settings?
  • Were new users, devices, or management agents added unexpectedly?

A technician account that normally manages a small group of endpoints but suddenly executes commands across unrelated customer environments warrants investigation.

Correlate Platform Logs With Endpoint Telemetry

Management platform activity records can establish which account initiated a session or administrative action.

Endpoint telemetry may provide further evidence of what occurred on the affected device.

Together, these sources can help reconstruct suspicious activity.

However, visibility varies by product and configuration. Some platforms record session metadata without capturing full command transcripts or remote desktop recordings.

Security teams should understand these limitations before relying on platform logs during an investigation.

Contain the Compromised Identity

When compromise is suspected, follow established incident response procedures to restrict the affected account and revoke unauthorized sessions.

Investigate exposed credentials, authentication methods, privileged access, and affected devices.

For MSPs, the investigation should include a review of customer environments accessible to the affected identity.

How MSPs and IT Teams Can Prevent RMM Abuse

Reducing RMM abuse requires controls across software execution, identity management, endpoint security, and administrative processes.

1. Maintain an Approved Remote Access Inventory

Document the RMM and remote support products authorized within the organization.

For each application, record its intended purpose, responsible team, permitted endpoints, and deployment method.

Include persistent agents and portable support executables.

Periodically compare the inventory against actual endpoint activity.

Unknown applications should be investigated and either approved through established procedures or removed through appropriate security processes.

2. Restrict Unauthorized Remote Administration Software

Use application control policies to restrict unapproved remote access applications.

On supported Windows systems, AppLocker and App Control for Business can help enforce software execution rules.

Application controls should account for portable executables and applications that can launch from user-writable locations.

Organizations should avoid excessively broad allowlist rules that permit entire categories of remote access software without approval.

Restrictions must be tested against legitimate support workflows before enforcement.

3. Secure RMM Accounts and Sessions

Management accounts should be treated as privileged identities.

Organizations should:

  • Require multifactor authentication.
  • Use individual technician accounts.
  • Apply role-based access control.
  • Limit access to assigned devices and customers.
  • Review administrative permissions regularly.
  • Revoke unnecessary or compromised sessions.
  • Remove access promptly when roles change.

MFA significantly reduces password-based compromise risks, but it does not eliminate session theft, social engineering, or other identity attacks.

4. Reduce the Scope of Administrative Privileges

Management permissions should match operational responsibilities.

A technician supporting a particular customer should not automatically have administrative access to unrelated customer environments.

For MSPs, properly scoped permissions help reduce the impact of compromised accounts.

Network segmentation and restrictions on administrative communication can further limit opportunities for lateral movement.

5. Monitor Remote Access and Administrative Behavior

Security monitoring should cover both the presence and behavior of remote management software.

Useful evidence includes process creation, service changes, authentication events, remote sessions, script execution, administrative account changes, and unusual network connections.

For a more detailed discussion of monitoring and accountability, see Remote Access Audit Logs Explained: How MSPs Improve Security, Compliance, and Operational Visibility.

Audit trails support investigation and accountability, but they do not automatically provide malicious-activity detection or alerting.

Organizations should understand exactly what their selected products record and use appropriate endpoint security monitoring to complement platform logs.

6. Keep Management Software and Endpoints Updated

Maintain current versions of operating systems, remote management agents, and supporting infrastructure.

Monitor for vulnerabilities in externally accessible management services.

Review administrative interfaces, authentication policies, access restrictions, and logging settings regularly.

Patch management should complement identity security and access control rather than serve as the sole defense against RMM abuse.

7. Train Employees to Verify Remote Support Requests

Establish a trusted procedure for confirming unexpected technical support contact.

Employees should not install remote access applications or approve sessions solely because someone claims to represent IT support.

Verification through an established help desk channel can reduce the effectiveness of technical support impersonation.

For broader guidance on securing RMM environments, see RMM Security: Best Practices to Protect Remote Monitoring and Management.

What to Do When an Unauthorized RMM Tool Is Discovered

An unfamiliar remote management application should be investigated as a potential security incident until its purpose and authorization are established.

The immediate priorities are containment, evidence preservation, and determining the scope of access.

1. Validate the Activity

Identify the application, affected devices, execution history, associated accounts, and available session records.

Check whether the activity corresponds to an approved deployment or support request.

2. Contain Unauthorized Access

Follow the organization's incident response procedures to isolate affected systems or restrict malicious connectivity.

For compromised management accounts, revoke unauthorized sessions and credentials while preserving relevant evidence.

3. Preserve Evidence

Collect available endpoint, identity, network, and RMM platform logs.

Where feasible, preserve relevant forensic information before uninstalling applications or making changes that could destroy evidence.

4. Investigate the Scope

Determine how the attacker obtained access, what administrative activity occurred, and whether credentials or additional endpoints were compromised.

MSPs should investigate potential effects on customer environments and follow applicable incident notification requirements.

5. Eradicate Unauthorized Access and Recover

Remove unauthorized agents, revoke compromised credentials and sessions, address the original intrusion path, and verify that additional persistence mechanisms are no longer present.

Restore affected systems through established recovery procedures and continue monitoring for recurrence.

Uninstalling an unauthorized agent may eliminate one access method while leaving other attacker-controlled mechanisms intact.

How Level Supports Secure Remote Management

The misuse of legitimate remote administration software reinforces an important principle: RMM security depends on controlling who can access endpoints, what they are permitted to do, and how administrative activity can be reviewed.

Level provides remote monitoring and management for MSPs and internal IT teams, with controls designed to govern authorized administration.

Role-Based Permissions and Device Scoping

Level supports role-based permissions that control which management actions technicians can perform.

Permissions can be scoped by device group, allowing organizations to assign different access rights based on technician responsibilities.

This helps implement least-privilege administration and reduce unnecessary access across managed environments.

For additional context, see Level's guide to role-based access control.

Two-Factor Authentication and IP Restrictions

Level allows administrators to require two-factor authentication for technician accounts.

Organizations can also configure IP restrictions that limit where technicians can access the management platform.

These controls help reduce exposure from stolen credentials and unauthorized login attempts.

They should be combined with appropriate session management, account reviews, and endpoint security.

Configurable Remote Control Approval

Level allows organizations to configure what happens when a technician initiates a remote control session.

Two approval modes are available:

  • Notify end user: A notification appears when the remote session starts, but the user does not need to approve the connection. This is the default.
  • Ask for approval: The user receives a request to approve or deny the session.

When approval is requested, administrators can configure whether an unanswered request eventually allows the connection or is denied.

Organizations that require explicit consent should select the option that denies the connection when the user does not respond.

These settings can also be configured at the device-group level.

Importantly, the approval requirement applies to interactive remote control sessions. Level's background management capabilities do not use the same end-user approval prompts.

Administrators should therefore protect background management through permissions, account security, and appropriate monitoring.

See Level's Remote Control Approval documentation for configuration details.

Administrative Activity and Session Visibility

Level provides activity records that help administrators review management operations.

Remote access activity records identify the technician, endpoint, session type, connection type, duration, and relevant timestamps.

Level also records script, automation, and configuration activity.

However, remote access Activity records contain session metadata rather than full terminal command transcripts or session video recordings.

These records support accountability and incident investigation, but they should not be treated as comprehensive endpoint threat detection.

Organizations requiring detailed endpoint-level investigation should supplement platform records with operating system logs, EDR telemetry, and other security monitoring.

See Level's Activity documentation for details about available records.

Security Configuration and Abuse Prevention

Level provides additional security settings, including inactivity timeouts and the ability to review signed-in sessions.

It also maintains an Abuse and Restricted Use Policy that prohibits malicious and unauthorized use of its services.

Level's published security information also describes platform-level abuse monitoring, including analysis of account, authentication, device, and execution signals. This monitoring complements, but does not replace, customer-side endpoint security and incident response.

Organizations reviewing their remote administration security can explore Level's security features and Securing Level configuration guide.

For MSPs and IT teams evaluating a new RMM platform, explore Level to see how its remote management capabilities, access controls, and administrative visibility fit into a secure IT management workflow.

Final Thoughts

Cybercriminals do not always need custom malware to maintain remote access to compromised systems. Legitimate remote management applications can provide many of the administrative capabilities attackers seek when they obtain unauthorized control.

For MSPs and internal IT teams, effective defense requires more than identifying installed remote management products.

Unauthorized agent deployment and compromised RMM accounts present different detection challenges. Organizations need visibility into software execution, technician identities, administrative permissions, and endpoint activity.

A practical starting point is to review approved remote access tools, management account permissions, and available security telemetry.

The objective is to preserve the operational benefits of remote administration while ensuring that powerful management capabilities remain under authorized control.

Frequently Asked Questions

1. Can legitimate RMM software be used as malware?

Legitimate RMM software is not inherently malware, but attackers can misuse its capabilities for unauthorized remote access, persistence, and command execution. An attacker may install an unauthorized agent or compromise an existing management account. Security teams should evaluate authorization and behavior rather than treating every legitimate application as safe or malicious.

2. How can IT teams detect unauthorized RMM tools?

IT teams can compare running processes and installed applications against an approved remote access inventory. They should also examine new services, unusual network connections, unexpected remote sessions, and suspicious administrative activity. Correlating multiple events helps distinguish malicious use from routine IT maintenance.

3. Can attackers abuse an RMM platform without installing new software?

Yes. An attacker who compromises an existing RMM account may be able to operate approved agents already deployed across managed endpoints. This makes identity security, session monitoring, role-based permissions, and activity logging critical, even when software inventories show no unauthorized applications.

4. Should organizations block all remote management software?

Organizations should restrict unauthorized remote administration software while preserving approved management tools required for business operations. Application controls, multifactor authentication, least-privilege permissions, and monitoring help reduce the risk of misuse without unnecessarily disrupting legitimate remote support and endpoint management.