A lot of valid user input can still be sensitive and should not be stored in your Jira instance. Whether it’s the carelessly uploaded password to a production system in a bug report or a customer asking for support and sending along their credit card: Sensitive data can get into Jira a lot quicker than admins want it to or can prevent. Our App PII Protection for Jira can!
Before we started developing, we had been looking for a long time for an app that manages the control of sensitive data in Jira. Finally we had to build it ourselves. Thanks to Forge, we could finally do so in a secure manner! As stated before, we wanted to make sure that we touch sensitive data as little as possible. The new Technology of Atlassian made this possible. Whenever an issue or comment is created or updated, a Forge function is triggered. PII Protection for Jira then checks whether the change introduces sensitive data into the instance. In case it find’s anything, our app notes the time, date, type of finding as well as the issue in question and add it to the findings list.
Before we had Forge, an app like this simply wasn’t possible. Sure, you can subscribe to events with Connect and perform the same checks we do in an Atlassian Connect app. But that app would be external to your Jira instance, which basically means that, in order to find out whether some data is sensitive and should not even be in Jira, you would have to export it to a 3rd party first. Forge lets us avoid this problem by keeping everything running within Altassian systems.
As an admin (or SecOps or Privacy Advocate or Compliance Manager), you simply cannot read every comment, every incoming Service Request. But our app can! Get it now in the Marketplace – it is free for small teams up to ten users.Install PII Protection for Jira
Looking for a way to protect PII and other sensitive data in Confluence? We got you covered here, too - with PII Protection for Confluence.Check out PII Protection for Confluence