Learn about security solutions and standards
Care about security? We do too. Learn what Atlassian does and what you can do too.
The BYOK encryption feature is available through an early access program (EAP) to a number of customers with Enterprise plans for Jira Software. For any issues, contact support.
Cloud Enterprise and Cloud Enterprise trial plans.
Jira Software and Jira Service Management (JSM).
Issue Summary, Description and fields content (including system and custom fields)
Comments
Attachments (except for attachments metadata)
Search data
Learn more about what data can be managed with BYOK encryption
There is minimal overhead resulting in an unnoticeable impact.
No, BYOK encryption can be enabled only on new product instances.
You can only enable BYOK at the product instance level, not on the Cloud site level. This means that if you create a BYOK-enabled Jira Software instance, and you add a Confluence product instance to the same site during the EAP, then that Confluence product instance will not be BYOK-enabled.
It’s different with the JIra software family, the BYOK setting must be consistent for all Jiras products on a site, because all Jira products are linked. For example, If JSM is BYOK-enabled, then JSW must be also BYOK-enabled on the same site.
You can have only one BYOK encryption policy (combination of AWS account ID and data residency location) per organization.
During the BYOK EAP, BYOK encryption can only be enabled by Atlassian support teams. Learn how to set up BYOK encryption
The encryption keys are provisioned and managed in AWS Key Management Service (KMS).
Re-encryption is not available during EAP.
AWS KMS auto-rotation can only be set with once-a-year key rotation. Note that this creates new keys that are used going forward; the old keys still exist.
Revocation granularity is for all data associated with a your BYOK encryption configuration. Revocation disables access to all BYOK-enabled product instances.
Atlassian systems stop having access to your data within 24 hours. This is the expected time, but we don’t guarantee this.
The key restoration process is detailed in Restore your BYOK encryption keys.
You can log root key access in your KMS via AWS CloudTrail. For help with this, contact AWS support.
When you set up your BYOK encryption, you are asked to choose a data residency location. You won’t be able to change to a different location after a BYOK instance has been created.
No, new instances using BYOK are excluded from Atlassian’s SLA, per Section 3(e).
Was this helpful?