Custom Policy Type

Use Custom policies when you need a non-standard policy classification for specialized workflows, integrations, or custom evaluators.


Step-by-step: Create a Custom policy (via Advanced JSON)

1
2

Click Create Policy

This will spawn the Create Policy modal form.

3

Define Policy Attributes

Choose a aptly discriptive name for your new policy.

Choose any existing policy type available in the UI for your new policy(this is just a starting template since Update Settings is set in JSON).

Choose a status for your new policy. We recommend monitor mode when initially setting up a policy.

Add one or more Controls by clicking on the "Add Control" button and then selecting the controls that you would like to see applied to your new policy.

Choose a User Group, a Machine Collection, and an Application Collection.

4

Configure Policy Targeting

Configure any targeting you want in the UI (collections/users/machines/apps/platforms). Who or What does your policy apply to?

5

Open the Policy’s Advanced Mode (JSON view)

To open the Policy's Advanced Mode, click on the "Advanced Mode" link in the bottom left corner of the Policy Form.

6

Redefine Policy Type in JSON

Set: PolicyType to "Custom"

7

Add Your Custom Fields

Add any custom fields your internal integration/evaluator expects (this is implementation-specific).

8

Save the Policy

Important Note

“Custom” is intentionally schema-less at the documentation level unless you publish:

  • the required JSON schema/keys,

  • what component consumes it,

  • and how customers verify enforcement.


Example JSON Snippets

Example 1: Custom policy (baseline allow)

Use this when you want a Custom policy that simply “matches” based on the same built-in checks, but does not require MFA/Justification/Approval.


Example 2: Custom policy that requires MFA + Justification + Approval

This mirrors Actions.OnSuccess.Controls, but with multiple controls.


Example 3: Custom policy with a custom payload (for a plugin/integration)

This uses the same shape as our templated policies, but puts a structured payload into Extension. Your (plugin/integration) can read this.

Last updated

Was this helpful?