How to Set Up the miniOrange Data – PII Scanner (DLP) for Jira
The Data - PII Scanner (DLP) for Jira is a tool designed to detect sensitive Personally Identifiable Information (PII) within Jira environments and prevent exposure. You can redact, encrypt/decrypt, and remove sensitive data to mitigate risks before they escalate.
As data security/privacy becomes increasingly critical, the PII Scanner for Jira helps you secure sensitive information and ensure compliance with data privacy protocols.
Installation
- Get started with DLP & PII Protection for Jira by installing it from the Atlassian Marketplace.
- Click “Try it free” to begin a new trial and install the app to your Jira instance.
- Now, log in to your Jira Admin Console.
- Locate the “DLP & PII Protection for Jira” app in your Jira menu and open it.
Key Configuration Concepts
- Detection Rule: A Detection Rule tells the system what to look for when scanning for sensitive data. For example, a rule could be a regular expression that matches a Social Security Number.
- Policy: A Policy groups detection rules. Scans are run based on policies. For example, an “HR Policy” that bundles all your HR-related templates. You can turn policies on and off; only active policies are enforced during a scan.
1. Create a Detection Rule
To create a Detection Rule:
- Navigate to Detection Engine > Detection Rules.
- The Detection Rules page displays the default Detection Rules available with the app. You can use the In-built and Custom filters to view each type of rule separately.
- Click New Rule to create a custom Detection Rule.
- For this guide, we will create a Detection Rule to identify IPV4 addresses.
- Enter a name for the Detection Rule.
- Enter a Description that explains what the rule detects. For example: Flags IPV4 addresses shared in Jira issues and comments.
- Enter the required Regex Pattern and press Enter to add it. You can add more than one pattern to the same rule. For example: \b(?:[0-9]{1,3}.){3}[0-9]{1,3}\b
- Use the Require keyword toggle to decide when a match should be flagged. When the toggle is off, every regex match is flagged. When it is on, the rule flags only the matches that appear near a keyword. For this guide, keep the toggle off.
- Use the Test Regex option to verify the pattern.
- Enter sample data and click Test to check whether the regex correctly identifies the required data. The sample text is not saved with the rule.
- Once the regex is verified, click Create.
Once created, the IPV4 address Detection Rule will be available in the Detection Rules list and can be added to a Policy.
2. Create a Policy
To create a Policy:
- Navigate to Detection Engine > Policies.
- The Policies page displays the default Policy. When you create custom policies, you can search for them, filter by status, or use the In-built and Custom filters to view each type separately.
- Click New Policy.
- Enter a name for the Policy. For this guide, we will use the DevOps Policy.
- Enter a Description that explains what the Policy is for. For example: Detects infrastructure details such as IP addresses shared in Jira issues.
- Under Detection Rules, select the rules you want to include in the Policy. You can use the search bar to find a rule quickly, and the counter shows how many rules you have selected.
- For this guide, we will select the IPV4 Address Detection Rule created in the previous step.
- Click Create.
3. Run a Scan
Once the Policy is configured, you can use it to scan your Jira instance for sensitive data.
To run a scan:
- Navigate to Scan & Redact > Issues.
- Select the Policy configured in the previous step and the spaces you want to scan.
- Start the scan to analyze your Jira instance based on the selected Policy.
That’s it! You have successfully completed your first scan and can now review your scan results from the Scan Results section of the same tab.
4. Review Results
After the scan is completed, review the scan results to identify the data detected based on the selected Policy.
Additional Resources
Did this page help you?
Try it for free