> Write, publish and distribute security advisories from the same place as your SBOMs and VEX. Per-product gating, CSAF 2.0 feeds, security.txt and CRA-ready disclosure, on your own Trust Center.

- **Updated:** 2026-11-10

**Every public advisory is also CSAF 2.0**
On your own Trust Center

# Answer “are we affected?” once, where customers look

Every new CVE turns into the same customer question. Write the answer as a proper advisory, next to the SBOMs and VEX it is about, and publish it for people and their tools in one step.

[Start free](https://app.sbomify.com)
[Book a demo](https://app.sbomify.com/enterprise-contact/)

An illustrative advisory for a fictional company, as a customer with access to two of its three products sees it.

Authoring

## Write it properly. In minutes, not a scramble.

Advisories live next to the SBOMs, findings and VEX they are about, so the facts are already there when you start writing.

- **Everything an advisory needs:** a summary, CVSS score and vector, CVE and OSV references, and remediation.
- **Version ranges as comparisons,** affected and fixed for every product, so readers can tell at a glance whether they are on an affected version.
- **An honest timeline.** Every update is dated and shows the gap since the last one, the number customers judge your incident handling on.

**Timeline**ACME-SA-2026-02

- 3 Nov 2026, 09:12
**Under investigation**
Reported through our disclosure policy. We are assessing which versions are affected.

- 4 Nov 2026, 16:401 day later
**Affected**
Confirmed in Acme Router 2.0.0 to 2.1.0. Restrict access to the web interface until you can upgrade.

- 7 Nov 2026, 11:053 days later
**Fixed**
Fixed in Acme Router 2.1.1.

Illustrative timeline for the advisory above.

Embargoes

## Gated advisories. That are actually gated.

Some advisories are for everyone. Some are only for the customers running the affected product, under NDA, until the fix ships. For those, even the fact that an advisory exists is sensitive.

### Gated per advisory

A reader needs approved access, with your NDA signed, and access to at least one affected product. A customer of one product never learns about an embargo in another.

### 404, not 403

A reader who may not see a gated advisory gets “not found”, not “forbidden”, so its existence is never confirmed.

### Products counted, not named

When an advisory spans several products, readers only see the names of the ones they are entitled to know about.

### Kept out of search

Gated pages are noindex and nofollow, and never appear in your public CSAF distribution. Private advisories never leave your workspace.

Advisories publish to your Trust Center, with a filterable index by product and severity. [Explore the Trust Center](https://sbomify.com/features/trust-center/)

Machine-readable

## CSAF 2.0 out of the box. For the tools that read it.

Enterprise customers don't read advisories one by one. Their vulnerability management tools pull them in and match them against their inventory.

- **Provider metadata and a ROLIE feed,** the entry points CSAF aggregators look for, so new advisories are picked up without anyone sending an email.
- **A security.txt that points to them,** laid out as BSI TR-03183-3 expects.
- **VEX vocabulary, mapped** with the CISA VEX-to-CSAF crosswalk, so not affected, under investigation and fixed mean the same in every format.

New to the format? [What a security advisory is, and how CSAF works](https://sbomify.com/faq/what-is-a-security-advisory/)

**trust.acme.example**Your Trust Center domain

- /.well-known/security.txtRFC 9116
- /.well-known/csaf/provider-metadata.jsonProvider
- /.well-known/csaf/white/feed-tlp-white.jsonROLIE feed
- /.well-known/csaf/white/<year>/<advisory>.jsonAdvisory

Updated as you publish

Cyber Resilience Act

## Disclosure the CRA can audit. With the numbers to prove it.

The [CRA](https://sbomify.com/compliance/eu-cra/) makes disclosure an obligation. Annex I, Part II asks you to publish information about fixed vulnerabilities, run a coordinated disclosure policy and give researchers a contact.

- **Disclose fixed vulnerabilities** with the description, affected products, severity and remediation the CRA lists.
- **Measure your patch SLA.** Set a fix target per severity and the CRA KPIs follow, the numbers an auditor will ask for.
- **Announce end of life** through the same channel. sbomify drafts the notice and pins the final SBOM and VEX; a person publishes it.

Reporting actively exploited vulnerabilities under Article 14 is separate: that goes to ENISA, not your customers. [How sbomify helps](https://sbomify.com/cra/#reporting)

**Patch SLA**The defaults, until you set your own

Critical

7 days

High

30 days

Medium

90 days

The CRA KPIs it makes measurable

- Mean time to triage
- Mean time to remediate
- Open criticals, with the KEV split
- Patch SLA compliance
- VEX publication latency

Learn more

## The processes behind it. Explained.

Guides to running product security disclosure well, whichever tool you use.

- [What is a security advisory?Contents, formats and examples](https://sbomify.com/faq/what-is-a-security-advisory/)
- [What is a PSIRT?Product security incident response, explained](https://sbomify.com/faq/what-is-a-psirt/)
- [What is a vulnerability disclosure program?Policies, CVD and the CRA](https://sbomify.com/faq/what-is-a-vulnerability-disclosure-program/)
- [What is security.txt?RFC 9116 fields, with an example](https://sbomify.com/faq/what-is-security-txt/)
- [How do I become a CNA?Assign CVE IDs for your own products](https://sbomify.com/faq/how-do-i-become-a-cve-numbering-authority/)
- [How do I use VEX?Say “not affected” once, in a format tools read](https://sbomify.com/faq/how-do-i-use-vex/)

**Tell your customers before they ask** Write advisories next to the SBOMs and VEX they are about, and publish them on your Trust Center and as CSAF in one step. [Book a demo](https://app.sbomify.com/enterprise-contact/) or [start free](https://app.sbomify.com).

---

From sbomify: https://sbomify.com/features/security-advisories/
