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
Data Loss Prevention 15.8 MP3
Data Loss Prevention 16.0.2
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.
Perform one of the following:
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.
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
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