Applies to: Microsoft Cloud App Security
Threat protection product names from Microsoft are changing. Read more about this and other updates here. We'll be updating names in products and in the docs in the near future.
If you enable content inspection, you can choose to use preset expressions or to search for other customized expressions.
You can specify a regular expression to exclude a file from the results. This option is highly useful if you have an inner classification keyword standard that you want to exclude from the policy.
You can decide set the minimum number of content violations that you want to match before the file is considered a violation. For example, you can choose 10 if you want to be alerted on files with at least 10 credit card numbers found within its content.
When content is matched against the selected expression, the violation text is replaced with "X" characters. By default, violations are masked and shown in their context displaying 100 characters before and after the violation. Numbers in the context of the expression are replaced with "#" characters and are never stored within Cloud App Security. You can select the option to Unmask the last four characters of a violation to unmask the last four characters of the violation itself. It's necessary to set which data types the regular expression searches: content, metadata and/or file name. By default it searches the content and the metadata.
Content inspection for protected files
Cloud App Security allows admins to grant Cloud App Security permission to decrypt encrypted files and scan their content for violations.
In order to give Cloud App Security the necessary permissions:
- Go to Settings and then Azure Information Protection.
- Enable Inspect protected files.
- Follow the prompt to allow the required permissions in Azure Active Directory.
- You can configure the settings per file policy to determine which policies will scan protected files.
If you run into any problems, we're here to help. To get assistance or support for your product issue, please open a support ticket.