Before you install
You need:
- A Laviq Console account with access to your organization.
- A supported Linux target and administrator access.
- An active organization API key created in the Console.
- Outbound network access to the Laviq installation and API endpoints.
The agent is observe-only by default. It collects runtime evidence; it does not autonomously remediate workloads or capture private keys.
Get the install command
- Sign in to the Laviq Console.
- Create or select an active API key in Settings → API Keys.
- Open Targets → Install Agent.
- Copy the install command shown there and run it on the target with administrator access.
The Console is the only public place that presents the installation command. This keeps the workflow tied to an authenticated organization and its active API key.
What the install command does
The Console-provided command detects the operating system and architecture, downloads the matching package, verifies its SHA-256 checksum, and installs the agent.
Enroll the target
The installer prompts for your organization API key unless it has already been provided by your approved automation. On first install it creates a stable agent UUID at:
/var/lib/laviq/agent-id
The agent uses that identity when it enrolls. A successful enrollment creates or refreshes the corresponding target in the Console.
Verify the result
- Open Console → Targets and confirm the target appears.
- Start or wait for the configured scan run.
- Review Raw Evidence and Scan Runs for collected data and coverage context.
Do not treat a target record alone as proof of complete workload coverage. Review the scan state and the evidence collected for the workload in scope.
If enrollment fails
Check the API key status, the target’s network connectivity, administrator permissions, and the agent service logs. Do not generate a new agent UUID merely to retry: restoring an existing known UUID is the supported recovery path.
sudo laviq agent-id restore --uuid <EXISTING_UUID_FROM_PLATFORM>
Contact Laviq support if the target identity is unknown or the recovery path is unclear.