User Docs
PlatformProduct updates
  • Getting started
    • What is DSPM?
    • Use DSPM in your company
    • Choose how to run DSPM
  • Quick start
  • Deployment guide
    • Sizing
    • Installation
      • Understand installation requirements
        • K3S installation
        • Configuring a HA K3s cluster
        • Configuring Rancher and Fleet agent to run behind an HTTP proxy
        • Install Synergy/Focus/Enterprise using Helm without Rancher
        • Install Synergy/Focus/Enterprise using Rancher
        • Air Gap Installation
        • Uploads to Rancher
      • Upgrade K3s
        • K3s - Upgrade
      • Troubleshooting
        • K3s on RHEL/CentOS/Oracle Linux
        • Networking
        • Configuring Rancher and Fleet agent to run behind a HTTP proxy if cluster was previously registered
    • Estimate hardware capacity needs
  • Administration guide
    • Customer Support Portal
    • Pattern matching
    • Data Controls
    • Analytics
    • Detectors
    • Import custom TLS certificate
    • GQL Quick Guide
    • Critical & Sensitive Classification Attribute Modification
    • How to Check AI Mesh Version
    • Webhooks
    • AI Mesh Overview
    • Is Customer Data Saved by Getvisibility?
  • Enterprise setup
    • Authentication
      • Keycloak configuration
      • Single Sign-on (SSO)
        • Using Azure AD as Keycloak Identity Provider
      • Keycloak User Federation Configuration (LDAP/AD)
      • Enable 2FA
      • Role-Based Access Control (RBAC)
      • Keycloak User Federation using LDAP over SSL
  • Implementation
    • Configuring Taxonomies & Labels
  • Integrations
    • GQL
    • Template Language
    • Multi-Language Machine Learning
    • SIEM Integration
    • Google Drive Auto-labelling
  • Scan with Getvisibility
    • Configure detectors
    • Configure data sources
      • Scan Configuration Fields
      • AWS IAM
      • AWS S3
      • Azure AD
      • Azure Blob
      • Azure Files
      • OneDrive
      • SharePoint Online
      • SharePoint on-premise
      • Box
      • Confluence Cloud
      • LDAP
      • SMB
      • Google IAM
      • Google Drive
      • ChatGPT
      • iManage
      • Dropbox
    • Scanning
      • Data Source Permissions
      • Scan Scheduler
      • Types of Scan
      • Scan History
      • Scan Analytics
      • Supported Languages for ML Classifiers
      • Rescan Files
    • Streaming
      • What is DDR?
      • How to Configure DDR Rules
      • Import Data Controls
      • Monitoring New Files via DDR Streaming
      • DDR Supported Events
      • Lineage
      • Supported Data Sources
      • Azure Blob Streaming Configuration
      • Azure Files Streaming Configuration
      • Confluence Cloud Streaming Configuration
      • Sharepoint Online Streaming Configuration
      • SMB Streaming Configuration
      • OneDrive Streaming Configuration
      • Azure AD Streaming Configuration
      • AWS S3 Streaming Configuration
      • Google Drive Streaming Configuration
      • Google IAM Streaming Configuration
      • AWS IAM Streaming Configuration
      • Box Streaming Configuration
      • Dropbox Streaming Configuration
    • Enterprise Search columns meaning
    • Supported File Types
  • Glossary
  • FAQ
  • EDC - All Documents
    • Deployment - Onboarding
      • EDC-Server Installation Guide
      • EDC-Deployment Flow Guide
        • EDC-installerConfig.json and CLI config Details
      • Deploying the agent using ManageEngine
      • EDC-Mac Agent - Installation Guide
      • Windows Agent Precheck Script
    • Functionality - Guides
      • EDC - Admin Guide - v4
      • EDC -Guide for writing Visual Labels
      • EDC- Guide for Header Footer Options
      • EDC-Metadata Details
      • EDC Supported File Types
      • Agent V4 - Configuration Options for Expert Mode
      • File Lineage - Agent Activities
      • Endpoint Data Discovery
    • Troubleshooting Documents
      • Preventing Users From Disabling Agent
      • Generate Installation Logs
      • Troubleshooting Agent for Windows
      • Guide for missing suggestions
      • Reseller Keycloak Quick Installation Guide
      • Alternative authentication methods for agent
  • EDC - All Documents
Powered by GitBook
On this page
  • What is Detector and how does it work?
  • Operations
  • Usages
  • Defining Data Asset
  • GQL queries
  • Analytics
  • Create Employee Lists

Was this helpful?

Export as PDF
  1. Administration guide

Detectors

How to set up a Detector

PreviousAnalyticsNextImport custom TLS certificate

Last updated 4 months ago

Was this helpful?

What is Detector and how does it work?

Detectors are features that allow users to set up alerts for certain parameters during a classification search. A user can set up a Detector to search for keywords within the entire contents of a document or file, as well as search for keyword hits within the file's pathname. It uses advanced AI and ML search techniques such as Fuzzy Word Search and Percolation to search through documents much more quickly than a traditional pattern-matching search, such as using Regular Expressions.

An example of a Detector that a user could set up is “Employee Salary”. A user might want to ensure that documents that contain this information are not publicly shared or shared internally throughout an organisation.

In order to set this up, click on Administration → Detectors to bring them to the Detectors page.

Here there is a list of pre-defined common Detectors that can be used.

To begin the setup click on the Create button on the top right corner of the screen.

This brings up the Detector Creation Screen.

  1. Provide a Query Name. For this example "Employee Salaries".

  2. Define where the Search Base of the Detector will look (i.e. search through the contents of a file or the file path). For example to search through the full document contents to look for certain salary-related keywords, select Content.

  3. In the Contain field set the relevant salary-related keywords that might trigger a detector hit in a potentially sensitive document. “Salary” “Compensation Package” “Payslip” “Payroll” “Compensation Structure” “OTE”

  4. If there are terms that the Detector is to ignore set them in in the Not Contain field.

  5. Click the Enabled button to turn on and then Save the Detector.

The new Detector named Employee Salaries should now be visible in the list of Detectors

A new scan will be needed to detect for Employee Salaries.

Operations

Each token that is added to a detector is related to the other tokens like an OR condition. AND conditions are not available detectors but this functionality can be configured indirectly through the data asset registry or directly through RegEx pattern matching.

Why it is different to Pattern Matching

Detectors work differently to Pattern Matching in a number of ways. Firstly, they can scan the entire contents of a document and path name for keywords while a traditional regex search is limited to searching through the first X amount of words across all documents. Detectors leverage advanced AI and ML techniques such as Fuzzy Word Search and Percolation Search in order to search for phrases across an entire document in a fraction of the time it would take to search with Pattern Matching.

Usages

Defining Data Asset

An important feature of DSPM is the ability to identify data assets that are important to the organisation and assign those assets in the inventory. Detectors are a powerful method that work in conjunction with the AI Mesh to find critical, sensitive, and regulated data during scans.

GQL queries

Analytics

Create Employee Lists

In order to identify employee data during scans it can be useful to add all employee names to a detector. This means a detector that helps identify HR data located throughout the data estate.

Overall, detectors give a better understanding of the data and help define very specific attributes as well as broad categories of data assets.

Once Detectors are configured and scans are underway, users can access them for describing queries in . Use the detectorHits value as shown below. will give suggestions to help speed up filtering.

Detectors are used along with the AI Mesh to analyse data and visually present findings in the . Detectors associated with various data assets and types can be found through the out-of-the-box widgets and play a crucial role in helping to identify specific important data.

GQL
GQL
Analytics Dashboard