Knowledge Base
Siberson
Siberson Verikor DLPSiberson Veriket Data ClassificationSiberson Veriket Data DiscoverySiberson Verifim FIM
By industryFinance & BankingPublic SectorDefense & AerospaceTelecomEnergy & UtilitiesHealthcareBy business challengePrevent data lossDiscover sensitive dataClassify & label dataContain insider riskSecure GenAI usageFile integrity & ransomwareBy roleCISO & SecurityDPO & PrivacyIT & SecOpsCompliance & AuditIntegrationsBy regulationKVKKGDPRPCI DSSISO 27001NIS2HIPAA
Partnership
BlogUse CasesCase StudiesDocumentationSupport
About UsQuality & Certifications
Contact Request a Demo

Siberson Veriket Endpoint Agent Installation For Linux

1. Overview

This guide explains how to install the Siberson Veriket Data Classification Linux Endpoint Agent on Linux endpoints. The endpoint agent is deployed together with a configuration file and, once installation completes successfully, the workstation should have the core Veriket runtime services running and verifiable through standard Linux system utilities (e.g., systemctl, ps, top/htop).

The document is intended for administrators performing manual rollout, pilot deployment, controlled validation, or preparing a standardized enterprise packaging workflow.

2. Prerequisites

Before starting the installation, confirm the following baseline requirements:

  • Supported Endpoint: A supported Linux endpoint running a Debian-based distribution (Ubuntu, Debian, Pardus) on x86_64 or arm64 architecture.
  • Administrative Access: The account performing the installation must have root privileges or sudo access on the target endpoint.
  • Disk Capacity: Sufficient free disk space must be available for the package extraction, installation, and runtime files.
  • Network Reachability: The endpoint must be able to reach the relevant Veriket backend / management environment defined in the deployment configuration.
  • Change Window: The installation should be executed during a controlled support window if endpoint security products (AV/EDR) or mandatory access control frameworks (SELinux, AppArmor) are known to inspect or restrict new installers aggressively.

3. Security Software Exceptions (AV / EDR / XDR)

Endpoint security tools may inspect or interrupt legitimate Veriket installation and runtime activities. The Veriket agent should be allowlisted before deployment. The recommended scope is as follows:

Exception Type Recommended Scope
Folder / Path /opt/veriket/, /etc/veriket/, /var/lib/veriket/, /var/log/veriket/
Installer Package veriket-agent_vx.xx.xx.xx_amd64.deb (or arm64 variant) and related deployment files in the staging folder.
Installed Components Veriket Linux Agent (veriket-agent systemd service); Veriket Information Assistant.
Signer / Publisher Siberson Corporation, where the security platform supports trusted publisher logic, or GPG-signed package verification using the official Siberson repository signing key.
Behavioral Exceptions systemd service registration, configuration writes under /etc/veriket/, boot-time auto-start persistence, policy synchronization, file manager / desktop environment / office suite integrations (e.g., Nautilus, Dolphin, LibreOffice), and resource management activities.

Operational recommendation: validate exclusions on a pilot machine first, then monitor the endpoint protection console for any detection, prevention, or quarantine activity during installation and first startup.

4. Installation Package Structure

The supplied installation folder contains one required file:

  • veriket-agent_vx.xx.xx.xx_amd64.deb: Debian package installer for the Veriket Linux Endpoint Agent (use the arm64 variant on ARM-based endpoints).

5. Installation

5.1 Stage the Installation Package

  1. Copy the .deb package to the target endpoint via your preferred file transfer method (SCP, SFTP, removable media, or an internal software distribution platform).
  2. Place the package in a staging directory accessible to the administrator account (for example, /tmp/veriket-install/ or /home//staging/).
  3. Verify file integrity against the checksum supplied with the package: sha256sum veriket-agent_vx.xx.xx.xx_amd64.deb
  4. Confirm the file is owned by a trusted user and has appropriate read permissions: ls -l veriket-agent_vx.xx.xx.xx_amd64.deb

5.2 Launch the Installation

  1. Navigate to the staging folder that contains the supplied .deb package: cd /path/to/staging-folder
  2. Verify the package file is present: ls -l veriket-agent_v*.deb
  3. Launch the installation using apt so that any required system dependencies are automatically resolved: sudo apt install ./veriket-agent_vx.xx.xx.xx_amd64.deb
  4. Alternatively, install directly with dpkg, followed by a dependency-fix step: sudo dpkg -i veriket-agent_vx.xx.xx.xx_amd64.deb then sudo apt-get install -f
  5. Provide the administrator password when prompted by sudo.
  6. Wait for the installation to complete. The package manager will extract the agent binaries to /opt/veriket/, register the veriket-agent systemd service, write the default configuration under /etc/veriket/, and report a clean exit code (0) on success.

Note: Do not interrupt the installation process. Closing the terminal, cancelling with Ctrl+C, or rebooting the endpoint mid-installation may leave the agent in a partially configured state and require manual cleanup before re-installation.

6. Post-Installation Verification

6.1 Check Runtime Processes

  • veriket-agent systemd service — verify with: systemctl status veriket-agent. The service should report active (running) and enabled.
  • Veriket Information Assistant — verify the user-space component is running with: ps -ef | grep -i veriket
  • CPU and network utilization should typically remain low when the endpoint is idle.
  • If one or more Veriket components do not appear, review installer execution privileges, endpoint protection (AV/EDR) logs, and the Linux system journal: sudo journalctl -u veriket-agent -b --no-pager. Additional logs may be available under /var/log/veriket/.

6.2 Verify Endpoint Registration

If your Veriket environment includes a central administration or policy management console, verify that the newly installed endpoint becomes visible after policy synchronization.

7. Troubleshooting

7.1 Installation Starts but Does Not Complete

  • Cause: Local security controls, AV/EDR application control policies, mandatory access control frameworks (SELinux, AppArmor), or insufficient privileges may be interrupting the installer.
  • Resolution: Re-run the installation with sudo / root privileges, review AV/EDR detections, verify that SELinux/AppArmor are not blocking package operations, and confirm that the package is allowlisted.

7.2 Veriket Processes Do Not Appear After Installation

  • Cause: Startup components may be blocked, quarantined, or not initialized correctly.
  • Resolution: Review the systemd service status, the system journal, Veriket runtime logs under /var/log/veriket/, and the endpoint security console. Reboot the endpoint if required by internal policy and validate again.

7.3 Endpoint Does Not Become Visible in Central Management

  • Cause: Connectivity, certificate trust, or configuration alignment issues may prevent successful registration.
  • Resolution: Verify network reachability to the management endpoint, confirm that the server.der certificate is installed in the system CA trust store (typically under /usr/local/share/ca-certificates/ on Debian-based systems and applied with sudo update-ca-certificates), and review the backend console or deployment logs.

7.4 High Delay During Installation

  • Cause: Real-time inspection from security software may be scanning the installer and newly created components.
  • Resolution: Re-check allowlisting definitions and validate the rollout on a pilot machine with monitoring enabled.

Last updated: 2026-05-11

↑