SupportBook a demoExplore the apps
Security · · 2 min read

How to run a monthly access review in Jira

Set up a monthly access review once: one work item for the review, a subtask per system, an owner for each, created on the same day every month.

Most security frameworks ask for the same thing: proof that someone checks who has access to what, on a schedule. Most teams do that check from memory. Someone opens a spreadsheet near the end of the month, copies last month’s tab, and hopes nothing got skipped.

Jira is a better place for it. Each review becomes a work item with an owner, a due date and a history. Here is how we set it up so the review creates itself every month.

What the review needs

A good access review has the same shape every month:

  • One work item for the review itself, owned by the person who signs it off
  • One subtask per system: Jira, email and calendar, the code repository, the VPN, your cloud console
  • A checklist on each subtask, so the reviewer records what they checked

That shape is a template set. You build it once in AppsDelivered Templates, and the app creates the whole structure each time it runs.

Illustration of the Monthly access review template set in the app, with sample data.

Build the template set

  1. In the app, create a template set and add the parent work item. Name it with a variable, such as Access review, $today, so each month’s work item carries its own date.
  2. Add one subtask for each system you review. Put the system’s owner in the Assignee field, so each subtask lands with the right person.
  3. Add a checklist to each subtask: export the user list, remove leavers, check admin rights, note any exceptions.
  4. Save the set in a space your security team already uses.

Put it on a schedule

Open the set’s schedule and pick Monthly, the day, the time and your time zone. The app also supports daily, weekly and yearly runs, or a custom CRON expression if your review follows a different rhythm. The calendar view shows every upcoming run, so you can see the next review before it arrives.

When the schedule runs, $today fills in the date, and the parent work item and its subtasks arrive with their owners already set.

Close the loop

The value of the review is the record it leaves. A few habits help:

  • Ask each owner to attach the user export to their subtask before they close it.
  • Use a resolution or label for exceptions, so you can search for them next quarter.
  • Point your auditor at the closed work items. Each one shows who did the review and when.

If you want to start from our version, the Monthly access review template set page lists every work item, subtask and variable in it.

Riley Venable co-founded AppsDelivered in 2017 and leads its engineering as CTO. He builds the Forge apps behind AppsDelivered Templates, Comments and Feeds. More about Riley

All posts
Security ·

From advisory to patched: vulnerability management in Jira

Templates ·

Recurring work items in Jira Cloud: your options

Templates ·

Variables in Jira templates: fill in what changes