Enterprise DLP
Double Byte Characters
Table of Contents
Expand All
|
Collapse All
Enterprise DLP Docs
Double Byte Characters
Enterprise Data Loss Prevention (E-DLP) supports detection of sensitive data in Chinese, Japanese,
and Korean (CJK) double byte characters.
Enterprise Data Loss Prevention (E-DLP) supports detection of sensitive data for the following double
bye character set languages:
- Chinese (simplified)
- Chinese (traditional)
- Korean
- Japanese
Review the table below to learn more about which Enterprise DLP enforcement
channels, file types, and detection methods support and don't support double byte
characters.
- SupportedCategorySupportedChannelPrisma Access (Managed by Strata Cloud Manager)SaaS Security (API and Inline)File Types.csv.pdf.txtMicrosoft Office (.doc, .docx, .ppt, .pptx, .xls, .xlsx)ZIP filesDetection MethodsPredefined and custom regular expression (regex) data patternsPredefined and custom file property data patterns
- Not SupportedCategoryNot SupportedChannelNGFW (Managed by Panorama)NGFW (Managed by Strata Cloud Manager)File TypesMicrosoft Visio (.vsd, .vsdm, .vsdx)Image files (.jpg, .jpeg, .png, .tif, .tiff)All source code file typesDetection MethodsTitus tags for file property data patterns(SaaS Security API and Inline) Regex data patterns for PDF files
For example, Enterprise DLP can inspect and block an outbound email if sensitive
data is written in double byte plaintext characters directly in the email subject or
body. However Enterprise DLP can't inspect and block an outbound email if sensitive
data is written in double byte plaintext characters in a document meant to be detected
with a custom document type.