Swift Security Docs
  • Introduction to Swift Security
  • Onboarding
    • Tenant Setup
    • Product Deployments
      • Browser Extension
      • LLM Guardrails
        • LLM Guardrails API Integration
      • VS Code IDE Extension
    • Directory Sync
      • Configuring Google Directory Sync
      • Configuring Microsoft Directory Sync
    • MDM
      • Extension Deployment Via Google Workspace
      • Extension deployment via google workspace + MDM at device level
      • Extension Deployment Via Microsoft Intune
        • Chromium Browsers in Windows
        • Edge Browsers in Windows
        • Firefox Browsers in Windows
      • Extension Deployment Via Kandji
        • Chromium Browsers in Mac
    • Infrastructure
      • SaaS Model
      • Hybrid deployment (coming soon)
  • SSO (Single Sign-On)
    • SSO Configurations identity provider - Google workspace
  • Administrative Guide
    • Console Users
      • Role Creation
      • RBAC General Settings for Login Methods (for the Console)
      • User Creation
      • SSO login(okta)
    • Swift Detection Engines
      • Data Identifiers
        • Custom Data Identifiers
      • EDM Dictionaries
        • EDM Rule
        • EDM Profile
        • EDM Extension Policy
      • Data Rules
        • Custom Rules
      • Data Profiles
      • LLM Guardrail Scanners
        • Data Protection Scanner
        • Gibberish Scanner
        • Ban Substrings Scanner
        • Invisible Text Scanner
        • Code Scanner
        • Language Scanner
        • Sentiment Analysis Scanner
        • Jailbreak Scanner
        • Toxicity Scanner
        • Prompt Injection Scanner
        • Token Limit Scanner
        • Reading Time Scanner
        • Language Same Scanner
        • No Refusal Scanner
        • Factual Consistency Scanner
        • Bias Detection Scanner
        • URL Reachability Scanner
        • Nudity Scanner
        • Gender Scanner
        • Celebrity Scanner
        • Face Scanner
        • Race Scanner
        • Performance and Benchmark
    • Browser Extension
      • Extension Installation
      • Granular Policies
        • Control URL access
        • Protect company data
        • Protect against Threats (Coming Soon)
      • Extension Alerts
      • Extension Events
      • Extension Popups
      • Browser Extension Coverage
    • LLM Guardrails
      • LLM Guardrails Policies
      • LLM Guardrails Alert
      • LLM Guardrails Events
    • Regulation Laws
  • Assets
    • Applications
    • Users
    • Extensions
  • Integration
    • Notification
      • Jira
      • ServiceNow
      • Slack
      • Splunk
    • Forensic
    • Feature
      • Rules Glossary
        • United States
        • Canada
        • Latin America
        • European Union
        • Australia
        • APAC (Asia-Pacific)
        • EMEA Countries
        • Others
      • Data identifiers Glossary
        • United States
        • Canada
        • Latin America
        • European Union
        • Australia
        • APAC (Asia-Pacific)
        • EMEA Countries
        • Others
      • Supported MIME Types
      • Supported OCR Format
    • Manage unauthorized access from unmanaged browser
  • Settings
    • Manage Reasons
    • Audit Log
  • Release Notes
    • Version - 1.27
    • Version - 1.26
    • Version - 1.25
    • Version - 1.24
    • Version - 1.23
    • Version - 1.16
    • Version - 1.15
    • Version - 1.14
    • Version - 1.13
    • Version - 1.12
    • Version - 1.11
    • Version - 1.10
    • Version - 1.09
    • Version - 1.08
    • Version - 1.07
    • Version - 1.06
    • Version - 1.05
    • Version - 1.04
    • Version - 1.03
    • Version - 1.02
    • Version - 1.01
Powered by GitBook
On this page
  1. Administrative Guide
  2. Swift Detection Engines

EDM Dictionaries

PreviousCustom Data IdentifiersNextEDM Rule

Last updated 3 months ago

In the context of Data Loss Prevention (DLP), Exact Data Match (EDM) refers to a technique used to identify and protect sensitive information by comparing data against a predefined set of values or patterns. Here's how it generally works:

  1. Define Sensitive Data: First, organizations create a reference set or "fingerprint" of sensitive data. This could be a list of Social Security numbers, credit card numbers, or other personally identifiable information (PII) that needs protection.

  2. Data Scanning: The DLP system scans data across various locations, such as databases, email communications, or file systems, looking for exact matches to the predefined sensitive data.

  3. Policy Enforcement: If an exact match is found, the DLP system can trigger actions based on predefined policies. This might include alerting administrators, blocking access, or encrypting the data to prevent unauthorized use.

  4. Reporting and Monitoring: The system typically provides reports and logs to help organizations monitor and manage data protection efforts.

EDM in DLP is particularly useful for scenarios where exact matches are necessary to identify specific sensitive data. It offers a high level of accuracy in detecting and preventing the unauthorized disclosure of confidential information.

To create an EDM Navigate to Policies section Select EDM Dictionaries and click On Add New EDM.

Provide the Exact Data Match Name, Description, and upload a sample CSV data file (ensure no real data is used). Click On Next.

Define fields & match conditions tab, by selecting at least one primary and any necessary secondary fields.

Scroll down Click On Create Dictionary.

Download EDM Dictionary tab, copy the Dictionary ID, and download the Data Indexer Tool jar file, Download the EDM Library Zip File(For Windows or Linux) and Extract the zip file.

Click on Next.

In Connect & Configure tab, Proceed to generate a key in Step 2 by Entering the API key name, description, selecting 'EDM Indexer' for key usage, granting read/write permissions, and setting the expiry date to 'Never expires.'

After creating the key, copy the key and secret, and save them in a notepad.

In Step 3, place the CSV, jar files and Extract Zip Files in the same folder.

Open the folder in Command Prompt and ensure that Java is installed on the system.

In Step 4, Run the following command in the Command Prompt to index the data:

Replace the placeholders with the appropriate values.

In Step 5, upload the generated EDM Rulepack to the Swift Platform under 'Upload XML Rulepacks' and finish the process.

Once complete, your EDM dictionary will be created and show as 'Indexed' with a green status.

You can now edit your EDM dictionary as needed by clicking on Indexed.

Click On the Edit button To Edit the EDM Dictionary.