PropRecChannel
HomeInsightsAcronis found extra remote tools on 63.1% of endpoints, so MSPs may need someone who owns access hygiene

Acronis found extra remote tools on 63.1% of endpoints, so MSPs may need someone who owns access hygiene

Acronis found extra remote access tools on 63.1% of endpoints running its RMM. MSPs must decide who owns access clean-up and patch prioritisation.

Acronis says leftover remote access tools and slow third-party patching are giving attackers room to work inside MSP customers. The hiring question for MSPs is whether access clean-up and patch prioritisation sit with a named, skilled owner, or are spread thinly across a service desk that is already busy. IT Europa reported the findings on 9 November.

What Acronis found on its own endpoints

The figures come from the Acronis TRU Cyber Pulse 2026 report. Acronis found that 63.1% of more than 1.8 million endpoints already running Acronis RMM had at least one additional remote-management or remote-access tool installed. In other words, nearly two thirds of the endpoints Acronis can see through its own product have a second way to be reached remotely.

Acronis also reports that third-party application patches took a median of 5.7 days to install in the second half of 2025, and the slowest 10% took more than 24.9 days. It points to the Red Heron campaign, where a working public exploit targeting Gitea servers appeared one day after a patch was released.

Gerald Caron, Chief Information Security Officer for Acronis, warned that "old agents and accounts can remain after a provider change." On incident response, he added that "installing the patch may leave access the attacker has already established."

Three skills this puts under pressure

The report reads as a tooling story, but each recommendation depends on a person doing the work properly.

Onboarding audits

Caron's advice is to review installations when a customer is onboarded and during ongoing service reviews, remove obsolete access and investigate unfamiliar administrators. That is detailed, unglamorous work. For many MSPs it is done by whichever engineer handles the onboarding, with no standard for what "clean" looks like. The likely constraint is engineers who know enough about remote access tooling, identity and administrator accounts to spot what should not be there.

Vulnerability prioritisation

A median of 5.7 days describes the middle of the range. The risk sits in the slow tail. Caron says MSPs and their clients need an agreed process for prioritising vulnerabilities and approving urgent changes outside normal maintenance windows. Our view is that this needs someone who can rank vulnerabilities by real exposure and explain that ranking to a customer's IT lead, not only someone who can deploy patches.

Incident response that checks for persistence

If exploitation is suspected, Caron says remediation has to look for persistence, account changes and exposed credentials. That is incident response work. Many MSPs rely on a security partner or a SOC provider for it. Those that handle it in-house need engineers who can investigate as well as fix.

Hire, train or partner

For a smaller MSP, a dedicated vulnerability management hire may not be affordable. Training senior service desk or infrastructure engineers in access reviews and patch prioritisation is often the quicker route. For larger MSPs with many customers, a specialist role that owns access hygiene and patch policy across the base can be easier to justify, because the same rules apply to every customer.

The risk with training alone is retention. An engineer who becomes the person who understands RMM sprawl, identity clean-up and exploit timelines becomes more valuable to competitors and to security vendors. That is worth planning for before it happens.

Practical steps for this quarter

  • Name an owner for access hygiene. Make one person accountable for removing old agents and accounts at onboarding and offboarding.
  • Write the urgent patch rule down. Agree with customers when a patch can go out of window and who approves it.
  • Test incident skills honestly. Ask whether your team could check for persistence and exposed credentials, or whether you need a partner.
  • Benchmark the specialist. Check the market rate for security engineers before you build the role around one person.

The decision in front of you

Acronis has shown how much access can be left behind and how long patching can take. The decision for MSPs is whether to build that discipline through a specialist hire, through training existing engineers, or through a partner, and how to keep the people who end up holding it. You can check pay with our salary benchmarking, assess flight risk in your security team with our attrition risk assessment, and see how we work with MSPs and resellers. To discuss a security hire, get in touch.

Sources

What this means for you

Get our view on your team.

Tell us a little about your business and a senior consultant will come back to you the same working day, in confidence.

Or book a call with Chris

We only use your details to reply, and treat everything you share in confidence. See our privacy policy.