Policies

Siberson Verikor DLP – Policy Management & Rule Configuration

The Siberson Verikor DLP Policy Management module enables administrators to define, manage, and enforce data protection policies across endpoints, email, and cloud environments. This module is the core control layer where sensitive data detection logic and enforcement actions are configured.

1. Policies List Screen (Policy Overview)

‌

‌

This screen provides a centralized view of all configured DLP policies.

Key Capabilities

• Policy Listing:
  Displays all policies with attributes such as:

  • Priority
  • Policy Name
  • Category (e.g., Data Privacy, PCI)
  • Classification Scope
  • Sensitivity
  • Region
  • Active Status

• Search & Filtering:
  Each column includes filtering options, enabling rapid identification of specific policies.

• Policy Actions (Top Menu):

  • New: Create a new policy
  • Copy: Duplicate an existing policy for faster configuration
  • Edit / Delete: Modify or remove policies
  • Display Columns: Customize visible fields
  • Export to Excel: Extract policy inventory for audit or reporting

Operational Insight

Policies are evaluated based on priority values (e.g., 1000, 1100). Lower or higher priority sequencing determines rule execution order depending on system configuration, making prioritization critical in overlapping scenarios.

2. Policy Edit Screen (Policy Definition)

‌

‌

This screen is used to configure the core attributes of a policy.

Core Fields

• Name:
  Defines the policy identifier (e.g., Credit Card/IBAN Policy)
• Priority:
  Determines execution order among policies
• Category:
  Groups the policy (e.g., PCI, Data Privacy)
• Industry:
  Aligns policy with sector-specific requirements (e.g., Finance)
• Validity Region:
  Defines geographical applicability (e.g., ALL, Asia)
• Classification Scope:
  Specifies where the classification applies (e.g., organization-wide)
• Sensitivity:
  Indicates whether personal or sensitive data is involved
• Classification:
  Defines data classification level (e.g., Secret, Top Secret)
• Active:
  Enables or disables the policy
• Description:
  Provides contextual explanation of the policy purpose

3. Policy Configuration Tabs

Policy configuration is modular and divided into multiple tabs:

• Rules: Detection logic
• Source: Data origin (e.g., endpoint, email)
• Destination: Data transfer targets
• Exclusions: Exceptions to policy enforcement
• Actions: Response behavior when a rule is triggered

4. Rules Tab (Detection Logic)

The Rules section defines how sensitive data is detected.

Key Components

• Rule Name: Identifies the detection rule
• Field: Typically “Content” (data being inspected)
• Expression Type: Usually Regular Expression
• Expression Value: Pattern used for detection (e.g., IBAN, credit card formats)
• Severity: Defines risk level (Low → Very High)
• Active Status: Enables/disables the rule

Rule Pattern

• The Rule Pattern field (e.g., (1 | 2 | 3 | 4 | 5)) defines how multiple rules are evaluated together.
• Option “Evaluate All Rules” ensures all rules are processed instead of stopping at the first match.

Best Practice

Use multiple granular rules (e.g., CVV, IBAN, expiration date) and combine them via rule patterns for higher detection accuracy.

5. Rule Edit Form (Detailed Rule Configuration)

‌

This modal allows fine-grained configuration of a specific rule.

Key Fields

• Expression Value:
  Regex-based detection logic (e.g., CVV patterns)
• Start / End Datetime:
  Defines rule activation period (useful for temporary controls)
• Resource Type / Resource:
  Scope limitation for specific systems or assets
• Log Masking:
  Masks sensitive data in logs for compliance
• Severity Threshold:
  Determines how many matches trigger escalation
• Active:
  Controls rule activation

Operational Value

This layer provides precision control for detection, enabling compliance with standards like PCI DSS, KVKK, GDPR.

6. Actions Tab (Response Management)

‌

‌

The Actions section defines what happens when a rule is triggered.

Severity-Based Actions

Each severity level can be mapped to a specific action:

• Low / Medium: Typically set to Allow
• High / Very High: Configured for stricter controls

Example:

• Very High → Audit and notify

7. Action Configuration (Edit Form)

‌

Available agent actions include:

• Allow: No restriction
• Audit Only: Log activity without blocking
• Audit and Notify: Log and alert user
• Block: Prevent data transfer
• Block and Notify: Block and alert user
• Allow with Encryption: Secure transfer
• Block Only USB Devices: Device-specific restriction

Strategic Recommendation

Align actions with risk levels:

• Low risk: Monitor (Audit)
• Medium risk: Alert
• High risk: Restrict or block

Summary

The Siberson Verikor DLP Policy Management module provides a comprehensive framework to:

• Define sensitive data detection rules using advanced pattern matching
• Control policy scope across regions, industries, and classifications
• Apply risk-based actions dynamically
• Ensure regulatory compliance through granular control and auditability

This layered architecture enables organizations to implement scalable, precise, and policy-driven data protection strategies across all environments.

Last updated: 2026-04-16