> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/risk-management/threat-model-coverage/sensitive-data-movement/jira-playbooks-for-sensitive-data-movement.md).

# Jira playbooks for sensitive data movement

To mitigate the risk associated with sensitive data movement in Jira, you can define automated workflows for these use cases: 

* [Notify on PII in Jira attachment](#notify-on-pii-in-jira-attachment)
* [Notify on PII in Jira comment](#notify-on-pii-in-jira-comment)
* [Notify on PII in new Jira issue](#notify-on-pii-in-new-jira-issue)
* [Notify on PII in updated Jira issue](#notify-on-pii-in-updated-jira-issue)
* [Remediate PII exposure in new Jira issue](#remediate-pii-exposure-in-new-jira-issue)

## Notify on PII in Jira attachment

When PII (personally identifiable information) is detected in a Jira attachment, the Security team is notified in Slack.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to sensitive data movement, and select the **Notify on PII in Jira attachment** playbook. 
3. Give an action name.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FNlf2pVlyKh2AQNjwBCCc%2FPB%20Jira%20attachment.png?alt=media&amp;token=db93d1c2-4cc2-4710-ae18-53fac3765932" alt=""><figcaption></figcaption></figure>
4. Under the **Issue updated** event, make sure that the:
   * `Get sub-issue entity` macro has at least one attachment.
   * Add any relevant conditions.
5. Customize the **PII scan** step that scans a Jira attachment:
   * Make sure that the **attachment** entity is selected.
   * Specify which PII labels to scan for, such as `password`.
   * Customize the error handling step in case of an error.
6. Customize the **Conditional** step:
   * If the PII scan didn't detect the specified label, such as `password`, end the workflow with `success` status.
   * If the PII scan detected the specified label, customize the Slack message to **Notify** the Security team:\
     `An attachment was added to Jira issue <number> by <actor name>. There's a high probability that this attachment contains PII.`

## Notify on PII in Jira comment

When PII (personally identifiable information) is detected in a Jira comment, the Security team is notified in Slack.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to sensitive data movement, and select the **Notify on PII in Jira comment** playbook.&#x20;
3. Give an action name.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FOQ5d7B3LWbT4rnDSfHDq%2FPII%20Jira%20comment.png?alt=media&amp;token=1e64c9b9-2b69-4ed1-9606-96ff6b90908c" alt=""><figcaption></figcaption></figure>
4. Under the **Comment created** event:
   * Enter a value for the `Get project name` macro.
   * Add any relevant conditions.
5. Customize the **PII scan** step that scans a Jira comment:
   * Make sure that the **comment** entity is selected.
   * Specify which PII labels to scan for, such as `password`.
   * Customize the error handling step in case of an error.
6. Customize the **Conditional** step:
   * If the PII scan didn't detect the specified label, such as `password`, end the workflow with `success` status.
   * If the PII scan detected the specified label, customize the Slack message to **Notify** the Security team:\
     `A comment <comment number> was added to Jira issue <number> by <actor name>. There's a high probability that this comment contains PII.`

## Notify on PII in new Jira issue

When PII (personally identifiable information) is detected in a new Jira issue, the Security team is notified in Slack.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to sensitive data movement, and select the **Notify on PII in new Jira issue** playbook.&#x20;
3. Give an action name.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FeFyuCbhYstnb4DvIOoml%2FPB%20Jira%20new%20issue.png?alt=media&amp;token=bd40352f-7734-494f-a8ec-405007fb9e28" alt=""><figcaption></figcaption></figure>
4. Under the **Issue created** event:
   * Enter a value for the `Get project name` macro.
   * Add any relevant conditions.
5. Customize the **PII scan** step that scans a Jira issue:
   * Make sure that the **Summary and description** entity is selected.
   * Specify which PII labels to scan for, such as `password`.
   * Customize the error handling step in case of an error.
6. Customize the **Conditional** step:
   * If the PII scan didn't detect the specified label, such as `password`, end the workflow with `success` status.
   * If the PII scan detected the specified label, customize the Slack message to **Notify** the Security team:\
     `A new issue <number> was created by <actor name>. There's a high probability that this issue contains PII.`

## Notify on PII in updated Jira issue

When PII (personally identifiable information) is detected in an updated Jira issue, the Security team is notified in Slack.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to sensitive data movement, and select the **Notify on PII in updated Jira issue** playbook.&#x20;
3. Give an action name.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FAXCCmqCo47XlQetjVla9%2FPB%20Jira%20updared%20issue.png?alt=media&amp;token=0f6c89e0-ab6d-4cdf-94de-b76cab69dbdf" alt=""><figcaption></figcaption></figure>
4. Under the **Issue updated** event:
   * Make sure the `Get sub-entity issue type` equals `summary` OR
   * Make sure the `Get sub-entity issue type` equals `description`&#x20;
   * Add any relevant conditions.
5. Customize the **PII scan** step that scans a Jira comment:
   * Make sure that the **Summary and description** entity is selected.
   * Specify which PII labels to scan for, such as `password`.
   * Customize the error handling step in case of an error.
6. Customize the **Conditional** step:
   * If the PII scan didn't detect the specified label, such as `password`, end the workflow with `success` status.
   * If the PII scan detected the specified label, customize the Slack message to **Notify** the Security team:\
     `An issue <number> was updated by <actor name>. There's a high probability that this issue contains PII.`

## Remediate PII exposure in new Jira issue

When PII (personally identifiable information) is detected in a new Jira issue, the Security team is notified in Slack.

1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to sensitive data movement, and select the **Remediate PII exposure in new Jira issue** playbook.&#x20;
3. Give an action name.<br>

   <figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FhaZr1FF98mSOnfV4ikJF%2FRemediate%20PII%20exposure%20in%20Jira%20issue.png?alt=media&amp;token=a9a14970-8f46-4488-82a7-d3fef81f9355" alt=""><figcaption></figcaption></figure>
4. Under the **Issue created** event:
   * Enter a value for the `Get project name` macro.
   * Define the `Get issue type name` macro as being in the **default file format for data scanning** lexical list.
   * Add any relevant conditions.
5. Customize the **PII scan** step that scans a Jira issue:
   * Make sure that the **Summary and description** entity is selected.
   * Specify which PII labels to scan for, such as `password`.
   * Customize the error handling step in case of an error.
6. Customize the **Conditional** step:
   * If the PII scan didn't detect the specified label, such as `password`, end the workflow with the`success` status.
   * If the PII scan detected the specified label:
     * Customize the **Notify in Slack** message to send to the Security team:\
       `A new issue <number> was created by <actor name>. There's a high probability that this issue contains PII.`
     * Customize the **Delete** issue step to delete the entire Jira issue, or only selected comments and attachments.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docontrol.io/docontrol-user-guide/risk-management/threat-model-coverage/sensitive-data-movement/jira-playbooks-for-sensitive-data-movement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.