Review queues: programs, files, network
The Dashboard shows what each program tried to run, read, write, or reach. Approve the intent; remove the rest before you turn on Lockdown.
Approve what each program may do
Linux lets any program run, read any file, and connect anywhere. Root Lock requires an allowlist entry for all three — per program, not per user.
Overview: By default, any program on a Linux server can execute, access any file, and connect to any destination. Root Lock by HeartSuite controls all three per program — not per user.
Two different programs running under the same user get separate allowlist entries with separate permissions. The Dashboard guides you through each approval and tracks your progress.
The Dashboard Lockdown Checklist shows three review queues, then Secure Script Launchers as a separate row (not a queue):
- Program Allowlisting (
[p]): Approve which programs may execute. - File Access Allowlisting (
[f]): Approve which files and directories each program can read or write. - Internet Access Allowlisting (
[i]): Approve which outbound internet destinations each program can reach. - Secure Script Launchers (
[s]): Give each Python, Perl, or PHP script its own allowlist entry. See Script Launchers.
Start from the Dashboard — it shows how many items are waiting in each queue and the Suggested Next Step directs you to whichever needs attention. The review queues manage volume through intelligent grouping. There is no Approve All.
In this section
- Allowlisting Basics — Core procedures for reviewing and approving programs, file access, and network connections.
- Batch Allowlisting Tools — Activity log format and CLI tools for scripted allowlisting workflows.
Allowlist many hosts without the TUI
CLI tools for scripted allowlisting when the Dashboard queues are not the right path — image builds, fleets, and repeatable installs.
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.