Data Loss Prevention - Source code detection improvements
Data Loss Prevention source code detection now focuses on whole file uploads and downloads with a minimum 500-character threshold, reducing false positives from embedded code snippets in chat, documentation, or other content. Users can tune sensitivity via confidence level settings to balance detection accuracy with noise reduction.
Data Loss Prevention (DLP) source code detection now focuses on identifying whole source code file uploads and downloads. Previously, source code detection performed partial scans resulting in a higher rate of false positives. Since only whole source code files are evaluated, code embedded in other content — such as chat messages, documentation, or code samples — is no longer flagged as source code, removing a common source of false positives.
Source code detection requires a minimum of 500 characters to evaluate a file. Files below this threshold are not flagged to reduce noise. This threshold filters out small fragments that lack enough context for reliable classification.
Enable and set confidence levels to tune match sensitivity. A higher confidence level reduces false positives by requiring stronger signals that the content is truly source code. A lower confidence level catches more files at the cost of additional noise.
Source code detection applies to standalone source code files in Gateway HTTP policies. It does not detect source code embedded within other file types or payloads, such as .docx files or chat messages.
For more information, refer to Source Code predefined profiles.
Source: original entry ↗