Cloud Data Loss Prevention (Cloud DLP) is now a part of Sensitive Data Protection. The API name remains the same: Cloud Data Loss Prevention API (DLP API). For information about the services that make up Sensitive Data Protection, see Sensitive Data Protection overview.
Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to add and edit infoTypes in your inspection
configuration through the Google Cloud console.
When you use Sensitive Data Protection to inspect or
profile data, you use an inspection configuration to
specify the information types (infoTypes)
that you want to scan for. The following Sensitive Data Protection operations in the
Google Cloud console let you set your inspection configuration:
These operations in the Google Cloud console have an InfoTypes section,
where you can select infoTypes, edit the settings of built-in
infoTypes, and add custom infoTypes. The step that contains the InfoTypes
section differs depending on the operation that you're performing. The
following table shows the relevant workflow step for each operation.
Operation
Relevant step
Creating an inspection template
Configure detection
Creating an inspection job or job trigger
Configure detection
Creating a discovery scan configuration
Select inspection template
Select built-in infoTypes
In the InfoTypes section, click Manage infoTypes.
To narrow the selection of infoTypes, apply filters in the Filter
field. Select a property name to filter on and
enter a property value. For example, to filter for all infoTypes related to
Australia, set the property name to Location. For the property value,
select or type Australia.
If you know the infoType name, you can also type it directly in the
Filter field.
To view all category tags for an infoType, click
expand_moreToggle full cell content for that infoType.
To hide or unhide columns, click view_column
Column display options, and select the names of the columns
that you want to display.
Select the infoTypes that you want to include in your inspection
configuration.
Click Done.
Edit the settings of a built-in infoType
As you set the infoTypes that you want to include in your inspection
configuration, you can additionally edit the settings of one or more of those
infoTypes. You can edit the sensitivity level and, for some infoTypes,
the infoType version.
Select the built-in infoTypes that you want to include
in your inspection configuration, including the infoTypes that you don't
need to edit. Don't click Done.
Click Edit selected infoTypes.
For each infoType that you want to edit, use the drop-down lists to select
a sensitivity level or a detector version.
Click Confirm.
Click Done.
Add custom infoTypes
This section describes how to add a custom infoType based on an
underlying set of data. The underlying data can be any of the following:
A list of words or phrases that you provide inline in the inspection
configuration.
A list of words or phrases that you store in a text file in Cloud Storage.
A large list of words or phrases that you store in a large text file in
Cloud Storage or a column in BigQuery.
For this type, you must first create a stored infoType
that points to the large custom dictionary, before performing this task.
A regular expression that you provide inline in the inspection
configuration.
Whether you can reuse the new custom infoType depends on which operation you
were performing when you created the custom infoType:
If you create a custom infoType while creating an inspection job or job
trigger, the custom infoType is available to only that job or job trigger.
If you create a custom infoType while creating an inspection template,
the custom infoType is available to any operation that uses the inspection
template.
If you create a custom infoType while configuring profiling,
Sensitive Data Protection creates a new inspection template from your inspection
configuration. The custom infoType is available to any operation that
uses that new inspection template.
To add a custom infoType detector, do the following:
In the InfoTypes section, click Manage infoTypes.
On the Custom tab, click Add custom infoType.
For Type, choose the type of custom infoType detector that you want to
create:
Words or phrases: Matches on one or more words or phrases that you
enter into the field. You can enter up to 128 KB of data, which equates to
thousands of entries.
When you select this type, the List of words or phrases field appears.
Enter the word or phrase that you want Sensitive Data Protection to match on. To
match on multiple words or phrases, press Enter after each entry. For
more information, see Creating a regular custom dictionary
detector.
Dictionary path: Matches on words or phrases that you store in a text
file in Cloud Storage. Use this custom infoType when you have hundreds
of thousands of words or phrases to search for. This approach is also
useful if your list contains sensitive terms and you don't want to store
them inline in the inspection configuration.
When you select this type, the Dictionary location field appears.
Enter or browse to the Cloud Storage path where the dictionary file is
stored. For more information, see
Creating a regular custom dictionary detector.
Regex: Matches content based on a regular expression.
When you select this type, the Regex field appears. Enter a regular
expression pattern to match words and phrases. For more information,
see the
supported regular expression syntax.
Stored infoType: Matches on words or phrases that you store in a large
text file in Cloud Storage or a single column in
BigQuery.
This option adds a large custom dictionary detector. Use this kind of
custom infoType if you have millions of words or phrases to search for.
For this type, you must have already created a stored infoType
that points to the underlying large custom dictionary.
When you select this type, the Stored infoType name field appears.
Enter the full resource name of the stored infoType.
For InfoType, enter a name for the custom infoType to be created.
If you're creating a custom infoType that is of type Stored infoType,
enter a name that is different from the name of the underlying stored
infoType.
For Likelihood, select the default likelihood level that you want to
assign to all findings that match this custom infoType. You can further
fine-tune the likelihood level of individual findings by using
hotword rules.
If you don't specify a default value, the default likelihood level is set
to VERY_LIKELY. For more information, see
Match likelihood.
For Sensitivity, select the sensitivity level that you want to assign to
all findings that match this custom infoType. If you don't specify a value,
the sensitivity levels of those findings are set to HIGH.
Sensitivity scores are used in data profiles. When
profiling your data, Sensitive Data Protection uses the sensitivity scores of the infoTypes to
calculate the sensitivity level.
Click Done.
Optional: To add another custom infoType, click Add custom infoType
again.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Manage infoTypes through the Google Cloud console\n\nThis page describes how to add and edit infoTypes in your inspection\nconfiguration through the Google Cloud console.\n\nWhen you use Sensitive Data Protection to [inspect](/sensitive-data-protection/docs/inspecting-storage) or\n[profile](/sensitive-data-protection/docs/data-profiles) data, you use an inspection configuration to\nspecify the information types ([*infoTypes*](/sensitive-data-protection/docs/concepts-infotypes))\nthat you want to scan for. The following Sensitive Data Protection operations in the\nGoogle Cloud console let you set your inspection configuration:\n\n- [Creating or editing an inspection template](/sensitive-data-protection/docs/creating-templates-inspect)\n- [Creating an inspection job or job trigger](/sensitive-data-protection/docs/creating-job-triggers)\n- [Creating a discovery scan configuration](/sensitive-data-protection/docs/profile-org-folder)\n\nThese operations in the Google Cloud console have an **InfoTypes** section,\nwhere you can select infoTypes, edit the settings of built-in\ninfoTypes, and add custom infoTypes. The step that contains the **InfoTypes**\nsection differs depending on the operation that you're performing. The\nfollowing table shows the relevant workflow step for each operation.\n\nSelect built-in infoTypes\n-------------------------\n\n1. In the **InfoTypes** section, click **Manage infoTypes**.\n2. To narrow the selection of infoTypes, apply filters in the **Filter**\n field. Select a property name to filter on and\n enter a property value. For example, to filter for all infoTypes related to\n Australia, set the property name to **Location** . For the property value,\n select or type **Australia**.\n\n If you know the infoType name, you can also type it directly in the\n **Filter** field.\n3. To view all category tags for an infoType, click expand_more **Toggle full cell content** for that infoType.\n\n4. To hide or unhide columns, click view_column **Column display options**, and select the names of the columns\n that you want to display.\n\n5. Select the infoTypes that you want to include in your inspection\n configuration.\n\n | **Tip:** If your scan results don't need to show the specific infoTypes that were detected, then consider selecting general infoTypes in your configuration. When you select a specific infoType covered by a general infoType, Sensitive Data Protection suggests the general infoType that you can use instead. To accept the recommended replacements, click **Apply\n | recommendations** . For information about the benefits of using general infoTypes, see [General and specific infoType\n | detectors](/sensitive-data-protection/docs/concepts-infotypes#general-specific-infotypes).\n6. Click **Done**.\n\nEdit the settings of a built-in infoType\n----------------------------------------\n\nAs you set the infoTypes that you want to include in your inspection\nconfiguration, you can additionally edit the settings of one or more of those\ninfoTypes. You can edit the sensitivity level and, for some infoTypes,\nthe infoType version.\n\n1. [Select the built-in infoTypes](#select-infotypes) that you want to include in your inspection configuration, including the infoTypes that you don't need to edit. Don't click **Done**.\n2. Click **Edit selected infoTypes**.\n\n [](/static/sensitive-data-protection/docs/images/edit-selected-infotypes_2x.png)\n3. For each infoType that you want to edit, use the drop-down lists to select\n a sensitivity level or a detector version.\n\n4. Click **Confirm**.\n\n5. Click **Done**.\n\nAdd custom infoTypes\n--------------------\n\nThis section describes how to add a custom infoType based on an\nunderlying set of data. The underlying data can be any of the following:\n\n- A list of words or phrases that you provide inline in the inspection configuration.\n- A list of words or phrases that you store in a text file in Cloud Storage.\n- A large list of words or phrases that you store in a large text file in\n Cloud Storage or a column in BigQuery.\n\n For this type, you must first [create a stored infoType](/sensitive-data-protection/docs/creating-stored-infotypes#create)\n that points to the large custom dictionary, before performing this task.\n- A regular expression that you provide inline in the inspection\n configuration.\n\nWhether you can reuse the new custom infoType depends on which operation you\nwere performing when you created the custom infoType:\n\n- If you create a custom infoType while creating an inspection job or job\n trigger, the custom infoType is available to only that job or job trigger.\n\n- If you create a custom infoType while creating an inspection template,\n the custom infoType is available to any operation that uses the inspection\n template.\n\n- If you create a custom infoType while configuring profiling,\n Sensitive Data Protection creates a new inspection template from your inspection\n configuration. The custom infoType is available to any operation that\n uses that new inspection template.\n\nFor more information about custom infoTypes, see [Custom infoType\ndetectors](/sensitive-data-protection/docs/creating-custom-infotypes).\n\nTo add a custom infoType detector, do the following:\n\n1. In the **InfoTypes** section, click **Manage infoTypes**.\n2. On the **Custom** tab, click **Add custom infoType**.\n3. For **Type**, choose the type of custom infoType detector that you want to\n create:\n\n - **Words or phrases:** Matches on one or more words or phrases that you\n enter into the field. You can enter up to 128 KB of data, which equates to\n thousands of entries.\n\n When you select this type, the **List of words or phrases** field appears.\n Enter the word or phrase that you want Sensitive Data Protection to match on. To\n match on multiple words or phrases, press `Enter` after each entry. For\n more information, see [Creating a regular custom dictionary\n detector](/sensitive-data-protection/docs/creating-custom-infotypes-dictionary).\n - **Dictionary path:** Matches on words or phrases that you store in a text\n file in Cloud Storage. Use this custom infoType when you have hundreds\n of thousands of words or phrases to search for. This approach is also\n useful if your list contains sensitive terms and you don't want to store\n them inline in the inspection configuration.\n\n When you select this type, the **Dictionary location** field appears.\n Enter or browse to the Cloud Storage path where the dictionary file is\n stored. For more information, see\n [Creating a regular custom dictionary detector](/sensitive-data-protection/docs/creating-custom-infotypes-dictionary).\n - **Regex:** Matches content based on a regular expression.\n\n When you select this type, the **Regex** field appears. Enter a regular\n expression pattern to match words and phrases. For more information,\n see the\n [supported regular expression syntax](https://github.com/google/re2/wiki/Syntax).\n - **Stored infoType:** Matches on words or phrases that you store in a large\n text file in Cloud Storage or a single column in\n BigQuery.\n\n This option adds a large custom dictionary detector. Use this kind of\n custom infoType if you have millions of words or phrases to search for.\n\n For this type, you must have already [created a stored infoType](/sensitive-data-protection/docs/creating-stored-infotypes#create)\n that points to the underlying large custom dictionary.\n\n When you select this type, the **Stored infoType name** field appears.\n Enter the full resource name of the stored infoType.\n4. For **InfoType**, enter a name for the custom infoType to be created.\n\n If you're creating a custom infoType that is of type **Stored infoType**,\n enter a name that is different from the name of the underlying stored\n infoType.\n5. For **Likelihood** , select the default likelihood level that you want to\n assign to all findings that match this custom infoType. You can further\n fine-tune the likelihood level of individual findings by using\n [hotword rules](/sensitive-data-protection/docs/creating-custom-infotypes-likelihood).\n If you don't specify a default value, the default likelihood level is set\n to `VERY_LIKELY`. For more information, see\n [Match likelihood](/sensitive-data-protection/docs/likelihood).\n\n6. For **Sensitivity** , select the sensitivity level that you want to assign to\n all findings that match this custom infoType. If you don't specify a value,\n the sensitivity levels of those findings are set to `HIGH`.\n\n\n Sensitivity scores are used in [data profiles](/sensitive-data-protection/docs/data-profiles). When\n profiling your data, Sensitive Data Protection uses the sensitivity scores of the infoTypes to\n [calculate the sensitivity level](/sensitive-data-protection/docs/sensitivity-risk-calculation).\n\n\n7. Click **Done**.\n\n8. Optional: To add another custom infoType, click **Add custom infoType**\n again.\n\n9. Click **Done**.\n\nWhat's next\n-----------\n\n- Refer to a list of [built-in infoType detectors](/sensitive-data-protection/docs/infotypes-reference).\n- Learn more about [custom infoType detectors](/sensitive-data-protection/docs/creating-custom-infotypes).\n- Learn how to [create a regular custom dictionary detector through the DLP API](/sensitive-data-protection/docs/creating-custom-infotypes-dictionary).\n- Learn how to [create a large custom dictionary detector through the DLP API](/sensitive-data-protection/docs/creating-stored-infotypes).\n- Learn how to [create a custom regular expression detector through the DLP API](/sensitive-data-protection/docs/creating-custom-infotypes-regex)."]]