This workflow template provides a systematic approach to identify and tag content within Confluence that contains Personally Identifiable Information (PII) as detected by BigID. The process initiates with a trigger from BigID concerning PII findings, automatically labels the implicated content in Confluence, and subsequently opens an issue in Jira. Additionally, it ensures key stakeholders are promptly notified via a Slack message with the details of the findings. This workflow is essential for Application Security Operations to promptly remediate PII exposure risks.
Trigger
BigID
Use Cases
Application Security Operations
Workflow Breakdown
Receive a trigger from BigID on PII findings in Confluence
Gather event findings from BigID
For each event, update the content in Confluence with a specific label
Open a Jira issue and send a Slack message containing the results of the findings
Vendors
Slack, Utils, Jira Cloud, BigID, Confluence
Workflow Output
Jira issue and Slack messages containing findings from BigID. Label directly in Confluence any content that contains PII