The custom entity types are built-in entity types DryvIQ created that allow you to leverage specific file information when creating a policy. This means you don’t have to create entity types for they file properties you want to use in your scans. You can use one of the custom entity types and simply specific the value you want to use in your policy. Refer to Uploading Samples to learn how to upload individual files for analysis against any entity type.
Active User Status
The Active User Status custom entity type allows you to scan files to identify the status of the owner and/or creator as well as identifying if the files are shared with any active users. Download a list of the 9 supported statuses below.
⬇️ Download the Active User Status list
Content Category
The Content Category custom entity type allows you to scan content based on the category the file belongs determined by its extension. This makes it possible to set your policy to include or exclude specific file types when scanning. The list of 8 categories and the file extensions included in each is below. For example, using this entity type, you can choose to exclude files that fall into the “movies,” “temporary files,” and “Windows OS/DB file” to limit the content the policy scans. All files with extensions that fall into these categories will be skipped. The categories are listed below. Expand each category to view the included extensions.
Custom Metadata
Some platforms support adding custom metadata to files so you can classify or organize them based on your company’s needs. The Custom Metadata built-in entity type allows you to leverage any custom metadata as part of a policy. This allows you to include or exclude a file from the policy scan based on a custom metadata field.
For example, your company does business in multiple countries, including Poland. You may have a metadata field on files that identifies the country. You can leverage this entity type in a policy to identify files with the metadata location of Poland and then scan the files using other entity types for data relevant to Poland, such as Polish identity card numbers and Polish Social Security numbers.
This classification doesn’t support scanning Network File System (NFS).
File Details
The File Details custom entity type allows you to leverage the file attributes (dates, timestamps, etc.) as part of your policy. This means you can include or exclude files based on any of these attributes. Download a list of the 45 supported file attributes below.
⬇ Download the File Details list
File Permissions
This entity type identifies files that have the selected permission level (Read, Write, Read and Write, or Full) or sharing. The permission levels you want to identify are set when creating the policy. Permissions level scans require you to specify the user(s) or group(s) whose permissions you want to verify. The scan will identify external users or groups based on email addresses or an email wildcard for a specific domain. See Using the File Permissions Entity Type in a Policy and Configuring Data Sources: File Permissions for more information. Download a list of the 24 supported permission queries below.
⬇ Download the File Permissions list
File Status
The File Status entity type provides details about a file's status, such as if it's locked or encrypted. Download the 15 supported file statuses below.
⬇ Download the File Status list
Tags
The Tags custom entity type is a built-in entity type that allows you to leverage tags or keywords as part of the criteria used for your policies. For platforms that support tags or keywords (Box, SharePoint 2013 and later, Microsoft Office 365, and Procore), you can choose to include or exclude specific tags or keywords to target or filter out specific files from the policy scans. For example, if you add a tag of “legal approved” to all documents your legal team has reviewed and approved, you can add this tag to be included in a policy to search for and scan only these files. Similarly, if your company adds a tag “cancelled” to all contracts that don’t close, you can set a policy to scan only these files and set the policy to take the appropriate action against them.
This classification doesn’t support scanning Network File System (NFS).