Siberson Veriket Data Discovery– Siberson Verikor DLP Integration Guide

Integration Scope Statement

Siberson Veriket Data Discoveryis designed to integrate seamlessly with all major Data Loss Prevention (DLP) solutions through metadata-based classification (Label / GUID mapping) and standard policy enforcement mechanisms.

This architecture enables organizations to leverage their existing DLP investments while enhancing enforcement accuracy with context-aware data classification.

The integration model is:

• Vendor-agnostic
• Scalable across multiple DLP platforms
• Based on standard labeling and policy frameworks

📌 Example Implementation

The following section provides a sample integration workflow using Siberson Verikor DLP as a reference implementation.

This example demonstrates:

• How classification labels generated by Veriket are consumed by a DLP engine
• How policies are enforced based on label-driven conditions
• How a closed-loop data protection workflow is achieved

⚠️ Note:
While Siberson Verikor DLP is used in this example, the same integration logic applies to other DLP solutions such as Forcepoint, Symantec (Broadcom), Microsoft Purview, McAfee/Trellix, and similar platforms.

Overview

This article provides a structured implementation guideline for integrating Siberson Veriket Data Discovery with Siberson Verikor DLP, enabling policy enforcement based on classification labels.

This integration establishes a classification-driven data protection model, where:

• Veriket → Identifies & classifies sensitive data
• Siberson Verikor DLP → Enforces policies based on labels (While discovering, they can also classify and label)

🏗️ Architecture Overview

[ Veriket Data Discovery ]
            │
            │ (Metadata / Label GUID)
            ▼
[ Classified Files (Endpoint / Server / Cloud) ]
            │
            ▼
[ Siberson Verikor DLP Engine ]
            │
            ▼
[ Policy Enforcement (Block / Audit / Encrypt) ]

Strategic Outcome:

• End-to-end visibility
• Automated enforcement
• Reduced human dependency

👤 CUSTOMER-FACING GUIDE

▶ Step 1 – Access Metada Labeling Module

Navigate to:

Resources → Meta Data Labes

‌

‌

▶ Step 2 – Create Metadata Label

1. Click New

2. Define:

   • Label Name (e.g., Confidential, Internal)
   • Key (Metadata field name)
   • Label GUID (from Veriket)

3. Save configuration

⚠️ Critical Note:
Label GUID must match exactly with Veriket output.

▶ Step 3 – Create DLP Policy

Navigate to:

Policies → New Policy

• Click New

• Navigate Rules Tab then Click New

‌

1. Define:

   • Rule Name (e.g., Metada Labe Rules)
   • Field Select (Metadata
   • Expression Select (Contains,Equal, Not Equal)
   • Resource Type Select (Meta Data Label)

2. Save ConfigurationsSave Configurations

‌

▶ Step 4 – Configure Conditions

• Go to Rule Pattern
• Define rule logic (can add too too many rules and define logical)

‌

▶ Step 5 – Define Actions

• Navigate to Actions

• Define:

  • Select Severity level
  • Select Action (Audit Only / Allow with encryption / Bock and Notify / Audit and notify / Block / Allow / [Custome Action Name ])

‌

▶ Step 6 – Deploy Policy

• Click DEPLOY
• Policies are pushed to endpoints

‌

✅ Validation Checklist

• Veriket labels applied correctly
• GUID mapping verified
• Policy triggered successfully
• Logs visible in Siberson Verikor DLP

🎯 Positioning Strategy

• “Classification without enforcement is incomplete”
• Veriket enables context-aware DLP policies
• Siberson Verikor DLP becomes policy execution layer

💡 Best Practices

• Start with Audit Mode
• Gradually switch to Block Mode
• Use high-value data sets for initial rollout
• Align labels with compliance frameworks (GDPR, KVKK)

⚠️ Common Pitfalls

📌 Summary

This integration delivers a closed-loop data protection lifecycle:

• Discover → Classify → Enforce → Monitor

Last updated: 2026-04-29