Policy Workflow

Summary

This section outlines a workflow for creating a policy. This workflow is used in examples and scripts that are provided in related sections of the documentation.

Here are the general steps of the Policy Workflow:

1. Initialize Policy Management
2. Prepare Data Element
3. Create Member Source
4. Create Role
5. Assign Member Source to Role
6. Create Policy Shell
7. Define Rule with Data Element and Role
8. Create Datastore
9. Deploy Policy to a Datastore
10. Confirm Deployment

Each step of the workflow has a sub-page that describes the workflow in detail, including a description, purpose, inputs, and outputs. Other sections of this documentation show examples of these steps for creating a policy, such as a policy to protect a credit card number.

Description

The workflow described in this section assumes that the reader is working in an environment where the core Protegrity platform components are already installed, accessible, and functioning correctly. The steps focus on policy creation and deployment, not on platform installation, infrastructure provisioning, or troubleshooting underlying system issues.

Assumptions

To execute any CLI or API command in this example, the following assumptions have been made:

• You are operating on a new AI Team Edition setup.
  • Set up the AI Team Edition by installing the Protegrity Provisioned Cluster. For more information about installing the PPC, refer to the section Installing PPC.
• You are connected to the Policy Manager container.
  • Connect to the Policy Manager container by deploying the Protegrity Policy Manager. For more information about deploying the Protegrity Policy Manager, refer to the section Installing Policy Workbench.

CLI Examples

To execute any CLI command in this example, the following additional assumption has been made:

• You have access to the PPC CLI.
  • For more information about accessing the PPC CLI, refer to the section Accessing the PPC CLI.
  • For more information about Policy Management CLI, refer to the section Policy Management Command Line Interface (CLI) Reference.

API Examples

To execute any API command in this example, the following additional assumption has been made:

• You have access to the Protegrity Policy Management REST APIs.
  • For more information about accessing the Policy Management REST APIs, refer to the section Using the Policy Management REST APIs.

Purpose

To clearly establish the scope of the workflow and avoid ambiguity about what the documentation covers versus what is expected to be completed beforehand. By defining these assumptions up front, the workflow can focus on explaining policy behavior and intent, rather than environmental setup.

Outcome

With these assumptions satisfied, the reader can proceed through the workflow steps with the expectation that each command or configuration action will succeed without requiring additional environment preparation.

Tips

• If any assumption is not met, resolve it before continuing with the workflow to avoid misleading errors later.
• For environment setup, installation, or operational guidance, refer to the dedicated platform installation and operations documentation rather than this workflow.