McAfee Data Loss Prevention Prevent 11.4.200 Release Notes

The McAfee DLP Prevent 11.4.200 release can update platform support.

Every update release is cumulative and includes all features and fixes from the previous release. We recommend that you always upgrade to the most current update.

Rating for update 11.4.200

The rating defines the urgency for installing this update.


Mandatory Critical High Priority Recommended

  • Recommended for all environments. Apply this update at the earliest convenience.
  • Not applicable to hotfixes, because a hotfix is only created in response to a business-impacting issue.
  • An update that resolves non-severe issues or improves product quality is considered as recommended.

For more information, see KB51560.

Release details

Release date — September 8, 2020

Release build:

  • McAfee® Data Loss Prevention Prevent (McAfee DLP Prevent) appliance installation images:
    • For VMware vSphere virtual appliance —
    • For Windows Hyper-V —
    • For hardware appliance — McAfee-PS-11.4.200-3593.100.iso
  • DLP Appliance Management extension — build
  • Data Loss Prevention extension — build

This release updates components that depend on these McAfee ePO extensions:

  • McAfee® Agent — version 5.6.2
    Note: McAfee Agent is built into the appliance software and can't be updated through McAfee ePO.
  • Appliance Management extension — build or later
  • Common UI extension — build or later

Updated platform, environment, or operating system support

You can get the latest information about supported platforms, environments, and operating systems from KB87112.

Data Loss Prevention (DLP) Long Term Support Releases

ImportantMcAfee is enhancing our McAfee DLP release process to better serve our customers' requirements. This is achieved via defining each release as either a Long Term Support release or Feature Release.

The Long Term Support (LTS) release allows customers to maintain a stable McAfee DLP version without changes to functionality and new features (for example, customers under tight change control). The LTS release will include only security updates, bug fixes and some optimization for the existing features by releasing only updates or hotfixes. As is currently the case, these releases will continue to be fully installable packages.

Note: The LTS initial release for McAfee DLP Prevent is version 11.4.100 (11.4 update 1) to ensure high quality before becoming the stable LTS build.

For more information about LTS releases, see KB91807.

Known issues

For a list of current known issues, see McAfee Data Loss Prevention 11.x.x Known Issues (KB89301).

Resolved issues

Important: This release is cumulative and contains fixes from all previous releases.

McAfee DLP appliance issues
Reference Resolution
DLPN-8662 This release fixes an issue where McAfee DLP Prevent Appliance certificates are possibly reset after an appliance restart.
DLPN-8452 This release fixes an issue that causes out of memory issues while scanning certain files.
DLPN-8664 This release fixes an issue where the email protection rule Count each match string only one time is not working as expected.

McAfee DLP now sends alerts, where policy is not applied if an LDAP server is not selected under Users and groups settings, but there are end user-based rules corresponding to that LDAP server.

DLPN-8666 This release fixes an issue where McAfee DLP detects a write-protected Microsoft Excel 97/2003 file as Password protected or other encryption type instead of Not Encrypted.
DLPN-8667 This release adds support for Azure Rights Management Encryption and fixes an issue related to McAfee Encrypted Self Extractor in ClassificationNew Content Classification CriteriaFile Encryption for McAfee DLP Prevent Appliances.
Note: It might not be possible to differentiate between Microsoft RMS and Azure RMS in certain cases. So, for full protection, it is recommended to have both Microsoft RMS and Azure RMS file encryption conditions configured.


The security vulnerability in McAfee DLP Appliances where CBC ciphers were being detected as vulnerable is now resolved.