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

Getting Started Guide

Getting Started with Siberson Veriket Data Discovery

Overview

Siberson Veriket Data Discovery is an enterprise data discovery solution designed to help organizations identify, locate, and analyze sensitive data across structured and unstructured data repositories. It enables security, compliance, and data governance teams to gain visibility into where critical information is stored, how it is distributed, and which areas may carry potential data exposure risks.

By scanning enterprise data sources and detecting sensitive information such as personal data, financial records, confidential business documents, and regulated information, Veriket Data Discovery helps organizations strengthen their data security posture and support compliance requirements such as KVKK, GDPR, ISO 27001, and internal data governance policies.

This guide provides a starting point for administrators who will configure, manage, and operate Siberson Veriket Data Discovery.

Key Capabilities

Siberson Veriket Data Discovery provides a centralized and scalable approach to discovering sensitive data across enterprise environments.

Core capabilities include:

  • Sensitive data discovery across selected data sources
  • Automated scanning and detection based on predefined or custom rules
  • Data source management for repositories, folders, shares, and storage locations
  • Risk visibility into sensitive data distribution
  • Classification-aware discovery when used with Veriket Data Classification
  • Policy-based scan configuration
  • Reporting and dashboard capabilities
  • Compliance-oriented data inventory support
  • Integration-ready architecture for broader data security operations

These capabilities help organizations understand their data landscape, reduce blind spots, and make informed decisions about data protection priorities.

Before You Begin

Before configuring Siberson Veriket Data Discovery, administrators should review the following preparation steps.

1. Define Discovery Scope

Start by identifying which data sources should be scanned. These may include:

  • File servers
  • Shared folders
  • Network drives
  • Endpoint file locations
  • Document repositories
  • Databases
  • Cloud storage platforms
  • Business application storage areas

A clearly defined scope helps avoid unnecessary scanning overhead and ensures that the discovery process is aligned with business priorities.

2. Identify Sensitive Data Categories

Define which types of sensitive information the organization needs to discover. Common examples include:

  • Personal identifiable information
  • National identity numbers
  • Customer records
  • Employee data
  • Financial information
  • Credit card or payment data
  • Contract documents
  • Intellectual property
  • Confidential business files
  • Regulated or sector-specific data

These categories should be aligned with compliance obligations, internal security policies, and risk management objectives.

3. Prepare Access Permissions

Veriket Data Discovery requires appropriate access permissions to scan selected data sources.

Before creating scan jobs, ensure that:

  • Required service accounts are available
  • Access permissions are limited to the required repositories
  • Read permissions are properly configured
  • Network paths and storage locations are reachable
  • Authentication requirements are documented
  • Access rights comply with internal security policies

Using controlled and auditable service accounts is recommended for enterprise deployments.

4. Plan Scan Strategy

A successful discovery project should be planned in phases. Instead of scanning all repositories at once, start with high-priority or high-risk areas.

Recommended initial scan targets may include:

  • HR folders
  • Finance repositories
  • Legal document archives
  • Customer data folders
  • Shared drives with broad user access
  • Legacy file shares
  • Business-critical storage locations

This phased approach helps administrators validate scan accuracy, performance, and reporting outcomes before expanding the scope.

1. Access the Management Console

Log in to the Siberson Veriket Management Console using an authorized administrator account. The console provides centralized access to data source configuration, scan policies, discovery rules, scan results, reports, and administrative settings.

After logging in, review the dashboard and navigation structure to understand the available modules.

2. Configure Data Sources

Add the data sources that will be scanned by Veriket Data Discovery. Depending on the deployment model, administrators may define repositories such as file shares, network folders, databases, or other supported storage locations.

When configuring a data source, review the following parameters:

  • Data source name
  • Repository type
  • Connection path or address
  • Authentication method
  • Service account information
  • Scan boundaries
  • Included and excluded folders
  • File type filters
  • Access validation status

A well-structured data source configuration enables controlled scanning and simplifies long-term governance.

3. Define Discovery Rules

Discovery rules determine what type of sensitive data the system should detect during scans.

Rules may be based on:

  • Keywords
  • Regular expressions
  • Data patterns
  • File types
  • Metadata
  • Predefined sensitive data templates
  • Custom organizational criteria
  • Classification labels, if integrated with Veriket Data Classification

For the initial deployment, it is recommended to start with a focused rule set that addresses the most critical compliance and security requirements.

4. Create Scan Policies

Scan policies define how, when, and where discovery scans will run.

A scan policy may include:

  • Target data sources
  • Selected discovery rules
  • Scan frequency
  • Scan depth
  • File size limitations
  • Included or excluded file extensions
  • Scheduling settings
  • Result handling preferences

Administrators should begin with limited pilot scans and gradually extend coverage after validating results and performance impact.

5. Run an Initial Discovery Scan

After data sources and scan policies are configured, run an initial scan on a controlled repository.

During the first scan, monitor:

  • Scan start and completion status
  • Number of scanned files
  • Number of sensitive data findings
  • Detection accuracy
  • Failed or skipped files
  • Access-related errors
  • System performance impact

The initial scan helps administrators verify whether the configuration is technically and operationally ready for broader use.

6. Review Discovery Results

Once the scan is completed, review the discovery results from the management console.

Administrators can analyze:

  • Sensitive data locations
  • Data type distribution
  • High-risk repositories
  • Frequently detected sensitive patterns
  • Files containing regulated data
  • Access or permission-related findings
  • Potential remediation priorities

This visibility enables security and compliance teams to understand where sensitive data is stored and which areas require further action.

7. Generate Reports

Reporting is a key part of data discovery operations. Reports can help stakeholders evaluate compliance status, data exposure risks, and remediation progress.

Typical reports may include:

  • Sensitive data inventory reports
  • Repository-based risk reports
  • Data category distribution reports
  • Scan summary reports
  • Compliance-oriented discovery reports
  • High-risk file location reports

Reports can support internal audits, management reviews, regulatory readiness, and continuous improvement initiatives.

8. Take Remediation Actions

Discovery results should be reviewed and prioritized based on risk. Depending on internal policies, remediation actions may include:

  • Moving sensitive files to secure locations
  • Restricting access permissions
  • Removing unnecessary duplicate data
  • Applying classification labels
  • Encrypting sensitive files
  • Archiving or deleting obsolete information
  • Updating business process controls
  • Creating DLP policies based on discovered data

When used together with Siberson Veriket Data Classification and Siberson Verikor DLP, discovery results can become a strong input for a broader data protection lifecycle.

Best Practices

To achieve stronger outcomes with Siberson Veriket Data Discovery, consider the following best practices:

  • Start with high-risk repositories before expanding to the full environment.
  • Use pilot scans to validate rules and reduce false positives.
  • Avoid scanning all enterprise repositories at once during the first phase.
  • Use clear naming standards for data sources and scan policies.
  • Align discovery rules with compliance and business requirements.
  • Review access permissions before scanning sensitive locations.
  • Schedule large scans outside business-critical hours where possible.
  • Use reports to track remediation progress.
  • Regularly update discovery rules as business and regulatory needs evolve.
  • Combine discovery insights with classification and DLP policies for stronger data protection.

Common Use Cases

Siberson Veriket Data Discovery can support multiple enterprise data security and compliance scenarios, including:

  • Identifying personal data stored in file shares
  • Discovering sensitive customer or employee records
  • Locating confidential business documents
  • Supporting KVKK, GDPR, and ISO 27001 compliance initiatives
  • Building a sensitive data inventory
  • Detecting data exposure risks in shared folders
  • Preparing for audits and regulatory reviews
  • Supporting data minimization and cleanup projects
  • Feeding classification and DLP policy design
  • Improving enterprise data visibility and governance maturity

Next Steps

After completing the initial setup, administrators can continue with detailed knowledge base articles for the following topics:

  • Management Console Configuration
  • Data Source Management
  • Discovery Rule Configuration
  • Scan Policy Management
  • Scheduled Scans
  • Scan Result Analysis
  • Reporting and Dashboard Usage
  • Risk Review and Remediation
  • Integration with Data Classification
  • Integration with DLP Policies
  • User Role and Permission Management

By following these steps, organizations can establish a strong foundation for enterprise data visibility, sensitive data inventory management, and compliance-driven data governance with Siberson Veriket Data Discovery.

Last updated: 2026-05-05

↑