Remediating Data Policies with Integrations

Policy Managers can leverage connections in the Integrations module to activate select actions based on violations identified by your data policy conditions. The seeded Data Policies Violations Identified trigger can launch these integrations based on specific policy details and use available event data to perform deletions, file uploads and parsing, ticket creation, and remediation updates in subsequent actions.

System Use Cases

Data Deletion in SharePoint, OneDrive, and Box
Ticket Creation in JIRA, ServiceNow

Available Triggers

Event Trigger

When creating a new connection workflow in the Integrations module, add the new Data Catalog trigger, Data Policies Violations Identified. You will need to specify the AND/ALL conditions and operators for when the integration should be triggered. Add multiple conditions to enforce stricter criteria before this connection gets triggered.

This event trigger will deliver the below event data, depending on the list condition(s). This will help pass details for ticketing use cases like name, description, number of violations found, data source, data system, etc. in the payload.

JSON

{
  "eventType" : "",
  "eventTime" : "",
  "eventId" : "",
  "payload" : {
    "documentId" : "",
    "documentType" : "",
    "documentName" : "",
    "documentLength" : "",
    "dataSourceId" : "",
    "policyId" : "",
    "dataSourceSystem" : "",
    "file" : ""
  }
}

{
  "eventType" : "",
  "eventTime" : "",
  "eventId" : "",
  "payload" : {
    "documentId" : "",
    "documentType" : "",
    "documentName" : "",
    "documentLength" : "",
    "dataSourceId" : "",
    "policyId" : "",
    "dataSourceSystem" : "",
    "file" : ""
  }
}

Policy Condition Fields

The following fields are available in the payload of subsequent actions:

event.payload.documentId
event.payload.documentType
event.payload.documentName
even.payload.documentLength
event.payload.dataSourceId
event.payload.dataSourceSystem
event.payload.file

Available Actions

Parse File to List

This seeded action allows the integration to read a file and retrieve a specific list of items. Parsing allows each identified row to become an element in an array of JSON objects which can then be referenced in logic steps, such as Apply to Each, later in the flow.

Note:

For more information on this action, see Parsing Files with OneTrust Workflows.

Apply To Each

This seeded action allows the integration to consider output from previous steps and house actions within a single conditional logic sequence. Depending on the logic and subsequent outcome, additional integration actions can be configured to handle actions like file deletion, remediations, etc.

Important:

Integration workflows can only have one Apply to Each logic action per workflow. This is designed to avoid excessive processing time, as workflows processing for more than 25 minutes will fail. OneTrust recommends to send a second Apply To Each loop to process in a subflow workflow.

Note:

For more information on how to use this logic action, see Using Apply to Each Logic in Integration Workflows.

GET Metadata by ID

This seeded action will retrieve metadata details by using a reference attribute to automatically identify the chosen parameter. Use this action to gather information in order to delete files using IDs, retrieve parsed files, or create third-party tickets.

CODE

${(step.applyEach_0["Data Asset Id"])!}

${(step.applyEach_0["Data Asset Id"])!}

Data Source Name
Data Source ID
Export File Name
Policy ID
File ID

GET Policy Details by ID

This seeded action will retrieve policy details according to the data policy ID that is captured from previous trigger conditions. Use this action to provide the workflow important information via the payload.