The following section covers some common use cases for Netskope with MPIP.
If a label is configured to apply content marking, then it is possible that the corresponding content marking may not be visible on the document the first time it is opened. This is possible only after the machine automatically applies the label. This behavior is in line with what is documented by Microsoft.
Inspecting Sensitive Content and Applying the MPIP Label
Netskope’s DLP can identify sensitive content in files stored on cloud apps. You can set up a policy to use MIP to label documents as sensitive.
- In the MIP tenant, go to Classification and create a new label you want to apply to files with sensitive content.
- Publish the label to all users and groups. Select All under Users and groups.
- In the Netskope tenant, create a new API-enabled Protection policy. Under Actions choose IRM Protect > MPIP and then the label you want to use.
For detailed instructions on creating a policy, see Configure an API Data Protection Policy for MIP.
The label application will be accurate and shows no change in behavior.
Netskope will always list the labels, but cannot apply labels due to custom protection.
Users will be able to view the document, but not edit. The label applies the rights to the document, not the label itself.
Netskope will always list the labels, but cannot apply labels due to custom protection.
Users will be able to view the document, but not edit. The label applies the rights to the document, not the label itself.
Revising the MPIP Label based on the Content
Files that are already labeled by MIP can be scanned by the API-enabled Protection policy for sensitive content. If the policy detects sensitive content in the files, then the policy replaces the file label with the appropriate label defined by MIP for the content type.