Data managed with encryption
App data types in-scope and not in-scope
Once you set up your Customer-managed keys (CMK) or Bring your own key (BYOK) encryption, certain Atlassian cloud apps will encrypt in-scope data types with keys hosted in your external AWS account. Data that is not in-scope is encrypted with Atlassian managed keys.
Apps not yet listed as supported remain accessible (with the exception of Rovo) to BYOK and CMK customers, who are expected to conduct risk assessments based on their business context before enabling them.
The list of supported apps is continuously expanding, and this page is regularly updated.
The following table lists the app data types based on:
â Data that is in-scope
Data not in-scope (lower sensitivity or transient)
Jira FamilyWe currently support encryption for Jira and Jira Service Management. However, as the Jira family of apps share the same database, some of the data encrypted for Jira and Jira Service Management extends to Jira Product Discovery on the same site. Otherwise, we don't support encryption for Jira Product Discovery. |
|---|
â All attachments |
â Asset data (Jira Service Management) |
â Board and sprint data |
â Comments |
â In-app notification data |
â Jira work item and field content (including system and custom fields) |
â Jira search data |
â Link related work |
â Overview name |
â Permissions and restriction configuration data |
â Rovo Search* |
Data not in-scope (lower sensitivity or transient):
|
*No additional data that is in-scope for CMK is created by Rovo Search. In-scope Jira and Confluence data ingested by Rovo Search remains supported by CMK.
Jira Service Management Operations |
â
Alerts, escalations, and teams: |
â
Chat: |
â
Incident: |
â
Integrations: |
â JEC (Jira Edge Connector) channel name |
â Rovo Search* |
â
Schedule: |
â
User and team roles: |
Data not in-scope (lower sensitivity or transient):
|
*No additional data that is in-scope for CMK is created by Rovo Search. In-scope Jira and Confluence data ingested by Rovo Search remains supported by CMK.
Confluence |
â AI summaries |
â Attachments |
â Blog content |
â Comments |
â Confluence questions |
â Databases |
â In-app notification data |
â Page content |
â Permission and restriction configuration data |
â Rovo Search* |
â Search data |
â Whiteboards |
Data not in-scope (lower sensitivity or transient):
|
*No additional data that is in-scope for CMK is created by Rovo Search. In-scope Jira and Confluence data ingested by Rovo Search remains supported by CMK.
Atlassian Analytics |
|---|
â Data from BYOK or CMK-enabled apps queried from the Atlassian Data Lake and data shares |
â Dashboards (including dashboard titles, settings except URL slugs, content elements, images, variables, subscription configurations, and activity logs) |
â Charts (including chart titles, settings, annotations, queries, and other Visual SQL steps) |
â Comments (for charts and dashboards) |
â Data source schemas |
Data not in-scope (lower sensitivity or transient):
|
Rovo |
Data not in-scope (lower sensitivity or transient): Rovo is not initially available for BYOK/CMK customers until it supports the use of customers' encryption keys. However, if desired, BYOK/CMK customers can request activation of Rovo in its current form (encrypted with Atlassian-managed keys) through their account teams. |
Atlassian Administration |
Data not in-scope (lower sensitivity or transient):
|
All apps |
Data not in-scope (lower sensitivity or transient):
|
App data definitions
Was this helpful?
