0 / 0
Authoring policies
Authoring policies

Authoring policies

You create policies to describe how to govern data in catalogs. Policies are governance artifacts that you create within a category.

If you have the required permissions, you can create policies.

Required permissions
You must have one of these category collaborator roles in the primary category for the policy to create, edit, or delete it:

  • Admin
  • Owner
  • Editor
  • A custom role with the permission to create, edit, or delete policies.

The following description can give you deeper insights into:

Parent policy

Select the parent policy for this policy. The parent policy must have been published. Subpolicies can have only one parent policy.

Primary category

The primary category identifies the policy.

Secondary categories

Secondary categories can include policies, but do not control them. A policy can be referenced by one or more secondary categories other than its primary category. See Adding secondary categories.

Details

You can edit custom attributes on the policy that provide additional information.
Custom attributes can be created using the Watson Knowledge Catalog API. If any custom relationship types are defined, they are also shown here. Inverse relationships show up in the other artifact after you publish the artifact where you created the relationship.

Subpolicies

You can assign subpolicies to the policy. The subpolicies that you select must be published. Each policy can contain multiple subpolicies and each policy can reference one or more rules. If a policy has subpolicies, it is the parent policy of those subpolicies. Subpolicies can have only one parent policy.

Policies and rules describe the characteristics for making information resources compliant with corporate objectives. You can organize policies in a hierarchy based on their meaning and relationships to one another.

For example, a policy named High Quality Data states that data must meet a high quality standard. A subpolicy of High Quality Data called High Quality Customer Data states that customer data must meet a high quality standard. The High Quality Customer Data policy references a governance rule called Postal Codes Verification. This rule states that customer addresses must use valid postal codes, as provided by the post office.

Another example: The policy Software Security states that security procedures must be in place concerning software. A second policy, named Firewalls states that a firewall must be implemented. A third policy named Credentials states that passwords are required for all computers hosting databases. The author of the policy Software Security specifies that Firewalls and Credentials are subpolicies of Software Security. Software Security is therefore the parent policy of the information governance policies Firewalls and Credentials.

You can add relationships between a policy and other types of governance artifacts.

Required permissions
You must have one of these category collaborator roles in the primary categories for both artifacts to add a relationship between them:

  • Admin
  • Owner
  • Editor
  • A custom role with the permission to edit both artifact types.

You can assign governance rules to the policy. The governance rules that you select must be published.

You can assign data protection rules to the policy.

You can assign the following artifacts to a policy:

  • Classifications
    Select the classifications to which you want to relate the policy. A policy can relate to multiple classifications.

  • Business terms
    Select the business term to which you want to relate the policy. A policy can relate to multiple business terms.

Learn more

Parent topic: Policies

Generative AI search and answer
These answers are generated by a large language model in watsonx.ai based on content from the product documentation. Learn more