System
A System is a model for describing anything that processes data for your organization (applications, services, 3rd party APIs, etc.) and describes how these datasets are used for business functions of instances of your data resources. It contains all 3 privacy attributes (data_category
, data_use
, and data_subject
).
1 2 3 |
|
Object Structure
fides_key constrained string
A string token of your own invention that uniquely identifies this System. It's your responsibility to ensure that the value is unique across all of your System objects. The value may only contain alphanumeric characters, underscores, and hyphens. ([A-Za-z0-9_.-]
).
name string
A UI-friendly label for the System.
description string
A human-readable description of the System.
system_type string
A required value to describe the type of system being modeled, examples include: Service, Application, Third Party, etc.
administrating_department string
An optional value to identify the owning department or group of the system within your organization
egress [array]
The resources to which the System sends data.
ingress [array]
The resources from which the System receives data.
privacy_declarations [array]
The array of declarations describing the types of data in your system. This is a list of the privcy attributes (data_category
, data_use
, and data_subject
) for each of your systems.
If a dataset is referenced as part of the system, all applicable data categories set on the dataset are treated as part of the system.
organization_fides_key string default: default_organization
The fides key of the Organization to which this System belongs.
Examples
Manifest File
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 |
|
Demo manifest file: /fides/demo_resources/demo_system.yml
API
POST /api/v1/system | |
---|---|
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 33 34 35 36 |
|