MantisOps
MANTISOPS Managed IT Operations
Home

Remote Access Security

MantisRMM security brief · updated November 7, 2026

Remote access is the most powerful thing an IT platform does, so it should be the most controlled. This page summarizes how MantisRMM limits and records it. The two-page brief has the full detail and a checklist of questions you can ask any remote access vendor.

Download the security brief (PDF)

How devices connect

  • Outbound only. The agent connects out to the platform. It does not listen for inbound connections for remote access.
  • Per-device identity. Each device has its own secret, stored hashed. A wrong secret is refused, and a cloned device is detected and held.
  • Temporary enrollment. Installer codes expire and are exchanged for a one-time key for a single device.

Who can use it

  • MFA for every password sign-in, with no opt-out. Admins can require passkeys.
  • Step-up. Opening a terminal or remote desktop on a Windows Server, Linux or macOS machine asks for a fresh authenticator code.
  • Granular permissions for terminal, remote desktop, scripts, files and software, enforced at the API and scoped to companies, sites or device groups.
  • IP allowlists for console sign-in, agents and probes. A list that would lock you out is refused.

Limits and kill switches

  • Bulk actions escalate. More than 10 devices needs a fresh code; more than 50 or across companies needs a second administrator. Destructive actions always need step-up.
  • Pause all dispatch cancels queued work, stops running work and ends open terminal and remote desktop sessions. Freeze a user takes effect immediately and ends their live sessions.

Visibility and trust

  • Always notified. Every remote desktop session shows the person at the machine who is connecting. It cannot be turned off.
  • Audit trail. Actions are logged with who, from where and which devices, in a hash-chained log kept outside your tenant database. Stream it to your own SIEM with signed lines.
  • Signed updates. The agent installs an update only if its manifest is signed by a pinned release key and every file matches.

This page and the brief describe how MantisRMM behaves at the time of writing. Defaults can be changed by tenant administrators, and some controls depend on agent version and platform. It is not a certification, an audit report or a guarantee against misuse. See also Trust & Security.

Contact

Security questions or reports: security@mantisops.net

← Back to MantisOps