Siberson Verikor Endpoint Agent Installation For Windows

This guide provides step-by-step instructions for installing the Siberson Verikor DLP Endpoint Agent on Windows workstations. The endpoint agent provides real-time data loss prevention monitoring and policy enforcement for endpoint devices.

Prerequisites

Before beginning the installation, ensure the following requirements are met.

System Requirements

• Operating System: Windows 10/11+ (64-bit/32-bit) or Windows Server 2016 / 2019 / 2022+

• Processor: x64 / x86-compatible CPU

• Memory: Minimum 4 GB RAM (8 GB recommended)

• Disk Space: 500 MB free disk space

• Network: Connectivity to the Siberson Verikor DLP Management Server (port 8443 / any defined secure port)

Installation Requirements

• Administrator Privileges: The user account performing the installation must have local administrator rights

• Installation Package: Both files must be present in the same directory:

◦       Verikor.Agent.vx.xx.xx.xx.x64.exe (Application installer)

◦       Config.ini (Configuration file)

• Security Software Compatibility: Exceptions must be defined in the endpoint’s AV / EDR / XDR solution before deployment — see Security Software Exceptions (AV / EDR / XDR) below.

Network Requirements

• Endpoint must be able to reach the DLP Management Server

• Firewall rules configured to allow outbound HTTPS (port 8443 / any secure port)

• DNS resolution for the DLP server FQDN

Security Software Exceptions (AV / EDR / XDR)

Endpoint security solutions — Antivirus (AV), Endpoint Detection and Response (EDR), Host Intrusion Prevention (HIPS), and Extended Detection and Response (XDR) — may interfere with the installation or runtime operation of the Verikor Endpoint Agent. The DLP agent performs legitimate but sensitive activities (kernel-mode driver loading, print-spooler monitoring, Outlook / browser integration, file-system and network inspection) that security tools frequently classify as suspicious.

Activities That Commonly Trigger False Positives

• Installation of kernel-mode minifilter drivers (file-system monitoring)

• Windows Filtering Platform (WFP) callout driver installation (network monitoring)

• Print-spooler hooking (print job monitoring)

• Outlook COM add-in registration (email content inspection)

• Browser extension / DLL injection (Web DLP)

• Service installation running in LocalSystem context

• Registry modification under HKLM\SOFTWARE and HKLM\SYSTEM\CurrentControlSet\Services

1. File Path and Folder Exclusions

Add the following directories to the exclusion list of every AV / EDR / XDR product on the endpoint:

2. Process and Executable Exclusions

3. Service Exclusions

4. Driver and Code-Signing Exclusions

Verikor installs kernel-mode drivers for file-system and network inspection. Some EDR products block driver load operations by default.

• Permit load of the Siberson file-system minifilter driver.

• Permit load of the Siberson network callout driver (Windows Filtering Platform).

Publisher (trust anchor): Siberson Corporation — WHQL-signed binaries.

5. Behavioral and Tamper-Protection Exclusions

In EDR platforms that rely on behavioral analytics or tamper protection, classify Verikor processes as trusted to suppress false positives on:

• Driver installation and kernel module loading

• Service creation and modification

• Registry hive modification (HKLM\SOFTWARE\Siberson, HKLM\SYSTEM\CurrentControlSet\Services)

• Outlook COM add-in registration

• Browser extension injection (required when Web DLP is enabled)

• Process self-protection (Verikor prevents unauthorized uninstall / termination)

Platform-Specific Configuration Notes

The following notes summarize where to configure exclusions in the most commonly encountered endpoint security platforms. Always consult the vendor’s current documentation for the exact navigation path in your console version.

Microsoft Defender / Defender for Endpoint (MDE)

• Console: Microsoft Defender Security Center → Device Configuration → Exclusions

• Group Policy: Computer Configuration → Administrative Templates → Windows Components → Microsoft Defender Antivirus → Exclusions

• MDE additional step: Create an Indicator Allow entry for the Siberson Corporation certificate thumbprint to prevent behavioral detection.

CrowdStrike Falcon

• Console: Falcon → Configuration → IOA Exclusions and Machine Learning Exclusions

• Classify Verikor processes as Trusted to prevent behavioral detection triggers.

SentinelOne

• Console: Sentinels → Policy → Exclusions

• Set Suppress Alerts for Verikor paths and add the agent to the Trusted Application list.

Sophos Intercept X / Central

• Console: Sophos Central → Global Settings → Global Exclusions

• Disable CryptoGuard tampering detection for Verikor processes.

Kaspersky Endpoint Security

• Console: Kaspersky Security Center → Policies → General → Exclusions

• Add Verikor paths to Trusted Applications and disable the “Detect other software that can be used by criminals to damage your computer” heuristic for Verikor components.

ESET Endpoint Security / PROTECT

• Console: Advanced Setup → Detection Engine → Exclusions

• Configure both Performance Exclusions and Detection Exclusions.

Bitdefender GravityZone

• Console: Policies → Antimalware → Settings → Exclusions

• Add Process exclusions and Folder exclusions for Verikor components.

Trend Micro Apex One

• Console: Policy → Antivirus → Real-time Scan → Exceptions

• Additionally configure Behavior Monitoring exceptions.

Palo Alto Cortex XDR

• Console: Endpoint Administration → Profiles → Exceptions

• Classify Verikor as a Trusted Signer using the Siberson Corporation certificate.

Verification After Exception Configuration

Before rolling out to production endpoints, verify that exclusions are effective on a pilot workstation:

1. Trigger a test installation of the Verikor Endpoint Agent on the pilot workstation.

2. Confirm that the AV / EDR console shows no quarantine, block, or detection events for Verikor files or processes.

3. Verify that the Verikor Agent and Verikor Printer processes are running in Task Manager.

4. Confirm that the endpoint appears with Connected status in the Verikor DLP Management Console.

5. Generate a test DLP event (e.g., copy a classified file to a USB device) to confirm the agent is actively enforcing policy.

Common Symptoms of Missing Exceptions

If any of the following symptoms appear, insufficient AV / EDR / XDR exceptions are the most likely cause:

• The installer process is silently terminated or quarantined before completion.

• Installation completes successfully but the Verikor services fail to start.

• Verikor.Agent.exe is deleted shortly after installation (indicates post-install quarantine).

• Driver installation fails with Access Denied (0x80070005) or driver-signature errors.

• Agent appears Connected briefly, then Disconnected repeatedly (EDR terminates the agent process).

• The Outlook add-in appears in the Disabled Items list immediately after installation.

• Abnormally high CPU usage from the AV / EDR engine scanning Verikor’s real-time activity.

Installation Package Structure

The installation package consists of two essential components that must be located in the same directory:

1. Verikor.Agent.vx.xx.xx.x.x64.exe/msi

• Type: Application installer (executable)
• Size: Approximately \~350 Mb
• Purpose: Core agent installer binary

2. Config.ini

• Type: Configuration settings file
• Size: 1 KB
• Purpose: Contains server connection parameters, policy settings, and deployment-specific configurations

CRITICAL: The Config.ini file must be present in the same folder as the executable installer. The installation will fail if this file is missing or located in a different directory.

Figure 1

Figure 1: Installation package showing both required files (Verikor.Agent.vx.xx.xx.xx.x64.exe and Config.ini) in the same directory

Configuration File (Config.ini)

The Config.ini file contains essential configuration parameters that are applied during installation. This file is typically pre-configured by your IT administrator or Siberson support team.

Sample Config.ini Contents

[MAIN]
[SERVICE]
ServiceAddress={Web Service Adres}
ServiceAddressAdmin={Web Service Adres}
ServiceClientKey=xxxxxxxxxxxxxxxxxxxx
FirstRunDiscovery=1
Company=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx

Important: Do not modify the Config.ini file unless instructed by your IT administrator. Incorrect configuration may prevent the agent from connecting to the management server.

Installation Process

Step 1: Prepare Installation Package

1. Download or copy the installation package to the target workstation
2. Extract the package to a local directory (e.g., C:\Temp\VerikorAgent)

3. Verify both files are present:

   • Verikor.Agent.vx.xx.xx.xx.x64.exe
   • Config.ini

Step 2: Launch Installation

1. Navigate to the directory containing the installation files
2. Right-click on Verikor.Agent.vx.xx.xx.xx.x64.exe

3. Select "Run as administrator"

   • If User Account Control (UAC) prompts appear, click "Yes" to allow the installation

Figure 2 ‌

Figure 2: Installation confirmation dialog showing publisher (Siberson Corporation) and version (xx.xx.xx.xx)

4. The installation confirmation dialog will appear showing:

   • Publisher: Siberson Corporation
   • Version: xx.xx.xx
   • Application: Verikor

5. Click the "Install" button to begin installation

Step 3: Installation Progress

The installation process typically completes in 15-20 seconds. During this time:

Figure 3 ‌

Figure 3: Installation progress showing "Installing Verikor Outlook Add-In" component

• The installer will deploy the following components:

  • Core agent service (Verikor Agent)
  • Print monitoring service (Verikor Printer)
  • Outlook add-in (if Microsoft Outlook is installed)
  • File system filter driver
  • Network monitoring components

• A progress bar will indicate installation status

• A "Cancel" button is available if you need to abort the installation

Note: The installation process includes:

• Service registration
• Driver installation
• Registry configuration
• Integration with Windows security subsystems

Step 4: Installation Completion

Figure 4 ‌

Figure 4: Installation completion dialog confirming successful deployment

When the installation completes successfully:

1. The dialog will display "Verikor has been installed"

2. Confirm the following information:

   • Publisher: Siberson Corporation
   • Version: xx.xx.xx.xx

3. Click "Finish" to close the installer

Post-Installation Verification

After clicking "Finish", verify the agent is running correctly:

Step 1: Check Background Processes

Figure 5 Figure 5: Windows Task Manager showing Verikor background processes running successfully

1. Open Windows Task Manager (Ctrl + Shift + Esc)
2. Navigate to the "Details" or "Processes" tab
3. Verify the following processes are running:

|| Process Name || Type || Memory Usage || Description || | Verikor Agent | Background process | \~26.8 MB | Core DLP monitoring service | | Verikor Printer | Background process | \~6.5 MB | Print job monitoring service |

Expected Behavior:

• Both processes should appear under "Background processes (2)"
• CPU usage should be minimal (0-1%) when idle
• Memory footprint should be approximately 27-33 MB total
• Network activity should be minimal (0 MB/s when idle, periodic spikes during policy sync)

Step 2: Verify Services

1. Open Services (services.msc)

2. Locate the following services and confirm they are "Running":

   • Siberson Verikor Agent Service
   • Siberson Verikor Printer Monitor

Step 3: Check Agent Connectivity

The agent should automatically connect to the DLP Management Server within 2-5 minutes after installation. Administrators can verify connectivity through the DLP Management Console:

1. Log in to the Siberson Verikor DLP Management Console
2. Navigate to Endpoints → Agent Status
3. Verify the newly installed endpoint appears with status "Connected"
4. Check that the agent version matches the deployed version (xx.xx.xx.xx)

Automated Deployment Methods

For large-scale deployments, the endpoint agent can be deployed using enterprise management tools:

Group Policy (GPO) Deployment

Example GPO startup script

$InstallerPath = "\fileserver\verikor\Verikor.Agent.v1.12.2.0.x64.exe" $ConfigPath = "\fileserver\verikor\Config.ini"

Copy files locally

Copy-Item $InstallerPath -Destination "C:\Temp\VerikorAgent" Copy-Item $ConfigPath -Destination "C:\Temp\VerikorAgent"

Run silent installation

Start-Process -FilePath "C:\Temp\VerikorAgent\Verikor.Agent.vx.xx.xx.xx.x64.exe" -ArgumentList "/silent" -Wait

Microsoft Intune/SCCM Deployment

Create an application package with:

• Installation Command: Verikor.Agent.vx.xx.xx.xx.x64.exe /silent
• Uninstall Command: msiexec /x {GUID} /quiet
• Detection Method: Check for process Verikor Agent or registry key
• Installation Behavior: System context
• User Experience: Silent installation

Silent Installation Parameters

|| Parameter || Description || | /silent | Performs installation without user interface | | /norestart | Prevents automatic system restart | | /log "C:\path\to\log.txt" | Generates installation log file |

Example Silent Installation:

Verikor.Agent.v1x.xx.xx.xx.x64.exe /silent /norestart /log "C:xxxx\xxxx\VerikorInstall.log"

Troubleshooting

Issue: Installation Fails with "Config.ini not found"

Cause: The Config.ini file is not in the same directory as the executable installer.

Resolution:

1. Verify both files are in the same folder
2. Check file names match exactly (case-sensitive on some systems)
3. Ensure Config.ini is not renamed or has incorrect file extension

Issue: Installation Requires Administrator Rights

Cause: The user account does not have local administrator privileges.

Resolution:

1. Right-click the installer and select "Run as administrator"
2. Contact your IT administrator to grant temporary elevation
3. Use enterprise deployment tools (GPO/SCCM) for automated installation with system privileges

Issue: Agent Processes Not Running After Installation

Cause: Service failed to start, driver installation blocked, or firewall blocking communication.

Resolution:

1. Check Windows Event Viewer for error messages:

   • Navigate to Event Viewer → Windows Logs → Application
   • Filter by source "Siberson" or "Verikor"

2. Verify services are set to "Automatic" startup type

3. Manually start services if stopped:

net start "Siberson Verikor Agent Service" net start "Siberson Verikor Printer Monitor"

4. Check firewall rules allow outbound connections to port 8443
5. Verify Config.ini contains correct server address

Issue: Agent Shows "Disconnected" in Management Console

Cause: Network connectivity issue, incorrect server address, or certificate validation failure.

Resolution:

1. Verify network connectivity to DLP server:

ping [yourcompany network] telnet [yourcompany network] 8443/any defined secure port

2. Check Config.ini for correct ServerAddress and ServerPort
3. Review agent logs
4. Verify SSL certificate is trusted (if using self-signed certificates)
5. Ensure no proxy or web filter is blocking communication

Issue: Outlook Add-In Not Appearing

Cause: Outlook was not running during installation, or add-in was disabled by Group Policy.

Resolution:

1. Close and restart Microsoft Outlook completely

2. Check if add-in is disabled:

   • Open Outlook → File → Options → Add-ins
   • Look for "Siberson Verikor DLP for Outlook"
   • If listed under "Disabled Items", enable it

3. Verify add-in is registered:

reg query "HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\Verikor.OutlookAddIn"

Uninstallation

To remove the Siberson Verikor DLP Endpoint Agent:

Method 1: Windows Settings (Recommended)

1. Open Settings → Apps → Apps & features
2. Search for "Verikor"
3. Click "Uninstall"
4. Confirm removal when prompted
5. Restart the computer to complete removal

Method 2: Control Panel

1. Open Control Panel → Programs and Features
2. Locate "Siberson Verikor DLP Agent"
3. Click "Uninstall"
4. Follow the uninstallation wizard

Method 3: Silent Uninstallation

msiexec /x {ProductGUID} /quiet /norestart

Note: Contact your IT administrator for the correct ProductGUID.

Last updated: 2026-05-08