Security and trust
How Enlist protects your MSP's and your clients' data. Last updated 18 November 2026.
Enlist is in early access and has no third-party certification yet. It is built so an MSP using it can pass SOC 2, HIPAA, ISO 27001, GDPR, PCI DSS, NIST SP 800-53, NIST CSF and CCPA/CPRA audits: the controls below are the ones those audits look for. An independent audit and penetration test come before general availability.
Signing in
- Passkeys only. Enlist has no passwords and no text-message codes, so there is nothing to phish or reuse.
- Optional Microsoft Entra or Google sign-in on top of the passkey, so your own conditional-access rules apply.
- Changing people, roles, sign-in settings and trusted passkeys, and viewing a device password, each need a fresh passkey check.
- Each MSP sets its own idle sign-out and longest session.
Who sees what
- Every MSP's data is kept apart by the database itself (row-level security), not only by the application.
- Roles (owner, admin, technician, read-only) can be limited to one client or one site.
- Device admin passwords and recovery keys are shown only with a passkey check and a written reason, and each view is logged.
- An access review report lists everyone's roles and last sign-in, and flags accounts unused for 90 days.
When Enlist staff can see your data
- Enlist staff can't see inside your MSP unless one of our owners or admins opens it for a support request. They sign in with three factors, and opening your MSP takes a fresh passkey check, a one-time code and a written reason.
- Your owners get an email as soon as it's opened, with the reason, and a summary when it's closed.
- Inside your MSP, staff work as a named support user ("Name (EnlistIt support)"). Your own permissions, row-level security and activity log apply, so every action shows in your log.
- A support session lasts an hour at most. The support user can never sign in on its own.
- Your devices only accept blueprint changes signed by our staff if your own trusted admins approve their passkey first.
Encryption
- TLS 1.2 or newer on every connection (1.3 preferred).
- Agents connect outbound only, over mutual TLS with a certificate unique to each device. No inbound ports are opened on your clients' networks.
- Stored data is encrypted at rest. Device passwords and recovery keys are encrypted again with a key per MSP, and that key is itself locked by a master key kept outside the database, in a file only the Enlist server can read.
- Agent updates are code-signed (Windows Authenticode, Apple Developer ID) and checked against a separate signed manifest before they install.
Audit log and alerts
- Every sign-in, change and sensitive view goes into an append-only, hash-chained audit log, so a removed or altered entry shows.
- Security alerts by email or webhook: a new admin, role changes, repeated failed sign-ins, many password views, sign-in setting changes and more.
- One person retiring many devices or viewing many secrets in a short time is paused until another admin lets them carry on.
Backups and recovery
- The database is backed up every night, encrypted, to separate storage: Oracle Cloud Object Storage in the United States, where the server can add backups but can't read, change or delete them, and where each copy is deleted after 35 days.
- A second encrypted copy is kept on WolfByte.Works's own backup storage in the United States for up to 6 months.
- Target recovery: no more than 24 hours of data lost and service back within 4 hours. The restore steps are written down.
Who processes data for us (subprocessors)
The companies that handle data so Enlist can run, what each does and where, are on the Subprocessors page. Any change is announced there, and to MSP owners by email, 30 days before it starts.
Who looks after what
| Area | Enlist | Your MSP |
|---|---|---|
| Servers, database, backups | Runs, patches, encrypts and backs them up | Nothing to do |
| Your team's access | Passkeys, roles, session limits, access reviews | Decides who gets which role, reviews access each quarter, removes leavers |
| Sign-in policy | Enforces passkeys and, if you choose, Entra or Google | Runs your Entra or Google conditional-access rules |
| Agents | Signs, updates and authenticates them | Chooses which devices are enrolled |
| Scripts and software you deploy | Scans packages for malware and logs every run | Decides what is deployed and what it does |
| Alerts | Detects and sends them | Routes them to someone who acts on them |
| Clients' own compliance | Provides the controls and the evidence | Owns the client relationship and its agreements |
Reporting a security issue
Email [email protected]. Please report it privately and give us a chance to fix it before you share it.