Applies to: Microsoft Cloud App Security
This article describes the process Microsoft Cloud App Security follows when performing DLP content inspection on data in your cloud.
Cloud App Security content inspection works as follows:
- First, Cloud App Security performs Near Real-Time (NRT) scan of drives and events that are detected to be new or changed.
- After this is complete, Cloud App Security performs a continuous scan of all relevant files in all drives.
Both the files in the NRT scan and the continuous scan are added to the queue for inspection. The order of the files in the scan queue is set per activity on files and on the scan of your drives. Files are scanned only if the file metadata shows that it's a supported MIME type. That this scan is for files that are relevant for data scan (documents, images, presentations, spreadsheets, text and zip/archive files).
After a file is scanned, the following occurs:
Cloud App Security applies all your custom policies that relate to metadata and not to the content itself. For example, a policy that alerts you when files are more than 20 MB or a policy that alerts you when docx files are saved to OneDrive.
If there is a policy that requires content inspection, and the file qualifies for content inspection, the content is queued for inspection. The queue length depends on the size of the tenant and the number of files that require scan.
At this point, you can view the status of the content inspection by going to Investigate > Files and clicking on a file. In the file drawer that opens with the details of the file, the Content Inspection status will display either Completed, Pending, Not applicable (if the file type is not supported) or a failure message. For information about content scan failure messages, see Troubleshooting content inspection.
If you see a dash in the scan status, this means that the file is not queued to be scanned. See File policies for information on setting content inspection policies.
Built-in content inspection scan policies can search for the following:
- Email addresses
- Credit card numbers
- All credit card companies (Visa, MasterCard, American Express, Diners Club, Discover, JCB, Dankort, UnionPay)
- Delimiters- space, dot or dash
- This scan also includes the Luhn validation
- SWIFT codes
- International passport numbers
- Drivers' license numbers
- Bank ABA routing transit numbers
- Bank identifier codes
- HIPAA HICN Health insurance claim numbers
- HIPAA NPI National provider identifier numbers
- PHI Full name and birth dates
- California ID or drivers' license numbers
- Drivers' license numbers
- Home addresses
- Passport cards
- Social security numbers
The Cloud App Security content inspection engine:
- Supports all Unicode characters
- Covers over 1,000 file types
- Multiple languages are supported, especially files that use Unicode character sets. Make sure to define your policies to account for those languages, for example if you are looking for keywords, you must put in the keywords across the languages you intend to use.
- In text-based file types that use non-Unicode encoding, for example Chinese GB2312, comparing against Unicode Chinese keywords will not work as expected.
- For file types that rely on third-party libraries, matching strings and words may not always work as expected. This is most common in files (such as binary file types) in which content inspection relies on third-party libraries that return Java strings for language and character sets.