Security

Trusted with other people's computers.

An RMM is the most privileged software an MSP runs. This page says plainly what FINN does to deserve that access, and what is still ahead of us.

What is in place

The controls.

Your data stays yoursEvery account's data is separated at the query level. Our own test suite makes about 20,000 requests from one account trying to reach another's records, on every release, and fails the build if any succeed.
Signing inPasswords are hashed with Argon2id. Two-factor codes with backup codes, and single sign-on through OIDC. Revoking a user ends their sessions immediately. Repeated failed sign-ins are slowed, by account and by address.
Who can do whatFour roles, from read-only to owner. A technician can be limited to particular clients, and an account can be limited to your office IP addresses.
The agentConnects outbound over TLS; it does not listen for incoming connections. Each device has its own key. Enrollment tokens can be revoked, and updates are verified by checksum before they are installed.
Remote sessionsThe computer being supported shows an on-screen indicator while a technician is connected. You can require the person at the keyboard to accept each session, client by client. Every session is listed and audited.
AI with a human in chargeThe assistant can propose a fix from a short, fixed list. The exact command is shown, stored, and run only when a technician approves it. Approval is single-use and is recorded on the ticket.
SecretsIntegration keys, tokens and stored credentials are encrypted with AES-256-GCM. API keys, device keys and enrollment tokens are stored only as hashes.
Audit logEvery change is recorded with who made it, what it touched, the result and the address it came from. The log can be streamed to your own log system.
In the browserHSTS, a content security policy that allows no inline script, and protection against the console being framed by another site.
BackupsThe database is backed up nightly, and a restore is tested automatically every week.
Our own dependenciesThird-party code is checked for known vulnerabilities weekly and whenever it changes.

Not done yet

Where we are being straight with you.

FINN has not yet had an independent penetration test or a SOC 2 audit. Both are planned. Until they are done we will not imply otherwise, and we will publish the results here when they are.

No covert features. FINN is for managing computers under a service agreement, with the knowledge of the people who use them. It has no hidden mode and nothing designed to avoid security software, and we will not build either.

See it for yourself.

The audit log, roles and session consent are all in the trial.