SMSMC Blog

The tool your MSP uses to run your computers: security settings in NinjaOne, N-central and Datto RMM compared

Your MSP's remote monitoring and management platform can reach every computer you own. Which security settings matter, how three common platforms document them, and what to ask your MSP to show you.

By Jim Venuto

One console, every computer

In July 2021, a supply-chain ransomware attack exploited a vulnerability in Kaseya’s VSA remote management software and reached multiple managed service providers and their customers. CISA and the FBI issued guidance within days. It told affected customers to keep current backups offline and separated from the network, apply least privilege to administrative accounts, and enable multifactor authentication.

The lesson for a small business is not about one vendor. It is that your MSP’s remote monitoring and management (RMM) platform is the most powerful tool anyone uses on your network. It can run scripts, install software and open remote sessions on every managed computer. If someone gets into the MSP’s console, they can do the same. CISA, the NSA and MS-ISAC made a related point in January 2023: attackers also misuse legitimate RMM software, so organizations should audit which remote access tools are in use and authorized, and use application controls to block unauthorized ones, including portable versions.

You do not run the RMM. You can ask how it is configured. This post compares how three platforms that many MSPs use document the settings that matter, so you know what a good answer looks like.

The settings that matter

Five controls do most of the work:

  1. Multifactor authentication for every technician, enforced by the platform rather than left to each user.
  2. Role-based access, so a junior technician cannot run scripts against every client.
  3. An activity or audit log of who did what, when, on which device, that the MSP keeps and can export.
  4. Login restrictions, such as allowing console access only from the MSP’s own network.
  5. Control over which devices can run jobs, so a newly added or unapproved device cannot receive automated scripts.

NinjaOne

MFA. NinjaOne’s documentation, updated November 3, 2026, states that all NinjaOne users are required to perform MFA both at login and when performing administrative actions. It supports authenticator apps, SMS and hardware security keys, and an administrative idle-time setting controls when users must re-authenticate before an admin task.

Activity log. NinjaOne describes its Activity Feed as a chronological audit log covering system-level actions such as creating customers, users and policies, device-level changes, triggered conditions, actions, remote sessions starting and ending, patching and antivirus scans. The feed in the interface holds up to 1,000 entries; NinjaOne says the full history is available through its API.

What to ask: whether SMS is allowed as a second factor for technicians, or only app and key methods; and how the MSP keeps activity history beyond what the console shows.

N-able N-central

MFA. N-central’s documentation describes making two-factor authentication the default for all user accounts, locking it so users cannot turn it off, and propagating the setting to existing users. Its MFA overview says admins can enforce MFA for all users under their service organization and recommends doing so, especially for privileged users, using authenticator apps. Separately, N-able announced in October 2025 that MFA would become mandatory for everyone who signs in to N-able products, including N-central, through N-able Login, its single sign-on, with anyone who lacks it prompted to set it up at next login. Ask your MSP whether that is now enforced on its account.

Federated sign-in. N-able notes that when sign-in is federated to an identity provider, MFA is handled by that provider rather than in N-central. If your MSP signs in through Microsoft Entra ID or another identity provider, the MFA question moves there.

What to ask: whether MFA is locked on as the default, and if sign-in is federated, whether the identity provider enforces MFA for every technician.

Datto RMM (Kaseya)

MFA. Datto RMM’s help pages state that two-factor authentication is enforced for all Datto RMM users; anyone without it is prompted to set it up at next login, using an authenticator app.

Other controls. Datto RMM’s security best practices recommend configuring security levels so staff get only the permissions they need, restricting web interface logins to an accepted range of IP addresses, using user activity logging to audit staff actions (noting that deleting a user does not delete their activity data), and requiring administrator approval before new devices can run jobs, download components or accept policies. Agent policies can stop specific devices from receiving jobs at all.

What to ask: whether IP restrictions are turned on for the web interface, and whether device approval is required.

Side by side

ControlNinjaOneN-able N-centralDatto RMM
MFA for techniciansRequired for all users at login and for admin actionsCan be set as the locked default for all users; required through N-able LoginEnforced for all users
Second-factor methods documentedAuthenticator, SMS, security keysAuthenticator apps (TOTP)Authenticator app
Activity or audit logActivity Feed; full history via APIAudit logs of user activity, logins and configuration changes, per N-able’s security guideUser activity logging, kept after user deletion
Login restriction by IPAsk your MSPAsk your MSPDocumented best practice
Device approval before jobsAsk your MSPAsk your MSPDocumented best practice

“Ask your MSP” means the vendor’s public documentation does not describe the setting, not that the product lacks it.

All three now require or can enforce MFA for technicians. The differences are in the details: which second factors are allowed, how long logs are kept and how easily they can be exported, and whether login and device restrictions are turned on. Those details are configuration choices your MSP makes, which is why the conversation matters more than the logo.

The questions to send your MSP

You do not need access to the console. Ask for answers in writing, ideally with a screenshot:

  1. Which RMM and remote access tools do you use on our systems?
  2. Is MFA enforced for every technician who can reach our environment, and which methods are allowed?
  3. Who on your team can run scripts against our devices, and how is that limited?
  4. How long do you keep the activity log for actions on our devices, and can you export it for us?
  5. Are console logins restricted to your network or another approved path?
  6. Do new devices need approval before they can receive automated jobs?
  7. How would you tell us if your RMM platform or your own network were compromised?

CISA’s 2021 guidance for small and mid-sized businesses working with MSPs supports the last question directly: it recommends that contracts include notification of confirmed or suspected security events on the provider’s infrastructure, appropriate monitoring and logging of provider-managed systems, and monitoring of the provider’s activity on your network.

When to get help

If the answers come back vague, or you are not sure whether they are good, an independent review can read them with you and turn the gaps into contract language and a follow-up list your MSP can work through.

Want to talk it through? Book a free 30-minute call with Security Medic Consulting.

Sources