A protection solution is a method of enforcing the data protection rules either in governed catalogs or by a deep enforcement solution.
A deep enforcement solution enforces rules on data that is outside of the platform when the data source is integrated with one of these services:
To configure the platform with a deep enforcement solution, you can create a data source definition to set the data source type. The data source type determines which types of connections the data source definition can be associated with and your available protection solution options. For more information, see Creating a data source definition.
Table: Protection solution options for a configured data source type
| Governed catalogs | IBM Data Virtualization | IBM watsonx.data | |
|---|---|---|---|
| Apache Hive | Default | ||
| IBM Data Virtualization | Default | ||
| Db2 | Default | ||
| IBM watsonx.data | Default | ||
| Microsoft SQL Server | Default | ||
| MySQL | Default | ||
| Oracle | Default | ||
| PostgreSQL | Default | ||
| Teradata | Default |
Governed catalogs as a protection solution
Data protection rules are enforced in catalogs when all prevailing conditions for enforcement are met. Conditions for enforcement can include catalog settings, the identity of the user, the data format, and the tool that is reading the data. Every time a user attempts to access a data asset in a governed catalog, data protection rules are evaluated for enforcement.
Supported data source types
Governed catalogs are the default protection solution for when you configure to one of the following data source types as your data source definition:
- Apache Hive
- Db2
- Microsoft SQL Server
- MySQL
- Oracle
- PostgreSQL
- Teradata
Learn more about governed catalogs as your protection solution
IBM Data Virtualization as a protection solution
If you have data protection rules that deny access to data or mask data, you can enforce those rules across the platform for virtualized tables in catalogs, regardless of where the current asset is located. Whether the asset is located in a governed or ungoverned catalog, or in a project; given that one copy of the asset exists in a governed catalog within the platform.
Supported data source types
IBM Data Virtualization is the default protection solution for when you configure the data source type to IBM Data Virtualization as your data source definition.
Learn more about IBM Data Virtualization as a protection solution
IBM watsonx.data as a protection solution
If you have data protection rules that deny access to data or mask data, you can enforce those rules across the platform for tables in catalogs, regardless of where the current asset is located. Whether the asset is located in a governed or ungoverned catalog, or in a project; given that one copy of the asset exists in a governed catalog within the platform.
Supported data source types
IBM watsonx.data is the default protection solution for when you configure the data source type to IBM watsonx.data as your data source definition.
Learn more about integrating IBM watsonx.data as a protection solution
Learn more
Parent topic: Data protection with data source definitions