Is security.txt mandatory?
The short answer: no EU law requires the file by name. But the Cyber Resilience Act requires manufacturers to offer an easy-to-find point of contact for vulnerability reports and to publish a coordinated disclosure policy, and NIS2 requires many companies to handle and disclose vulnerabilities in an orderly way. security.txt is the standard way to meet both requirements and to prove it. This page sets out exactly what is required, of whom and from when.
The short answer
security.txt is an IETF standard (RFC 9116), not a law. Neither the Cyber Resilience Act (CRA, Regulation (EU) 2024/2847) nor the NIS2 Directive mentions the file, and neither does the European Commission's CRA FAQ (version 1.4).
That does not mean offering a reporting channel is optional. Both frameworks prescribe outcomes, not formats:
- Manufacturers of products with digital elements need, under the CRA, a contact address for vulnerability reports, a single point of contact that users can easily identify, and a published policy on coordinated vulnerability disclosure. This applies from 11 December 2027.
- Essential and important entities under NIS2 must be able to handle and disclose vulnerabilities. How they receive reports from outside is left open.
- Anyone following the German BSI TR-03183-3 must publish a security.txt. The guideline is voluntary, but it spells out the manufacturer obligations of the CRA in detail.
- Dutch public bodies have been required to use security.txt since 2023. That is the one place in the EU where it is genuinely mandatory.
For everyone else the file is a recommendation, made among others by national cybersecurity agencies. It costs very little, and it is the first place security researchers, CSIRTs and scanning services look.
What the Cyber Resilience Act requires
The CRA covers the cybersecurity of products with digital elements, meaning hardware and software placed on the EU market. The main obligations fall on the manufacturer: whoever develops or manufactures such products, or has them designed or made, and markets them under their own name or trademark (Article 3, point 13). Five provisions matter for reporting channels.
Contact address for vulnerabilities (Annex I, Part II)
Annex I, Part II sets out the vulnerability handling requirements. Under point (5), manufacturers must "put in place and enforce a policy on coordinated vulnerability disclosure". Under point (6), they must facilitate the sharing of information about potential vulnerabilities, "including by providing a contact address for the reporting of the vulnerabilities discovered in the product with digital elements".
Single point of contact (Article 13(17))
Article 13(17) requires manufacturers to designate a single point of contact so that users can communicate with them "directly and rapidly", including to report vulnerabilities. It contains three requirements: the point of contact must be "easily identifiable by the users", it must be included in the user information under Annex II, and users must be able to choose their preferred means of communication, which may not be limited to automated tools. A chatbot alone does not qualify. Recital 63 adds that manufacturers should keep the contact information up to date.
Information for users (Annex II, point 2)
Under Annex II, point 2, the product must come with "the single point of contact where information about vulnerabilities of the product with digital elements can be reported and received, and where the manufacturer's policy on coordinated vulnerability disclosure can be found". The reporting address and the policy belong together.
Evidence in the technical documentation (Annex VII, point 2(b))
The technical documentation must include, among other things, the coordinated vulnerability disclosure policy and evidence of the provision of a contact address for reporting vulnerabilities. If a market surveillance authority later asks you to show that the address existed, an email address buried in your legal notice is weak evidence.
From when, and what is at stake
The Regulation applies from 11 December 2027 (Article 71(2)). The reporting obligations in Article 14, including the early warning for actively exploited vulnerabilities within 24 hours, have applied since 11 September 2026. If you have to report, you should already be receiving reports from outside reliably. Under Article 64(2), breaches of Annex I and Article 13 can lead to fines of up to EUR 15 million or 2.5 percent of worldwide annual turnover, whichever is higher.
Not every website falls under the CRA. Recital 12 excludes websites that do not support the functionality of a product. The obligations attach to the product, not to your corporate website. But security.txt on that website is where users and researchers will look for the product's point of contact.
How these obligations fit together is explained in detail in the guide security.txt under the CRA on cra-response-center.com.
Why security.txt is the obvious way to comply
The CRA does not prescribe a format. Put its requirements next to the security.txt fields, though, and they line up almost one to one:
| CRA requirement | Provision | How security.txt covers it |
|---|---|---|
| Contact address for vulnerability reports | Annex I, Part II (6) | Contact field |
| Point of contact easily identifiable | Art. 13(17) | Fixed, well-known location /.well-known/security.txt, machine-readable |
| Choice of communication means, not only automated | Art. 13(17) | Several Contact lines: email address, web form, phone |
| Disclosure policy can be found | Annex I, Part II (5); Annex II (2) | Policy field linking to your CVD policy |
| Contact information kept up to date | Recital 63 | Expires field: the file goes stale if nobody maintains it |
| Evidence of the contact address | Annex VII (2)(b) | Dated, signed file; keep earlier versions on record |
There is also a practical reason. Security researchers, national CSIRTs and automated scanners look exactly there. Each Member State designates a CSIRT as coordinator for coordinated vulnerability disclosure (NIS2, Article 12), and that coordinator needs a manufacturer contact when someone reports a flaw in your product. Without the file, the report ends up at info@, in the sales contact form, or nowhere. What each field means is explained in the guide.
BSI TR-03183-3: voluntary, but explicit about the file
On 20 August 2025 the German Federal Office for Information Security (BSI) published Technical Guideline TR-03183-3 "Vulnerability Reports and Notifications", version 1.0.0, in English. It is addressed to manufacturers as defined in the CRA and describes how they should receive vulnerability reports. It is not law and nobody is obliged to follow it. Anyone who claims to follow it, towards customers or authorities, has to meet its MUST requirements, and those are clear:
- Section 4.2: a security.txt in accordance with RFC 9116 "MUST be created and made available on the manufacturer's website".
- 4.2.1: it sits at
/.well-known/security.txt. - 4.2.9: an expiry date is mandatory and the information is checked at least quarterly.
- 4.2.10: the file is signed with OpenPGP.
- 4.2.11: it must be retrievable automatically by web crawlers, so a bot challenge in front of it is a breach.
The guideline also requires two role mailboxes (a PSIRT for products and a CSIRT for your own IT), a reporting page and a policy. Although it comes from a German authority, it is currently the most precise benchmark for manufacturers anywhere in the EU, because it turns the open wording of the CRA into checkable steps. Whether to follow RFC 9116 or the TR is compared in the guide.
NIS2: handling and disclosing vulnerabilities
The NIS2 Directive (EU) 2022/2555 does not regulate products but companies in certain sectors above a certain size. Under Article 21(2)(e), the cybersecurity risk-management measures include "security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure". Each Member State transposes this into national law; in Germany, for example, it is section 30(2), point 5 of the BSI Act.
NIS2 does not require security.txt either. But if you have to explain how vulnerability information from outside reaches your organisation, a maintained file, a role mailbox and a published policy give you a simple answer you can document. Article 12 additionally requires each Member State to designate a CSIRT as coordinator for coordinated vulnerability disclosure, acting as a trusted intermediary between reporters and companies. That coordinator has to be able to reach you, too.
Whether your company falls under NIS2 depends on sector, size and turnover, and on the national transposition. Have this checked for your specific case; the vulnerability handling obligation applies regardless of whether you are also a manufacturer under the CRA.
Recommendations and obligations by country
Netherlands: mandatory for the public sector
The Dutch Forum Standaardisatie lists security.txt as mandatory under "comply or explain" (pas toe of leg uit), decided on 25 May 2023. The obligation covers central government, provinces, municipalities, water authorities and institutions in the (semi-)public sector, for all systems publicly reachable via HTTPS. These bodies must require the standard when procuring IT, so suppliers to Dutch public bodies often meet it in the tender documents.
Germany: recommended by the BSI
The BSI recommends security.txt in its cybersecurity recommendation BSI-CS 149 on publishing security contacts with a security.txt under RFC 9116. The requirements of TR-03183-3 build on that recommendation.
United States: recommended, not required
US federal civilian agencies have had to publish a vulnerability disclosure policy since CISA's Binding Operational Directive 20-01. The directive does not require security.txt; CISA states that its use is not required but can help people find whom to share findings with. So even in the often-cited US case, the file is welcome but not a condition.
Tenders, customer questionnaires and audit reports
In practice the question about security.txt is raised less often by legislation than by customers and auditors:
- Audit reports and scanners. Penetration tests, external security ratings and website scanners list a missing or expired file as a finding. What to do next is covered on scanner says "security.txt not configured" and security.txt expired.
- Supplier assessments. Large customers ask in security questionnaires how vulnerabilities can be reported. A link to your security.txt and policy answers that in one line.
- Public procurement. In the Netherlands the standard is part of procurement; other contracting authorities increasingly orient themselves on the CRA.
- Customers with their own CRA obligations. Manufacturers must also handle vulnerabilities in third-party components (Annex I, Part II, point 6). If you supply components, software or modules, expect to be asked about your reporting channel.
Who needs what?
A rough classification based on our reading of the rules. It does not replace an assessment of your specific case.
| You are | Legal position | Recommendation |
|---|---|---|
| Manufacturer of products with digital elements (devices, software, apps, machinery with software) | CRA: contact address, single point of contact and CVD policy from 11 Dec 2027; reporting obligations since 11 Sep 2026 | security.txt under BSI TR-03183-3, signed, with PSIRT mailbox, reporting page and policy |
| Essential or important entity under NIS2 | Vulnerability handling and disclosure (Art. 21(2)(e) and national law), format open | security.txt under RFC 9116 with a role mailbox and policy, ideally under the TR |
| Company with a corporate website only, no products of its own | no obligation | security.txt under RFC 9116 with a security@ address; little effort, prevents lost reports |
| Dutch public body or (semi-)public institution | mandatory ("comply or explain") for all publicly reachable systems | security.txt on every publicly reachable domain |
| Other public authority, municipality, university | no explicit obligation for the file; NIS2 obligations depending on the body and the Member State | security.txt under RFC 9116, following your national agency's advice |
| Distributor or importer | own obligations under the CRA; the point of contact is provided by the manufacturer | security.txt for your own website; forward reports about third-party products to the manufacturer |
How to get it done in an afternoon
- Pick an address. A role mailbox such as
security@, or under the TRpsirt@andcsirt@, read by at least two people. What matters is covered in setting up a security contact. - Publish a policy. A short page with scope, reporting channel and commitments. The CVD template drafts one for you.
- Create the file. With the generator; ready-made samples are in the examples.
- Upload and check. How to do it on your system is described in security.txt on your platform; then run the checker.
- File the evidence. Store a dated copy of the file with your technical documentation and add a new version whenever it changes.
- Set a reminder. Renew before the expiry date; under the TR, review at least quarterly.
If you would rather not keep that last step in a calendar: monitoring checks the file every day and reminds you well before it expires, for EUR 60 net per domain and year.
Frequently asked questions
Is security.txt required by law?
Not in the EU as a whole. No EU law names the file. From 11 December 2027 the CRA requires manufacturers to provide an easily identifiable contact address for vulnerabilities and a coordinated disclosure policy, but no format. In the Netherlands security.txt is mandatory for public bodies.
Does the Cyber Resilience Act require security.txt?
Not explicitly. It requires a contact address for vulnerability reports (Annex I, Part II, point 6), an easily identifiable single point of contact (Article 13(17)) and evidence of the contact address in the technical documentation (Annex VII). security.txt covers these points with a single machine-readable file.
Do I need security.txt for NIS2 compliance?
NIS2 requires vulnerability handling and disclosure (Article 21(2)(e)) but no particular file. security.txt is a simple, documentable building block that shows how vulnerability information from outside reaches you.
Is BSI TR-03183-3 binding?
No, BSI Technical Guidelines are voluntary. If you apply it, you must publish a signed security.txt under RFC 9116 (section 4.2). For manufacturers it is the most precise benchmark for implementing the open wording of the CRA.
Is an email address on the contact page enough?
For general contact perhaps, for vulnerability reports hardly. The CRA requires a point of contact that is easy to identify, together with the disclosure policy. No automated service finds an address on a contact page, and it says nothing about how reports are handled.
Does the CRA apply to my corporate website?
No. Under recital 12, websites that do not support the functionality of a product are outside the CRA. The obligations attach to the product. But your website's security.txt is where researchers will look for the point of contact for your product.
What are the consequences of not having a contact address?
For manufacturers the contact address is part of the essential requirements in Annex I. From 11 December 2027, breaches of Annex I and Article 13 can be fined up to EUR 15 million or 2.5 percent of worldwide annual turnover (Article 64(2)). The more common consequence is practical: a report never reaches you, and the vulnerability is published without you.
Does the US require security.txt?
No. CISA's BOD 20-01 requires federal civilian agencies to publish a vulnerability disclosure policy, but CISA states that security.txt is not required by the directive.
Sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Article 3(13), Article 13(17), Article 14, Article 64(2), Article 71, Annex I Part II points (5) and (6), Annex II point 2, Annex VII point 2(b), recitals 12 and 63.
- Directive (EU) 2022/2555 (NIS2), Article 12 and Article 21(2)(e).
- Section 30 of the German BSI Act (BSIG), subsection 2, point 5.
- BSI TR-03183-3 Vulnerability Reports and Notifications, version 1.0.0, sections 1 and 4.2, Federal Office for Information Security, 20 August 2025.
- BSI-CS 149: Sicherheitskontakte mit Hilfe einer security.txt nach RFC 9116 angeben, Alliance for Cyber Security (in German).
- RFC 9116: A File Format to Aid in Security Vulnerability Disclosure, IETF, April 2022.
- security.txt on the "comply or explain" list, Forum Standaardisatie (Netherlands), decision of 25 May 2023.
- BOD 20-01: Develop and Publish a Vulnerability Disclosure Policy, CISA, including the FAQ on security.txt.