Policy
A Policy is your privacy policy as code, it lists a set of acceptable and non-acceptable rules and uses all 3 privacy attributes (data_category
, data_use
, data_subject
). The purpose of the policy is to state what types of data are allowed for certain usages.
1 2 3 |
|
Object Structure
fides_key constrained string
A string token of your own invention that uniquely identifies this Policy. It's your responsibility to ensure that the value is unique across all of your Policy objects. The value may only contain alphanumeric characters, underscores, and hyphens. ([A-Za-z0-9_.-]
).
name string
A UI-friendly label for the Policy.
description string
A human-readable description of the Policy.
data_categories string
The Data Categories privacy attribute describes types of sensitive data as defined in the taxonomy.
data_uses string
The Data Use privacy attribute describes the various categories of data processing and operations at your organization.
data_subject string
The Data Subjects privacy attribute describes the individual persons whose data your rule pertains to.
matches enum
ANY
ALL
NONE
OTHER
The matches criteria describes how you would like this rule to be evaluated. These basic logic gates determine whether the array of privacy attributes will be fully included (ALL
), not included at all (NONE
), only included if at least 1 item in the array matches (ANY
), or excluded with any additional attributes included (OTHER
).
organization_fides_key string default: default_organization
The fides key of the Organization to which this Policy belongs.
Examples
Manifest File
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
|
Demo manifest file: /fides/demo_resources/demo_policy.yml
API Payload
POST /api/v1/policy | |
---|---|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 |
|