Blog ·

Jira SOX compliance: the SOC 1 report, and the controls you still run

Jira SOX compliance comes in two parts. Atlassian's part is a SOC 1 report, which your external auditors can use to judge the controls Atlassian runs on Jira Cloud. Your part is the controls you run yourself: who has access, how changes are approved, and the evidence that each periodic review actually happened. Jira can hold that evidence well, as long as the reviews are raised as tickets on a schedule rather than remembered. This guide covers what the SOC 1 report is for, which controls stay with you, and how to set up a review calendar that creates its own tickets.

Statements about Atlassian's compliance programme are as of October 2026, read from Atlassian's own Trust Center. This is a practical guide, not audit or legal advice. Your controller, internal audit team and external auditor decide which controls are in scope.

What SOX asks of the tools you use #

The Sarbanes-Oxley Act applies to companies whose shares trade publicly in the United States. Section 404 is the part that reaches IT: management must assess its internal control over financial reporting (ICFR) every year, and for larger filers the external auditor attests to that assessment.

Jira is rarely a financial system itself. It comes into SOX scope in two ways:

In both cases, the auditor wants the same thing: proof that a control operated, every time it was supposed to, through the whole year.

Is Jira SOX compliant? #

No product is SOX compliant on its own, because SOX is an obligation on the company, not on its vendors. What a vendor can supply is assurance about its own controls. For Atlassian, that assurance is the SOC 1 report. Atlassian's SOC 1 page describes it this way:

SOC 1 is an examination of controls at a service organization that are likely to be relevant to user entities' internal control over financial reporting.

The same page says the report is meant for the companies using the service and "the CPAs that audit the user entities' financial statements". It lists Jira, Confluence and Jira Service Management as the relevant products, and points to the Trust Portal, where Atlassian says you can access all of its SOC reports after accepting a non-disclosure agreement.

Get the SOC 1 report to your auditor early in the year. They will read its description of Atlassian's controls, and they will also read the section listing the controls Atlassian expects you, the customer, to run. Those are usually called complementary user entity controls, and they are where your work starts.

SOC 1 or SOC 2: which one the auditor wants #

The two reports answer different questions, and a SOX audit asks the first one.

SOC 1 SOC 2
Question it answers Do the vendor's controls support your financial reporting? Does the vendor keep data secure, available and confidential?
Main reader Your external financial auditor Your security, procurement and risk teams
Used for SOX and ICFR work Vendor security reviews, customer questionnaires
Where Atlassian publishes it Trust Portal, under NDA Trust Portal, under NDA

Our Atlassian SOC 2 report guide covers the security side. For SOX, start with SOC 1, and keep the SOC 2 report handy for the security questions your IT audit team will also ask.

The IT general controls that stay yours #

SOX IT work is usually organised as IT general controls (ITGCs). For a Jira site that holds in-scope work, these are the ones auditors most often test. The cadence column is an example; your control owners set the real one.

Control What it checks Example cadence
User access review Everyone with access to in-scope projects still needs it Quarterly
Privileged access review Site and org admins, and project admins on in-scope projects Quarterly
Leaver check Accounts of people who left were removed on time Monthly
Change approval sample Production changes had an approved ticket before release Monthly or quarterly
Segregation of duties check The person who approves a change did not also build and release it Quarterly
Workflow and permission scheme review Nobody quietly removed the approval step Quarterly
Vendor report review The latest SOC 1 report and its bridge letter are on file and read Yearly

Two of these trip teams up more than the rest.

The access review is only as good as its date. An access review done in the second month of one quarter and the last week of the next leaves a long gap with no review at all, and the auditor will notice the uneven spacing. A review that arrives as a ticket on the first working day of each quarter, with a due date, fixes the spacing problem.

The approval step lives in the workflow. If the change control relies on a Jira workflow that requires an approval before "Done", the control is only as strong as that workflow's configuration. A periodic check that the workflow and its permission scheme still match the documented control belongs on the calendar too. Our Jira change management template shows a workflow with the approval built in.

Evidence: what an auditor samples #

For a recurring control, the auditor picks a sample of periods and asks for the evidence for each. That means a ticket for every quarter, not a sentence saying the reviews happen.

A good review ticket carries:

A missing quarter is a control failure, even if the review happened somewhere else. That is why the creation of the ticket matters as much as the work inside it.

Three ways to raise the review tickets #

By hand Jira Automation scheduled rule Recurring Work Items for Jira
Effort Every ticket, every period 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 controls 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 handful of controls and one disciplined owner who clones last period's ticket. Our Jira task template guide makes those clones quick. The risk is the period the owner is away.

Jira Automation #

A scheduled rule can create a work item at a fixed rate or on a cron expression, and it covers most of the table above. Quarterly schedules are where it gets fiddly: "the first working day of each quarter" is hard to say in cron, and our Jira cron expression guide explains why. Rule runs also count toward your plan's automation usage, covered in Jira Automation pricing. Remember that the automation rules themselves are configuration an auditor may ask about, since a rule anyone can edit is a control anyone can switch off.

A scheduling app #

Recurring Work Items for Jira creates issues on a schedule, with rules scoped to one project. The controls calendar lives inside the controls project instead of a site-wide rules list, and a project administrator turns it on for that project alone. Each rule keeps a run history that records whether the ticket was created, skipped or failed, and why.

Set up the SOX review calendar #

Whichever tool you choose, the shape is the same. With Recurring Work Items it goes like this:

  1. Create a controls project, or use the one internal audit already owns, with permissions that keep reviewers from editing their own evidence after sign-off.
  2. Turn the app on for that project only.
  3. Create one rule per control. A quarterly access review is a monthly rule repeating every 3 months; the yearly vendor report review repeats every 12.
  4. Pick the day, such as "the 1st" or "the first Monday of the month", so the spacing between periods stays even.
  5. 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 that would fall on a weekend or a public holiday moves to a working day: a new rule runs on the day it falls on, holiday or not.
  6. Title each period distinctly with tokens, for example Quarterly access review {{now.year}}-{{now.month}}, so the auditor's sample request maps to one ticket.
  7. Fill in the template: the control owner, a due date a set number of days after the run, a label such as sox-itgc, and a description naming the control ID and the steps.
  8. Add subtasks for the steps: export user list, review with managers, remove stale access, attach evidence, record sign-off.

When the audit comes, a filter on the label and the period answers the sample request in one query. If you also run broader housekeeping, our Jira hygiene guide fits alongside this.

When the manual way is enough #

A scheduled calendar earns its keep once controls outnumber what one person tracks reliably. You may not need one if:

In that last case, the SOX answer for Jira is simply to document that it is out of scope, and why.

FAQ #

Is Jira SOX compliant? SOX applies to your company, not to a tool. Atlassian provides a SOC 1 report covering controls relevant to your financial reporting, and you run the controls that stay on your side.

Where do I get Atlassian's SOC 1 report? As of October 2026, Atlassian's Trust Center directs you to its Trust Portal for all SOC reports, behind a non-disclosure agreement.

Do I need SOC 1 or SOC 2 for a SOX audit? SOC 1 is the report aimed at financial statement auditors. SOC 2 covers security and availability and is usually requested by security and procurement teams.

Can Jira remind us about quarterly access reviews? Not from a date field on its own. A scheduled rule, in Jira Automation or an app like Recurring Work Items for Jira, can create each review ticket on the first working day of the quarter, with the owner and due date already set. The Jira HIPAA compliance and Jira ISO 27001 guides use the same pattern for their own review calendars.