Skip to content

Glossary of Key Terms

Fidesops terms

  • Privacy Request: A Privacy Request is a fidesops representation of what is more widely known as a Data Subject Request, or Data Subject Access Request.

    • access request: The customer wants to see the data an organization has collected about them.
    • erasure request: The customer wants an organization to delete the data they have collected about them.
  • Policy: Different from a fidesctl Policy, this is a configuration that describes how to handle a Privacy Request. For example, you might define a simple policy that when given an email, it locates all the related data the customer has provided to you, and upload that to a specific S3 bucket.

  • ConnectionConfig: A configuration for how to connect a database to fidesops, so it can retrieve or remove customer data.

  • DatasetConfig: A resource that contains a fidesctl Dataset (the annotation of a database schema) and its related ConnectionConfig

  • StorageConfig: A configuration for where the customer's data is going to be sent after an access request.

  • MaskingStrategy: A configuration for how to erase customer data - for example, you might replace a customer's email with a random string.

  • Identity: A piece of information used to uniquely identify an individual, like an email or a phone number.

  • Identity Graph: A mapping that knows where personal data lives and how to look it up. For example, you might have photos stored in a MySQL database and customer information stored in a PostgreSQL database. The identity graph might say to get the customer id from the PostgreSQL database, and use that to look up the customer's photo in the MySQL database.

  • Traversal: Created from an identity and an identity graph. In short, it says here's the first table I'm going to visit, I'm going to get this Field, cache it, and then use that to get this information from the next Collection, and so on.

  • PolicyPreWebhook: Webhooks configured on a Policy to be triggered before a PrivacyRequest is executed.

  • PolicyPostWebhook: Webhooks configured on a Policy to be triggered after a PrivacyRequest is executed.

  • Database terms:

    • Datasets - Resources at the database level. Datasets can have many Collections.
    • Collections - A table, or a Collection of related data. Collections can have many Fields.
    • Fields - Attributes on Collections.

Fidesctl terms

See the fidesctl repo for more information, but here's some fidesctl terms that might be helpful in fidesops.

  • Manifest: YAML files that describe different types of objects within Fides, with a high-level "privacy as code" language.

  • Policy: Different from a fidesops Policy, this controls what kinds of data you are permitted to commit to source code. For example, you might create a fidesctl policy that says, I am not going to allow any System that takes in provided contact information and uses it for marketing purposes.

  • Dataset: An annotation of a database schema, which describes the Collections in a database, the Fields, the Data Categories of those fields, and the relationships between relevant Collections.

  • System: Systems represent the applications, services, integrations, and any software that processes data for a specific use case.

  • Privacy Data Types:

    • Data Category - What kind of data is it? For example, the Data Category user includes things like contact email and street address.
    • Data Use - Why is it being used? For example, for advertising or to improve the system.
    • Data Subject - Whose data is it? For example, a customer.
    • Data Qualifier - How is the data being protected? For example, it might be aggregated.
Back to top