Choose vulnerability feeds
Affectra creates findings from several vulnerability feeds. Every feed is on for your organization until an admin or owner turns it off. You can turn off the feeds that create findings and that are not OSV: NVD and each CSAF provider. A feed you turn off changes your organization only.
Why turn a feed off
Section titled “Why turn a feed off”- Your organization does not use what a feed covers. A CSAF provider of industrial controllers, for example, creates findings you never act on.
- A feed produces more noise than value for your products, and you assess its findings by other means.
Turning a feed off is a choice about what your organization sees. It is not a way to resolve a finding. To say that a finding does not apply to your build, assess it with a VEX statement.
Turn a feed off or on
Section titled “Turn a feed off or on”- Open Settings.
- In Vulnerability feeds, clear the box of the feed.
- Confirm. The dialog tells you that the feed’s findings are hidden from every release.
To turn it on again, select the box. Settings shows each feed with its state, its publisher for a CSAF provider, and who changed it last and when.
Members and viewers see the list and cannot change it.
What changes
Section titled “What changes”When a feed is off:
- Findings that only that feed reports disappear from lists, counts, groups, exports, the graph and the agent tools, in every release of your organization. A finding that other feeds report too stays, with the other feeds’ advisories.
- Nothing is deleted. When you turn the feed on again, its findings come back, with their assessments.
- VEX statements you made are not deleted. A CSAF VEX export lists the feeds you turned off in its notes, so a reader knows the document does not cover them.
- Notifications and webhooks send no
finding.resolvedwhen you turn a feed off, and nofinding.newfor the findings that return when you turn it on. Findings that a feed creates while it is on notify as usual. - Package mappings stay. A mapping to a feed that is off creates no findings, and the mappings page says so.
- The data freshness line above a release leaves the feed out. For NVD it says NVD is off for this organization.
Other organizations are not affected.
Feeds you cannot turn off
Section titled “Feeds you cannot turn off”OSV is always on, because it matches most packages. The feeds that only add context to findings are also always on: both KEV lists, the EUVD IDs, EPSS and the MITRE catalogs. Settings lists them as always on.
Vulnerability sources describes each feed.
Who can change it
Section titled “Who can change it”Admins and owners turn feeds on and off. Every member sees the list. Roles and what each may do lists the rest.
Use the API
Section titled “Use the API”GET /v1/orgs/{org}/feeds lists the feeds with key, name, kind, subscribable, subscribed, publisher, state, checked_at, changed_at and changed_by. Any role can read it.
PUT /v1/orgs/{org}/feeds/{feed} with the body {"subscribed": false} turns a feed off, and {"subscribed": true} turns it on. It needs an admin or owner. The feed is nvd, or csaf: and the provider, such as csaf:siemens; encode the colon in the path. A feed you cannot turn off answers 400 with the code feeds.notSubscribable.
Agents see the same choices with the list_feeds tool, and a graph answer marks a feed you turned off with subscribed: false in feed_status. An agent can explain why a CVE has no finding, and cannot change a feed. See the MCP reference.
Each change is an org.feed_subscription_changed event in the events feed and for webhooks that select it.