Add a File Property Data Pattern

Use custom or extended file properties in Office and PDF documents as match criteria in asset policy rules on SaaS Security API.
For data governance and protection of information, if you use classification labels or embed tags in MS Office and PDF documents to include more information for audit and tracking purposes, you can create a file property data pattern to match on the metadata or attributes that are a part of the custom or extended properties in the file. Regardless of whether you use an automated classification mechanism such as Titus or require users to add a tag, you can specify a name-value pair to match on a custom or extended property embedded in the file.
For example, you can define a file property data pattern to create an incident when a user on your network uploads a file labeled as Customer Data to a folder that has external collaborators.
  1. Select
    Data Patterns
    Add New
    Add New File Property
    SaaS Security API supports file property data patterns in MS Office and PDF documents. Both the OLE (.doc/.ppt) or XML (.docx/.pptx) formats of MS Office are supported.
  2. Enter a
    and a
    Short Label
    for the file property data pattern.
  3. Select the
    Extended Properties
    that you want to include as match conditions.
    Enter the name-value pair for the property that you want to look for. You can add as many file properties as you’d like. When you later reference the file property data pattern in an asset rule in Step 6 below, a boolean OR match is used in the match criteria.
  4. Select the predefined category with which you want to associate this file property.
  5. Save
    the file property data pattern.
  6. Add a New Asset Rule and add your new file property data pattern as match criteria.
    In the match criteria, you can decide whether you want to look for any property, or more than or fewer than a specified number of properties that you’ve included in the file property data pattern.

Recommended For You