Knowledge Base
Browse Docs
  • Introduction
    1. DefensX
    2. DNS & Web Filtering
    3. Zero Trust Files
    4. Zero Trust Credentials
    5. ADWare Protection
    6. Remote Browser Isolation
    7. Secure Browser Extension
    8. Secure Mobile Browser
    9. System & Browser Requirements
  • Deployment
    1. Deployment via RMM
    2. Operating System Agent
    3. Deployment via GPO
    4. Deployment via Intune
    5. VDI and Remote Desktop Services (RDS)
    6. Windows Manual Deployment
    7. Mac MDM Deployment
    8. Mac Manual Deployment
    9. Network Deployment
    10. Secure Mobile Browser
    11. Bypass Option
    12. SaaS Restrictions
    13. Bookmark Manager
    14. Remote Uninstall
    15. Bulk Create Customers
  • Management
    1. Role-Based Access Control
    2. Message Templates
    3. AI Protections
    4. LLM Prompt Logger
  • Integrations
    1. Azure AD
    2. Identity Providers
    3. SIEM
  • Nexi AI
    1. Nexi AI
    2. Nexi AI for MSPs
    3. Nexi AI for End Users
    4. Bookmark Prompts and Schedule Reports in Nexi AI
  • Policy Management
    1. Policy Groups
    2. Trust Profiles
    3. Consents
    4. Time-Based Policy
    5. Malvertising Protection
    6. Login Guard
    7. Watermark
    8. Sensitive Data Protection
  • Secure Access (ZTBA, formerly ZTNA)
    1. Introduction to ZTBA
    2. Configuration
  • Auto Pilot
    1. Auto Pilot
  • Training Videos
    1. Onboarding Videos
    2. Attack Scenarios
    3. MSP Admin Training Series
  • Questions & Answers
    1. Licensing
    2. Incognito Mode
    3. Onboarding
    4. Active Directory
    5. Group Synchronization
    6. Agent
    7. Conflicting Softwares
    8. Reporting
    9. Virtual Desktops
    10. Using the Backend
    11. DNS & Web Filtering
    12. Managing AI Tool Access
  • MSP Automation
    1. Overview
    2. External Notifications
    3. Integrations
    4. Partner API
  • Feature Requests
    1. Submitting and Voting on Feature Requests
ONLINE DOCUMENTATION

Sensitive Data Protection

In this document
  • Overview
  • How it works?
  • Configuration
    • Adding Data Types
    • Creating a Sensitive Data Policy
    • Assigning Data Type Actions
    • Applying the Policy
  • Viewing Sensitive Data Logs
  • Summary

Overview

Sensitive Data Protection detects sensitive values in the browser and protects them at the two points where they are exposed: when they are displayed on a page, and when a user types or pastes them into one.

What counts as sensitive is defined by data types. DefensX provides a library of common personal, financial, health and technical identifiers. Organizations can also define their own data types from keywords, regex, or both, to cover internal terms and record formats.

Tip
Sensitive Data Protection requires a CORE+ subscription or higher.

How it works?

In a Sensitive Data Policy, each data type is given two actions: Visual Protection for what is displayed and Data Entry Protection for what is entered. The two are set independently, so a passport number can be masked on screen and blocked on entry.

A policy is applied through a Custom URL Group. The group decides which addresses are inspected, and the policy group where it is assigned decides which users or devices are covered.

Configuration

Adding Data Types

Start with the data types the policy will detect. Navigate to Policies → Sensitive Data Protection and open Data Types.

kbsd1

Click the arrow next to Data Types. From Library opens the built-in set, while Keyword-Based Data Type, Regex-Based Data Type and Combined Data Type are used to define detection of your own.

kbsd2

The library is organized by category. Select a category, then the data types to monitor, and click Add Selected.

kbsd3

The data type now appears in the list, where Assigned Policies shows how many policies use it.

kbsd4

Custom data types are created from the same menu:

Keyword-Based Data Type:

kbsdkey

Regex-Based Data Type:

kbsdreg

Combined Data Type:

kbsdcom

Library data types are placed in their categories automatically, as shown under Data Categories. Adding categories of your own is optional.

kbsd5

Creating a Sensitive Data Policy

With the data types in place, open Data Policies and click Add Policy.

kbsd6

Enter a Policy Name and, optionally, a Description, then click Create Policy. Active controls whether the policy is enforced once it is assigned, so clearing it allows a policy to be prepared in advance and switched on later.

kbsd7

Assigning Data Type Actions

Creating the policy opens Edit Data Type Actions, where protection is set for each data type. Click Add Data Type Mapping.

kbsd8

In Add Data Type Mapping, select the data types to protect.

Visual Protection decides what happens when a match appears on a page. Blur obscures the value but leaves it in place. Persistent Data Masking permanently replaces the value with a mask.

kbsd9

Data Entry Protection decides what happens when a user tries to submit a match. Log Only records the event without interrupting the user. Ask User Consent stops the submission and asks the user for consent, which is recorded for that website. Block stops the submission with no way through. Persistent Data Masking permanently replaces the matched value in the field with a mask, so the original never reaches the destination.

kbsd10

Once the actions are set, click Add Selected.

kbsd11

The selected data type is added to the table, where its actions can still be changed. Click Update Data Type Actions to save the policy.

kbsd12

The policy now appears under Data Policies. Expand it to see how each data type is protected.

kbsd13

Applying the Policy

The policy takes effect once it is assigned to a Custom URL Group. To assign it, navigate to Policies → Policy Groups, open the policy group and go to the Web Filters tab.

kbsd14

Select the policy in the Sensitive Data Protection column of the Custom URL Group.

kbsd15
Note
The Custom URL Group's Action must be Allow, Isolate or ReadOnly for the policy to be enforced.

The policy now protects sensitive data on every address in the Custom URL Group.

kbsd16

Viewing Sensitive Data Logs

Matches are recorded under Logs → Sensitive Data Logs. Each entry includes the action taken, the hostname, the user, the policy applied and the date.

kbsdlogg

Summary

Sensitive Data Protection detects sensitive values through data types and protects them with separate actions for what appears on a page and what a user submits. These actions are set in a Sensitive Data Policy and enforced through a Custom URL Group in a policy group.

www.defensx.com
Secure Industries, Inc 101 Avenue of The Americas, Floor 9 New York, NY 10013