Securing data transfer in web browsers on DLP Endpoint for Windows using the Browser API integration

Prev Next

The Browser API Integration feature allows security administrators to monitor, detect, and prevent unauthorized transfers of sensitive data across web applications, web forms, and web agents such as AI tools. It serves as a modern alternative to the Web Browser Extension and DLL Injection method, integrating directly with enterprise browsers to secure data without relying on injected libraries.

Method comparison: When to use which integration

Administrators can deploy web protection on DLP via one of two primary integration methods. Choosing the right method depends on your organization's specific monitoring requirements and browser ecosystem:

  1. Browser API Integration

    ​

    Integrates with enterprise browsers (Google Chrome, Microsoft Edge, Mozilla Firefox, and Island browsers) by communicating directly through built-in browser APIs.

    When to choose this method:

    • Stability and performance priority: You want to eliminate browser crashes and latency associated with DLL hooking.

    • Island browser environments: You utilize the Island enterprise browser, which is supported exclusively through this API method.

    • Zero-touch configuration: You prefer backend settings to be automatically applied without deploying separate extensions.

    • Modern web architectures: Your organization relies heavily on enterprise-managed browsers (like Chrome Enterprise) and wants a native protection layer.

  2. Web Extension and DLL Injection

    Injects Dynamic-Link Libraries (DLLs) directly into active browser processes and relies on browser-specific web extensions to coordinate communication between the browser, target URLs, and the local endpoint agent.

    When to choose this method:

    Text Input Monitoring Required: You must monitor manually typed text or text box submissions in web forms or AI tools (the API method does not support this).​

       

    Note

    This article is focused on the Browser API Integration which is the recommended approach for customers, where text monitoring is not required.

Key benefits of Browser API Integration

  • ​​Real-time data monitoring:​​ Inspects and protects data in real-time, reducing the risk of a data leak and ensuring compliance with PCI, PII, HIPAA, and other regulations.

  • Comprehensive endpoint visibility:​​ Enforces consistent incident logging, reporting, and user justification prompts across supported endpoint platforms.

  • Improved stability:​​ Reduces latency and prevents browser crashes compared to the alternative Web Extension method.

  • Simplified configuration:​​ Backend settings are automatically applied when enabled in the Trellix Windows Client Configuration (WCC), eliminating additional deployment steps.

  • Zero-touch configuration:​​ You prefer backend settings to be automatically applied without deploying separate extensions.

Protection vectors covered

This section details the specific data loss protection vectors and monitored capabilities supported across Browser API Integration and legacy Web Extension methods.

Category

Feature

Monitored capabilities

Supported browsers

Browser API Integration

File upload monitoring

Monitor and block classified file uploads into a browser.

Chrome, Edge, Firefox, Island

Browser printing protection

Monitor and block printing of classified (the files that have the sensitive information) files via the browser (Excludes "Save As PDF").

Chrome, Edge, Firefox, Island

URL blocking

Monitor and block a URL within the browser to prevent a user accessing a website.

Chrome, Edge, Firefox

Web extension

Text Input monitoring

Monitor text input into a browser (example, webform, AI web agents like Copilot, Gemini) for classified information.

Chrome,Edge

File  upload monitoring

Monitor and block a classified file uploads into a browser via drag-and-drop, file picker and copy and paste.

Chrome, Edge, Firefox

Text copy-paste protection

Monitor and block copy-paste of text within a classified file into a browser.

Chrome, Edge, Firefox

Browser printing protection

Monitor and block printing of classified files via the browser (Excludes "Save As PDF").

Chrome, Edge, Firefox

URL blocking

URL blocking

Chrome, Edge

Policy precedence and dependencies

Understand how this integration interacts with existing configurations to ensure consistent protection and prevent policy conflict:

  • ​​Configuration precedence:​​ You cannot use the Browser API Integration and the Web Extension method simultaneously. Once enabled, the Browser API Integration takes precedence over standard Web Extension and Web Handler settings.​

  • Browser-specific requirements:​

    • Google Chrome:​ You must configure the Browser API Integration for Google Enterprise. This requires a Google Cloud Management Token (see ​Chrome Browser Cloud Management​​).

    • Microsoft Edge and Mozilla Firefox:​​ Enabling the feature auto-registers the required registry settings/policies.

    • Island Browser:​​ Contact the Island Support Team for details on how to set up the browser.

  • Rule dependencies:​​ The following protections are not processed via the Browser API Integration itself and requires active rules to be setup:

    • Drag-and-Drop: To block users from dragging and dropping sensitive text within files utilise the Web Protection rule.

    • Copy-and-Paste: to block copy-and-paste activate the Clipboard Protection configured in Trellix​ WCC.

Activate DLP Browser API Integration

Before beginning, ensure you have access to Trellix​ WCC, active baseline protection rules (Web, Printer, and Clipboard), and your Google Cloud management token if deploying on Chrome.

If a Beta version of the Browser API Integration was previously installed, you will need to first perform the following cleanup actions:

  • Delete all Advanced Parameters associated with the Browser API Integration in ​​Windows Client Configuration​​—> Policy Catalog​ —> Advanced Configuration​​​.

  • Delete all existing registry settings configured for the Microsoft Edge.

  • Delete the ​policies.json​​ file associated with the Mozilla Firefox.

Perform the following steps to activate the Browser API Integration.

  1. In Trellix​ ePO, navigate to ​​Menu —> ​Policy —> Policy Catalog.

  2. From the Product drop-down list, select ​Data Loss Prevention (or DLP Endpoint)​​, then select ​Windows Client Configuration​​ as the category.

  3. Select ​Operation Mode and Modules​​ in the policy catalog.

  4. Select ​Browser API Integration​​ to activate the feature.

  5. Choose target browsers to protect under this integration, such as Chrome, Edge, Firefox, or Island.

  6. Confirm active baseline protection policies, including Web Protection Policy, Printer Protection Rules, and Clipboard Protection Rules.

  7. Click ​Apply Policy​​.

Considerations and Workarounds

Parameter

Limitation

Workaround

Clipboard Protection

Relies on injected DLLs and hooks; it is not processed directly via the Browser API Integration.

Configure standard copy-and-paste rules in Trellix​ WCC under Clipboard Protection.

Text Input Monitoring

Does not support monitoring of manually typed text or text box submissions.

Disable Browser API Integration and use the Web Extension method.

Known limitations

Limitation

Description

Text Input Blocking

Does not block text prompts, or copy and paste of manually typed text.

Web Application Control (WAC)

Does not operate on the island browser.

Destination URL capture

Destination URLs are not captured in incident logs for Clipboard Protection Rules on Island Browser.

HTTP Downloads

HTTP file downloads are outside the scope of the Browser API Integration.

Edge Pop-ups

Edge native block pop-ups cannot be disabled when using this feature.

Large file analysis

Adheres to strict timeout windows (e.g., 30 seconds) to conserve system resources.

Terms and definitions

  • Browser API Integration: A data protection architecture utilizing the browser Content Analysis Connector SDK to monitor, inspect, and prevent unauthorized data transfers.

  • Clipboard Protection Rules:​​ An endpoint rule category that monitors and blocks unauthorized copying and pasting of text or sensitive data.

  • Destination URL Tracking:​​ A capability that captures and records the target URL of an incident in Trellix DLP logs.

  • ​DLL Injection (Hooking):​​ An operating system process where Trellix​ DLP Agent (TA) injects dynamic-link libraries directly into active browser memory processes to monitor and intercept actions.

  • ​Island Browser:​​ A Chromium-based enterprise browser designed with deep security integrations. Supported by Trellix DLP exclusively through the Browser API Integration.

  • Legacy Web Extension Method:​​ A traditional browser security architecture relying on browser-specific extensions and DLL injection to monitor web user activity.

  • ​Printer Protection Rules:​​ A policy rule set that intercepts, monitors, or blocks files sent to physical printers, network printers, or image/PDF writers.

  • Text Upload Monitoring:​​ A capability that monitors and blocks manually typed text or text box submissions in a web form or AI tool (Supported by Legacy Web Extension only).

  • Web Application Control (WAC):​​ A policy that blocks browser access to specific websites or URLs.

  • Web Handler:​​ A core Trellix​ DLP Endpoint agent service responsible for performing DLL injection.

  • Web Protection Policy:​​ A rule set designed to monitor and block data from being posted to websites, webmail, and web-based tools by evaluating file uploads, drag-and-drop operations, and address bar URLs.