Skip to content

Glossary

These are the words Affectra uses in the app, the API and these docs. Each means the same thing everywhere.

  • Affectra: The service these docs describe: SBOMs from CI, findings and VEX statements, and a collector for units in the field.
  • product: Something you build and ship, such as a gateway or a controller; it has one or more variants and releases.
  • product key: The short slug your firmware reports as PRODUCT=<key> so that Affectra can link a unit to its releases. It is not a licence key.
  • support end: The last day a product gets security updates, for the support period the Cyber Resilience Act asks for.
  • variant: A build of a product with its own releases, such as a hardware revision, a platform or an edition.
  • release: One version of a product (or of one of its variants) that you ship; SBOMs, findings and VEX statements belong to a release.
  • version: The version string of a release, for example 1.4.0.
  • alias (release alias): Another version text that units report, linked to a release by hand when it differs from the release’s own version.
  • firmware: The software that runs on a unit.
  • SBOM: A software bill of materials, the list of components a release is built from; you upload one from CI for every release.
  • component: A package listed in an SBOM.
  • package: A piece of software, such as a library or an operating-system package, that a release or a unit contains.
  • purl: A package URL, a standard way to name a package, for example pkg:npm/lodash@4.17.21.
  • CPE: A Common Platform Enumeration name, the way the NVD names products.
  • CPE mapping: A rule that says which CPE name a component corresponds to, so that NVD data can be matched to it.
  • unit: A deployed device that reports to Affectra. It is not a unit of measure.
  • collector: The agent that runs on a unit and reports which packages are installed.
  • report (inventory): What a collector sends about a unit.
  • offline bundle: Reports carried in by hand from a site that has no connection to the internet.
  • link (a unit to a release): Connect a unit to the release it runs; a linked unit inherits that release’s VEX statements.
  • stale: A unit that has not reported for 7 days. It is about reporting, not about the age of the software.
  • stale (feed): Vulnerability data that has not been checked within its threshold.
  • vulnerability: A weakness in software that has been published with an identifier, usually a CVE.
  • CVE: A Common Vulnerabilities and Exposures identifier, such as CVE-2024-12345.
  • finding: A vulnerability matched to a release.
  • finding group: One problem in a release: a CVE, or, for advisories without a CVE, an advisory together with its aliases that have no CVE either, however many advisories and components bring it in. Affectra counts finding groups, so a CVE that OSV, NVD and a distribution all publish counts once.
  • finding ID: The readable ID of a finding group, such as Gateway/rev-b@1.4.0:CVE-2024-1234: product, variant, version and the CVE. See Finding IDs.
  • exposure: Which units and releases a vulnerability affects.
  • advisory: A vendor’s or a feed’s published notice about a vulnerability.
  • known exploited: Listed in CISA’s Known Exploited Vulnerabilities catalog, or on ENISA’s EU KEV list from a source other than CISA, which means it is being used in attacks.
  • CISA KEV: The Known Exploited Vulnerabilities catalog published by the US Cybersecurity and Infrastructure Security Agency.
  • ENISA EU KEV: The list of known exploited vulnerabilities in the EU Vulnerability Database of ENISA, the EU Agency for Cybersecurity. It includes CISA’s catalog; Affectra counts only the entries from other sources.
  • ENISA EUVD: The EU Vulnerability Database of ENISA, the EU Agency for Cybersecurity, from which Affectra takes EUVD IDs.
  • EUVD ID: A vulnerability’s ID in ENISA’s EU Vulnerability Database, such as EUVD-2025-4893, which EU customers and CRA reports cite.
  • vendor advisory: A security advisory of a product’s vendor, or of a coordinator such as BSI or CISA, that Affectra reads as a signed CSAF document and shows on findings with the same CVE.
  • EPSS: The Exploit Prediction Scoring System, a score for how likely a vulnerability is to be exploited in the next 30 days.
  • OSV: The Open Source Vulnerabilities database, one of the sources Affectra reads.
  • NVD: The US National Vulnerability Database, one of the sources Affectra reads.
  • VEX: A Vulnerability Exploitability eXchange, a statement from you about whether a vulnerability affects your product.
  • VEX statement: Your decision about one vulnerability in one release, with a status (affected, not affected, fixed or under investigation); for not affected it also gives a justification.
  • justification (VEX): The reason a release is not affected, as a value from the VEX specification such as component_not_present.
  • impact statement: Free text explaining why a vulnerability does not affect a release.
  • action statement: Free text telling users of the product what they should do.
  • signature: A cryptographic proof of who produced an SBOM or a VEX statement and that it was not changed.
  • attestation: A signed statement about a build, such as the one actions/attest-sbom creates in GitHub.
  • trusted publisher: A GitHub repository that is allowed to upload SBOMs for an organization.
  • signature policy: The organization setting that decides whether only SBOMs signed by its trusted publishers are accepted.
  • organization: Your company’s account in Affectra; everything you upload belongs to it and no other organization can see it.
  • member (person): A person who belongs to an organization.
  • role: What a member may do in an organization: viewer, member, admin or owner.
  • viewer (role): Reads everything and changes nothing.
  • member (role): Can upload SBOMs and record VEX statements.
  • admin (role): Manages members, API keys and settings.
  • owner (role): Can do everything an admin can, and can also grant and remove owners.
  • API: The HTTP interface to Affectra, used by CI, collectors and your own tools.
  • API key: A secret that lets a program use the API for one organization.
  • suspended: An organization whose access has been paused.
  • scheduled for deletion: An organization whose data is deleted after a waiting period.
  • audit log: The record of what Affectra staff changed in your organization, shown to owners as Staff activity on Members. See Owners see what staff changed.
  • agent: An AI agent that reads your data through Affectra’s tools and files proposals; it is not the collector on a unit.
  • MCP: The Model Context Protocol, the standard way AI assistants call tools. Affectra serves your data as MCP tools. See MCP server.
  • proposal (agent): A VEX statement or CPE mapping that an agent suggests, for a person to accept or reject.
  • carry-over: A proposal whose basis is a statement carried over from another release with the same dependency path.
  • analysis (basis): A proposal whose basis is the agent’s own argument.
  • evidence: The facts in your data that a proposal rests on.
  • four eyes: An organization setting under which nobody decides a proposal filed with their own sign-in or with an API key they created.
  • digest (proposals): The optional daily email that lists the agent proposals waiting for your decision. See Daily digest of agent proposals.
  • CRA: The EU Cyber Resilience Act, which requires manufacturers of products with digital elements to handle vulnerabilities for the support period of the product.