Organizations and data isolation
Your organization is your company’s account in Affectra. Everything you upload, and everything Affectra derives from it, belongs to your organization and to no other. This page lists what Affectra guarantees, and for each guarantee how you can check it.
One organization never sees or changes another’s data
Section titled “One organization never sees or changes another’s data”Another organization cannot read your products, releases, SBOMs, units, findings or VEX statements. It cannot change them either.
The organization comes from the credential. An API key belongs to exactly one organization. A person’s access comes from their membership of an organization. Neither depends on a name or an ID that the caller puts in a request. If a request names a different organization than the credential allows, Affectra does not switch over. It refuses.
- A person can use an organization only if they are a member of it.
- A GitHub Actions run can use an organization only if that organization lists its repository as a trusted publisher.
- A collector report or an offline bundle names the organization it was made for. Affectra refuses to import it into another one.
Another organization looks like no organization. A request for an organization that you do not belong to gets the same answer as a request for one that does not exist: 404, not found. You cannot find out which organizations exist.
Check it. With an API key of your organization, ask for the units of an organization name you made up, and for one that you know exists but is not yours. Both answers must be the same 404:
curl --silent --output /dev/null --write-out '%{http_code}\n' \ --header "Authorization: Bearer $AFFECTRA_API_KEY" \ https://api.example.com/v1/orgs/some-other-organization/unitsReplace the host with your Affectra’s. Keep the key in an environment variable, as in API keys.
The database enforces it too
Section titled “The database enforces it too”Affectra does not rely on the application alone. Every table that holds customer data is tied to one organization, and the database itself refuses to return or change a row of another organization, even if the application had a mistake. Every way in to your data is also tested with two organizations, to prove that one cannot read or write the other’s.
You cannot check this part yourself. It is a property of how Affectra is built and tested, and it is the reason a mistake in one place does not become a leak.
Shared public packages leak nothing
Section titled “Shared public packages leak nothing”Affectra stores each public package once, however many organizations use it, and matches it once. This saves work, and it does not mix your data with anyone else’s:
- Findings of a shared package depend only on public data. Your upload cannot change another organization’s results, and theirs cannot change yours.
- Nobody learns which packages you use. An organization sees only the findings of components in its own releases, and cannot list or look up shared packages.
- Vendor code stays private to you. A component that is vendor code, or whose package URL points at a private repository, belongs to your organization only.
- Your mappings are yours. A package mapping adds findings to your releases only.
Check it. How matching works has the rules, and Why a finding is or isn’t shown lists every one. On a release, the tag on a finding’s component tells you how it was matched.
Your component lists never leave Affectra
Section titled “Your component lists never leave Affectra”Matching runs inside Affectra, against a copy of public vulnerability data. Affectra downloads whole public data sets. It never asks a source about a particular package, so no source learns what is in your products.
Two things leave Affectra only because you choose them:
- Exports you download, such as VEX files.
- What your own AI agent reads. If you give an agent an API key, it reads what that key may read. Affectra itself calls no AI model and sends no data of yours to one. Give agents a Read only key. See Connect an AI assistant.
Check it. Vulnerability sources lists every source. Each one is a public download.
Staff cannot read your data
Section titled “Staff cannot read your data”Affectra staff use a separate console with their own sign-in, a second factor and a role. Their credentials never work on your organization’s routes, and yours never work on theirs.
The console shows staff an organization’s name, its status, its owners, its signature policy, the vulnerability feeds it has turned off (who did and when), and counts and times of use, such as how many releases it has. It does not show your products, SBOMs, units, findings or VEX statements. Staff cannot read them there.
Staff can do a few things to an organization, which are the work of setting it up and keeping it running: create it, rename it, add an owner, change its signature policy, suspend it, schedule its deletion, and change its request limits. Staff never remove a member. The one exception is an owner they added who has never signed in, for example because of a typo in the email address: staff can withdraw that invite, since the person never had access. If Affectra support needs to look at your data, you invite a person as a member, like anyone else, and you can remove them again.
Owners see what staff changed
Section titled “Owners see what staff changed”Staff adding an owner is the most sensitive of these, because an owner can see everything. So owners see it.
Check it. If you are an owner, open Members in the app. At the bottom, the card Staff activity shows What Affectra staff changed in this organization. Only owners see this. Each row has a time and a sentence, for example Affectra staff made … an owner. The list covers:
- creating the organization;
- adding an owner, and the role the person had before;
- renaming the organization;
- turning the signature policy on or off;
- suspending and reactivating the organization;
- scheduling its deletion, with the date.
It says “Affectra staff”, never the name of a person. Other members do not see it. Changes to your request limits are not in the list. They do not touch your data.
When an organization is suspended or scheduled for deletion, its members, API keys and trusted publishers cannot use it. Its data is kept until the deletion date.
Evidence is only added to
Section titled “Evidence is only added to”Some records are the evidence of what was decided and who signed it. Affectra only adds to them and reads them. It never edits them:
- VEX statements. To change your mind, you record a new statement. The old one stays in the history. See Assess findings with VEX.
- Signatures and build provenance. The record of who signed an SBOM or built a release stays as it was when it arrived. The signature bundle is kept exactly as uploaded.
- The staff record. Every staff action is written to a log that can only be added to.
VEX statements are never deleted. A release that has any cannot be deleted, and neither can its variant or product. Signatures and build provenance go away only when you delete what they belong to: deleting an SBOM deletes its signatures, and deleting a release without statements deletes its SBOMs and provenance. Only an admin can do that, and the app asks you to confirm.
Check it. On the VEX tab of a release, History shows every statement, including the ones that were replaced. For a signed SBOM, download its bundle and check it with cosign verify-blob, without trusting Affectra. See Sign SBOMs.
What this page does not promise
Section titled “What this page does not promise”- Affectra says who built a document. It does not say that the document’s content is safe.
- Isolation is between organizations. Inside your organization, what a person sees depends on their role.