Blog ·

Jira ISO 27001: the certificate, and the ISMS work you still run

Jira ISO 27001 questions usually come in two forms. The first is from a security questionnaire: is Jira itself certified? Yes. Atlassian lists Jira among the products covered by its ISO/IEC 27001:2022 certification, and you can download the certificate from its trust center. The second question matters more if your own company is going for certification: can Jira run our ISMS? It can hold the work well, but nothing in Jira schedules the reviews the standard keeps asking for. This guide covers both: what Atlassian's certificate gives you, and a way to make your recurring ISMS activities arrive as tickets before they are due.

Statements about Atlassian's compliance programme are as of October 2026, read from Atlassian's own trust center. This is a practical guide, not certification advice. Your auditor and your ISMS owner decide what your controls and cadences are.

Is Jira ISO 27001 certified? #

Yes, as Atlassian publishes it. Its ISO/IEC 27001:2022 page in the trust center lists Jira, Jira Service Management, Confluence Cloud, Jira Product Discovery, Bitbucket Cloud, Trello and others as relevant products. The page describes the basis of the certification this way:

The basis of this certification is the development and implementation of a rigorous security program, which includes the development and implementation of an Information Security Management System (ISMS), which we call the Atlassian Trust Management System (ATMS)

The same page names a related certification, ISO/IEC 27018, which covers the protection of personal information in public cloud services. It says the ATMS "is governed by the implemented controls in accordance with the organizational Statement of Applicability".

For a vendor questionnaire, that is usually the whole answer: attach the certificate, name the products it covers, and note the date you downloaded it.

What Atlassian's certificate does not cover #

Atlassian's certificate covers Atlassian's ISMS. It does not certify yours. If your company is pursuing ISO 27001, the auditor is looking at your scope, your risks and your controls. Using a certified vendor helps with your supplier controls, because you can evidence that a key supplier is certified. It does nothing for the rest.

Three gaps catch teams out:

The recurring work an ISMS asks for #

An ISMS is mostly a calendar. Certification itself runs in cycles: a certificate is normally valid for three years, with a surveillance audit by the certification body each year in between. The auditor at each visit wants evidence that the planned activities happened when your own documents say they would.

A typical calendar looks like this. The cadence is your organisation's choice, stated in your own procedures, so treat this column as an example to adjust:

Activity Example cadence What goes wrong without a ticket
User access review (admins, privileged roles, leavers) Quarterly Leavers keep access, and the auditor samples one
Information security risk assessment review Yearly, and after major changes The risk register describes a system you no longer run
Internal audit (one area of the ISMS per cycle) Quarterly, covering every area within the year An area goes unaudited and becomes a finding
Management review Yearly, often twice a year The meeting slips to the week before the external audit
Supplier review (certificates, contracts, access) Yearly A supplier's certificate expired months ago
Security awareness training reminder Yearly Nobody chases staff who did not complete it
Backup restore test Quarterly or yearly The first restore attempt happens during an incident
Policy review (each policy against current practice) Yearly Policies drift from what people actually do
Statement of Applicability review Yearly Controls added or removed with no record of why

Each of these should create its own ticket, assigned and dated, before it is due. A spreadsheet of dates, or one person's calendar, is a single point of failure. An auditor asks for evidence that each activity happened, and a closed ticket with a date and an owner is easy evidence to show.

Where the ISMS work should live in Jira #

Before choosing how to schedule anything, give the work a home:

  1. Create one ISMS project, separate from delivery work, so the compliance tickets have their own board, filters and permissions.
  2. Limit who can see it. Risk registers and audit findings are sensitive. A project open to the whole site is itself an access control question.
  3. Use issue types or labels per activity: access-review, internal-audit, management-review, supplier-review. Filters by label become your evidence lists.
  4. Link, do not paste. The ticket records that the review happened and links to where the evidence lives, such as an exported access list in your document store.

Our Jira risk register guide covers the register itself, and Jira for legal teams covers a wider compliance calendar.

Three ways to make the reviews create tickets #

By hand Jira Automation scheduled rule Recurring Work Items for Jira
Effort Every ticket, every cycle One rule per activity, written once One rule per activity, 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 ISMS 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 #

Workable for a small company with a short calendar. One ISMS owner clones last cycle's ticket each time. Our Jira task template guide makes those clones quick. The weak point is the owner's holiday, which tends to fall right before a surveillance audit.

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 calendar above. Two cautions. A date like "the first working day of the quarter" is awkward in cron, as our Jira cron expression guide explains. And rule runs count toward your plan's automation usage, covered in Jira Automation pricing. Rules also live in a list that other admins can edit, so record in your ISMS who may change them.

A scheduling app #

Recurring Work Items for Jira creates issues on a schedule, with rules scoped to one project. Your ISMS calendar lives inside the ISMS project instead of a site-wide rules list, and a project administrator turns the app on for that project alone. As with any Marketplace app, add it to your supplier register and review it with the rest.

Set up the ISMS calendar #

Whichever tool you choose, the setup has the same shape. With Recurring Work Items it runs like this:

  1. Turn the app on for the ISMS project only.
  2. Create one rule per activity. A quarterly access review is a monthly rule repeating every 3 months; a yearly management review repeats every 12 months.
  3. Pick the day, such as "the 1st" or "the first Monday of the month".
  4. Set working days and holidays, then choose Move it to the next working day under If it falls on a non-working day, so an activity that would land on a weekend moves to a working day: a new rule runs on the day it falls on, holiday or not. See Jira holidays for how holidays behave elsewhere in Jira.
  5. Title each cycle distinctly with tokens, for example Access review {{now.year}}, so this quarter's ticket and last quarter's never get confused in an evidence list.
  6. Fill in the template: the owner, a due date a set number of days after the run, the label, and a description naming the control and the procedure to follow.
  7. Add subtasks where the activity has steps. For an access review: export admin list, compare to HR roster, remove stale access, record sign-off.

The run history then answers the auditor's first question, which is whether the review ticket was raised on time. The ticket's own history answers the second: who closed it, and when.

Rotating the internal audit #

Internal audits are the activity most likely to drift, because they rotate. One common pattern is a quarterly audit that covers a different area each time, so that every part of the ISMS is audited within the year. Two ways to schedule that:

The second is more setup and gives cleaner evidence. Either works, as long as your audit programme document says which you use.

When the manual way is enough #

A scheduled calendar pays off once the activities outgrow one person's memory. You may not need one if:

In that last case, the certificate from Atlassian's trust center is the whole job.

FAQ #

Is Jira ISO 27001 certified? As of October 2026, Atlassian's trust center lists Jira among the products covered by its ISO/IEC 27001:2022 certification, and offers the certificate for download.

Does using Jira make my company ISO 27001 compliant? No. Atlassian's certificate covers Atlassian's ISMS. Your certification covers your own scope, risks and controls, including how you configure Jira and which apps you install.

Do Marketplace apps share Atlassian's certificate? No. Each Marketplace app is run by its own vendor, so treat each one as a separate supplier in your ISMS.

Can Jira remind us about ISMS 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 ahead of its due date. Our Atlassian SOC 2 report guide covers the same shape for SOC 2.