← Digital Channel and Technical Security

CYB-11 · Cyber security

Vulnerability disclosure — security.txt file present for responsible disclosure

The security.txt standard (RFC 9116) defines how organisations can communicate their vulnerability disclosure policy and security contact. Its presence signals security maturity and enables ethical hackers to report issues before they are exploited. Required at /.well-known/security.txt.

Low priority

Trigger

When this rule fires

No security.txt file at /.well-known/security.txt; or security.txt present but expired (Expires field in the past)

Applicability gate

Confirm the entity's role before treating this as a duty

This is a readiness rule mapped to JS2 themes. Its presence in the library does not establish that JS2 applies directly to the firm.

  • Insurance Broker: Most independent non-life Category I brokers are not directly in JS2's defined scope. A broker may be directly in scope if it separately meets a listed category, and may face contract or oversight requirements from an in-scope institution. Third-party provisions impose duties on the in-scope financial institution. They do not themselves make every supplier or intermediary directly subject to JS2.
  • Uma Binder Holder: UMA or binder-holder status is not itself listed in JS2's definition. Direct scope depends on another listed capacity; insurer contracts and oversight may create evidence requirements. JS2 paragraph 3.3 concerns juristic persons structured under an insurer or designated insurance group; it is not a blanket rule for every independent UMA or intermediary.
  • Insurer: An insurer as defined in the Insurance Act is directly in scope of JS2 from 1 June 2025. Apply proportionality and distinguish the insurer's own duty from requirements it places on third parties.

Citation

Mapped source

This control maps to the public instruments below. The mapping does not establish entity applicability.

Section
RFC 9116 / NCSC guidance / Joint Standard 2 best practice
Legislation
  • Joint Standard 2 of 2024 (best practice)

Remediation

How to close the gap

Create a security.txt file at /.well-known/security.txt. Include: Contact: (email or URL), Expires: (12 months forward), Preferred-Languages: en, Encryption: (GPG key URL if available).

Evidence required

Evidence to prepare if this control applies

  • security.txt file accessible at /.well-known/security.txt
  • Expires field set at least 30 days in the future

Automated assessment

Verified by the Provantis cyber scanner. Machine checks performed:

  • SECURITY_TXT