Can buyers and researchers find your vulnerability reporting channel?
Run a free check to see whether your domain publishes a security.txt that follows RFC 9116 and a CVD policy. Results in seconds, no signup.
Checks /.well-known/security.txt and eight common policy paths. Without the web search, no data goes to third parties. Up to five scans per hour.
Two checks. An RFC 9116 security.txt and a CVD policy.
/.well-known/security.txt
We fetch the file and parse it for an RFC 9116 Contact field and a non-expired Expires field. A working security.txt is the public signal that researchers and CSIRTs use to report vulnerabilities to you.
Discoverable CVD policy
We follow the Policy field in your security.txt, then probe five common policy paths (security, disclosure, vulnerability-disclosure-policy, etc.). From 11 December 2027 the CRA requires a CVD policy (Annex I Part II point 5).
CRA compliance now decides EU deals.
Companies that demonstrate CRA compliance win bigger deals and shorter procurement cycles. Companies without it lose access to the EU market.
- Win more EU enterprise RFPs.
CVD policy plus security.txt is now a checkbox on every serious procurement questionnaire. Show it before the buyer asks.
- Shorten security review cycles.
A one-line link to your published CVD process replaces a 40-question vendor security questionnaire round-trip.
- Justify a price premium.
Verifiable CRA compliance signals operational maturity, the same way SOC 2 did for the US market a decade ago.
- Keep selling in the EU.
From 11 December 2027, a national market surveillance authority can order a non-compliant product withdrawn from the EU market (Articles 54 and 58). Compliance keeps your market access.
- Sell CRA-readiness as a service.
White-label CVD Portal under your brand and bill recurring compliance fees.
- De-risk your client portfolio.
Every connected-product client you ship needs a CVD policy and a contact address by 11 December 2027 (Annex I Part II). After that date, an authority can order a non-compliant product withdrawn (Articles 54 and 58).
- Stop losing deals to compliance gaps.
A scanned, badged, and documented portal closes the procurement loop your prospect cannot close on their own.
“[O]rganisations increasingly recognise that software development nowadays requires an active (positive) response to vulnerability reports, which strengthens security and is becoming a strong selling point when handled properly.”