Skip to main content
v2026.11,986 entries · CC-BY 4.0

Vulnerability Disclosure: security.txt, VDPs and CVD Explained

Vulnerability disclosure explained: RFC 9116 security.txt fields, CISA’s VDP template and the seven-stage CVD process, with a field-by-field table.

Written and maintained by CASRAI Editorial Board

Published

On this page

Vulnerability disclosure is the process by which someone who finds a security weakness in software or a system tells the party that can fix it, and by which the fix and the facts about the weakness are later shared with everyone affected. In practice it has two sides: the organisation publishes a policy and a contact route so that reports have somewhere to go, and, for flaws in products used by many parties, a coordinator manages the timing of public release. This guide explains both sides, shows the exact fields of a security.txt file under RFC 9116, and maps CISA’s published policy template and coordination process.

What vulnerability disclosure is used for in research

Research teams meet vulnerability disclosure from two directions. As finders, they discover flaws in instruments, laboratory software, data platforms or open-source libraries while doing their work and need to know where and how to report them. As operators, universities, labs and research infrastructures run public systems (repositories, portals, instrument gateways) and need a channel through which outsiders can tell them about weaknesses before attackers exploit them. The same vocabulary applies in both roles, and the CERT Guide to Coordinated Vulnerability Disclosure describes the finder or reporter as often being an independent security researcher.

Three terms are easy to confuse, and the sources separate them clearly.

  • Vulnerability disclosure is the general process. The CERT Guide to CVD quotes ISO/IEC 29147 in describing it as a process through which vendors and vulnerability finders may work cooperatively to reduce the risks associated with a vulnerability.
  • Coordinated vulnerability disclosure (CVD) adds a managed sequence of steps among finder, vendor, downstream vendors, coordinators and deployers. The CERT Guide stresses that CVD is a process, not an event: even for one vulnerability, disclosure is not a single moment.
  • A vulnerability disclosure policy (VDP) is an organisation’s statement of how it receives reports about its own public systems. CISA states that its Vulnerability Disclosure Process is separate from CVD and that a VDP does not involve coordination, remediation or advisory publication.

The older phrase responsible disclosure is deliberately avoided by CERT/CC. Its guide says that what counts as responsible behaviour is a matter of opinion framed within the values of whoever uses the term, and that CERT/CC and other organisations promote coordinated vulnerability disclosure to reduce misunderstanding and promote cooperation.

Disclosure records connect to the identifiers used elsewhere in vulnerability management. A coordinated case may end with a CVE record, a severity rating such as a CVSS score, and prioritisation under a scheme like SSVC; Europe’s registry is covered in our EUVD guide. Regulated research settings, for example clinical systems, carry additional expectations; see healthcare cybersecurity for that context.

How to access vulnerability disclosure channels: security.txt and VINCE-NT

Find an organisation’s reporting route with security.txt

RFC 9116 (April 2022) defines security.txt, a plain-text file that tells outsiders how to report a vulnerability. For web services the file belongs at the /.well-known/ path, for example https://example.com/.well-known/security.txt. A copy or redirect at the top level of the site is allowed for legacy compatibility, but if both exist the /.well-known/ version takes precedence. The file must be retrieved over HTTPS with a content type of text/plain and UTF-8 character set, and it applies only to the domain or IP address in the URI used to retrieve it, so it does not automatically cover subdomains or parent domains.

If you are a finder, fetch that path first and read the Contact lines (listed in order of preference), then the Policy link, which should describe scope and process. RFC 9116 is explicit that the presence or absence of a security.txt file does not itself grant or deny permission to test; any authorisation has to come from the policy it points to. The data table below lists every field the RFC defines.

Report to a coordinator through VINCE-NT

When the affected vendor is unresponsive or the flaw spans several vendors, a coordinator can take the case. CISA accepts reports through VINCE-NT (Vulnerability Information and Coordination Environment – New Technologies), the coordinated vulnerability disclosure platform that CISA sponsors, hosts and manages. The CISA process page describes the route a submitted report then follows, covered step by step below.

How to publish a vulnerability disclosure policy step by step

CISA’s vulnerability disclosure policy template, written to align with Binding Operational Directive 20-01 for federal agencies, is a usable skeleton for any organisation. Its sections run in a fixed order, and the numbered steps below follow it.

  1. Write the Introduction. State who the policy covers and why you welcome reports.
  2. Add the Authorization section. The template commits that the organisation will not recommend or pursue legal action related to a finder’s research.
  3. Set the Guidelines. The template lists activities that are not permitted, including network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data, and physical testing such as office access, open doors or tailgating.
  4. Describe the Test Methods you do and do not accept.
  5. Define the Scope. List the systems in scope explicitly. The template’s wording is that any service not expressly listed, such as any connected services, is excluded from scope.
  6. Explain Reporting a vulnerability, with two subsections: what you would like to see from the reporter and what they can expect from you. The template’s example commitment is to acknowledge receipt within 3 business days.
  7. Give a Questions contact and keep a Document change history.
  8. Publish a pointer to the policy. Create the security.txt file with Contact, Expires and a Policy field linking to the policy page, serve it from /.well-known/security.txt, and set a calendar reminder before the expiry date.

Decide the acknowledgement time yourself and then keep it: the 3-business-day figure is CISA’s template wording, and CISA adds that it applies when the reporter provides contact information. A policy that promises a response period the team cannot meet is worse than a longer, honest one.

How to read the output: advisories, CVE records and KEV

A coordinated case ends in published artefacts. CISA’s process page lists seven stages: vulnerability report submission; CVD intake and triage; CVD coordination; CVE record determination (if applicable); advisory development and publication preparation; public disclosure; and Known Exploited Vulnerabilities (KEV) evaluation and publication. The table below shows what each stage means for someone reading the result.

CISA CVD stage What happens What you can read afterwards
Report submission A researcher or supplier reports a suspected flaw to CISA Nothing public yet
Intake and triage CISA checks whether the report appears legitimate, is actionable and is in scope Nothing public yet
Coordination Supplier outreach, technical analysis, timeline tracking and mediation Nothing public yet
CVE record determination CISA decides whether a CVE ID is warranted and which CNA will publish it A CVE ID, where applicable
Advisory development Participants agree the final advisory text and publication timing Nothing public yet
Public disclosure CISA publishes its outputs and notifies reporters and vendors CISA advisory, enriched CVE record, machine-readable CSAF advisory
KEV evaluation Follows disclosure; assesses whether the flaw belongs in the Known Exploited Vulnerabilities catalogue A KEV catalogue entry if added

CISA states that it has no fixed timeline for the process and that it may disclose vulnerabilities as early as 45 days after the initial attempt to contact the vendor is made, regardless of the availability of a patch or update. That statement applies when a vendor is unresponsive or will not agree a reasonable remediation timeframe, and it matters to finders because it sets a realistic expectation of how long silence can last. The CSAF format is the Common Security Advisory Framework, the machine-readable counterpart to the human-readable advisory.

When you read a published advisory, separate three questions: which identifier names the flaw (the CVE record), how severe it is rated (see CVSS scores above), and whether action should be prioritised now (KEV listing, or a decision framework such as SSVC). For the difference between the identifier and the score, see CVE vs CVSS.

Troubleshooting vulnerability disclosure

The problems below follow directly from what RFC 9116 and CISA’s pages say.

  • The security.txt file is ignored or rejected by tooling. Check that it contains a Contact field and exactly one Expires field; both are required. Check that it is served over HTTPS as text/plain in UTF-8 and that the file sits at /.well-known/security.txt, which takes precedence over a top-level copy.
  • The file has gone stale. RFC 9116 recommends an Expires value less than a year in the future to avoid staleness, so renew it on a schedule.
  • A subdomain returns no file. The file applies only to the exact domain it is retrieved from. Publish one for each host you want covered.
  • The public key is pasted into the Encryption field. The RFC says keys must not appear there; the field holds a URI from which the key can be retrieved.
  • You assume the file authorises testing. It does not. Read the policy linked in the Policy field, and stay inside its scope and prohibited-activity list.
  • The vendor does not answer. Move to a coordinator. CISA’s process allows disclosure as early as 45 days after the first attempt to contact the vendor, so keep a dated record of each attempt.
  • A report was filed against the wrong asset. Under the CISA template, any service not expressly listed in scope, including connected services, is excluded.

Free alternatives to a single disclosure channel

There is no single tool to replace. Organisations combine routes, and each of the following is described in a primary source. The data table below sets out the security.txt fields; this table compares the three routes.

Route Best understood as Where defined
security.txt file A machine-readable pointer to contact details and a policy, per domain RFC 9116
Published VDP page The human-readable rules: authorisation, scope, test methods, what the reporter can expect CISA VDP template
Coordinated disclosure through a coordinator Multi-party handling with vendor outreach, CVE determination and advisory publication CISA CVD process; CERT Guide to CVD

The three work together: a security.txt Policy field links the VDP page, and an unresolved or multi-vendor case can be escalated to a coordinator. ISO/IEC 29147 (Vulnerability disclosure) is the international standard behind the process definition quoted by the CERT Guide, which is a useful reference when an institution wants to align its policy with a recognised standard.

Sources

Data: security.txt fields defined in RFC 9116 and whether each is required

Field-by-field compilation of the eight security.txt fields defined in RFC 9116 (April 2022): requirement level, what each field holds and the RFC section that defines it. Compiled from the RFC text read on the RFC Editor site.

Period covered: 2022.

security.txt fields defined in RFC 9116 and whether each is required
FieldRequirementWhat it holdsRFC 9116 section
ContactRequired (MUST be present)How to reach the security team: mailto:, tel: or https: URI; repeatable, listed in order of preference2.5.3
ExpiresRequired (once only)Timestamp after which the file is stale; recommended less than a year ahead2.5.5
PolicyOptionalLink to the vulnerability disclosure policy describing scope and process2.5.7
EncryptionOptionalURI from which an encryption key can be retrieved; keys must not appear in the field2.5.4
AcknowledgmentsOptionalLink to a page recognising researchers who reported vulnerabilities2.5.1
CanonicalOptionalURI where the file is canonically located2.5.2
HiringOptionalLink to the organisation's security-related job openings2.5.6
Preferred-LanguagesOptionalComma-separated language tags; order is not a priority; English assumed if absent2.5.8

Sources

Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · free to try

Ask about Vulnerability Disclosure: security.txt, VDPs and CVD Explained

2 free questions a day, no account.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →