Symantec Data Loss Prevention System Requirements and

Compatibility Guide

Version 15.7

Last updated: March 25, 2021

 Symantec Data Loss Prevention System Requirements and Compatibility Guide

Table of Contents

About system requirements................................................................................................................4

About updates to Symantec Data Loss Prevention system requirements...............................................................4
About deprecated platforms.......................................................................................................................................... 6
System requirements and recommendations...................................................................................7
Deployment planning considerations........................................................................................................................... 7
The effect of scale on system requirements............................................................................................................... 7
Minimum system requirements for Symantec Data Loss Prevention servers..........................................................9
Single-tier installation minimum hardware requirements........................................................................................... 9
Very small installation minimum hardware requirements..........................................................................................9
Small installation minimum hardware requirements................................................................................................ 10
Medium installation minimum hardware requirements............................................................................................. 11
Large enterprise minimum hardware requirements.................................................................................................. 12
Operating system requirements for servers.............................................................................................................. 13
Installing patches for Windows Server 2012 R2..................................................................................................... 15
Installing fonts on Linux servers.............................................................................................................................. 15
Linux partition guidelines......................................................................................................................................... 15
System requirements for OCR Servers...................................................................................................................... 16
Endpoint computer requirements for the Symantec DLP Agent.............................................................................16
Windows operating system requirements for endpoint systems.............................................................................17
macOS operating system requirements for endpoint systems................................................................................19
macOS 11 compatibility and testing................................................................................................................. 19
Support for running DLP Agents on Apple Silicon systems.............................................................................21
Memory and disk space requirements for the Symantec DLP Agent......................................................................21
Supported languages for detection............................................................................................................................ 21
Oracle database requirements.................................................................................................................................... 23
Running Oracle 19c Standard Edition 2 software on alternate platforms................................................................24
Browser requirements for accessing the Enforce Server administration console.................................................25
Deploying Data Loss Prevention on public cloud infrastructures...........................................................................25
Deploying Symantec Data Loss Prevention on Amazon Web Services infrastructure............................................25
Deploying Symantec Data Loss Prevention on Microsoft Azure.............................................................................25
Deploying Symantec Data Loss Prevention on Oracle Cloud.................................................................................26
Virtual machine support............................................................................................................................................... 26
Virtual server support.............................................................................................................................................. 27
Virtual desktop and virtual application support with Endpoint Prevent....................................................................27
Supported operating systems for the EMDI, EDM, and IDM Remote Indexers.......................................................29

2
 Symantec Data Loss Prevention System Requirements and Compatibility Guide
Third-party software requirements and recommendations......................................................................................29

Product compatibility.........................................................................................................................33
Environment compatibility and requirements for Network Prevent........................................................................33
Proxy server compatibility with Network Prevent for Web......................................................................................33
SSL monitoring with Network Monitor....................................................................................................................... 34
Secure ICAP support for Network Prevent for Web.................................................................................................. 34
High-speed packet capture cards............................................................................................................................... 34
Veritas Data Insight compatibility with Symantec Data Loss Prevention................................................................35
Integrations with other Symantec products.............................................................................................................. 36
Network Discover compatibility.................................................................................................................................. 37
Supported Box cloud storage targets...................................................................................................................... 37
Supported file system targets................................................................................................................................. 37
Supported IBM (Lotus) Notes targets...................................................................................................................... 37
Supported SQL database targets........................................................................................................................... 38
Supported SharePoint server targets...................................................................................................................... 38
Supported Exchange Server targets....................................................................................................................... 38
Supported file system scanner targets.................................................................................................................... 38
Supported Documentum (scanner) targets............................................................................................................. 39
Supported OpenText (Livelink) scanner targets...................................................................................................... 39
Supported web server (scanner) targets................................................................................................................. 39
Endpoint Prevent supported applications................................................................................................................. 39
Applications Supported by Endpoint Prevent on Windows.....................................................................................40
Applications Supported by Endpoint Prevent on macOS........................................................................................ 43
Browser beta compatibility and testing.................................................................................................................... 45
Support for Monitoring Applications Protected by System Integrity Protection........................................................47
Default SIP monitoring..................................................................................................................................... 47
Monitoring SIP-protected applications on updated macOS endpoints.............................................................47
Steps to monitor SIP-protected applications on updated macOS endpoints....................................................47
Endpoint known issues............................................................................................................................................ 51
Copyright statement...........................................................................................................................53

3
About system requirements
• About updates to Symantec Data Loss Prevention system requirements
• Products included in system requirements
• About deprecated platforms

About updates to Symantec Data Loss Prevention system

requirements
System requirements are occasionally updated as new information becomes available.
The following table provides the history of updates to system requirements.

Table 1: Change history for the system requirements

Date Description
25 March 2021 Added support for Firefox 87 on both Windows and macOS.
16 March 2021 Added support for Edge (Chromium-based) version 89.
9 March 2021 Added support for Chrome 89 on both Windows and macOS with DLP 15.7 MP2.
3 March 2021 Added support for macOS 11.2.2 on DLP Agents.
26 February 2021 Added support for Firefox version 86 on both Windows and macOS with DLP 15.7 MP2.
12 February 2021 Clarified support for Microsoft Windows Server 2019, Datacenter and Standard.
9 February 2021 Added support for macOS 11.2 on DLP Agents.
4 February 2021 Added support for Chrome 87 for accessing the Enforce Server administration console.
1 February 2021 Added support for Firefox version 85 on both Windows and macOS with DLP 15.7 MP2.
25 January 2021 Added support for Edge (Chromium-based) version 88.
21 January 2021 Added support for the Rosetta 2 emulation app.
Added support for Chrome 88 on both Windows and macOS.
10 January 2021 Added support for running OpenJRE 1.8.0_275 on all DLP servers.
21 December 2020 Added support for running OpenJRE 1.8.0_262 on all DLP servers.
Added support for macOS 11.1 on DLP Agents.
Added support for Firefox 84 on both Windows and macOS.
3 December 2020 Added support for running Oracle 19c Standard Edition 2 on platforms that Oracle supports.
Added support for the Database Release Update 19.9.0.0.
Added support for Citrix XenApp and XenDesktop 7 2009.
20 November 2020 Added support for Edge (Chromium-based) version 87.
19 November 2020 Added support for Chrome 87 on both Windows and macOS.
13 November 2020 Added support for Chrome 86 on both Windows and macOS.
10 November 2020 Added support for Microsoft Windows Server 2019 Standard Edition and Enterprise Edition for operating
systems for servers. Added support for Microsoft Windows Server 2019 Core for operating systems for detection
servers.
3 November 2020 Added support for Red Hat Enterprise Linux 7.9 for operating systems for servers.
Added support for VMware Horizon 8 2006 with Symantec Data Loss Prevention 15.7 MP1.
26 October 2020 Added support for Firefox 82 on both Windows and macOS.
 Date Description
21 October 2020 Added support for Windows 10 version 20H2 on DLP Agents.
13 October 2020 Added support for Edge (Chromium-based) version 86.
Added support for macOS 10.15.7 on DLP Agents.
29 September 2020 Added support for Firefox 81 on both Windows and macOS.
25 September 2020 Added support for Oracle 19c Database Release Update 19.8.0.0.
Added support for Citrix XenApp 7.15 LTSR CU6 and Citrix XenDesktop 7.15 LTSR CU6.
14 September 2020 Added support for VMware Horizon View 7.12
Added support for Oracle 19c Database Release Update 19.6.0.0 (only on Linux servers).
Corrected support for Chrome 85 on Windows for DLP Agent version 15.5 MP1.
3 September 2020 Added support for Edge (Chromium-based) through version 85.
Added support for Chrome 85 on both Windows and macOS.
31 August 2020 Added support for Firefox 80 on both Windows and macOS.
27 August 2020 Clarified support for Oracle 19c (for Enterprise Edition and Standard Edition) to include 19.3.0.0.0.
25 August 2020 Corrected support for Chrome 75 on Windows endpoints to include support on Symantec Data Loss Prevention
version 15.5 MP1.
20 August 2020 Corrected support for Citrix XenDesktop 7 2003 to indicate support with Windows 10 20H1 (version 2004).
17 August 2020 Added support for Citrix XenApp 7 2003 and Citrix XenDesktop 7 2003.
3 August 2020 Added support for Firefox 79 on both Windows and macOS.
31 July 2020 Added support for Oracle 19c (for Oracle 19c Enterprise Release 1 and Oracle 19c Standard Edition).
23 July 2020 Support for macOS 10.15.6 on DLP Agents.
16 July 2020 Added support for Chrome 84 on both Windows and macOS.
10 July 2020 Corrected details about number of patches that are required for running Windows Server 2012 R2.
Added topic macOS 11 compatibility and testing.
1 July 2020 Added support for the Microsoft Exchange Server 2019 server target.
Added support for Firefox 77 and 78 on both Windows and macOS.
10 June 2020 Removed references to the Symantec Support Portal and pointed relevant links to the Tech Docs Portal.
4 June 2020 Added support for Red Hat Enterprise Linux 7.8 for operating systems for servers.
2 June 2020 Added support for macOS 10.15.5 on DLP Agents.
29 May 2020 Added support for Chrome 83 on both Windows and macOS. Removed references to Chrome 83 beta support.
Added support for Windows 10 Version 2004 (OS build 19041.264) on DLP Agents.
15 May 2020 Added support for Firefox 76 on both Windows and macOS. Removed references to Firefox 76 beta support.
Added support for Data Insight 6.1.5.
Added support for the following Napatech Driver packages:
• Windows: 11.8.1
• Linux: 12.1
23 April 2020 Added content from TECH235226 (see Support for Monitoring Applications Protected by System Integrity
Protection )
Added known issues that are associated with Firefox 75 and macOS 10.15.4.
Added support information for the following browsers in beta:
• Firefox 76 (for macOS)
• Firefox 76.0.0.7415 (for Windows)
• Chrome 83.0.4103.14 (for Windows and macOS)
 Date Description
9 April 2020 Added support for Chrome 81 on both Windows and macOS.
Added support for Firefox 75 on both Windows and macOS.
Added support for macOS 10.15.4 on DLP Agents.
Added support for the following EMDI, EDM, and IDM Remote Indexer platforms:
• Red Hat Enterprise Linux 6.8, 6.9, and 6.10
• Red Hat Enterprise Linux 7.3 through 7.7
• Oracle Linux 7.3 and 7.6
Added information on default SIP support and included steps to update SIP settings.
24 March 2020 Removed support for SICAP for the McAfee Web Gateway proxy.
17 March 2020 Added support for Firefox 74 on macOS.
21 February 2020 Added support for Firefox 73 on both Windows and macOS.
19 February 2020 Added support for VMware Horizon View 7.11 for DLP Agents.
14 February 2020 Added support for macOS 10.15.3 on DLP Agent version 15.7.

About deprecated platforms

Certain platforms are referred to as “deprecated.” That indicates that while the deprecated platform is supported in the
current release, Symantec plans to remove support in an upcoming release. If your Symantec Data Loss Prevention
environment includes a deprecated platform, you should plan on updating the platform to a later supported version or a
different supported platform as soon as possible.
System requirements and recommendations
Deployment planning considerations
The effect of scale on system requirements
Minimum system requirements for Symantec Data Loss Prevention servers
Single-tier installation minimum hardware requirements
Very small installation minimum hardware requirements
Small installation minimum hardware requirements
Medium installation minimum hardware requirements
Large enterprise minimum hardware requirements
Operating system requirements for servers
System requirements for OCR Servers
Endpoint computer requirements for the Symantec DLP Agent
Supported languages for detection
Available language packs
Oracle database requirements
Browser requirements for accessing the Enforce Server administration console
Deploying Data Loss Prevention on public cloud infrastructures
Virtual machine support
Supported operating systems for the EMDI, EDM, and IDM Remote Indexers
Third-party software requirements and recommendations

Deployment planning considerations

Installation planning and system requirements for Symantec Data Loss Prevention depend on:
• The type and amount of information you want to protect
• The amount of network traffic you want to monitor
• The size of your organization
• The type of Symantec Data Loss Prevention detection servers you choose to
install These factors affect both:
• The type of installation tier you choose to deploy (three-tier, two-tier, or single-tier)
• The system requirements for your Symantec Data Loss Prevention installation
The effect of scale on system requirements

The effect of scale on system requirements

Some system requirements vary depending on the size of the Symantec Data Loss Prevention software deployment.
Determine the size of your organization and the corresponding Symantec Data Loss Prevention deployment using the
information in this section.
The key considerations in determining the deployment size are as follows:
• Number of Enforce Server users
• Number of detection servers
• Daily incident volume
• Amount of network traffic to monitor
• Size of Exact Data Match profile (EDM), Exact Match Data Identifier profile (EMDI), or Indexed Data Match
profile (IDM)
• Size of your Form Recognition profile
The following table outlines five sample deployments based on enterprise size. Review these sample deployments to
understand which best matches your organization’s environment.

Table 2: Types of enterprise deployments

Very small
Variable Single tier (minimum Small Medium Large
supported system)
Number of Enforce N/A 5 10 20 30
Server users
Number of detection N/A 5 10 50 100+
servers
Daily incident volume N/A 5000 10,000 50,000 100,000
Volume of network 30-40 Mbps 30-40 Mbps 30-40 Mbps 30-40 Mbps >40 Mbps
traffic to monitor
EDM/EMDI/IDM EDM 4 million cells See the Symantec See the Symantec See the Symantec See the Symantec
index size or IDM 250 MB Data Loss Data Loss Data Loss Data Loss
(1400 files). See Prevention Prevention Prevention Prevention
the Symantec Data Administration Administration Administration Administration
Loss Prevention Guide for Guide for Guide for Guide for
Administration information about information about information about information about
Guide for EDM, IDM, and EDM, IDM, and EDM, IDM, and EDM, IDM, and
information about EMDI impact on EMDI impact on EMDI impact on EMDI impact on
EDM, IDM, and sizing for enterprise sizing for enterprise sizing for enterprise sizing for enterprise
EMDI impact on deployments. deployments. deployments. deployments.
sizing for enterprise
deployments.
Form Recognition See Form See Form See Form See Form See Form
profile size Recognition sizing Recognition sizing Recognition sizing Recognition sizing Recognition sizing
and performance at and performance at and performance at and performance at and performance at
the Tech Docs Portal the Tech Docs Portal the Tech Docs Portal the Tech Docs Portal the Tech Docs Portal
for information about for information about for information about for information about for information about
Form Recognition Form Recognition Form Recognition Form Recognition Form Recognition
sizing. sizing. sizing. sizing. sizing.
Hardware Single-tier Very small Small installation Medium installation Large enterprise
requirements installation installation minimum hardware minimum hardware minimum hardware
minimum hardware minimum hardware requirements requirements requirements
requirements requirements

For additional related information see also Symantec Data Loss Prevention Network Monitor and Prevent Performance
Sizing Guidelines, available at the Tech Docs Portal.
Minimum system requirements for Symantec Data Loss Prevention
servers
All Symantec Data Loss Prevention servers must meet or exceed the minimum hardware specifications and run on one of
the supported operating systems.
• Single-tier installation minimum hardware requirements
• Very small installation minimum hardware requirements
• Small installation minimum hardware requirements
• Medium installation minimum hardware requirements
• Large enterprise minimum hardware requirements
• Operating system requirements for servers
NOTE
Requirements for Symantec Data Loss Prevention Virtual Appliances are the same as for the software server
counterparts, except for virtual environment support. Virtual server support
If the Oracle database for Symantec Data Loss Prevention is installed on a dedicated computer (a three-tier deployment),
that system must meet its own set of system requirements.
Oracle database requirements

Single-tier installation minimum hardware requirements

The following table provides the system requirements for branch office or small organization single-tier deployments.
Because single-tier deployments include the Enforce Server, the Oracle database, and the detection server all on the
same computer, the processing and memory requirements are higher than they might be on dedicated servers in a two- or
three-tier deployment.
NOTE
The default content size for detection is 30 MB. If you plan to scan files larger than 30 MB, see article
Guidelines for tuning Symantec Data Loss Prevention to scan large files at the Tech Docs Portal for information
about tuning your system for large file inspection.

Table 3: Single-tier installation minimum hardware requirements

Required for Single Server Installation

Processor Eight-core CPU
Memory 64 GB RAM
Disk 3 TB, RAID 5 configuration (with a minimum of five spindles)
NICs 1 copper or fiber 1 Gb Ethernet NIC (if you are using Network Monitor you will need a minimum of two
NICs)

Very small installation minimum hardware requirements

The following table provides the system requirements for the smallest supported installation of Symantec Data Loss
Prevention. This is a two-tier installation, in which the Enforce Server and Oracle database are both hosted on the same
computer.
 NOTE
The default content size for detection is 30 MB. If you plan to scan files larger than 30 MB, see Guidelines for
tuning Symantec Data Loss Prevention to scan large files at the Tech Docs Portal for information about tuning
your system for large file inspection.

Table 4: Very small installation minimum hardware requirements

Network Discover, Network

Required for Enforce Server Network Monitor Prevent, Cloud Prevent for
Email, or Endpoint Prevent
Processor Two-core CPU Four-core CPU Four-core CPU
Memory 8 GB RAM 6–8 GB RAM (See the 6–8 GB RAM (See the
Symantec Data Loss Prevention Symantec Data Loss Prevention
Administration Guide for Administration Guide for
information about EDM, IDM, information about EDM, IDM,
and EMDI impact on sizing. See and EMDI impact on sizing. See
Form Recognition sizing and Form Recognition sizing and
performance at the Tech Docs performance at the Tech Docs
Portal for information about Portal for information about
Form Recognition sizing.) Form Recognition sizing.)
Disk 500 GB hard drive storage. 140 GB 140 GB
For Network Discover deployments, For Network Discover
approximately 150 MB of disk space is deployments, approximately 150
required to maintain incremental scan MB of disk space is required
indexes. This is based on an overhead of to maintain incremental scan
5 MB per incremental scan target and 50 indexes. This is based on
bytes per item in the target. an overhead of 5 MB per
incremental scan target and 50
bytes per item in the target.
NICs One copper or fiber 1 Gb/100 Mb 1 copper or fiber 1 Gb/100 1 copper or fiber 1 Gb/100
Ethernet NIC to communicate with Mb Ethernet NIC to Mb Ethernet NIC to
detection servers. communicate with the communicate with the
Enforce Server. Enforce Server.

Small installation minimum hardware requirements

The following table provides the system requirements for a small installation of Symantec Data Loss Prevention. This is a
three-tier installation, in which the Enforce Server and Oracle database are hosted on separate computers.
NOTE
The default content size for detection is 30 MB. If you plan to scan files larger than 30 MB, see article
Guidelines for tuning Symantec Data Loss Prevention to scan large files at the Tech Docs Portal for information
about tuning your system for large file inspection.
Table 5: Small installation minimum hardware requirements

Network Discover,
Network Prevent,
Required for Enforce Server Oracle database Network Monitor Cloud Prevent
for Email, or
Endpoint Prevent
Processor Two-core CPU Two-core CPU Four-core CPU Four-core CPU
Memory 8 GB RAM 8 GB RAM 6–8 GB RAM (See the 6–8 GB RAM (See
Symantec Data Loss the Symantec Data
Prevention Administration Loss Prevention
Guide for information about Administration Guide
EDM, IDM, and EMDI impact on for information about
sizing. See Form Recognition EDM, IDM, and EMDI
sizing and performance at the impact on sizing. See
Tech Docs Portal for information Form Recognition sizing
about Form Recognition sizing.) and performance at the
Tech Docs Portal for
information about Form
Recognition sizing.)
Disk 500 GB hard drive storage. 500 GB - 1 TB 140 GB 140 GB
For Network Discover Oracle database For Network Discover
deployments, approximately requirements deployments,
150 MB of disk space is approximately 150
required to maintain incremental MB of disk space is
scan indexes. This is based required to maintain
on an overhead of 5 MB per incremental scan
incremental scan target and 50 indexes. This is based
bytes per item in the target. on an overhead of 5 MB
per incremental scan
target and 50 bytes per
item in the target.
NICs One copper or fiber 1 N/A 1 copper or fiber 1 Gb/100 Mb 1 copper or fiber 1
Gb/100 Mb Ethernet NIC to Ethernet NIC to communicate Gb/100 Mb Ethernet
communicate with detection with the Enforce Server. NIC to communicate
servers. with the Enforce Server.

Medium installation minimum hardware requirements

The following table provides the system requirements for medium installations of Symantec Data Loss Prevention. This is
a three-tier installation, with the Enforce Server and Oracle database hosted on separate computers.
NOTE
The default content size for detection is 30 MB. If you plan to scan files larger than 30 MB, see Guidelines for
tuning Symantec Data Loss Prevention to scan large files at the Tech Docs Portal for information about tuning
your system for large file inspection.
Table 6: Medium installation minimum hardware requirements

Network Discover,
Network Prevent, Cloud
Required for Enforce Server Oracle database Network Monitor
Prevent for Email,
or Endpoint Prevent
Processor Two-core CPU Four-core CPU Four-core CPU Four-core CPU
Memory 12 GB RAM 16 GB RAM 6–8 GB RAM (See the 6–8 GB RAM (See the
(EDM/IDM and Form Symantec Data Loss Symantec Data Loss
Recognition profile size Prevention Administration Prevention Administration
can increase memory Guide for information Guide for information
requirements. See Form about EDM, IDM, and about EDM, IDM,
Recognition sizing and EMDI impact on sizing. and EMDI impact
performance at the See Form Recognition on sizing. See Form
Tech Docs Portal for sizing and performance Recognition sizing and
information about Form at the Tech Docs Portal performance at the
Recognition sizing.) for information about Tech Docs Portal for
Form Recognition information about Form
sizing.) Recognition sizing.)
Disk 500 GB hybrid storage. 500 GB - 1 TB 140 GB 140 GB
For Network Discover Oracle database For Network Discover
deployments, requirements deployments,
approximately 150 MB approximately 150 MB
of disk space is required of disk space is required
to maintain incremental to maintain incremental
scan indexes. This is scan indexes. This is
based on an overhead based on an overhead
of 5 MB per incremental of 5 MB per incremental
scan target and 50 scan target and 50
bytes per item in the bytes per item in the
target. target.
NICs 1 copper or fiber 1 N/A 1 copper or fiber 1 1 copper or fiber 1
Gb/100 Mb Ethernet NIC Gb/100 Mb Ethernet NIC Gb/100 Mb Ethernet NIC
to communicate with to communicate with the to communicate with the
detection servers. Enforce Server. Enforce Server.

Oracle database requirements

The effect of scale on system requirements

Large enterprise minimum hardware requirements

The following table provides the system requirements for large installations of Symantec Data Loss Prevention. This is a
three-tier installation, with the Enforce Server and Oracle database hosted on separate computers.
NOTE
The default content size for detection is 30 MB. If you plan to scan files larger than 30 MB, see Guidelines for
tuning Symantec Data Loss Prevention to scan large files about tuning your system for large file inspection.
Table 7: Large enterprise minimum system requirements

Network Discover,
Network Prevent, Cloud
Required For Enforce Server Oracle database Network Monitor
Prevent for Email,
or Endpoint Prevent
Processor Four-core CPU Six-core CPU Eight-core CPU Eight-core CPU
Memory 16 GB RAM 32 GB RAM 8–16 GB RAM (See the 8–16 GB RAM (See the
(EDM/IDM and Form Symantec Data Loss Symantec Data Loss
Recognition profile size Prevention Administration Prevention Administration
can increase memory Guide for information Guide for information
requirements. See the about EDM, IDM, and about EDM, IDM, and
Symantec Data Loss EMDI impact on sizing. EMDI impact on sizing.
Prevention Administration See Form Recognition See Form Recognition
Guide for information sizing and performance sizing and performance
about EDM and IDM for information about for information about
sizing. Form Recognition sizing. Form Recognition sizing.
See Form Recognition
sizing and performance
for information about
Form Recognition sizing.
Disk Requirements 1 TB storage (SSD or 500 GB - 1 TB 140 GB 140 GB
SAN) Oracle database For Network Discover
For Network Discover requirements deployments,
deployments, approximately 1 GB of
approximately 1 GB of disk space is required
disk space is required to maintain incremental
to maintain incremental scan indexes. This is
scan indexes. This is based on an overhead
based on an overhead of 5 MB per incremental
of 5 MB per incremental scan target and 50 bytes
scan target and 50 bytes per item in the target.
per item in the target.
NICs To communicate with N/A To communicate with the To communicate with the
detection servers: Enforce Server: Enforce Server:
1 copper or fiber 1 1 copper or fiber 1 1 copper or fiber 1
Gb/100 Mb Ethernet NIC Gb/100 Mb Ethernet Gb/100 Mb Ethernet NIC
For network traffic
monitoring (pick one):
1 copper or fiber 1
Gb/100 Mb Ethernet NIC.
High-speed packet N/A N/A High-speed packet N/A
capture cards capture cards

Oracle database requirements

The effect of scale on system requirements

Operating system requirements for servers

Symantec Data Loss Prevention servers can be installed on a supported Linux or Windows operating system. Different
operating systems can be used for different servers in a heterogeneous environment.
Symantec Data Loss Prevention supports the following 64-bit operating systems for Enforce Server and detection server
computers:
• Microsoft Windows Server 2012 R2, Datacenter Edition with
patches Installing patches for Windows Server 2012 R2
• Microsoft Windows Server 2012 R2, Standard Edition with
patches Installing patches for Windows Server 2012 R2
• Microsoft Windows Server 2016, Standard Edition
• Microsoft Windows Server 2016, Datacenter Edition
• Microsoft Windows Server 2019, Datacenter and Standard
NOTE
You can run detection servers on Microsoft Windows Server Core.
• Red Hat Enterprise Linux 6.8, 6.9, and
6.10 Installing fonts on Linux servers
• Red Hat Enterprise Linux 7.3 through
7.9 Installing fonts on Linux servers
• Oracle Linux 7.3 and 7.6
Installing fonts on Linux
servers
Symantec Data Loss Prevention supports the 64-bit operating system for detection server computers on Microsoft
Windows Server 2016, Core.
Operating system requirements for Single Server deployments
Symantec Data Loss Prevention supports the following 64-bit operating systems for Single Server deployments:
• Microsoft Windows Server 2012 R2, Datacenter Edition with
patches Installing patches for Windows Server 2012 R2
• Microsoft Windows Server 2012 R2, Standard Edition with
patches Installing patches for Windows Server 2012 R2
• Microsoft Windows Server 2016, Standard Edition
• Microsoft Windows Server 2016, Datacenter Edition
• Microsoft Windows Server 2019, Datacenter and Standard
• Red Hat Enterprise Linux 6.8, 6.9, and
6.10 Installing fonts on Linux servers
• Red Hat Enterprise Linux 7.3 through
7.9 Installing fonts on Linux servers
• Oracle Linux 7.3 and 7.6
Installing fonts on Linux
servers
English language and localized versions of both Linux and Windows operating systems are supported.
Supported languages for detection
See also the Symantec Data Loss Prevention Administration Guide for detailed information about supported languages
and character sets. You can find the Symantec Data Loss Prevention Administration Guide at the Tech Docs Portal.
Operating system requirements for the domain controller agent
The domain controller agent enables you to resolve user names from IPv4 addresses in HTTP/S and FTP incidents. See
the Symantec Data Loss Prevention Installation Guide for domain controller agent installation details.
Symantec Data Loss Prevention supports the following operating systems for the domain controller agent:
• Microsoft Windows Server 2012, Datacenter Edition (64-bit)
• Microsoft Windows Server 2012, Standard Edition (64-bit)
• Microsoft Windows Server 2012 R2, Datacenter Edition with patches
 Installing patches for Windows Server 2012 R2
• Microsoft Windows Server 2012 R2, Standard Edition with
patches Installing patches for Windows Server 2012 R2

Installing patches for Windows Server 2012 R2

If you use Windows Server 2012 R2, you must install three Microsoft patches: KB2919355, KB2919442, and
KB2999226. Go to https://support.microsoft.com/en-us/kb/2919355 and install KB2919355.
Go to https://support.microsoft.com/en-us/kb/2919442 and install KB2919442. Go to
https://support.microsoft.com/en-us/kb/2999226 and install KB2999226.

Installing fonts on Linux servers

You must have at least one font installed on your Linux servers. However, Symantec recommends installing all available
fonts on your Linux servers if you intend to use Form Recognition detection. To install all available fonts, run: yum
groupinstall fonts on each Linux Enforce Server and detection server.

Linux partition guidelines

Minimum free space requirements for Linux partitions vary according to the specific details of your Symantec Data
Loss Prevention installation. The table below provides general guidelines that should be adapted to your installation
as
circumstances warrant. Symantec recommends using separate partitions for the different file systems, as indicated in the
table. If you combine multiple file systems onto fewer partitions, or onto a single root partition, make sure the partition
has enough free space to hold the combined sizes of the file systems listed in the table.
NOTE
Partition size guidelines for detection servers are similar to those for Enforce Server without an Oracle database.
Linux partition minimum size guidelines—Enforce Server without a database, or detection server

Table 8: Linux partition minimum size guidelines—Enforce Server with Oracle database

Partition Minimum free space Description and comments

/home 6 GB Store the Oracle installation tools, Oracle installation ZIP
files, and Oracle critical patch update (CPU) files in /
home.
/tmp 1.2 GB The Oracle installer and installation tools require space in
this directory.
/opt 500 GB for Small/Medium installations Contains installed programs such as Symantec Data
1 TB for Large installations Loss Prevention, the Oracle server, and the Oracle
database. The Oracle database requires significant
space in this directory. For improved performance, you
may want to mount this partition on different disks/SAN/
RAID from where the root partition is mounted.
/var 15 GB for Small/Medium installations Contains logs, EDM/IDM indexes, Form Recognition
46 GB for Large installations indexes, incremental scan indexes, and network packet
capture directories.
Note: The /var/spool/pcap and /var/
SymantecDLP/drop_pcap directories must reside
on the same partition or mount point.
 Partition Minimum free space Description and comments
/boot 100 MB This must be in its own ext2 or ext3 partition, not part of
soft RAID (hardware RAID is supported).
swap Equal to RAM If you need to have the memory dump in case of system
crash (for debugging), you may want to increase these
amounts.

Table 9: Linux partition minimum size guidelines—Enforce Server without a database, or detection server

Partition Minimum size guidelines Description and comments

/opt 10 GB Contains installed programs such as Symantec Data
Loss Prevention and the Oracle client.
/var 15 GB for Small/Medium installations Contains logs, EDM/IDM indexes, Form Recognition
46 GB for Large installations indexes, incremental scan indexes, and network packet
capture directories.
Note: The /var/spool/pcap and /var/
Symantec/DataLossPrevention/drop_pcap
directories must reside on the same partition or mount
point.

/boot 100 MB This must be in its own ext2 or ext3 partition, not part of
soft RAID (hardware RAID is supported).
swap Equal to RAM If you need to have the memory dump in case of system
crash (for debugging), you may want to increase these
amounts.

System requirements for OCR Servers

Operating system requirements for OCR Servers
Symantec supports deployment of OCR Servers on the Windows operating system. The same Windows servers
supported for installation of the Enforce Server are supported for installation of OCR Servers.
Operating system requirements for servers
For more information on OCR Server system requirements and sizing guidelines, see Using the OCR Server Sizing
Estimator Spreadsheet.
Symantec Data Loss Prevention compatibility with OCR Servers
OCR Server version 1 is compatible with the following Symantec Data Loss Prevention versions:
• 15.1
• 15.5
• 15.7

Endpoint computer requirements for the Symantec DLP Agent

To implement Endpoint Prevent, the endpoint computers on which you install the Symantec DLP Agent must meet the
requirements that are described in the following sections.
• Windows operating system requirements for endpoint systems
• macOS operating system requirements for endpoint systems
• Memory and disk space requirements for the Symantec DLP Agent
Windows operating system requirements for endpoint systems
Support assumes that you have installed the latest DLP hot fix from Symantec (where applicable).
Endpoint Data Loss Prevention can operate on Endpoint systems that use the following Windows operating systems:
• Windows Server
• Windows 7
• Windows 8
• Windows 10 Enterprise, Pro PC operating system (64-bit) operating systems

Windows Server

Version DLP version 15.1 DLP version 15.5 DLP version 15.7
Windows Server Enterprise or Yes Yes No
Standard (64-bit) 2008 R2
Windows Server Enterprise or Yes Yes Yes
Standard (64-bit) 2012 R2
Microsoft Windows Server 2016 Yes Yes Yes
Standard or Datacenter Edition
(64-bit)
No service pack
Microsoft Windows Server 2019 No Yes Yes
(64-bit)
No

Windows 7

Version DLP version 15.1 DLP version 15.5 DLP version 15.7
Windows 7 Enterprise, No No No
Professional, Ultimate (32-bit)
No service pack
Windows 7 Enterprise, Yes Yes No
Professional, Ultimate (32-bit)
SP1
Windows 7 Enterprise, No No No
Professional, Ultimate (64-bit)
No service pack
Windows 7 Enterprise, Yes Yes No
Professional, Ultimate (64-bit)
SP1
Windows 8

Version DLP version 15.1 DLP version 15.5 DLP version 15.7
Windows 8.1 Enterprise, Pro PC Yes Yes Yes
operating system (64-bit)
Windows 8.1 Enterprise, Pro Yes Yes Yes
PC operating system (64-bit)
Update 1
Windows 8.1 Enterprise, Pro Yes Yes Yes
PC operating system (64-bit)
Update 2
Windows 8.1 Enterprise, Pro Yes Yes Yes
PC operating system (64-bit)
Update 3

Windows 10 Enterprise, Pro PC operating system (64-bit) operating systems

Version DLP version 15.1 DLP version 15.5 DLP version 15.7
Version 1703 Yes Yes Yes
(Creators Update)
a

Version 1709 Yes Yes Yes

(Fall Creators Update)
Version 1803 Yes Yes Yes
(April 2018 Update)
[OS build 17134.48]
Version 1607 Yes (on DLP Agent version 15.1 Yes Yes
(LTSB) MP1)
Version 1809 Yes (on DLP Agent version 15.1 Yes Yes
(Creators Update) MP1)
Version 1903 Yes (on DLP Agent version 15.1 Yes (on DLP Agent version 15.5 Yes
(May 2019 Update) MP2) MP1)
Version 1909 Yes (on DLP Agent version 15.1 Yes (on DLP Agent version 15.5 Yes
(OS build MP2) MP2)
18363.1171)b
Version 2004 Yes Yes Yes
(OS build
19041.572)c
Version 20H2 Yes Yes
(OS build
19042.572)

See the Symantec Data Loss Prevention Administration Guide for detailed information about supported languages and
character sets.

a. See Known Issues for DLP Agent Support of Microsoft Windows 10 Creators Update
b. There are known issues with monitoring drag and drop activity for Edge on Windows 10 (Version 1909). You must apply a hot fix for support of
the Edge browser.
c. Edge monitoring on Windows 10 Version 2004 is supported on DLP Agent version 15.7 MP1. Edge monitoring is not supported with DLP
Agent versions 15.1, 15.5, and 15.7.
Related Links
About Endpoint Data Loss Prevention compatibility
About Symantec Management Platform server requirements

macOS operating system requirements for endpoint systems

Support assumes that you have installed the latest DLP hot fix from Symantec (where applicable).
See Endpoint known issues for a list of the latest known issues.
Endpoint Data Loss Prevention can operate on Endpoint systems that use the following macOS operating systems:

Table 10: Endpoint Data Loss Prevention supported macOS operating systems

Operating system DLP version 15.1 DLP version 15.5 DLP version 15.7
Apple macOS 10.8 (64-bit) No No No
Apple macOS 10.9 (64-bit) No No No
Apple macOS 10.10 (64- No No No
bit)
Apple macOS 10.11 (64- Yes Yes No
bit)
Apple macOS 10.12 (64- Yes Yes Yes
bit)
Apple macOS 10.13 (64- Yes (through 10.13.6) Yes (through 10.13.6) Yes (through 10.13.6)
bit)a, b
Apple macOS 10.14 (64- 10.14.1, 10.14.2, and 10.14.5 on 10.14.1 - 10.14.4 on version 15.5 10.14.1 - 10.14.5
bit)c version 15.1 MP2 10.14.5 on version 15.5 MP1
10.14.6 on 15.5 MP1
Apple macOS 10.15 (64- 10.15.1 - 10.15.6 on version 10.15.1 - 10.15.7 on version 15.5 10.15.1 - 10.15.4
bit)d 15.1 MP2 MP2 10.15.5 - 10.15.7 on 15.7 MP1
Apple macOS 11.1 (64-bit) No No 11.1 on 15.7 MP2
Apple macOS 11.2 (64-bit) No No Yes, on 15.7 MP2
Apple macOS 11.2.2 (64- No No Yes, on 15.7 MP2
bit)

Symantec DLP Agents can also be installed on supported localized versions of these Windows and macOS operating
systems.

macOS 11 compatibility and testing

Update November 18, 2020
macOS 11 is compatible with Data Loss Prevention 15.7 MP2. See the Symantec Data Loss Prevention Release Notes,
Version 15.7 Maintenance Pack 2, at Related Documents at the Tech Docs Portal.
Update November 11, 2020:

a. See Known issues using macOS 10.13 with DLP Agent versions 14.6 MP2 through 15.5
b. See Known issues upgrading from macOS 10.13.6 to macOS 10.14 with DLP Agent version 15.1
c. See Known issues upgrading from macOS 10.13.6 to macOS 10.14 with DLP Agent version 15.1
d. See Configuring MDM profiles for Full Disk Access for macOS 10.15 and DLP Agent support
The public release date of macOS 11 is November 12, 2020. Symantec plans to complete testing of the macOS 11 public
release with the new DLP Agent in four weeks.
If there are no significant compatibility issues encountered during testing, the expected release date for Data Loss
Prevention 15.7 MP2 is in mid-December 2020.

Apple has announced that, in the upcoming release of macOS 11, kernel extensions will be replaced by system
extensions. System extensions are a more secure alternative to kernel extensions because third-party code runs in the
user space instead of in the kernel. This change in architecture protects the operating system by eliminating third-party
access to the kernel, while simultaneously granting a high level of privilege to third-party applications through system
extensions.
In response to the introduction of system extensions in macOS, Symantec is migrating the DLP Agent to the system
extensions architecture. To ensure the same level of functionality and data protection as previously, Symantec is testing
the new DLP Agent with macOS 11 beta builds.
To continue monitoring endpoints that have upgraded to macOS 11, you will need to deploy the new DLP Agent, which will
be based on the version 15.7 agent. Compatibility with macOS 11 will be introduced in Symantec Data Loss Prevention
15.7 Maintenance Pack 2, available in the fall or early winter of 2020. Previous versions of the DLP Agent will not be
supported with macOS 11.
Update August 6, 2020:
Symantec has completed testing macOS 11 Developer Beta 3 with the rearchitected DLP Agent (in development). Aside
from the system extensions changes that are already known, Symantec has not encountered other changes that could
adversely impact the DLP Agent.
Going forward, Symantec will continue testing with new beta releases when they are released, and will continue to rebuild
the macOS agent to support system extensions with the upcoming release.
Additional updates will be published here if there are significant testing results of beta versions of macOS 11
interoperability with the rearchitected DLP Agent to share with Data Loss Prevention Endpoint customers.
Update August 26, 2020:
Symantec has completed testing macOS 11 Developer Beta 5 with the rearchitected DLP Agent (in development).
Developer Beta 5 does not include certain third-party libraries that are required for the DLP Agent service to start.
Symantec is investigating alternatives to resolve this issue.
Update September 11, 2020:
Symantec has resolved the issue caused by the removal of certain third-party libraries in Developer Beta 5 and Public
Beta 2 and has begun testing with Public Beta 3.
Update October 15, 2020:
Symantec has completed testing macOS 11 Public Beta 9 with the rearchitected DLP Agent (in development).
Symantec is modifying the new add-in based Microsoft Outlook monitoring solution to conform to the truststore security
changes in Public Beta 9. In addition, the new agent has been validated by DLP customers that participated in a limited
Beta testing program.
NOTE
Monitoring support for Cloud Storage and Application File Access on macOS 11 endpoints will be available in
Symantec Data Loss Prevention 15.8.
Symantec is waiting for the release of the macOS 11 public release, after which qualification testing will be completed
within four weeks. Following qualification, Symantec Data Loss Prevention 15.7 Maintenance Pack 2 will be released.
Support for running DLP Agents on Apple Silicon systems
The DLP Agent version 15.7 MP2 is supported on the Rosetta 2 emulation app on Apple Silicon hardware.
See the FAQ: DLP Endpoint support for macOS 11 and Apple Silicon article for additional details:
https://support.broadcom.com/external/content/product-advisories/FAQ-DLP-Endpoint-support-for-macOS-11-and-Apple-
Silicon/16147

Memory and disk space requirements for the Symantec DLP Agent
The Symantec DLP Agent software reserves a minimum of 25 MB to 30 MB of memory on the Endpoint computer,
depending on the actual version of the software. The DLP Agent software temporarily consumes additional memory while
it detects content or communicates with the Endpoint Prevent server. After these tasks are complete, the memory usage
returns to the previous minimum.
The initial Symantec DLP Agent installation consumes approximately 70 MB to 80 MB of hard disk space. The actual
minimum amount depends on the size and number of policies that you deploy to the endpoint computer. Additional disk
space is then required to temporarily store incident data on the endpoint computer until the Symantec DLP Agent sends
that data to the Endpoint Prevent server. If the endpoint computer cannot connect to the Endpoint Prevent server for an
extended period of time, the Symantec DLP Agent will continue to consume additional disk space as new incidents are
created. The disk space is freed only after the agent software reconnects to the Endpoint Prevent server and transfers the
stored incidents.
NOTE
The default content size for detection is 30 MB. If you plan to scan files larger than 30 MB, see Guidelines for
tuning Symantec Data Loss Prevention to scan large files at the Tech Docs Portal for information about tuning
your system for large file inspection.

Supported languages for detection

Symantec Data Loss Prevention supports a large number of languages for detection. Policies can be defined that
accurately detect and report on the violations that are found in content in these languages:
• Arabic
• Brazilian Portuguese
• Chinese (traditional)
• Chinese (simplified)
• Czech
• Danish
• Dutch
• English
• Finnish
• French
• German
• Greek
• Hebrew
• Hungarian
• Italian
• Japanese
• Korean
• Norwegian
• Polish
• Portuguese
• Romanian
• Russian
• Spanish
• Swedish
• Turkish*
*Symantec Data Loss Prevention cannot be installed on a Windows operating system that is localized for the Turkish
language, and you cannot choose Turkish as an alternate locale.
A number of capabilities are not implied by this support:
• Technical support provided in a non-English language. Because Symantec Data Loss Prevention supports a particular
language does not imply that technical support is delivered in that language.
• Localized administrative user interface (UI) and documentation. Support for a language does not imply that the UI
or product documentation has been localized into that language. However, even without a localized UI, user-
defined portions of the UI such as pop-up notification messages on the endpoint can still be localized into any
language by entering the appropriate text in the UI.
• Localized content. Keywords are used in a number of areas of the product, including policy templates and data
identifiers. Support for a language does not imply that these keywords have been translated into that language.
Users may, however, add keywords in the new language through the Enforce Server administration console.
• Localized content. Keywords are used in a number of areas of the product, including policy templates and data
identifiers. Support for a language does not imply that these keywords have been translated into that language.
Users may, however, add keywords in the new language through the Enforce Server administration console.
• New file types, protocols, applications, or encodings. Support for a language does not imply support for any new file
types, protocols, applications, or encodings that may be prevalent in that language or region other than what is
already supported in the product.
• Language-specific normalization. An example of normalization is to treat accented and unaccented versions of
a character as the same. The product already performs a number of normalizations, including standard
Unicode
 normalization that should cover the vast majority of cases. However, it does not mean that all potential normalizations
are included.
• Region-specific normalization and validation. An example of this is the awareness that the product has of the format
of North American phone numbers, which allows it to treat different versions of a number as the same, and to identify
invalid numbers in EDM source files. Support for a language does not imply this kind of functionality for that
language or region.
Items in these excluded categories are tracked as individual product enhancements on a language- or region-specific
basis. Contact Symantec Technical Support for additional information on language-related enhancements or plans for the
languages not listed.
About support for character sets, languages, and locales

Oracle database requirements

Symantec Data Loss Prevention supports the following Oracle databases:
• Oracle 19c Enterprise (19.3.0.0.0).
Support is included for the following Database Release Updates (RUs):
– 19.6.0.0 (only on Linux servers)
– 19.8.0.0
– 19.9.0.0
You must obtain software and support from Oracle. For implementation details, see the Symantec Data Loss
Prevention Oracle 19c Implementation Guide at the Tech Docs Portal.
• Oracle 19c Standard Edition 2 (19.3.0.0.0). Support is included for the following Database Release Updates
(RUs): Support is included for the following Database Release Updates (RUs):
– 19.6.0.0 (only on Linux servers)
– 19.8.0.0
– 19.9.0.0
You can obtain the software from Symantec. For implementation details, see the Symantec Data Loss Prevention
Oracle 19c Implementation Guide at the Tech Docs Portal.
NOTE
Symantec recommends that you run the Oracle 19c Standard Edition 2 database on a supported version
of Windows or Linux. Symantec Data Loss Prevention supports running the Oracle 19c Standard Edition
2 database on platforms that Oracle supports. See Running Oracle 19c Standard Edition 2 software on
alternate platforms.
• Oracle 12c Enterprise Edition
Oracle 12.1.0.2 and 12.2.0.1 are tested with the Symantec Data Loss Prevention schema. You must obtain software
and support from Oracle. For implementation details, see the Symantec Data Loss Prevention Oracle 12c
Enterprise Implementation Guide at the Tech Docs Portal.
• Oracle 12c Standard Edition 2 (12c SE2) (12.1.0.2)
• Oracle 12c Standard Edition 2 Release 2 (12c SE2 R2) (12.2.0.1)
Symantec provides Oracle 12.2.0.1 Standard Edition with Symantec Data Loss Prevention.
See the Symantec Data Loss Prevention Oracle 12c Standard Edition 2 Release 2 Installation and Upgrade Guide
to install Oracle at the Tech Docs Portal.
The Symantec Data Loss Prevention database schema is supported on all editions of Oracle.
Symantec Data Loss Prevention requires the Oracle database to use the AL32UTF8 character set. If your database is
configured for a different character set, the installer notifies you and cancels the installation.
See the Symantec Data Loss Prevention Oracle 12c Standard Edition 2 Release 2 Installation and Upgrade Guide to
install Oracle with the provided template and scripts.
You can install Oracle on a dedicated server (a three-tier deployment) or on the same computer as the Enforce Server (a
two-tier or single-tier deployment):
• Three-tier deployment.
System requirements for a dedicated Oracle server are listed below. Note that dedicated Oracle server deployments
also require that you install the Oracle 12c Client on the Enforce Server computer to communicate with the remote
Oracle 12c SE2 instance.
• Single- and two-tier deployments.
When installed on the Enforce Server computer, the Oracle system requirements are the same as those of the Enforce
Server.
Single-tier installation minimum hardware requirements
Very small installation minimum hardware requirements
If you install Oracle on a dedicated server, that computer must meet the following minimum system requirements for
Symantec Data Loss Prevention:
• One of the following operating systems:
– Microsoft Windows Server 2012 R2 Standard, Enterprise, or Datacenter (64-bit)
– Microsoft Windows Server 2016 Standard or Datacenter (64-bit)
– Red Hat Enterprise Linux 6.9 (64-bit)
– Red Hat Enterprise Linux 7.3 through 7.9 (64-bit)
– Oracle Linux 7.3 or Oracle Linux 7.3 with RHCK (Red Hat compatible kernel)
• 8-32 GB of RAM
• 8-16 GB of swap space (equal to RAM up to 16 GB)
• 500 GB – 1 TB of disk space for the Enforce database
On a Linux system, if the Oracle database is on the same computer as the Enforce Server, then the /opt file system
must have at least 500 GB of free space for small or medium installations. 1 TB of free space is required for large
installations. If Oracle is installed on a different computer from the Enforce Server, then the /opt file system must have
at least 10 GB of free space, and the /boot file system must have at least 100 MB of free space.
The exact amount of disk space that is required for the Enforce Server database depends on variables such as:
• The number of policies you plan to initially deploy
• The number of policies you plan to add over time
• The number and size of attachments you want to store (if you decide to store attachments with related incidents)
• The length of time you intend to store incidents
See the Symantec Data Loss Prevention Administration Guide for more information about developing policies.
See the Symantec Data Loss Prevention Oracle Installation and Upgrade Guide for more Oracle installation information.

Running Oracle 19c Standard Edition 2 software on alternate platforms

You can run the Oracle 19c Standard Edition 2 software on platforms supported by the Oracle database software. See the
Oracle documentation for a list of supported platforms and information on installing the database software:
https://docs.oracle.com/en/database/oracle/oracle-database/19/install-and-upgrade.html
Obtain the installation files, CPUs, and RUs for your particular platform from Oracle.
If you run the database software on an alternate platform you can use the database templates that Symantec provides.
However, you must update paths in the template to be compatible with your platform and database software.
Symantec recommends that you use the Linux version of the database template. The Linux template uses elements
(for example, backslashes [/] for directories) most similar to alternate platforms.
Browser requirements for accessing the Enforce Server administration
console
You can access the Enforce Server administration console using any of the following browsers:
• Microsoft Internet Explorer 10 or 11
• Mozilla Firefox 62 through 69, and Firefox Enterprise (ESR) 68.
• Google Chrome 75 through 79, and 87
NOTE
You must install a Microsoft Language Pack on a Windows client system to support certain languages.

Deploying Data Loss Prevention on public cloud infrastructures

Symantec supports deployment of Data Loss Prevention servers on the following public clouds:
• Amazon Web Services (AWS)
Deploying Symantec Data Loss Prevention on Amazon Web Services infrastructure
• Microsoft Azure
Deploying Symantec Data Loss Prevention on Microsoft Azure
• Oracle Cloud public clouds
Deploying Symantec Data Loss Prevention on Oracle Cloud

Deploying Symantec Data Loss Prevention on Amazon Web Services

infrastructure
Table 11: Deploying Symantec Data Loss Prevention 15.7 on AWS lists the servers and operating systems that are
supported for deployment of Data Loss Prevention on AWS. You can run Symantec Data Loss Prevention on AWS on
supported operating systems.
Minimum system requirements for Symantec Data Loss Prevention servers

Table 11: Deploying Symantec Data Loss Prevention 15.7 on AWS

Data Loss Prevention servers

Enforce Server with Oracle database on the same computer (two-tier deployments) Oracle database with Amazon RDS (three-tier deployments)
Cloud Prevent for Email Network Prevent for Web Network Prevent for Email Endpoint Prevent Network Discover
API Detection for Developer Apps Appliance

For more information, see Deploying the Symantec Data Loss Prevention on Amazon Web Services (AWS) Infrastructure
at the Tech Docs Portal.

Deploying Symantec Data Loss Prevention on Microsoft Azure

Deploying Symantec Data Loss Prevention on Microsoft Azure lists the servers that are supported for deployment of
Data Loss Prevention on Microsoft Azure. You can run Symantec Data Loss Prevention on Microsoft Azure on supported
operating systems.
Minimum system requirements for Symantec Data Loss Prevention servers

Table 12: Deploying Symantec Data Loss Prevention on Microsoft Azure

Data Loss Prevention servers

Enforce Server with Oracle database Cloud Prevent for Email

Network Prevent for Web Network Prevent for Email Endpoint Prevent Network Discover

Symantec supports SIR (Symantec Image Recognition) including OCR and Form Recognition with Cloud Prevent for
Email on Azure.
Symantec supports the use of the Azure load balancer to balance the endpoint client connections to the Endpoint Server.

Deploying Symantec Data Loss Prevention on Oracle Cloud

Symantec Data Loss Prevention is supported in the following environments:
• Oracle Cloud IaaS
• Oracle Bare Metal Cloud with managed Virtual Machine (VM) instances
Deploying Symantec Data Loss Prevention on Oracle Cloud Infrastructure as a Service lists the servers that are
supported for deployment of Data Loss Prevention on Oracle Cloud Infrastructure as a Service. You can run Symantec
Data Loss Prevention on Oracle Cloud on supported operating systems.
Minimum system requirements for Symantec Data Loss Prevention

Table 13: Deploying Symantec Data Loss Prevention on Oracle Cloud Infrastructure as a Service

Data Loss Prevention servers

Enforce Server with Oracle database on the same computer (two-tier deployments) Network Prevent for Email
Endpoint Prevent Network Discover

NOTE
Three-tier Symantec Data Loss Prevention deployments are not supported on Oracle.

Virtual machine support

The following lists virtual machine support:
• Virtual server
support Virtual
server support
• Virtual desktop and virtual application support with Endpoint
Prevent Virtual desktop and virtual application support with
Virtual server support
Symantec supports running Symantec Data Loss Prevention servers on VMware ESXi 6.x and Windows Hyper-V
virtualization products, provided that the virtualization environment is running a supported operating system.
NOTE
Symantec Data Loss Prevention Virtual Appliances are supported in a virtualization environment on VMware
ESXi 5.5.0 Update 2 and VMware ESXi 6.5.
Operating system requirements for servers
At a minimum, ensure that each virtual server environment matches the system requirements for servers described in this
document.
System requirements for Symantec Data Loss Prevention servers
Consider the following support information when configuring a virtual server environment:
• Endpoint Prevent servers are supported only for configurations that do not exceed the recommended number
of connected agents.
• Symantec does not support running the Oracle database server on VMware ESXi 5.x, VMware ESXi 5.x, and
VMware ESX 6.x virtual hardware. If you deploy the Enforce Server to a virtual machine, you must install the Oracle
database using physical server hardware.
• Symantec supports running the Enforce Server and Oracle database server in a Windows Hyper-V environment.
• Symantec does not support Single Server installations on virtual machines.
A variety of factors influence virtual machine performance, including the number of CPUs, the amount of dedicated
RAM, and the resource reservations for CPU cycles and RAM. The virtualization overhead and guest operating system
overhead can lead to a performance degradation in throughput for large datasets compared to a system running on
physical hardware. Use your own test results as a basis for sizing deployments to virtual machines.
See the Symantec Data Loss Prevention Network Monitor and Prevent Performance Sizing Guidelines, available at the
Tech Docs Portal for additional information about running Network Prevent servers on virtual machines.

Virtual desktop and virtual application support with Endpoint Prevent

You can deploy the DLP Agent on Citrix and VMware virtual machines to monitor virtual desktops and prevent remote
users from copying sensitive data that is accessible through a virtual desktop.
Citrix virtualization support
The DLP agent is supported to run on the following Citrix XenDesktop virtual workstations and Citrix XenApp server
configurations:
• Citrix XenApp
 – Citrix XenApp 7.6 on Windows Server 2008 Enterprise Edition R2 (64-bit) and Windows Server 2012 R2
Standard Edition
– Citrix XenApp 7.9 on Windows Server 2012 R2 Standard Edition
– Citrix XenApp 7.11 on Windows Server 2012 R2 Standard Edition
– Citrix XenApp 7.12 Windows Server 2012 R2 Standard Edition
– Citrix XenApp 7.13 Windows Server 2012 R2 Standard Edition
– Citrix XenApp 7.14 Windows Server 2012 R2 Standard Edition
– Citrix XenApp 7.15 on Windows Server 2016 Standard Edition
– Citrix XenApp 7.15 Long Term Service Release (LTSR), Update 2 on Windows Server 2016 Standard Edition
– Citrix XenApp 7.15 LTSR, Cumulative Update (CU) 6 on Windows Server 2016 Standard Edition with Symantec
Data Loss Prevention 15.7 MP1
– Citrix XenApp 7.16 on Windows Server 2016 Standard Edition
– Citrix XenApp 7.17 on Windows Server 2016 Standard Edition
– Citrix XenApp 7.18 on Windows Server 2016 Standard Edition
– Citrix XenApp 7.19 on Windows Server 2016 Standard Edition
– Citrix XenApp 7 2003 on Windows Server 2019 Standard
– Citrix XenApp 7 2009 on Windows Server 2019 Standard
NOTE
Files saved from Microsoft Office (using Save As) to client drives hosted on Citrix XenApp 7.13 through 7.18
and Citrix XenApp 7 2003 are not monitored. However, if you are running Citrix XenApp 7.13 or later with
version 7.12 Virtual Delivery Agent (VDA), files saved to client drives (using Save As) are monitored. You can
find steps on enabling monitoring for these save operations. See Known issue running Citrix XenApp and
XenDesktop versions 7.13 through 7.18 at the Tech Docs Portal.
• Citrix XenDesktop
– Citrix XenDesktop 7.9 on Windows 8.0, 8.1, and Windows 10 (64-bit)
– Citrix XenDesktop 7.12 on Windows 10 (64-bit)
– Citrix XenDesktop 7.12 on Windows 10 (64-bit)
– Citrix XenDesktop 7.14 on Windows 10 (64-bit)
– Citrix XenDesktop 7.15 on Windows 10 RS2 (64-bit)
– Citrix XenDesktop 7.15 Long Term Service Release (LTSR), Update 2 on Windows 10 RS4 (version 1803) (64-bit)
– Citrix XenDesktop 7.15 LTSR, CU 6 on Windows 10 (version 2004) with Symantec Data Loss Prevention 15.7 MP1
– Citrix XenDesktop 7.16 on Windows 10 RS2 (64-bit)
– Citrix XenDesktop 7.17 on Windows 10 RS3 (version 1703) (64-bit)
– Citrix XenDesktop 7.18 on Windows 10 RS4 (version 1803) (64-bit)
– Citrix XenDesktop 7.19 on Windows 10 RS4 (version 1803) (64-bit)
– Citrix XenDesktop 7 2003 on Windows 10 20H1 (version 2004) (64-bit)
– Citrix XenDesktop 7 2009 on Windows 10, version 20H2 (64-bit)
NOTE
Files saved from Microsoft Office (using Save As) to client drives hosted on Citrix XenDesktop 7.13 through
7.18 and Citrix XenDesktop 7 2003 are not monitored. However, if you are running Citrix XenDesktop 7.13
or later with version 7.12 Virtual Delivery Agent (VDA), files saved to client drives (using Save As) are
monitored. See Known issue running Citrix XenApp and XenDesktop versions 7.13 through 7.18 at the Tech
Docs Portal.
VMware virtualization support
Symantec supports running the Symantec DLP Agent software on virtual workstations using one of the following:
• VMware Workstation 6.5.x
 NOTE
VMware Workstation 6.5.x is deprecated in Symantec Data Loss Prevention 15.0.
• VMware View 4.6
• VMware Horizon View:
– 6.0.1
– 6.2.1
– 7.1
– 7.3.1
– 7.4
– 7.6
– 7.9–7.12
• VMware Horizon 8 2006 with Symantec Data Loss Prevention 15.7 MP1
• VMware Fusion 7 (macOS)
• Hyper-V and Hyper-V (WS 2012 R2)

Supported operating systems for the EMDI, EDM, and IDM Remote
Indexers
You can install the Remote EMDI Indexer, the Remote EDM Indexer, and the Remote IDM Indexer on all Windows and
Linux platforms that are supported for installing the Enforce Server and detection servers. In addition, you can install the
indexers on the following Windows endpoint operating systems:
• Windows 8.1 (64-bit) Enterprise, Professional
• Windows 8.1 Update 1 (64-bit) Enterprise, Professional
• Windows 8.1 Update 2 (64-bit) Enterprise, Professional
• Windows 8.1 Update 3 (64-bit) Enterprise, Professional
• Windows 10 Update [1511] (64-bit] Enterprise, Professional
• Windows 10 Red Stone Update [1607 - RS1] (64-bit] Enterprise, Professional
• Microsoft Windows 10 Creators Update (RS2 v1703)
• Microsoft Windows 10 Creators Update (RS3 v1709)
• Microsoft Windows 10 Creators Update (RS4 v1803)

Third-party software requirements and recommendations

Symantec Data Loss Prevention requires certain third-party software. Other third-party software is recommended. See:
• Required third-party software for required software
• Required Linux RPMs for required Linux RPMs
• Recommended third-party software for recommended software
Table 14: Required third-party software

Software Required for Description

Adobe Reader All systems Adobe Reader is required for reading the Symantec Data Loss
Prevention documentation.
Download from http://www.adobe.com.
Apache Tomcat version 9 Enforce Server Required to support the reporting system.
The correct version of Tomcat is automatically installed on the
Enforce Server by the Symantec DLP Installation Wizard and does
not need to be obtained or installed separately.
Java Runtime Environment All servers You install the JRE from Symantec Data Loss Prevention software
(JRE) JRE 1.8.0_202 ZIP files.
You can run OpenJRE 1.8.0_262 or 1.8.0_275 as alternatives to
the JRE provided in the software ZIP files. See "About upgrading
the JRE to the latest version" available in the Symantec Data Loss
Prevention Installation Guide for information on migrating to the
latest JRE version.
Flex SDK 4.6 Network Discover Server Required SDK for Folder Risk Reporting.
Napatech driver package Napatech NT20E2, NT4E, Provides high-speed monitoring.
8.0.3 (driver version 3.5.1) NT40A01, and NT40E3 high- Symantec supports
(Windows Server 2012 R2 speed packet capture card • Multiple capture ports per Napatech Network capture card
and Windows Server 2016) • NT40A01 Napatech Network Accelerator
and driver package 8.1.0
• NT40E3 and NT20E2 10 gigabit interfaces
(driver version 3.5.0) (RHEL
6x/7x) • Multi-threaded packet capture
• Napatech hardware filtering
• Napatech third-generation card drivers for Windows and
RHEL platforms
• Virtualized Data Loss Prevention Network Monitor with
capture cards as PCI pass-through devices in the VMware
ESXi platform
Napatech cards are not supported on Single Server installations.
WinPcap 4.1.3 Required for Windows-based Windows packet capture library.
Network Monitor Server. WinPcap Download from http://www.winpcap.org/install/default.htm.
4.1.3 is required for Microsoft
Windows Server 2012.
Recommended for all Windows-
based detection servers.
NPcap 0.99xx Can be used in place of WinPcap During the Symantec Data Loss Prevention installation, select
for Windows-based Network WinPcap compatibility mode.
Monitor Server.
Endace card driver 5.3.1 Detection servers equipped with Endace cards are not supported on Single Server installations.
an Endace network measurement Download from http://www.endace.com.
card. Medium installation minimum hardware requirements
VMware Required to run supported Virtualization software.
components in a virtualized Download from https://www.vmware.com/download/vi.
environment.
Virtual server support
Microsoft Active Directory Required versions for connecting Provides directory services for Windows domain networks.
2012, 2012 R2, or 2016 to Active Directory.
In addition to the Linux Minimal Installation, Linux-based Symantec Data Loss Prevention servers require the Red Hat
Package Managers (RPM) listed in Required Linux RPMs.

Table 15: Required Linux RPMs

Linux-based servers Required RPMs

Enforce Server apr
Oracle server apr-util
binutils
expat
libicu
Xorg-x11*
*Required only for graphical installation.
Console-mode installation does not
require an X server.
Network Monitor Server apr
apr-util
expat
libicu
Xorg-X11*
*Required only for graphical installation.
Console-mode installation does not
require an X server.

Red Hat Enterprise Linux version 6 has these additional dependencies:

• Desktop Platform Development group package (yum groupinstall "Desktop Platform Development")
• compat-openldap
• compat-expat1
• compat-db43
• openssl098e
Red Hat Enterprise Linux version 7 has these additional 64-bit only package dependencies:
• Server with GUI group package (yum groupinstall "Server with GUI")
• Dev Tools group package (yum groupinstall "Development Tools")
• compat-openldap
• compat-db
• libpng
• compat-libtiff3
• gtk+-devel
• gtk2-devel
• gstreamer
• libstdc++.so.5
• libX11
• libXext
• libXi
• libXrender
• libXtst
• wget
• unzip
NOTE
SeLinux must be disabled on all Linux-based servers.
Symantec recommends the third-party software listed in Recommended third-party software for help with configuring and
troubleshooting your Symantec Data Loss Prevention deployment.

Table 16: Recommended third-party software

Software Location Description

Wireshark Any server computer Use Wireshark (formerly Ethereal) to verify that the detection server NIC
receives the correct traffic from the SPAN port or tap. You can also use
Wireshark to diagnose network problems between other servers.
Download the latest version from http://www.wireshark.org.
dagsnap Network Monitor Server computers Use in combination with Wireshark to verify that the detection server
that use Endace cards Endace NIC receives the correct traffic from the SPAN port or tap. Dagsnap
is included with Endace cards, and is not required with non-Endace cards.
Sysinternals Suite Any Windows server computer Troubleshooting utilities. Recommended for diagnosing problems on
Windows server computers.
Download the latest version from http://technet.microsoft.com/en-us/
sysinternals/bb842062.aspx.
LDAP browser Enforce Server An LDAP browser is recommended for configuring or troubleshooting
Active Directory or LDAP.
Product compatibility

Environment compatibility and requirements for Network Prevent

Proxy server compatibility with Network Prevent for Web
SSL monitoring with Network Monitor
Secure ICAP support for Network Prevent for Web
High-speed packet capture cards
Veritas Data Insight compatibility with Symantec Data Loss Prevention
Integrations with other Symantec products
Network Discover compatibility
Endpoint Prevent supported applications

Environment compatibility and requirements for Network Prevent

The Network Prevent Server is compatible with a wide range of enterprise-grade third-party SMTP-compliant MTAs and
hosted email services. Consult your MTA vendor or hosted email service for specific support questions.
Network Prevent Server can integrate with an MTA or hosted email service that meets the following requirements:
• The MTA or hosted email service must be capable of strict SMTP compliance. It must be able to send and receive
mail using only the following command verbs: HELO (or EHLO), RCPT TO, MAIL FROM, QUIT, NOOP, and DATA.
• When running the Network Prevent Server in reflecting mode, the upstream MTA must be able to route messages
to the Server once and only once for each message.
In practice, these requirements mean that you can use an SMTP-compliant MTA that can route outbound messages from
your internal mail infrastructure to the Network Prevent Server. For reflecting mode compatibility, the MTA must also be
able to route messages that are returned from the Network Prevent Server out to their intended recipients.
Cloud Prevent for Email Server attempts to initiate a TLS connection with a downstream MTA only when the upstream
MTA issues the STARTTLS command. The TLS connection succeeds only if the downstream MTA or hosted email service
supports TLS and can authenticate itself to the Cloud Prevent for Email Server. Successful authentication requires that
the appropriate keys and X509 certificates are available for each mail server in the proxied message chain.
See the Network Prevent MTA Integration Guide for Network Prevent for Email for information about configuring TLS
support for Cloud Prevent for Email Servers operating in forwarding mode or reflecting mode.

Proxy server compatibility with Network Prevent for Web

Network Prevent for Web Servers use a standard Internet Content Adaptation Protocol (ICAP) interface and support many
proxy servers. Network Prevent for Web supported proxy servers indicates the servers and the protocols.
Endpoint Prevent also supports secure ICAP (SICAP). You can set up secure ICAP with Blue Coat ProxySG through the
Enforce Server administration console. You can set up other proxies with secure ICAP using stunnel. See Secure ICAP
support for Network Prevent for Web
Table 17: Network Prevent for Web supported proxy servers

Proxy Supported protocols Configuration information

Blue Coat ProxySG versions 6.7 for ICAP, SICAP, HTTP, HTTPS, or FTP proxy Blue Coat product documentation
Network Prevent for Web
Cisco IronPort S-Series versions 9.1.x, ICAP, HTTP, HTTPS Cisco IronPort product documentation 9.1.x
10.1.x, and 10.5.x and 10.5.x support Secure ICAP 10.1.x
does not support SICAP
F5 BIG-IP System version 12.0.x, 13.1.0.8, ICAP, HTTP, HTTPS See Using the F5 Proxy with Symantec
14.1.0 Data Loss Prevention Network Prevent for
Web for information on integrating the F5
BIG-IP System with Network Prevent for
Web as an ICAP client-server solution.
Fortinet FortiGate-VM 5.6.x and 6.2.x ICAP, HTTP, HTTPS FortiGate-VM product documentation
McAfee Web Gateway (formerly Secure ICAP, HTTP, HTTPS, or FTP proxy Secure Web documentation (particularly the
Computing Secure Web Webwasher) chapter that describes setting up Secure
version 7.7.x, 7.8.x Web with a DLP Solution)
Squid Web Proxy versions 3.5.x ICAP, HTTP, HTTPS See the Symantec Data Loss Prevention
Integration Guide for Squid Web Proxy
Websense Appliance V5000 and V10000, ICAP, HTTP, HTTPS, FTP Does not support redaction.
with Websense Web Security version 8.4 Only supports "Block HTTP/HTTPS".
RESPMOD is not supported.
Websense blocks the traffic only when the
size of the Symantec Data Loss Prevention
rejection message (in the response rule)
is larger than 512 bytes. If the rejection
message is less than 512 bytes, an incident
is generated but the network traffic is not
blocked.

SSL monitoring with Network Monitor

Symantec has certified Network Monitor to monitor Blue Coat SSL Visibility Appliance.
For details, see Using the Blue Coat SSL Visibility Appliance with Network Monitor at the Tech Docs Portal.

Secure ICAP support for Network Prevent for Web

You configure your system to use integrated Secure ICAP for Network Prevent for Web. See the Symantec Data Loss
Prevention Administration Guide for configuration details.

High-speed packet capture cards

This topic describes the high-speed packed capture cards that are supported for Network Monitor.
Table 18: Supported high-speed packet capture cards

Card Version Driver version

Endace DAG 7.5 G2/G4 (PCI-E) 5.7.1
DAG 10X2
Note: Endace cards for use with Data Loss Prevention
are supported on Linux 64-bit systems only. Endace
cards are not supported on Single Server installations.

Napatech NT20E2, NT20E3, NT4E, NT40A01, and NT40E3 Symantec Data Loss Prevention supports the
following drier pacakges:
• Driver package 8.0.3 (driver version 3.5.1)
and 11.8.1 (driver version 3.15.x) for Windows
• Driver package 8.1.0 (driver version
3.5.0) and 12.1 (driver version 3.19.x) for
Linux
Symantec Data Loss Prevention supports the
following:
• Multiple capture ports per Napatech
Network capture card
• NT40A01 Napatech Network Accelerator
• Multi-threaded packet capture
• Napatech hardware filtering
• Napatech third-generation card drivers
for Windows and RHEL platforms
• 10 gigabit adapters
• Virtualized Data Loss Prevention Network
Monitor with capture cards as PCI pass-
through devices in the VMware ESXi
platform

Veritas Data Insight compatibility with Symantec Data Loss Prevention

Veritas Data Insight is a separately licensed option to Symantec Data Loss Prevention that helps organizations solve the
problem of identifying data owners and responsible parties for information due to incomplete or inaccurate metadata or
tracking information. Data Insight provides a connection from the Enforce Server to a Data Insight Management Server.

Table 19: Supported versions of Veritas Data Insight and Symantec Data Loss Prevention

Data Insight version DLP version 15.1 DLP version 15.5 DLP version 15.7
5.1.1 Yes Yes Yes
5.2 Yes Yes Yes
6.0 Yes Yes Yes
6.1 Yes Yes Yes
6.1.1 Yes Yes Yes
6.1.2 Yes Yes Yes
6.1.3 Yes, on version 15.1 MP1 Yes Yes
6.1.4 No Yes Yes
6.1.5 No No Yes
Integrations with other Symantec products
This section describes compatibility of various integrations of Symantec Data Loss Prevention with the following Symantec
products:
• Symantec PGP Universal Gateway Email
Table 20: Symantec PGP Universal Gateway Email
• Symantec Messaging Gateway (SMG)
Table 21: Symantec Messaging Gateway (SMG) (8200 and 8300 Series)
• Symantec Web Gateway (SWG)
Table 22: Symantec Web Gateway (SWG)
• Symantec Endpoint Protection
Table 23: Symantec Endpoint Protection
• Symantec Encryption Management Server (DLP Encryption Insight)
Table 24: Symantec Encryption Management Server (DLP Encryption Insight)

Table 20: Symantec PGP Universal Gateway Email

Version DLP version 15.1 DLP version 15.5 DLP version 15.7
3.3.x Yes Yes Yes

Table 21: Symantec Messaging Gateway (SMG) (8200 and 8300 Series)

Version DLP version 15.1 DLP version 15.5 DLP version 15.7
10.6.x Yes Yes Yes
10.7.x No Yes Yes

Table 22: Symantec Web Gateway (SWG)

Version DLP version 15.1 DLP version 15.5 DLP version 15.7
5.2.7 Yes Yes Yes

Table 23: Symantec Endpoint Protection

Version DLP version 15.1 DLP version 15.5 DLP version 15.7
12.1.6 (12.1 RU6 MP6) Yes Yes Yes
14.0 Yes Yes Yes
14.0.1 and 14.0.1 MP1 Yes Yes Yes

Table 24: Symantec Encryption Management Server (DLP Encryption Insight)

Version DLP version 15.1 DLP version 15.5 DLP version 15.7
3.4 Yes Yes Yes
Network Discover compatibility
Network Discover locates exposed confidential data by scanning a broad range of enterprise data repositories such as:
file servers, databases, Microsoft SharePoint, Lotus Notes, Documentum, Livelink, Microsoft Exchange, and Web
servers.
The following lists scan support for enterprise data repositories:
• Supported Box cloud storage targets
• Supported file system targets
• Supported IBM (Lotus) Notes targets
• Supported SQL database targets
• Supported SharePoint server targets
• Supported Exchange Server targets
• Supported file system scanner targets
• Supported Exchange scanner targets
• Supported Documentum (scanner) targets
• Supported OpenText (Livelink) scanner targets
• Supported web server (scanner) targets

Supported Box cloud storage targets

The Box target supports scanning of files and folders in enterprise Box cloud storage accounts.

Supported file system targets

The File System target supports scanning of the following network file systems.
Supported file servers:
• CIFS Servers only
Supported file shares:
• CIFS:
– Windows Server 2012 R2 (SMB 1.0 and 2.0 supported on Windows and Linux Network Discover servers)
– Windows Server 2016 (SMB 1.0 and 2.0 supported on Windows and Linux Network Discover servers)
• NFS on Red Hat Enterprise Linux 7.x
• DFS scanning on Windows 2012 R2 and 2016.
NOTE
DFS is not supported with Network Protect.
In addition, the File System target supports scanning of Microsoft Outlook Personal Folders (.pst files) created with
Outlook 2010, 2013, and 2016.
The Network Discover Server scanning this target must be running a Windows operating system, and Outlook 2007 or
later must be installed on that system.
NOTE
You can use SSHFS to scan File System targets on UNIX systems. Ensure that you use Fuse components and
packages that are validated and adhere to your organisation's security policies. Technical support is available
only for Symantec components.

Supported IBM (Lotus) Notes targets

The IBM Notes (formerly known as Lotus Notes) target supports scanning of the following versions:
• Lotus Notes 8.5.x
• IBM Notes 9.0.x
The files Notes.jar and NCSO.jar are in the Lotus Notes client installation directory. The manifest version number of
these files depend on the Domino server version.
• Version 8 has a manifest version in the JAR file of 1.5.0
• Version 9 has a manifest version in the JAR file of 1.6.0

Supported SQL database targets

The following SQL Databases were tested with Network Discover Target scans:
• Oracle 11g (11.2.x), 12c (12.1.x), and 18c (12.2.x) (the vendor_name is oracle)
• SQL Server 2014 and 2016 (the vendor_name is sqlserver)
• DB2 10.5 (the vendor_name is db2)
Contact Symantec Data Loss Prevention support for information about scanning any other SQL databases.

Supported SharePoint server targets

The following SharePoint server targets are supported:
• Microsoft Office SharePoint Server 2010 SP2
• Microsoft Office SharePoint Server 2013 SP1
• Microsoft Office SharePoint Server 2016
• Microsoft Office SharePoint Server 2019
NOTE
You must install the Symantec SharePoint solution to scan SharePoint Server 2019 targets.

Supported Exchange Server targets

Symantec Data Loss Prevention supports the following Exchange Server targets:
• Microsoft Exchange Server 2010 SP3
• Microsoft Exchange Server 2013
• Microsoft Exchange Server 2013 SP1
• Microsoft Exchange Server 2016 (on-premises)
• Microsoft Exchange Server 2019
To use the Exchange Web Services connector, Exchange Web Services and the Autodiscover Service must be enabled
on your Exchange server and are accessible to the Network Discover server.
You can scan the data objects that are stored within Public Folders, such as:
• Email messages
• Message attachments
• Microsoft Word documents
• Excel spreadsheets
The Exchange scan also targets mail stored in Exchange 2013 and 2016 Personal Archives.

Supported file system scanner targets

The following remote Windows systems can be scanned:
• Windows Server 2012 R2
• Windows Server 2016
The following Linux file systems can be scanned:
• Red Hat Enterprise Linux 6.x
• Red Hat Enterprise Linux 7.4
The following AIX file systems can be scanned:
• AIX 7.1
AIX requires the following C run time libraries, as well as Java 1.8 and Java 8 JRE:
• xlC.aix50.rte (v8.0.0.0+)
• xlC.rte (v8.0.0.0+)
The following 32-bit Solaris file systems can be scanned (64-bit systems are not supported):
• Solaris 10 (SPARC platform)
Solaris requires the following patch levels for the scanner:
• Solaris 9, 115697-01
File systems on UNIX systems can also be scanned using the SFTP protocol. This protocol provides a method similar to
share-based file scanning, instead of using the File System Scanner. Contact Symantec Professional Services for details.

Supported Documentum (scanner) targets

The Documentum scanner supports scanning a Documentum Content Server 5.3.x or 6.6.x, and 6.7 repository.

Supported OpenText (Livelink) scanner targets

The Livelink scanner supports scanning of OpenText (Livelink) Server 9.x targets. This version is deprecated in Symantec
Data Loss Prevention 15.5. Livelink scanners will be removed in the next release of Symantec Data Loss Prevention.

Supported web server (scanner) targets

The web server scanner supports scanning of a static HTTP web site.

Endpoint Prevent supported applications

Applications supported by Endpoint Prevent on Windows describes individual applications that can be monitored using
Endpoint Prevent on Windows; Applications supported by Endpoint Prevent on macOS describes browsers that can be
monitored using Endpoint Prevent on macOS.
Endpoint Prevent enables you to add monitoring support for other third-party applications not listed in the following tables.
An example of a third-party application is Thunderbird. You add monitoring support for an application on the Enforce
Server administration console. Always test monitoring support for applications before you enable monitoring on a large
number of endpoints. Individual applications may need additional filtering settings to maintain acceptable performance.
See the Symantec Data Loss Prevention System Administration Guide for more information about configuring and using
application monitoring.
NOTE
Applications supported by Endpoint Prevent on Windows and Applications supported by Endpoint Prevent on
macOS assume that you have installed the latest DLP hot fix from Symantec.
Applications Supported by Endpoint Prevent on Windows
This section describes individual applications that can be monitored using Endpoint Prevent on Windows
IMPORTANT
You must install the latest hotfix for Symantec Data Loss Prevention to ensure that you have the platform
support as indicated in the following tables. In some cases, platform support as indicated is enabled only when
you apply the latest hotfix.
Support is listed for the following items:
• HTTP support
• Secure HTTP (HTTPS)
• Instant messaging
• Email
• FTP
• CD/DVD
• Cloud Sync Apps
• Misc.

HTTP support

Software DLP 15.1 DLP 15.5 DLP 15.7

All browsers Yes Yes Yes

Secure HTTP (HTTPS)

Software and version DLP 15.1 DLP 15.5 DLP 15.7

Internet Explorer 10.0 Yes Yes Yes
Internet Explorer 11.0 Yes Yes Yes
Edge RS1 Deprecated No No
Edge RS2 Yes Yes Yes
Edge RS3 and RS4 Yes Yes Yes
Edge (Chromium-based) Yes, on version 15.1 MP2 Yes, on version 15.5 MP2 Yes, on version 15.7 MP1
through version 85
Edge (Chromium-based) No Yes Yes
version 86 though 87
Edge (Chromium-based) No Yes, on version 15.5 MP2 Yes, on version 15.7 MP2
version 88
Edge (Chromium-based) No No Yes, on version 15.7 MP2
version 89
Firefox 23 through 46.0.1 Yes Yes Yes
Firefox 51-54 Yes Yes Yes
Firefox 56-61 Yes Yes Yes
Firefox 62 Yes Yes Yes
Firefox 63 Yes, on version 15.1 MP1 Yes Yes
Firefox 64, 65 No Yes Yes
 Software and version DLP 15.1 DLP 15.5 DLP 15.7
Firefox 66 Yes, on version 15.1 MP1 Yes Yes
Firefox 67 Yes, on version 15.1 MP1 Yes, on version 15.5 MP1 Yes
Firefox 68 Yes, on version 15.1 MP2 Yes, on version 15.5 MP1 Yes
Firefox 69 Yes, on version 15.1 MP2 Yes, on version 15.5 MP1 Yes
Firefox 70 Yes Yes Yes
Firefox 71 Yes, on version 15.1 MP2 Yes, on version 15.5 MP2 Yes
Firefox 73-80 Yes Yes Yes
Firefox 81 and 82 No Yes Yes
Firefox 84 and 85 No Yes, on version 15.5 MP2 Yes, on version 15.7 MP2
Firefox 86 No No Yes, on version 15.7 MP2
Firefox 87 No Yes, on version 15.5 MP2 Yes, on version 15.7 MP2
Chrome 38 through 59 Yes Yes Yes
Chrome 60 through 69 Yes Yes Yes
Chrome 70, 71 Yes, on version 15.1 MP1 Yes Yes
Chrome 72, 73 Yes, on version 15.1 MP1 Yes Yes
Chrome 74 No Yes, with version 15.5 MP1 Yes
Chrome 75 Yes, on version 15.1 MP2 Yes, on version 15.5 MP1 Yes
Chrome 76 Yes, on version 15.1 MP2 Yes, on version 15.5 MP1 Yes
Chrome 77 Yes, on version 15.1 MP2 Yes, on version 15.5 MP1 Yes
Chrome 78-81 Yes, on version 15.1 MP2 Yes, on version 15.5 MP2 Yes
Chrome 83-85 Yes, on version 15.1 MP2 Yes, on version 15.5 MP2 Yes
Chrome 86-88 No Yes, on version 15.5 MP2 Yes
Chrome 89 No No Yes, on 15.7 MP2

Instant messaging

Software and version DLP 15.1 DLP 15.5 DLP 15.7

AIM Yes Yes Yes
AIM Pro Yes Yes Yes
AIM6 Yes Yes Yes
Microsoft Office Comm- unicator Yes Yes Yes
Skype Yes Yes Yes

Email

Software and version DLP 15.1 DLP 15.5 DLP 15.7

Outlook 2010 Yes Yes Yes
Outlook 2013 Yes Yes Yes
Outlook 2016 Yes Yes Yes
Outlook 2019 Yes, on 15.1 MP1 Yes Yes
 Software and version DLP 15.1 DLP 15.5 DLP 15.7
Outlook Web Access (rich and Yes Yes Yes
light mode) 2010
Outlook Web Access (rich and Yes Yes Yes
light mode) 2013
Outlook Web Access (rich and Yes Yes Yes
light mode) 2016
Lotus Notes (IBM Domino) Yes (8.5.3) Yes (8.5.3) Yes (8.5.3)
Lotus Notes (IBM Domino) Yes Yes Yes

FTP

Software version DLP 15.1 DLP 15.5 DLP 15.7

N/A Yes Yes Yes

CD/DVD

Software version DLP 15.1 DLP 15.5 DLP 15.7

BsClip Yes Yes Yes
Bs Recorder Gold Yes Yes Yes
BurnAware Yes Yes Yes
Cheetah Burner Yes Yes Yes
Command Burner Yes Yes Yes
CopyToDVD Yes Yes Yes
Creator10 Yes Yes Yes
GEAR for Windows Yes Yes Yes
mkisofs Yes Yes Yes
Nero Yes Yes Yes
Nero Start Smart Yes Yes Yes
Roxio Yes Yes Yes
Roxio RecordNow Yes Yes Yes
Roxio5 Yes Yes Yes
Roxio Mediahub Yes Yes Yes
Silent Night Micro Burner Yes Yes Yes
Star Burn Yes Yes Yes

Cloud Sync Apps

Software version DLP 15.1 DLP 15.5 DLP 15.7

Box 4.0.6169 Yes Yes Yes
Box (Most recent version Yes Yes Yes
available)
 Software version DLP 15.1 DLP 15.5 DLP 15.7
Dropbox Yes Yes Yes
3.2.x, Version 31.4.x - 38.4.x
6.4.x,
8.4.x
12.4.x, 13.4.x, 14.4.x, 15.4.x,
17.4.x, 19.4.x, 20.4.x - 38.4.x
Dropbox (Most recent version Yes Yes Yes
available)
Microsoft OneDrive Yes Yes Yes
15.0.4675. 1003 for Win 8.1
(default) 17.3.4726. 0226 and
17.3.6517. 0809 for Win 7 x86/
x64 (desktop client)
Hightail 2.4.7. 1621 Yes Yes Yes
Google Backup and Sync 3.35.x Yes Yes Yes
Google Backup and Sync 3.37.x Yes Yes Yes
Google Backup and Sync 3.41.x Yes Yes Yes
Google Backup and Sync 3.46.x Yes
Google Drive Yes Yes Yes
1.20.x, 1.30.x, 1.32.x, 2.34.x -
3.37.x
Apple iCloud Yes Yes Yes
4.0.3.56, 4.0.5.20

Misc.

Software version DLP 15.1 DLP 15.5 DLP 15.7

Adobe Reader Yes Yes Yes
Apple iTunes Yes Yes Yes
Click-to-Run Yes Yes Yes
Microsoft Pro 2013
Roxio_ Central Yes Yes Yes
WebEx Communi- cations Yes Yes Yes
Module

Applications Supported by Endpoint Prevent on macOS

This section describes individual applications that can be monitored using Endpoint Prevent on macOS.
IMPORTANT
You must install the latest hotfix for Symantec Data Loss Prevention to ensure that you have the platform
support as indicated in the following tables. In some cases, platform support as indicated is enabled only when
you apply the latest hotfix.
See Endpoint known issues for a list of the latest known issues.
Support is listed for the following items:
• Secure HTTP (HTTPS)
• Email
• Instant messaging

Secure HTTP (HTTPS)

Software Version DLP 15.1 DLP 15.5 DLP 15.7

Firefox 36.0.4, Firefox 31.X ESR No Yes Yes
Firefox 38 ESR, 45 ESR, 45.1.1 Yes Yes Yes
ESR, 45.4.0, 46.0.1 ESR, 49.0.2
ESR
Firefox 68 ESR No No Yes
Firefox 49 and 50 Yes Yes Yes
Firefox 51-54 Yes Yes Yes
Firefox 56-61 Yes Yes Yes
Firefox 62 Yes Yes Yes
Firefox 63 Yes, on version 15.1 MP1 Yes Yes
Firefox 64, 65 No Yes Yes
Firefox 66 Yes, on version 15.1 MP1 Yes Yes
Firefox 67 Yes, on version 15.1 MP1 Yes, on version 15.5 MP1 Yes
Firefox 68 Yes, on version 15.1 MP2 Yes, on version 15.5 MP1 Yes
Firefox 69 Yes, on version 15.1 MP2 Yes, on version 15.5 MP1 Yes
Firefox 70 Yes Yes Yes
Firefox 71 Yes, on version 15.1 MP2 Yes, on version 15.5 MP2 Yes
Firefox 73-80 Yes Yes Yes
Firefox 81 and 82 No Yes Yes
Firefox 84 and 85 No Yes, on version 15.5 MP2 Yes, on 15.7 MP2
Firefox 86 No No Yes, on 15.7 MP2
Firefox 87 No No Yes, on 15.7 MP2
Safari 10.0.x Yes Yes No
Safari 10.1.x Yes (macOS 10.11, 10.12.1, Yes Yes
10.12.2, and 10.12.3)
Safari 11 Yes (on macOS 10.12.4 and Yes Yes
later)
Safari 12 Yes (on macOS 10.12.6 and Yes Yes
later starting on DLP Agent
version 15.1 MP1)
Safari 13 No No Yes
Chrome 41.0.x No Yes Yes
Chrome 50 Yes Yes Yes
Chrome 51 Yes Yes Yes
Chrome 52 Yes Yes Yes
Chrome 53 Yes Yes Yes
Chrome 55 Yes Yes Yes
 Software Version DLP 15.1 DLP 15.5 DLP 15.7
Chrome 56 Yes Yes Yes
Chrome 57 Yes Yes Yes
Chrome 58 Yes Yes Yes
Chrome 59 Yes Yes Yes
Chrome 60 through 69 Yes Yes Yes
Chrome 73 No Yes Yes
Chrome 74 No Yes, on version 15.5 MP1 Yes
Chrome 75 Yes, on version 15.1 MP2 Yes, on version 15.5 MP1 Yes
Chrome 76 Yes, on version 15.1 MP2 Yes, on version 15.5 MP1 Yes
Chrome 77 Yes, on version 15.1 MP2 Yes, on version 15.5 MP1 Yes
Chrome 78-81 Yes, on version 15.1 MP2 Yes, on version 15.5 MP2 Yes
Chrome 83-85 Yes, on version 15.1 MP2 Yes, on version 15.5 MP2 Yes
Chrome 86-88 No Yes, on version 15.5 MP2 Yes
Chrome 89 No No Yes, on version 15.7 MP2

Email

Software Version DLP 15.1 DLP 15.5 DLP 15.7

Outlook 2011 Yes Yes No
Outlook 2016 Yes Yes Yes
Outlook 2019 Yes, on version 15.1 MP1 Yes Yes

Instant messaging

Software Version DLP 15.1 DLP 15.5 DLP 15.7

Cisco Jabber Yes Yes Yes
Skype Yes Yes Yes

Browser beta compatibility and testing

Symantec tests beta releases of Google Chrome, Microsoft Edge Chromium, and Mozilla Firefox for compatibility
with Data Loss Prevention.
The information on this page is updated approximately every two weeks or as needed, and indicates whether critical
issues have been observed.
The following tables provides the test results for recent beta builds of Chrome, Edge Chromium, and Firefox.

Table 25: Browser beta test results; Updated on February 4, 2021. DLP version tested: 15.7 MP1

Browser Beta build Platform Result

Google Chrome 89.0.4389.40 Windows 10 Enterprise 1909 No issues were observed.

 Browser Beta build Platform Result

89.0.4389.40 macOS 10.15.7 No issues were observed.

Edge Chromium 89.0.774.18 Windows 10 Enterprise 1909 No issues were observed.
Mozilla Firefox 86.0b5 Windows 10 Enterprise 1909 No issues were observed.
86.0b4 macOS 10.15.7 No issues were observed.

Table 26: Browser beta test results; Updated on January 19, 2021. DLP version tested: 15.7 MP1

Browser Beta build Platform Result

Google Chrome 88.0.4324.96 Windows 10 Enterprise 1909 No issues were observed.

88.0.4324.96 macOS 10.15.7 No issues were observed.
Microsoft Edge Chromium 88.0.705.45 Windows 10 Enterprise 1909 No issues were observed
Mozilla Firefox 85.0b9 Windows 10 Enterprise 1909 No issues were observed.
85.0b macOS 10.15.7 No issues were observed.

Table 27: Browser beta test results; Updated on January 6, 2021. DLP version tested: 15.7 MP1

Browser Beta build Platform Result

Microsoft Edge Chromium 88.0.705.29 Windows 10 Enterprise 1909 No issues were observed
Mozilla Firefox 85.0b4 Windows 10 Enterprise 1909 No issues were observed.
85.0b4 macOS 10.15.7 No issues were observed.

Table 28: Browser beta test results; Updated on December 22, 2020. DLP version tested: 15.7 MP1

Browser Beta build Platform Result

Google Chrome 88.0.4324.50 Windows 10 Enterprise 1909 No issues were observed.

88.0.4324.50 macOS 10.15.7 No issues were observed.
Microsoft Edge Chromium 88.0.705.22 Windows 10 Enterprise 1909 No issues were observed
Mozilla Firefox 85.0b3 Windows 10 Enterprise 1909 No issues were observed.
85.0b3 macOS 10.15.7 No issues were observed.

Table 29: Browser beta test results; Updated on December 4, 2020. DLP version tested: 15.7 MP1

Browser Beta build Platform Result

Google Chrome 88.0.4324.27 Windows 10 Enterprise 1909 No issues were observed.

88.0.4324.27 macOS 10.15.7 No issues were observed.
Microsoft Edge Chromium 87.0.664.55 Windows 10 Enterprise 1909 No issues were observed
Mozilla Firefox 84.0b8 Windows 10 Enterprise 1909 No issues were observed.
84.0b7 macOS 10.15.7 No issues were observed.
Support for Monitoring Applications Protected by System Integrity Protection
The DLP Agent monitors applications that are protected by System Integrity Protection (SIP) on macOS 10.11 through
10.15, 11.1, and 11.2. You can find the latest macOS version support at Default SIP Monitoring.

Default SIP monitoring

The DLP Agent monitors macOS applications protected by System Integrity Protection (SIP). The table below lists the
DLP Agent and macOS versions where SIP monitoring is supported for a given Symantec Data Loss Prevention release.

Table 30: SIP monitoring supported by default

DLP Agent
SIP monitoring supported by default
version
15.1.x macOS 10.11 through 10.11.6
macOS 10.12 through 10.12.6
macOS 10.13 through 10.13.3 (through 10.13.6 on MP1)
15.5.x macOS 10.11 through 10.11.6
macOS 10.12 through 10.12.6
macOS 10.13 through 10.13.6
macOS 10.14.0
15.7 macOS 10.11 through 10.11.6
macOS 10.12 through 10.12.6
macOS 10.13 through 10.13.6
macOS 10.14 through 10.15.2
macOS 11.1 (on MP2)

Monitoring SIP-protected applications on updated macOS endpoints

If you plan to update the macOS to a version that exceeds the default supported version for a given DLP Agent version,
you must update the agent configuration to continue monitoring applications protected by System Integrity Protection
(SIP). If you do not update the agent configuration, the DLP Agent can no longer monitor these applications. The agent
continues to monitor all other channels.
NOTE
For a list of the DLP Agent and macOS versions where SIP monitoring is supported by default, see Default SIP
monitoring.
Steps to monitor SIP-protected applications on updated macOS endpoints.

Steps to monitor SIP-protected applications on updated macOS endpoints

Complete the following steps to monitor SIP-protected applications on updated macOS endpoints:
1. Log in to the Enforce Server administration console.
2. Go to System > Agents > Agent Configuration and click an agent configuration that is applied to the macOS agent.
3. Click the Advanced agent settings tab and locate the
setting:
Hooking.SIP_AGENT_OSX_VERSION_COMPATIBILITY.str.
4. Add the DLP Agent version and updated macOS version to the default value separated by a
semicolon. The following tables list SIP monitoring support for macOS and DLP Agent version
combinations:
 • Table 31: macOS 10.11 and DLP Agent version 15.x combinations
• Table 32: macOS 10.12 and DLP Agent version 15.x combinations
• Table 33: macOS 10.13 and DLP Agent version 15.x combinations
• Table 34: macOS 10.14 and DLP Agent version 15.x combinations
• Table 35: macOS 10.15 and DLP Agent version 15.x combinations
Each table lists the value you enter to enable SIP monitor coverage. "Not supported" indicates that SIP monitoring is
not supported for the macOS and DLP Agent version combination. "Supported" indicates that you are not required
to enter a string to monitor SIP-protected application on the macOS/DLP Agent version.
5. Consider the following when adding strings to the Hooking.SIP_AGENT_OSX_VERSION_COMPATIBILITY.str setting:
• Add new values using the default syntax: DLPAgent-version:macOS-version.
• Add a value for each DLP Agent version running on endpoints. For example, if you are running version 15.1 and
15.1 MP1 agents with macOS version 10.14.1, you enter a separate value for each agent version (15.1 and
15.1 MP1 agents). For this example scenario, you would enter 15.1.0:10.14.1;15.1.0100:10.14.1.
• Enter a DLP Agent version that exactly matches the version that displays on the Enforce Server administration
console. Refer to the Agent Overview screen in the Enforce Server administration console to confirm the
agent version.
• Enter a macOS version equal to or greater than the macOS version running on endpoints. If you enter
15.1.0100:10.14.4, macOS versions 10.14 through 10.14.4 are monitored on version 15.1 MP1 agents.
• Add a value for each DLP Agent version running on endpoints. For example, if you are running DLP Agent
version 15.1 (on macOS 10.14.1 endpoints) and 15.1 MP1 (on macOS endpoints up to version 10.14.4) in
your environment, you enter the following: 15.1.0:10.14.1;15.1.0100:10.14.4.
NOTE
DLP Endpoint Agent hot fixes are cumulative for both Mac and Windows machines. Thus, if you have
applied a subsequent hot fix for your Mac Agent, you will need to update the SIP settings accordingly.
6. Save your changes to apply the setting. After saving changes, the agent begins monitoring SIP-protected applications.

Table 31: macOS 10.11 and DLP Agent version 15.x combinations

macOS version DLP version 15.1 DLP version 15.5 DLP version 15.7
10.11.3 Supported Supported Supported
10.11.4 Supported Supported Supported
10.11.5 Supported Supported Supported
10.11.6 Supported Supported Supported

Table 32: macOS 10.12 and DLP Agent version 15.x combinations

macOS version DLP version 15.1 DLP version 15.5 DLP version 15.7
10.12.0 Supported Supported Supported
10.12.1 Supported Supported Supported
10.12.2 Supported Supported Supported
10.12.3 Supported Supported Supported
10.12.4 Supported Supported Supported
10.12.5 Supported Supported Supported
10.12.6 Supported Supported Supported
Table 33: macOS 10.13 and DLP Agent version 15.x combinations

macOS version DLP version 15.1 DLP version 15.5 DLP version 15.7
10.13.0 Supported Supported Supported
10.13.1 Supported Supported Supported
10.13.2 Supported Supported Supported
10.13.3 Supported Supported Supported
10.13.4 • For 15.1 enter: Supported Supported
15.1.0:10.13.4
• Supported on 15.1 MP1
and MP2
10.13.5 • For 15.1 enter: Supported Supported
15.1.0:10.13.5
• Supported on 15.1 MP1
and MP2
10.13.6 • For 15.1 enter: Supported Supported
15.1.0:10.13.6
• Supported on 15.1 MP1
and MP2

Table 34: macOS 10.14 and DLP Agent version 15.x combinations

macOS version DLP version 15.1 DLP version 15.5 DLP version 15.7
10.14 • For 15.1 enter: Supported Supported
15.1.0:10.14.0
• Supported on 15.1 MP1
and MP2
10.14.1 • Not supported on 15.1 and • For 15.5 enter: Supported
15.1 MP2 15.5.0:10.14.1
• For 15.1 MP1 enter: • For 15.5 MP1 enter
15.1.0100:10.14.1 15.5.0100:10.14.1
• For 15.5 MP2 enter
15.5.0:10.14.1
10.14.2 • Not supported on 15.1 and • For 15.5 enter: Supported
15.1 MP2 15.5.0:10.14.2
• For 15.1 MP1 enter: • For 15.5 MP1 enter
15.1.0100:10.14.2 15.5.0100:10.14.2
• For 15.5 MP2 enter
15.5.0:10.14.2
10.14.3 Not supported • For 15.5 enter: Supported
15.5.0:10.14.3
• For 15.5 MP1 enter
15.5.0100:10.14.3
• For 15.5 MP2 enter
15.5.0:10.14.3
 macOS version DLP version 15.1 DLP version 15.5 DLP version 15.7
10.14.4 Not supported • For 15.5 enter: Supported
15.5.0:10.14.4
• For 15.5 MP1 enter
15.5.0100:10.14.4
• For 15.5 MP2 enter
15.5.0:10.14.4
10.14.5 • Not supported for 15.1 • Not supported for 15.5 Supported
• For 15.1 MP2 enter: • For 15.5 MP1 enter
15.1.0200:10.14.5 15.1.0104:10.14.5
You must install the latest
15.5 MP1 Hotfix to use this
string.
• For 15.5 MP2 enter:
15.5.0204:10.14.5
10.14.6 • Not supported for 15.1 • Not supported for 15.5. Supported
• For 15.1 MP2 enter: • For 15.5 MP1 enter
15.1.0200:10.14.6 15.5.0106:10.14.6
You must install the latest
15.5 MP1 Hotfix to use this
string.
• For 15.5 MP2 enter:
15.5.0204:10.14.6
You must install the latest
15.5 MP2 Hotfix to use this
string.

Table 35: macOS 10.15 and DLP Agent version 15.x combinations

macOS version DLP version 15.1 DLP version 15.5 DLP version 15.7
10.15 • Not supported on 15.1 and • Not supported on 15.5 and Supported
15.1 MP1 15.5 MP1.
• For 15.1 MP2 enter: • For 15.5 MP2 enter:
15.1.0200:10.15.0 15.5.0204:10.15.0
You must install the latest
15.5 MP2 Hotfix to use this
string.
10.15.1 • Not supported on 15.1 and • Not supported on 15.5 and Supported
15.1 MP1 15.5 MP1.
• For 15.1 MP2 enter: • For 15.5 MP2 enter:
15.1.0209:10.15.1 15.5.0204:10.15.1
You must install the latest You must install the latest
15.1 MP2 Hotfix to use this 15.5 MP2 Hotfix to use this
string. string.
10.15.2 • Not supported on 15.1 and • Not supported on 15.5 and Supported
15.1 MP1 15.5 MP1.
• For 15.1 MP2 enter: • For 15.5 MP2 enter:
15.1.0209:10.15.2 15.5.0204:10.15.2
You must install the latest You must install the latest
15.1 MP2 Hotfix to use this 15.5 MP2 Hotfix to use this
string. string.
 macOS version DLP version 15.1 DLP version 15.5 DLP version 15.7
10.15.3 Not supported • Not supported on 15.5 and Supported
15.5 MP1.
• For 15.5 MP2 enter:
15.5.0304:10.15.2
You must install the latest
15.5 MP2 Hotfix to use this
string.
10.15.4 • Not supported on 15.1 and • Not supported on 15.5 and Enter 15.7.0:10.15.4
15.1 MP1. 15.5 MP1.
• For 15.1 MP2 enter: • For 15.5 MP2 enter:
15.1.0212:10.15.4 15.5.0210:10.15.4
You must install the latest You must install the latest
15.1 MP2 Hotfix to use this 15.5 MP2 Hotfix to use this
string. string.
10.15.5 • Not supported on 15.1 and • Not supported on 15.5 and • Not supported on 15.7.
15.1 MP1. 15.5 MP1. • For 15.7 MP1 enter:
• For 15.1 MP2 enter: • For 15.5 MP2 enter: 15.7.0100:10.15.5
15.1.0215:10.15.5 15.5.0213:10.15.5
You must install the latest You must install the latest
15.1 MP2 Hotfix to use this 15.5 MP2 Hotfix to use this
string. string.
10.15.6 • Not supported on 15.1 and • Not supported on 15.5 and • Not supported on 15.7.
15.1 MP1. 15.5 MP1. • For 15.7 MP1 enter:
• For 15.1 MP2 enter: • For 15.5 MP2 enter: 15.7.0100:10.15.6
15.1.0215:10.15.6 15.5.0213:10.15.6
You must install the latest You must install the latest
15.1 MP2 Hotfix to use this 15.5 MP2 Hotfix to use this
string. string.
10.15.7 Not supported • Not supported on 15.5 and • Not supported on 15.7.
15.5 MP1. • For 15.7 MP1 enter:
• For 15.5 MP2 enter: 15.7.0100:10.15.7
15.5.0213:10.15.7
You must install the latest
15.5 MP2 Hotfix to use this
string.

Endpoint known issues

This table lists the Endpoint known issues in 15.7.
Table 36: Endpoint known issues in 15.7

Issue Description Workaround

4151955 On Windows endpoints, if a user attempts to upload None.
multiple sensitive files to Firefox using drag and drop to a
site that does not support drag and drop, then performs the
same action with the same files to a site that supports drag
and drop, block pop-ups display twice for each file and two
incidents are logged for each upload attempt.
4208190 On Windows endpoints, filters for HTTPS are not applied Add * to the beginning and end of the HTTPs filter. For
to files saved using a Save As operation from Microsoft example, if the existing HTTPS filter is -dav.box.com,
Office applications to SharePoint or OneDrive. which correctly applies a filter to Internet Explorer and
Firefox, add another filter to monitor Save As operations
from Office apps: *dav.box.com*.
4248826 Users are unable to paste content to Internet None.
Explorer from the Clipboard when Edge is monitored
using the Application Monitoring feature.
4248828 Opening a Microsoft Office file that contains sensitive data None.
residing on a network share triggers an incident.
4249161 Symantec Data Loss Prevention Endpoint Discover now None.
supports the Limit Incident Data Retention response
rule for eDAR scans on Microsoft Windows endpoints;
however, you cannot use the Limit Incident Data
Retention response rule in combination with any other
response rule.
4250243 If a user launches an application while logged on as None.
another user (Run as different user) and attempts to
upload sensitive information, an incident is generated as
expected. However, no pop-up alert is displayed to the
user, even if the response rule is configured to display a
pop-up alert.
4268115 If a user running macOS 10.15.4 saves a .doc None.
file that contains sensitive data to a removable
storage device, detection does not occur.
4268116 If a user running macOS 10.15.4 uploads a sensitive file to None.
Box using Safari, detection occurs, and a file with a zero
byte size is uploaded to Box.
4267712 If a user installs Firefox 74 for the first time with the Complete the following to enable URL filters and URL
DLP Agent running, URL filters do not work and Block information:
and notify pop-ups display unknown for the URL when 1. Uninstall Firefox 74.
sensitive files are uploaded. 2. Confirm that the DLP Agent is running on the
endpoint and install Firefox 73.
3. Upgrade to Firefox 74.
Copyright statement
Copyright statement
Broadcom, the pulse logo, Connecting everything, and Symantec are among the trademarks of Broadcom.
Copyright ©2021 Broadcom. All Rights Reserved.
The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, please visit
www.broadcom.com.
Broadcom reserves the right to make changes without further notice to any products or data herein to improve reliability,
function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does
not assume any liability arising out of the application or use of this information, nor the application or use of any product or
circuit described herein, neither does it convey any license under its patent rights nor the rights of others.