Getting started
- Getting started with Provetry
From sign-up to your first release watched, in five steps.
- Add a product and its CRA profile
Name, kind, your role, CRA category and support period: what each field is for.
Products and releases
- Upload a release: SBOM or lock files
The files Provetry reads, what it does with them, and supported releases.
- Send releases from your CI
The GitHub action and the GitLab template: an SBOM at every tag, sent on its own.
Vulnerabilities
- Read the vulnerabilities of a release
Exploited first, then the rest: EPSS, the fixed version, components at end of life.
- Assess a vulnerability (VEX)
Not affected, affected, fixed or under investigation: record your decision and why.
- Reachability: is the vulnerable code used?
Suggestions from your CI that a vulnerability is loaded, called or never run, with the evidence.
Reporting to ENISA
- Open a reporting case and follow the clock
Early warning, notification, final report: drafts, deadlines and what you submit to ENISA.
- The Reviewed reports add-on
A certified security expert reads every draft before it reaches you; the early warning never waits.
- Rehearse with a reporting drill
A pretend exploited vulnerability starts the 24-hour clock, now or by surprise.
What you publish
- Your disclosure policy and security.txt
The policy the CRA asks for, written from your answers, and a security.txt to publish and renew before it expires.
- Share a security pack with buyers
One page per product for a buyer: support period, SBOM if you wish, VEX feed, disclosure policy, advisories and correction times, behind a secret link.
- Publish security advisories (CSAF)
A public page per product, CSAF 2.0 advisories signed with OpenPGP, and a VEX feed.
Proof and documentation
- The evidence journal
Every decision recorded, chained and timestamped, so you can show what you did and when.
- Correction times
How long each vulnerability took to handle, against the targets you set per severity, and the dated evidence log.
- Answer security questionnaires
Paste a customer’s questions: answers proposed from your product’s records and your library of past answers.
- The compliance dossier
Technical documentation, Annex I requirements and the EU declaration of conformity, as you fill them in.
Team, alerts and integrations
- Alerts by e-mail
Who receives what: by product, by severity, or only exploited vulnerabilities and deadlines.
- Tickets in GitHub, Jira or Linear
Exploited or severe vulnerabilities become tickets, by hand or on their own, and are updated once dealt with.
- Consultants: a workspace per client
Consultant plan: client workspaces, your logo on the technical documentation, and the bulk import of products.
- Members, roles and API keys
Owner, admin, member, viewer: who can do what, and keys for your CI.
Plan, account and data
- Plans and billing
Choosing, changing or ending a plan, the card, VAT, invoices and the Reviewed reports add-on.
- Order a CRA readiness audit
One product, paid once, reviewed by a certified expert: what you get and when.
- Secure your account
Passkeys, two-factor authentication, trusted devices, changing your e-mail address or password.
- Your data: where it is, export and deletion
What is encrypted, where it is hosted, how to export it and delete the workspace.
Can’t find what you need? Write to us at hello@provetry.com.