security.txt Not Published
The site does not publish a security.txt file, so people who find a vulnerability have no clear, standard way to report it to the organisation.
| Severity | Informational |
| CVSS 3.1 | 0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N Open in the calculator |
| CVSS 4.0 | 0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1059: Insufficient Technical Documentation |
| Category | Security Misconfiguration |
Description
The site does not publish a security.txt file at /.well-known/security.txt. Defined in RFC 9116, the file is a short, machine-readable text document that tells security researchers and others how to report a vulnerability to the organisation. It must contain at least one Contact field, such as an email address or web form, and an Expires field, and can also link to the organisation's vulnerability disclosure policy and encryption key, state preferred languages and name its own canonical address.
A missing file is not a vulnerability and gives an attacker nothing. Without it, or an equivalent, clearly published disclosure policy, someone who finds a security issue may not know whom to tell, may send the report to a general address where it is overlooked, or may give up or disclose it publicly instead, so vulnerabilities found by others are more likely to reach the organisation late, through the wrong channel or not at all, which lengthens the period in which they could be exploited. The value of publishing one is greatest for organisations with a large internet-facing presence.
A file that has passed its Expires date, names an unmonitored address or is not served over HTTPS is a weaker variant of the same finding. The issue is identified by requesting /.well-known/security.txt over HTTPS, and the older location /security.txt, on the organisation's main domains.
Remediation
Publish a security.txt file at /.well-known/security.txt on each main web domain, served over HTTPS as plain text:
- Include at least one
Contactfield pointing to a monitored address or form, and anExpiresfield less than a year ahead, with a process to renew it before it lapses. - Add a
Policyfield linking to a vulnerability disclosure policy that sets out what may be tested, how reports are handled and how researchers acting in good faith will be treated, and optionallyEncryption,Preferred-LanguagesandCanonicalfields. - Consider signing the file with OpenPGP, as the standard recommends, and redirecting
/security.txtto the well-known location for older tools. - Make sure reports sent to the contact are triaged and acknowledged within a defined time.
Confirm the fix by requesting the file over HTTPS and checking that the required fields are present and the expiry date is in the future.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.