Credit Card Number Data Identifier does not trigger after upgrading to 16.0.2 from 15.8 MP3
search cancel

Credit Card Number Data Identifier does not trigger after upgrading to 16.0.2 from 15.8 MP3

book

Article ID: 381017

calendar_today

Updated On:

Products

Data Loss Prevention Data Loss Prevention Core Package Data Loss Prevention Discover Suite Data Loss Prevention Endpoint Discover Data Loss Prevention Endpoint Prevent Data Loss Prevention Endpoint Suite Data Loss Prevention Enforce Data Loss Prevention Enterprise Suite Data Loss Prevention Network Discover Data Loss Prevention Network Email Data Loss Prevention Network Monitor Data Loss Prevention Network Monitor and Prevent for Email Data Loss Prevention Network Monitor and Prevent for Email and Web Data Loss Prevention Network Monitor and Prevent for Web Data Loss Prevention Network Prevent for Email Data Loss Prevention Network Protect Data Loss Prevention Network Web Data Loss Prevention Plus Suite

Issue/Introduction

After upgrading from DLP 15.8 MP3 directly to DLP 16 RU2 (16.0.2) detections from the Credit Card Number Data Identifier do not trigger.

 

The issue can be reproduced when using the following upgrade paths:
DLP 15.8 > DLP 16.0.2
DLP 15.8 > DLP 16.0.2 > 16.1

 

Environment

Data Loss Prevention 15.8 MP3
Data Loss Prevention 16.0.2 

Cause

The migration of Data Identifiers during the upgrade of DLP 15.8 MP3 directly to DLP 16.0.2 does not convert the legacy Data Identifier patterns to regex. This conversion would have been performed if an earlier version of DLP 16.x was included in the upgrade path.

Resolution

Perform one of the following:

  1. Customers planning to upgrade from DLP 15.8 MP3 to DLP 16.0.2, but have not yet installed DLP 16.0.2, should re-download the DLP 16.0.2 platform packages if the package was downloaded before Nov 19th 2024. The md5 identifier for the new file can be found under "Additional Information" below.

  2. Customers on DLP 15.8 MP3 who have installed the DLP 16.0.2 side by side, but have not yet migrated to DLP 16.0.2, can either re-install the side by side by downloading the updated DLP 16.0.2 install which includes the updated 'UpgradeSchema_DataIdentifier_Migration.sql' OR manually update the 'UpgradeSchema_DataIdentifier_Migration' before migrating.

    To manually update the 'UpgradeSchema_DataIdentifier_Migration.sql' before migrating
    1.  On the Enforce Server, rename the file <DLP install Folder>\EnforceServer\16.0.20000\Protect\Migrator\SQL\UpgradeSchema_DataIdentifier_Migration.sql to UpgradeSchema_DataIdentifier_Migration.RU2bk
    2. Download and copy the attached script "UpgradeSchema_DataIdentifier_Migration.sql.RU2CCNFix" into the same directory on the Enforce Server, renaming the file to UpgradeSchema_DataIdentifier_Migration.sql
    3. Run the migrator as normal when ready to upgrade.

  3. If the upgrade of DLP 15.8 MP3 directly to DLP 16.0.2 is already complete, run the attached SQL script "Post-upgrade-fix-CCN-regex-patterns.sql" against the DLP database.

  4. For customers who have followed upgrade path 15.8 MP3 > 16.0.2 > 16.1, run the attached SQL script "Post-upgrade-fix-CCN-regex-patterns.sql" against the DLP database. 

 

Contact support if you have any questions or problems executing the solutions.

NOTE: Broadcom recommends that when running SQL scripts manually (by following either of points 3 or 4 above), this should be done with the DLP services on Enforce earlier stopped. Then once the script is ran and makes the required changes in the database, you can start the DLP services on Enforce back up. 

Additional Information

Upgrade paths that do not see the issue:
DLP 15.8 MP3 > DLP 16.0 > DLP 16.x
DLP 15.8 MP3 > DLP 16.0.1 > DLP 16.x
DLP 15.8 MP3 > DLP 16.1

 

The MD5 identifiers of the post November 19th, 2024 DLP 16.0 RU2 install packages.
 
filename=Symantec_DLP_16.0.2_Platform_Win-IN_16.0.20000.60702.zip
md5=7fe2123d936957a83947d4b5443b5cb0
sha1=4cf86963304b10badd79679ad3b0aff950ab3dd5
filesize=3018692914
filename=Symantec_DLP_16.0.2_Platform_Lin-IN_16.0.20000.60702.zip
md5=5ed7815db0d73dfcd7fd6cc8af1da384
sha1=e75d5629078a99071cfdd354fcf6c4b48139367f
filesize=2956288613
 

Attachments

Post-upgrade-fix-CCN-regex-patterns.sql get_app
UpgradeSchema_DataIdentifier_Migration.sql.RU2CCNFix get_app