Remote monitoring and management
An RMM that leads with security.
See, patch, monitor, and fix your Windows, macOS, and Linux endpoints from one console. Lavawall® is built and run by ThreeShield, a Calgary audit firm, so the security controls an assessor asks for are the defaults, not add-ons.
What an RMM is for, and where most fall short
An RMM exists to do five things: see every device, patch it, watch it, fix it, and prove all of that happened. Most tools do the first four adequately and treat security and compliance as a separate purchase, so the evidence an auditor wants lives in yet another console. Lavawall was built by people who sit on the auditor’s side of the table, so patching, monitoring, remote support, and the compliance record run together.
You can run Lavawall as your RMM, or add it beside the one you have. If you are keeping your current tool, RMM augmentation covers what to layer on and why, and what RMM augmentation means explains the approach.
The modules, in one console
Each is a page of its own. Together they are the platform.
Remote support and Windows administration
A real administration cockpit in the browser, not a bolted-on screen-share. Summary below.
Patching, 7,400+ apps
Cross-platform patch management for Windows, macOS, and Linux, with the third-party apps most tools miss, and patch status kept as evidence.
Configuration vulnerabilities
Find the misconfigurations that scanners rate as findings, and fix them from the same console.
Device health and replacement
Battery, disk, memory, temperature, and reboot history, with a replacement priority so a slow machine is a plan, not a surprise.
Scripting
Run and schedule scripts across the fleet, from a signed library, with the results kept.
Application control and elevation
Let people run what they need as administrator, without a standing local-admin account and without a separate elevation product.
LAN and WAN monitoring
Watch the network the endpoints depend on, and the links between sites.
Out-of-band and environmental
Temperature, water, power, and access sensors on a radio path that keeps alerting when the internet is down.
Unified MDR alerts
Bring the alerts from Sophos, Huntress, and Microsoft Defender into one queue instead of three consoles.
Microsoft 365 and Google Workspace
Breach detection for the cloud accounts behind the endpoints. Google Workspace too.
Akira Ransomware Hunter
Catch the staging that precedes an encryption event, days before the ransom note.
Access reviews
Certify who has access to what, on a schedule, with the record an auditor accepts.
The differentiator
Remote support that is a Windows cockpit, not a screen-share
Every RMM has a remote-control button. Lavawall gives a technician the real thing, in the browser, with nothing to install and without interrupting the person at the keyboard.
The centre of it is an intelligent Backstage that extends the built-in Windows administration tools: a grouped Task Manager with live CPU, memory, disk, network, and thread figures, per-process detail down to the parent process and signature, and a file explorer you can run or download from. During an interactive session it launches more than 45 built-in admin tools as administrator, without pushing a UAC prompt to the user and without a separate elevation product.
The user stays in control the whole time. A translucent, movable notice sits on their screen so they always know someone is connected, with one click to chat or to take their privacy back. Technicians get on-screen drawing, automatic cursor hand-off, file transfer with full attributes, plain-language restart reasons, tickets on the session screen, and near-instant full-colour PowerShell, even from a phone.
Every GUI session, shell session, and shell command is logged, country and IP restrictions are on by default, and the remote desktop session is protected in transit by a FIPS 140-3 validated cryptographic module, NIST CMVP certificate #5247.
Built by an audit firm, so the security is the default
Lavawall is built and used by ThreeShield, a Calgary firm that does cybersecurity audits for a living. That shows up in the defaults: remote sessions are logged in full, country restrictions are on out of the box, the platform pushes admin tools without leaving standing local-admin rights behind, and the compliance evidence lands in the same console through the GRC module. For teams under a CJIS, HIPAA, PCI DSS, or NIST 800-171 obligation, the remote path carries a FIPS 140-3 validated module, and FIPS 140-3 support sets out exactly what is validated and what is not.
Frequently asked
- What platforms does the Lavawall RMM manage?
- Windows, macOS, and Linux endpoints from one console: patching, configuration checks, device health, scripting, and remote support across all three, plus Microsoft 365 and Google Workspace monitoring for the accounts behind them.
- Is Lavawall a full RMM, or does it add to the one I have?
- Either. You can run it as your RMM, or add it beside an existing RMM for the security, compliance, and remote-support pieces most RMMs leave thin. See RMM augmentation for that path.
- How is Lavawall’s remote support different from the remote control in a typical RMM?
- Most RMMs bolt on a basic screen-share. Lavawall gives a technician a real Windows administration cockpit in the browser: an intelligent Backstage that extends the built-in Windows admin tools, launches them as administrator without a UAC prompt, and never interrupts the user. It runs from any browser, including a phone, and every session is logged.
- Is the remote path encrypted to a FIPS 140-3 standard?
- A remote desktop session is protected in transit by a FIPS 140-3 validated cryptographic module, NIST CMVP certificate #5247. See FIPS 140-3 support for what that covers and what it does not.