Create a data lineage for a processing activity

Establish a data lineage to visualize data consumption, sharing, and the associated risks for a processing activity. Each processing activity involves multiple information objects classified as personal information. These objects exchange data with various other entities, making it essential to establish a data lineage or hierarchy that tracks where personal data is shared. This understanding helps mitigate privacy-related risks.

Avant de commencer

The processing activity must be in Discover state or later. If the processing activity is in New state, move it to Discover before proceeding.

Role required: sn_privacy.business_user

Pourquoi et quand exécuter cette tâche

You add data lineage relationships from the Hierarchy tab using the Add button. The Add dialog is a two-step flow. In the first step you define the relationship, and in the second step you provide the relationship details.

Procédure

1. Navigate to Workspaces > Privacy Workspace > Processing activities > All processing activities.
2. Navigate to the Hierarchy tab.
3. Select Add.
4. Select the Primary node field.
   Primary node is the record for which you're creating the relationship. While this field is automatically set to the record that is selected, you can change the node.
5. In the Relationship Type field, select the relationship type that describes how this processing activity relates to the node you want to add.
   Select from the following options:

   1. Depends on: The primary node depends on the related node. Data flows from the related node to the primary node. The related node becomes the parent and the primary node becomes the child.
   2. Contains: The primary node contains the related node. The primary node becomes the parent and the related node becomes the child.
   3. Contained by: The primary node is contained by the related node. The related node becomes the parent and the primary node becomes the child.
   4. Sends data to: The primary node sends data to the related node. The primary node becomes the parent and the related node becomes the child.
   5. Used by: The primary node is used by the related node. The primary node becomes the parent and the related node becomes the child.
   6. Receives data from: The primary node receives data from the related node. The related node becomes the parent and the primary node becomes the child.
6. In the Related Node Type field, select the type of entity you want to add.
   The available types are Processing Activity, Entity, Business Application, Business Process, Business Service, Company, and Vendor.
7. Select from the available related nodes list and select Next.
   You can add more than one related node.
8. For each related node, set the following options:
   1. Review the Key Relationship option that is enabled by default.
      Keep it selected if this node is important to the current processing activity. Clear it if the relationship does not need to be marked as key.
   2. Description — Enter a description of the relationship for this node.
   3. If you have added multiple nodes and want to apply the description of one node to all other nodes, click Copy Details on that node.
      This copies the description to all other related nodes in the list. If any other node already has a description, it will be overwritten.
   4. To remove a node before saving, click the remove icon next to that node.
9. Select Add.

Résultats

The new node appears in the Hierarchy tab list. When you select the View lineage map, the node appears in the graphical view. If the related node is itself a processing activity with existing relationships, those connections also appear in the map.

• Edit a data lineage relationship
  Edit an existing data lineage relationship to update the relationship type, description, or key relationship status of a connected node.
• Delete a data lineage relationship
  Edit an existing data lineage relationship to update the relationship type, description, or key relationship status of a connected node.