Blog ·
Atlassian SOC 2 report: how to get it, and the controls you still run in Jira
The Atlassian SOC 2 report for Jira Cloud is available from Atlassian's Trust Portal. You open the SOC 2 page in Atlassian's Compliance Resource Center, follow the link to the portal, accept a non-disclosure agreement, and download the report for the product family you need. Jira sits in the "Cloud Products" report. That report tells your vendor reviewer how Atlassian runs its side. It says nothing about how your team runs yours, and if your company is working toward its own SOC 2, the controls you operate inside Jira are what your auditor will test. This guide covers both: getting Atlassian's report, and keeping your own recurring control work on time.
Statements about Atlassian's compliance programme are as of October 2026, read from Atlassian's own trust pages. This is a practical guide, not audit advice. Your auditor and your compliance lead decide what your controls are.
What a SOC 2 report is #
Atlassian's SOC 2 page describes the report like this:
System and Organization Controls (SOC) 2 reports are independent third-party examination reports that demonstrate how an organization achieves key compliance controls and objectives.
The criteria come from the AICPA's Trust Services Criteria, which cover security, availability, processing integrity, confidentiality and privacy. Atlassian's page says its audits are carried out by a certified public accountant firm, and that the auditor checks whether controls "are designed appropriately, were in operation on a specified date, and were operating effectively over a specified time period."
That last phrase is the difference between the two report types you will see named:
| Type 1 | Type 2 | |
|---|---|---|
| Question it answers | Are the controls designed well, on one date? | Did the controls work, across a period? |
| Evidence needed | Policies and a snapshot | Records that each control ran, every cycle |
| What a vendor reviewer usually wants | Accepted for a new product | Preferred for anything holding real data |
A Type 2 report is a record of repetition. The auditor samples the period and asks for proof that each recurring control happened when it was meant to. Keep that in mind for the second half of this guide.
How to download the Atlassian SOC 2 report #
As of October 2026 the steps are:
- Open Atlassian's Compliance Resource Center and choose SOC 2. The page says "Access all of our SOC reports on our Trust Portal".
- Accept the NDA. The download sits behind a click-through non-disclosure agreement. If you accept for your company, the page notes that you represent you have authority to bind it.
- Pick the report that covers your products. The download list on the SOC 2 page includes:
| Report on the page | Covers |
|---|---|
| Cloud Products SOC 2 | Atlassian's main cloud apps, which is where Jira is |
| Loom Product SOC 2 | Loom |
| Rovo, Atlassian Guard Premium, and Data Manager SOC 2 | Those three products |
| Atlassian Admin, Connect, Confluence Databases and Confluence Whiteboards SOC 2 | The admin layer and those Confluence features |
| SOC 2 Bridge Letter | The gap between the last audit period and today |
- Grab the bridge letter too. A SOC 2 report covers a period that ended before you read it. Vendor reviewers often ask for the bridge letter to cover the months since.
The same page links to a separate Type 1 report for Atlassian Focus, so check the product name on each download rather than assuming one report covers everything Atlassian sells.
What Atlassian's report does not cover #
This is where vendor reviews and internal audits both go wrong. Atlassian's report is about Atlassian's controls: its infrastructure, its staff access, its change process. Your SOC 2 is about yours. In a Jira site that means, among other things:
- Who has access to which project, and whether leavers lose it.
- How admin rights are granted and reviewed.
- Which Marketplace apps are installed and what data they can read. Each app vendor is a separate vendor review, with its own report or questionnaire.
- Whether your change and incident processes actually run in Jira the way your policies say.
A good vendor file therefore holds Atlassian's report, the bridge letter, and your own notes on the complementary controls you operate. SOC 2 reports normally list those under a heading such as complementary user entity controls; read that section of the downloaded report, because it is Atlassian's own list of what it expects you to do.
The recurring controls SOC 2 auditors test #
Most SOC 2 programmes include a set of controls that repeat on a calendar. The cadence is your company's decision, written into your policies, so treat this column as an example to adjust:
| Control | Example cadence | What the auditor asks for |
|---|---|---|
| User access review (Jira, Confluence, the apps behind them) | Quarterly | The review ticket, the list reviewed, the removals made |
| Admin and privileged access review | Quarterly | Same, for admin groups only |
| Vendor review (including Atlassian and each Marketplace app) | Yearly | The vendor's current report or questionnaire, and sign-off |
| Policy review and approval | Yearly | The approved version and who approved it |
| Risk assessment | Yearly | The updated register |
| Security awareness training follow-up | Yearly | Completion records and chases |
| Backup restore test | Yearly | The test ticket and its result |
| Incident response tabletop | Yearly | The exercise notes |
A control that relies on someone remembering is a control that will be missed in the sample. For a Type 2 period, one forgotten quarterly review can be an exception in the report. The fix is dull and reliable: each review creates its own ticket, assigned and dated, before it is due. Our Jira risk register and Jira backup guides cover two of those rows in depth.
Three ways to make the controls create tickets #
| By hand | Jira Automation scheduled rule | Recurring Work Items for Jira | |
|---|---|---|---|
| Effort | Every ticket, every cycle | One rule per control, written once | One rule per control, chosen from a form |
| Schedule | Whoever remembers | Fixed rate or cron expression | Daily, weekly, or monthly on a day or a weekday, every N months |
| Lives in | Somebody's calendar | The automation rules list | The compliance project itself |
| Evidence a run happened | The ticket, if it was made | The rule's audit log | Run history: created, skipped or failed, with the reason |
By hand #
Fine for a startup with a single owner and six dates a year. Clone last quarter's ticket, change the title, assign it. Our Jira task template guide makes the clone quick. The weak point is the owner's holiday, which tends to fall in the audit period.
Jira Automation #
A scheduled rule can create an issue at a fixed rate or on a cron expression, and covers most of the table above. Two cautions: "the first working day of each quarter" is awkward to say in cron (see Jira cron expression), and rule runs count toward your plan's automation usage, explained in Jira Automation pricing. Rules also live in a site-wide list that other admins can edit, which an auditor may ask about.
A scheduling app #
Recurring Work Items for Jira creates issues on a schedule, with rules scoped to one project. A compliance team's calendar lives inside the compliance project instead of the site-wide rules list, and a project administrator turns it on for that project alone. The app is itself a Marketplace app, so it belongs in your vendor review like any other.
Set up a SOC 2 control calendar in Jira #
Whichever tool you choose, the setup has the same shape. With Recurring Work Items it runs like this:
- Create a compliance project. It tracks that each control ran and links to where the evidence lives.
- Turn the app on for that project only.
- Create one rule per control. A quarterly access review is a monthly rule repeating every 3 months; a yearly policy review repeats every 12 months.
- Pick the day, such as "the 1st" or "the first Monday of the month".
- Set working days and holidays, then choose Move it to the next working day under If it falls on a non-working day, so a review never lands on a weekend: a new rule runs on the day it falls on, holiday or not.
- Title each cycle distinctly with tokens, for example
Access review {{now.year}}-{{now.month}}, so every sampled ticket is easy to find by period. - Fill in the template: the owner, a due date a set number of days after the run, a label such as
soc2-control, and a description naming the control ID from your policy and the steps to follow. - Add subtasks for multi-step reviews: export user list, compare to HR roster, remove stale access, record sign-off.
When the auditor samples the period, a JQL search on the label returns one ticket per cycle, each with its owner, its dates and its comments. The run history covers the rarer question of why a ticket is missing.
When the manual way is enough #
You may not need a scheduled calendar if:
- you only need Atlassian's report for a vendor review, and your company is not pursuing SOC 2 itself;
- you run a dedicated compliance platform that already assigns and evidences these controls;
- your control list is short and one person tracks it reliably.
For the first case, the download steps above are the whole job.
FAQ #
Where do I get the Atlassian SOC 2 report? From Atlassian's Trust Portal, linked from the SOC 2 page of its Compliance Resource Center. You accept an NDA, then download the report for your product. As of October 2026 Jira is in the Cloud Products report.
Is there a bridge letter? Yes. The SOC 2 page lists a SOC 2 Bridge Letter among its downloads.
Does Atlassian's SOC 2 cover Marketplace apps? Atlassian's reports name Atlassian products. Each Marketplace app is a separate vendor, so ask that vendor for its own security documentation.
Does Atlassian's SOC 2 make my company SOC 2 compliant? No. It covers Atlassian's controls. Your auditor tests the controls you run, including the recurring reviews above. For the same question under a different regime, see our Jira HIPAA compliance guide.