Policies with MIP classification rule become corrupted after MIP decryption profile is deleted

Products

• Data Loss Prevention

Issue/Introduction

Policies with MIP classification rule become corrupted after MIP decryption profile is deleted.

Cause

There is a bug in the code that incorrectly references the description profile when it should be reference the classification profile.  When the classificaiton profile is deleted for whatever reason, it removes the incorrect references which leaves them as blank.  Now when you try and modify the policy, it expects a value but gets nothing which causes an RSOD.  In the enforce logs you will notice the following logs:

04 Dec 2023 16:23:32,769- Thread: 106 SEVERE [com.vontu.manager] [/SelectEditPolicy]

Cause:

java.lang.IllegalArgumentException: source cannot be nulljava.lang.IllegalArgumentException: source cannot be null

                at org.modelmapper.internal.util.Assert.notNull(Assert.java:53)

                at org.modelmapper.ModelMapper.map(ModelMapper.java:338)

                at com.symantec.dlp.policy.archive.converter.AipConditionModelConverter.convertToJaxb(AipConditionModelConverter.java:203)

                at com.symantec.dlp.policy.archive.converter.AipConditionModelConverter.convertToJaxb(AipConditionModelConverter.java:56)

                at com.symantec.dlp.enforcedomainservices.policy.archive.converter.TypeConverter$1.apply(TypeConverter.java:44)

 

Resolution

It's best to not delete the MIP profiles as it avoids this situation.  If you do need to delete MIP profiles, please make sure at a minimum to be at one of the below versions. This issue is addressed in the following versions:

15.8 MP3 HF20 build 15.8.00320.01003

16.0 MP2 HF6 build 16.0.00206.60362

16.0.1 HF4 build 16.0.10004.60103