Highlighted

Atlassian Cloud Tenant Isolation

bill Atlassian Team Feb 26, 2020

At Atlassian, we are well aware of the importance of the data that you, our customers, store in our products. We aim to give you insight on all our products, but we’d like to start with Confluence and the Jira product family, including Jira Software, Jira Service Desk, and Jira Core.

There are two primary goals of tenant isolation in a multi-tenant cloud environment:

  1. Prevent leakage of, or unauthorized access to, customer content across tenants; and

  2. Prevent the actions of one tenant from adversely affecting the service for another tenant.

Both Jira and Confluence started their life as products you would download and install in your own environment --- and we still offer on-premise versions --- and our first iterations of our cloud offerings for these products were built around those code bases. Our early cloud offerings built upon our on-premises software to run single-tenanted virtual containers on behalf of our customers, hosted in Atlassian-operated data centers. Since 2017, we have been running Jira and Confluence Cloud in a multi-tenanted environment. One of the benefits of this approach is that we changed the applications to a multi-tenanted application, and built a secure, multi-tenanted environment around them. 

Read more about our approach to tenant isolation and our Tenant Context Service.

1 comment

Goal 3: Prevent the leakage of, or unauthorized access to, customer metadata—arguably, part of Goal 1, but worth mentioning separately. Customers should have no visibility or knowledge of other, unrelated customers.

Comment

Log in or Sign up to comment
TAGS