Confidential Fields with Data Residency for Jira

 

 


Overview

“Confidential Fields with Data Residency for Jira” lets you set up a special type of custom field called Confidential Field. The app has three main components:

The app provides security and protects your most sensitive data in Jira Cloud: the data within custom fields.

 

Use cases

We built this app to resolve typical problems/requirements that companies face when using Jira Cloud:

Company problem: I have to control which system has access to specific data.
Solution: Store the encrypted data in the Jira database → see Hosting options

Company problem: I have regulatory requirements.
Solution: Follow regulations by storing data in a secure database located in a specific region → see Hosting options.

Company problem: Data sovereignty is key for my company.
Solution: Store encrypted data in your own database (coming soon).

Company problem: I want to restrict who can view or edit sensitive data.
Solution: Set specific permission setting for any custom field → see How to set Confidential Field permissions.

 

App Components

Data Hosting

Atlassian Cloud customers can already choose their data residency. However, the options are limited to a few countries. This is an issue for (potential) cloud customers in the EU and Switzerland, no name but a few. “Confidential Fields” gives you more options. Read more …

Data Encryption

Once active, the app will encrypt the data of newly created Confidential Fields. The private key is stored at Atlassian, and for each value, an additional random initialization vector is saved in the database. No unencrypted data is ever stored in the Atlassian Cloud or on bitvoodoo’s Infrastructure. Read more …

Access permission

Define who can view and edit data in custom fields. Read more …

 

Security in Confidential Fields with Data Residency for Jira