Before You Begin
System requirements and prerequisites for installing Root Lock by HeartSuite.
Getting Started
Choose your setup path and begin installation.
Overview: On a single host, Root Lock by HeartSuite uses Cloud Path (pre-installed instance, Dashboard appears on first login) or Local Path (manual installation with multiple reboots). Cloud Path and Local Path both arrive at the Dashboard after initial setup.
Before you begin
Check Before You Begin for system requirements and prerequisites, then follow Cloud Path or Local Path below.
Order of work
On Local Path, finish distribution updates and install the packages and services this host will actually run. Then run the installer. After the first reboot into the Root Lock kernel, leave the host quiet until the Dashboard appears.
On Cloud Path, Root Lock already finished initial setup during image preparation. First-boot leftovers can still appear in the queues — do not approve them if they are not runtime.
When the Dashboard appears, Root Lock has already added the programs that executed at boot and shutdown. In Setup Mode, Root Lock logs the rest of the workload. Allowlisting Basics covers approve and skip. After Lockdown, add software through Protecting During Maintenance.
Choose your path
Cloud Path
Launch a pre-installed Root Lock instance. No download or kernel installation required. First-boot leftovers can still appear in the queues — dismiss them if they are not runtime.
- Launch the instance — start a pre-installed image on AWS, Google Cloud, Azure, DigitalOcean, Linode, or another provider.
- Open the Dashboard — you boot into Setup Mode and the Dashboard appears on first login. Initial setup is already complete.
- Verifying Installation — confirm the Dashboard is ready, then follow the Suggested Next Step to begin allowlisting.
Local Path
Install Root Lock on bare metal or a full virtual machine with hardware virtualization. Finish distribution updates and the packages this host will actually run, then:
- Obtaining Root Lock — download the installer from heartsecsuite.com.
- Installation Part 1 — verify the download, run the installer, and reboot into the Root Lock kernel.
- Installation Part 2 — complete initial setup through multiple reboot cycles until the Dashboard confirms it is complete.
- Verifying Installation — confirm initial setup is complete in the Dashboard.
Many hosts still install through Cloud Path or Local Path on each machine. Ansible, Terraform, and GitOps apply allowlist policy after that install — see Central Policy.
Once initial setup is complete, Cloud Path and Local Path merge — the Dashboard shows the setup checklist and the Suggested Next Step directs you to begin allowlisting.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.