Table of contents

Implementing security.txt

Domains where the Ministry of Justice (MoJ) is primarily responsible for cyber security SHALL redirect the /.well-known/security.txt location to the central security.txt file.

This redirection SHOULD be accessible from the public Internet whether or not the underlying applications or systems are. For example, https://test.not-production.justice.gov.uk may be a web-application requiring authentication, however https://test.not-production.justice.gov.uk/.well-known/security.txt SHOULD still be accessible without authentication.

security.txt

/.well-known/security.txt SHALL HTTP 301 (permanent redirect) to https://security-guidance.service.justice.gov.uk/.well-known/security.txt.

For example, https://www.prisonvisits.service.gov.uk/.well-known/security.txt SHALL HTTP 301 to https://security-guidance.service.justice.gov.uk/.well-known/security.txt.

/.well-known/

We use /.well-known/ to house security.txt as RFC5785 defines it as a path prefix for “well-known locations” in selected Uniform Resource Identifier (URI) schemes.

Internal-facing domains

Internal-facing domains resolvable from the public Internet (for example, intranet.justice.gov.uk is based on .gov.uk with a publicly routeable IP address) SHOULD also implement security.txt as described previously.

Non-production domains

Non-production domains resolvable from the public Internet (for example, a demonstration deployment of a MoJ digital service or prototype) SHOULD also implement security.txt as described previously.

Feedback

If you have any questions or comments about this guidance, such as suggestions for improvements, please contact: itpolicycontent@digital.justice.gov.uk.