Using these new content conditions, admins can set up various DLP rules for added protection, such as:
- File names: Block files containing text string “funkyword”
- File extensions: Block .java files
- File types: Block custom mime type such as application/custom_app
- Proximity matching: Detect “routing number” in proximity of 100 characters of “account number”
Additional details
In addition to file-based conditions, administrators can utilize associated proximity conditions to identify sensitive information in the file. This feature allows for the detection of sensitive data that appears within a specified distance of other predefined data types, regular expressions, or word lists.
For example, a rule can be configured to trigger when a bank account number is found within 100 characters of a routing number. By identifying data in context, proximity matching helps administrators reduce false positives and more accurately secure financial information or proprietary content.
Key functionality in DLP rules for file attachments and associated proximity conditions include:
- Ability to match against common or custom MIME types and system file categories
- Support for scanning attachments in Gmail, Drive, and Chat to set rules across communication channels
- Granular distance settings for proximity matching, allowing admins to define a range of up to 1,000 characters between matched conditions
Getting started
- Admins: When configuring DLP rules in the admin console, admins can locate the new content conditions of file extension, file name, and file type under content conditions. Admins can also select the option of proximity matching to set a maximum distance between two pieces of matched texts. Visit the Help Center to
Content conditions for DLP in the Admin console to configure policies for sensitive file attachments
Rollout pace
Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf workspaceupdates.googleblog.com.
SOCIAL SHARE CARD GENERATOR