Siberson Veriket Endpoint Agent Installation For macOS

1. Overview

This guide explains how to install the Siberson Veriket Data Classification MacOs Endpoint Agent on MacOs endpoints. The endpoint agent is deployed together with a configuration file and, once installation completes successfully, the workstation should display the core Veriket runtime components in Activity Monitor.

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 MacOs endpoint with arm64 or intel architecture.
• Administrative Access: The account performing the installation must have local administrator privileges.
• 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 are known to inspect new installers aggressively.

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

Endpoint security tools may inspect or interrupt legitimate Veriket installation and runtime activities. In environments protected by Antivirus (AV), Endpoint Detection and Response (EDR), Extended Detection and Response (XDR), Host Intrusion Prevention (HIPS), or application control platforms, the Veriket agent should be allowlisted before deployment to avoid false positives, quarantine actions, incomplete installation, or unstable runtime behavior.

The recommended scope is as follows:

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.Install.vx.xx.xx.pkg: MacOs Installer package for the endpoint agent.

5. Installation Process

5.1 Prepare the Package

1. Copy the installation package to a local or approved software distribution directory on the target endpoint.
2. Confirm that the deployment file is present in the folder.
3. If required by your environment, perform the rollout from an elevated terminal session (sudo) or via software distribution tooling running with administrative context.

5.2 Launch the Installation

1. Double-click the .pkg package or execute it through an elevated administrative context.
2. If macOS or endpoint protection prompts for approval, allow the package to continue.
3. Wait while macOS starts configuring the Veriket Agent.

5.3 Monitor Installation Progress

During installation, macOS displays a progress dialog while the Veriket components are copied, registered, and initialized. Depending on workstation performance and endpoint security inspection overhead, the elapsed time can vary.

• Avoid interrupting the workstation or forcibly terminating the installer session.
• If the progress window stalls for an unusual duration, first review whether AV / EDR activity is blocking the package.

5.4 Completion Expectations

Once installation completes, the macOS Installer session should close normally. In tightly controlled environments, there may be a short delay before all Veriket background components initialize and appear in Activity Monitor.

6. Post-Installation Verification

After installation, verify that the Veriket runtime components are active on the endpoint.

6.1 Check Runtime Processes

Open macOS Activity Monitor and confirm that the Veriket background components are visible.

• CPU and network utilization should typically remain low when the endpoint is idle.
• A short stabilization period immediately after installation is normal.
• If one or more Veriket processes do not appear, review installer elevation, endpoint protection logs, and Console.app system logs.

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.

8. Silent / Enterprise Deployment Notes

Because the supplied installer is a .pkg package, enterprise rollout for macOS endpoints is standardized through Jamf Pro. Any final command line, configuration profile, and certificate payload should be validated in your own environment before mass deployment.

• Distribution Tool: Jamf Pro is the primary distribution tool for the Veriket Agent on macOS. The .pkg package is uploaded to Jamf as a standard package and deployed through a Policy or as part of a PreStage Enrollment workflow.
• Full Disk Access Requirement: The Veriket Agent requires Full Disk Access to read and label files outside of its sandbox. In Jamf-managed deployments, deliver this permission via a Privacy Preferences Policy Control (PPPC) configuration profile that pre-approves Full Disk Access for the Veriket Agent before the .pkg is installed.
• Certificate Installation (server.der): The deployment includes a DER-encoded trust certificate (server.der) that must be installed into the macOS System Keychain before the agent can authenticate to the central management environment. In Jamf, distribute server.der using a Configuration Profile with a Certificate payload.
• Packaging Reminder: Confirm with the Siberson delivery team whether the deployment requires any companion files (e.g., a configuration file alongside the .pkg).

9. Troubleshooting

9.1 Installation Starts but Does Not Complete

• Cause: Local security controls, application control policies, Gatekeeper, or insufficient privileges may be interrupting the installer.
• Resolution: Re-run with administrative rights, review AV / EDR detections, and verify that the package is allowlisted.

9.2 Veriket Processes Do Not Appear After Installation

• Cause: Startup components may be blocked, quarantined, or not initialized correctly.
• Resolution: Review Activity Monitor, Console.app system logs, and the endpoint security console. Reboot the endpoint if required by internal policy and validate again.

9.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, confirm that the server.der certificate is installed in the System Keychain, and review the backend console or deployment logs.

9.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-08