SupportBook a demoExplore the apps

Run vulnerability management in Jira

Track each vendor advisory from the day it's posted to the day the patch is verified, with all three AppsDelivered apps.

The three steps

  1. 01An advisory arrives as a work item
  2. 02The team triages it in a thread
  3. 03If it affects you, roll out the patch
The process

Three steps, one app at each step

Each step is one person's action with one app. Your team moves the advisory from step to step in Jira, the same way it moves any other work.

  1. Step 01AppsDelivered Feeds

    An advisory arrives as a work item

    Subscribe to your vendors' advisory feeds with a reviewer. Each new post becomes a work item assigned to that person.

    You set up the subscriptions once. After that, the reviewer finds each new advisory in Jira, next to the rest of the team's work.

    Start from the Vendor security advisories collection

    Illustration of the app in Jira Cloud, with sample data.

  2. Step 02AppsDelivered Comments

    The team triages it in a thread

    The reviewer adds the Triage result comment template, and the team answers in an internal thread.

    The template asks for the same three things every time: the result, the systems and when to patch. The people who run those systems reply in the thread, so the decision and the reasons behind it stay on the advisory.

    Illustration of the app in Jira Cloud, with sample data.

  3. Step 03AppsDelivered Templates

    If it affects you, roll out the patch

    Apply the Patch rollout template set from the app and type the advisory name. It creates the epic and its work items. Link the epic to the advisory.

    Every rollout gets the same four steps, from listing the affected systems to closing the advisory. If the triage result is Not affected, the reviewer closes the advisory work item and stops there.

    See the Patch rollout set in the template library

    Illustration of the app in Jira Cloud, with sample data.

The result

What you end up with

One advisory, one decision and one rollout, linked together in Jira.

When someone asks later what happened with an advisory, open its work item. The triage result, the thread and the linked rollout epic show what was decided, who decided it and what was done.

  • Advisory: VPN client update for remote laptopsThe advisory's work item, assigned to the reviewerFeeds
    • Triage result and internal threadAffected, which systems, when to patch, and the team's repliesComments
    • Patch rollout, VPN client updateA linked epic, from the Patch rollout setTemplates
      • List the affected systemsChecklist of 3
      • Patch the affected systemsChecklist of 5
      • Verify the patch
      • Close the advisory

What you need

Each app installs on its own from the Atlassian Marketplace. Use all three, or start with the step your team needs most.

  • AppsDelivered Feeds

    Step 01: turns each new advisory into a work item with a reviewer.

    Free on the Atlassian Marketplace.

    Get it free
  • AppsDelivered Comments

    Step 02: holds the Triage result template and the internal thread.

    Free for up to 10 users. Larger teams get a 30-day free trial, then pay per user, billed by Atlassian.

    See the price for your team
  • AppsDelivered Templates

    Step 03: holds the Patch rollout template set.

    Free for up to 10 users. Larger teams get a 30-day free trial, then pay per user, billed by Atlassian.

    See the price for your team

Used on this page

The template set, comment template and feed collection behind the three steps.

Template set

Patch rollout

An epic and four work items, from listing the affected systems to closing the advisory.

1 epic, 4 work items · On request

See it in the template library
Comment template

Triage result

Three lines the reviewer fills in: the result, the systems and the patch date. Save it once in the comments app, and every advisory gets its answer in the same shape.

See AppsDelivered Comments
Feed collection

Vendor security advisories

Advisory feeds from the vendors in your stack, checked every hour, with each feed's link ready to copy into the feeds app.

See the feed collection

Vulnerability management: common questions

Do the apps pass work to each other?

No. Each app does its own step, and your team moves the work along in Jira.

Can a transition apply the Patch rollout set?

Yes. In a company-managed space, a workflow transition can apply a whole template set, so moving the advisory to Affected builds the Patch rollout structure.

Do we need all three apps?

No. Each step works without the others. You can start with the Patch rollout set and log advisories by hand, then add the feeds app later.

See the three steps in Jira.

Book a demo with your own vendors and systems in mind, or try each app in your Jira site.

Book a demoCompare the three apps