Built-in Sensitive info types

%3CLINGO-SUB%20id%3D%22lingo-sub-3035026%22%20slang%3D%22en-US%22%3EBuilt-in%20Sensitive%20info%20types%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3035026%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20a%20way%20to%20remove%20some%20of%20the%20built-in%20sensitive%20info%20types%20located%20in%20365%20Compliance%3F%20I'm%20seeing%20a%20lot%20of%20false%20positives%20in%20content%20explorer%20due%20to%20so%20many%20sensitive%20info%20types%20we%20do%20not%20need.%20Is%20it%20possible%20to%20remove%20them%20by%20modifying%20the%20exportedrules.xml%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EChad%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3035026%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EData%20Loss%20Prevention%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Regular Visitor

Is there a way to remove some of the built-in sensitive info types located in 365 Compliance? I'm seeing a lot of false positives in content explorer due to so many sensitive info types we do not need. Is it possible to remove them by modifying the exportedrules.xml?

 

Thanks,

Chad

0 Replies