Per RFC 9116 On all your domains Never expires

Custom security.txt integration development

Anyone who finds a vulnerability in your website needs to know who to report it to. That is what security.txt is for: a small file in a fixed location on every domain, with contact details and a link to your vulnerability disclosure policy. For government and the (semi-)public sector it is on the comply-or-explain list. Appfront builds the integration that generates the file for all your domains from a single register, signs it, renews it on time and checks it.

What is a security.txt integration?

A security.txt integration ensures that every domain of your organisation serves the security.txt file correctly and up to date. The format is defined in RFC 9116, published in April 2022 as an informational RFC by the IETF. The file sits at /.well-known/security.txt, is served over HTTPS only and is plain text in UTF-8. Two fields are mandatory: Contact, with one or more ways to reach you, such as an email address, phone number or web page, in order of preference, and Expires, the date on which the content expires. The RFC recommends setting that date less than a year ahead. There are also optional fields such as Policy for your disclosure policy, Encryption for a key, Preferred-Languages, Acknowledgments, Canonical and Hiring.

In 2023, the Forum Standaardisatie (the Dutch standardisation forum) put security.txt on the comply-or-explain list. Dutch government bodies and organisations in the (semi-)public sector apply it to all systems that are publicly accessible over HTTPS. The Forum also advises setting up a Coordinated Vulnerability Disclosure (CVD) policy, in other words the coordinated reporting of vulnerabilities, as the NCSC (the Dutch National Cyber Security Centre) describes it. security.txt is the signpost here, not a contract: according to the Forum, the file cannot be used to impose conditions unilaterally on the reporter. Central government domains can use a redirect to point to the NCSC's central file. Note that a file only applies to the domain it sits on, not to subdomains.

We build this as a custom solution because the file itself is simple, but keeping it up to date is not. An organisation with dozens of domains, subdomains and standalone applications soon forgets one, or lets the expiry date lapse, and then the file points to a mailbox nobody reads any more. The integration maintains a single register with contact details, policy, key and languages, generates the file for each domain from it, signs it with OpenPGP if you want, and prepares it for your web servers, CDN or hosting provider. It then checks every domain: is the file in the right place, served over HTTPS, with a valid date and a matching signature?

Per the RFC

Mandatory fields always present.

Every domain

Generated from a single register.

Up to date

Expiry date renewed on time.

How we build your security.txt integration

We start with your domains and your reporting process: which domains and subdomains you offer publicly, where they are hosted, who handles vulnerability reports and whether you already have a CVD policy. Then we set up the register and show, per domain, whether a file already exists, whether it is correct and when it expires. We first build the generation and publishing for a few domains and have your security officer review the result. The remaining domains, the signature and forwarding reports to your ticketing system follow once that goes well. After that, we maintain the integration as your domains or the standard change.

1
Domains mapped

Hosting, owner, reporting process.

2
Setting up the register

Contact, policy and key.

3
First domains

Published and reviewed.

4
Go-live and maintenance

Go-live, monitoring, and management of new domains.

What a security.txt integration actually does

The components below appear in almost every security.txt integration. Which ones you need depends on the number of domains and on how you handle reports.

Register

Contact, policy and languages in one place.

Compile

File per domain.

Signing

With an OpenPGP signature.

Due date

Renewed on time.

Validation

Location, HTTPS and validity.

Notifications

Routed to the right handler.

Who we build a security.txt integration for

The integration is intended for organisations with more than a handful of public domains, and for parties that manage domains on behalf of others. The more domains and applications you have, the more it delivers.

Government bodies

Comply or explain.

Institutions

Education, healthcare, semi-public bodies.

Hosting providers

Files for customers.

Web agencies

Every site you deliver.

Technology and integrations

This page is about the security.txt file itself: drafting, publishing, renewing and checking it. If you want to find, prioritise and fix vulnerabilities in your systems, see our page on setting up vulnerability management. For other internet standards around email and DNS, there is DMARC, DKIM, SPF and DNSSEC monitoring, and for the broader requirements for government software, BIO-compliant software and NIS2-compliant software. You can read about our approach on building software.

RFC 9116 /.well-known/security.txt HTTPS OpenPGP signature Contact and Expires Policy and CVD policy Web server and CDN Ticketing system Roles and permissions Audit log

Why Appfront for your security.txt integration?

A security.txt that expired months ago, a contact address belonging to an employee who has left, or a new subdomain without a file all mean that a reporter cannot reach you or gives up. We build around that: a single register as the source, an expiry date that never passes unnoticed, and a check per domain that shows deviations before anyone else finds them.

Reachable

The right contact on every domain.

Up to date

Never an expired file.

Demonstrable

Check per domain recorded.

Security and privacy in a security.txt integration

The information in security.txt is deliberately public, and the Forum Standaardisatie points out that it can be misused for spam. That is why we recommend a functional address or a reporting form instead of an employee's name. The integration only puts the details you approve in the register into the file, and logs every change with the time and user. Where reports contain the reporter's personal data, the GDPR applies.

The integration runs in a European data centre, with encrypted connections and storage. The private key for the OpenPGP signature is kept shielded and is not visible to staff; the integration only uses it to sign. We agree with you in advance who may change the register, who may approve a new file and who can see reports.

Frequently asked questions about a security.txt integration

Questions that government bodies, institutions and hosting providers ask before they get started.

A text file in a fixed location on your domain, /.well-known/security.txt, in which you state how someone can report a vulnerability they have found. The format is defined in RFC 9116 and is readable by both people and software.

Contact and Expires. Contact provides one or more ways to reach you, such as an email address, phone number or web page. Expires is the date on which the contents expire and may appear only once; the RFC recommends setting it less than a year ahead.

For Dutch government bodies and (semi-)public sector institutions, security.txt is on the Forum Standaardisatie's comply-or-explain list, for all systems that are publicly accessible via HTTPS. For other organisations it is not mandatory, but it is the standard place where reporters look.

CVD stands for Coordinated Vulnerability Disclosure, the coordinated reporting of vulnerabilities. In security.txt, you use the Policy field to point to your CVD policy. The Forum Standaardisatie advises setting up such a policy and points out that the file cannot impose one-sided conditions on the reporter.

No. Under RFC 9116, a security.txt only applies to the domain or IP address it is served on. Every public subdomain therefore needs its own file, or a redirect to a file that is also intended for that domain. Dutch central government domains can point to the central NCSC file.

It is not mandatory, but RFC 9116 recommends an OpenPGP signature so that a reporter can verify the file really comes from you. If you sign it, the Canonical field should also be included, stating where the file is supposed to be hosted.

For organisations with many domains and applications, for hosting providers and web agencies that maintain files for clients, and for public bodies that must demonstrate that every public system has a valid file. If you have a single website, a hand-written file with a calendar reminder is enough.

security.txt on all your domains, and never expired?

Tell us how many domains you have, where they run and who handles reports. We will show you how an integration keeps security.txt correct and up to date everywhere.

Edit content