Learn about security solutions and standards
Care about security? We do too. Learn what Atlassian does and what you can do too.
BYOK encryption for Jira Software is available to all customers with Enterprise plans.
BYOK encryption for Confluence is available through an early access program (EAP) to a number of customers with Enterprise plans. If you're interested in participating in the EAP reach out to your Enterprise account representative.
Cloud Enterprise and Cloud Enterprise trial plans.
Jira Software for all customers with Enterprise plans
Confluence for customers who’re participating in the Confluence early access program (EAP).
Jira Software:
Issue Summary, Description and fields content (including system and custom fields)
Comments
Attachments (except for attachments metadata)
Search data
Confluence (only for EAP customers):
Page content
Blog content
Comments
Attachments
Confluence questions
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 add product to your site after you enabled BYOK for another product, but the new product will not be BYOK-enabled.
If you want to add a BYOK product to your site after you've enabled BYOK for another product, you need to reach out to your Atlassian Enterprise account representative to add the product to your site. If you add the product directly, it will not be BYOK enabled. Learn how to set up BYOK encryption
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 configuration (combination of AWS account ID and data residency location) per organization.
BYOK encryption can only be provisioned by Atlassian support.
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.
You’ll need to update a policy in AWS, and then contact us. Learn how to restore access to your 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.
New BYOK-enabled Jira products are subject to Atlassian’s SLA.
Since Confluence is in EAP, new BYOK-enabled Confluence products are excluded from Atlassian’s SLA, per Section 3(x) and trial clause.
Issues caused by third party e.g. AWS are excluded from Atlassian’s SLA, per Section 3(e).
Was this helpful?