Every vendor in your stack publishes security advisories. Most of them also publish those advisories as an RSS feed. The problem is not finding the advisories. It is making sure someone reads each one and decides what it means for you.
An inbox is a bad place for that decision. A Jira work item is a good one: it has an owner, a status and a history. Here is how to connect the two.
Find the official feeds
Start with the vendors whose products you run: your firewall, VPN, operating systems, browsers and cloud provider. Look for a security advisories page and its RSS link. Use the vendor’s own feed, not a news site that summarizes it.
Our vendor security advisories collection lists the official feeds we follow, with each feed’s link and how often it posts.
Add a subscription for each feed
In AppsDelivered Feeds, add each feed by its link. Then add a scheduled subscription for it:
- Pick the space where advisories should land, such as your Security space.
- Pick the work type, such as Task.
- Pick the reviewer. Each new post from that feed becomes a work item assigned to that person.
The app checks each subscription every 10 minutes. Feed settings and posts stay inside your Atlassian site.
Triage in one place
Now every advisory is a work item. The reviewer opens it, follows the link to the vendor’s advisory, and decides: affected or not affected.
- Not affected: close it with a short comment, so the record shows someone checked.
- Affected: link it to the patch work. If you use a template set for patch rollouts, apply it and link its epic to the advisory.
What this gives you
After a month, search the Security space for closed advisory work items. You get a list of every advisory you received, who reviewed it and what they decided. That is the record a security questionnaire asks for, and it builds itself as you work.
The feeds app is free. If you want to see the full flow from advisory to patch, read our vulnerability management use case.



