Skip to content

How Affectra fits your process

This page walks through the processes you follow with Affectra and says who does each step. It ties the guides together, and it describes only what Affectra does today.

Each step starts with who does it:

  • Affectra does it by itself.
  • Member is a person in your organization, in the app. Most steps need the member role or higher, and some need an admin. Roles and what each may do has the table.
  • Assistant is an AI assistant of your own that you connect to Affectra. Affectra is built for it: it reads your data and proposes. A member decides. It never records a statement or a mapping by itself. See Built for AI assistants.
  • Your tools are your CI, your build, your devices and your own process. Affectra is not involved.

There are two sides. A maker builds products and publishes releases. An operator runs units in the field. One organization can be both.

  1. Affectra creates your organization and its first owner.
  2. Member (the owner) invites the other members and sets their roles. Members and roles.
  3. Member (an admin) lets your CI upload. Either create an API key that can propose changes, or trust a GitHub repository so that its workflows need no secret.
  4. Member creates products, variants and releases in the app, or leaves it to the first upload, which creates what is missing. Products, variants and releases.
  5. Member connects an assistant, signed in as themselves or with a read-only API key.
  1. Your tools build the release and write its SBOM.
  2. Your tools upload the SBOM to Affectra, from GitHub Actions or any other CI. They can sign it and attach build provenance: Sign SBOMs. An admin can require signed uploads.
  3. Affectra matches the components against the vulnerability sources and lists the findings of the release. It matches again whenever the sources change, so a release that was clean yesterday can have a finding today. How matching works.
  1. Affectra shows the findings of each release with the markers known exploited (KEV) and EPSS, and how current the data behind them is. Assess findings with VEX.
  2. Assistant ranks the open findings, explains how a finding reaches your product, checks in your source code whether the vulnerable code is reached (Assess findings with your source code), finds the same vulnerability assessed on your other releases, and proposes a VEX statement, or a package mapping for a component that has no package URL.
  3. Member accepts, edits or rejects each proposal, or records a statement without an assistant. With Four eyes for agent proposals on, the person the assistant signed in as, or who created its key, cannot decide its proposals. When the same vulnerable component is reached the same way in another release, the assistant can propose to carry a statement over, and a member reviews these proposals as one batch.
  4. Your tools fix the code and publish the next release, which starts again at the step before. An assistant in your repository can prepare the fix as a pull request for your review.

Why a finding is or isn’t shown explains what Affectra shows and hides.

  1. Member exports the VEX statements of a release as OpenVEX, CycloneDX or CSAF for customers, integrators and authorities. Export VEX.
  2. Your tools send the file to them. Affectra does not send it for you.
  1. Member installs the collector on a unit, once. Install the collector.
  2. Affectra receives the reports. The collector sends one on a timer. A unit without a connection writes bundle files instead, and a Member carries them out and imports them. Air-gapped units and bundles.
  3. Affectra links a unit to a release when the version it reports names one. For a version that names none, a Member (an admin) links it under Units, or the Assistant proposes the link and a Member decides. Find affected units.
  1. Member looks up the affected package in Fleet lookup and sees which units run a version below the fixed one, and which release each unit runs. Assistant answers the same question for a vulnerability ID, across releases and units, with the VEX status, KEV and EPSS of each. Find affected units.
  2. Member reads the VEX statements of the release a unit runs, to see what its maker says about the vulnerability.
  3. Your tools patch the units and roll the update out. The next report of each unit shows the new package version, and Affectra matches it again.

Vulnerability handling under the Cyber Resilience Act

Section titled “Vulnerability handling under the Cyber Resilience Act”
  1. Member (an admin) records the support end of each product: the last day it gets security updates. Products, variants and releases.
  2. Affectra keeps the evidence of what you did: the SBOM of every release, its signature and provenance when you signed it, and every VEX statement with its history, who made it and when.
  3. Your tools and your own process do the rest of the duty: the report to the authority and the advisories to your users.

Read this before you plan a process around Affectra.

  • No notifications. Affectra does not tell you about a new finding or a new proposal. Someone in your organization has to open the app and look at the releases and at Proposals.
  • No history of exposure. Affectra shows the state of your releases and units now. It does not keep a timeline of how many units were exposed to a vulnerability, or for how long.
  • The CRA report is filed outside Affectra. Affectra does not prepare, track or send the notification of an actively exploited vulnerability to the authority, and it has no reminders for its deadlines.
  • No support period overview. The support end is recorded on the product. The overview uses it to list the releases of products past their support end last, but Affectra does not list the supported products that have known-exploited vulnerabilities you have not assessed.
  • Downstream files are sent by you. An export is a file you download. Affectra does not publish it to your customers.

Your first release takes you from an SBOM to a VEX statement. Your first unit adds a device.