Trust

Security policy and vulnerability disclosure

Updated

If you think you have found a security vulnerability in anything halfnine makes, email To be decided: security contact address. Please do not open a public issue or post details until we have had a chance to fix it. We will acknowledge your report, keep you informed, and credit you if you want to be credited.

halfnine is at an early stage: the controller, runtime, local supervisor and cloud alarm service are in development and not yet sold. This policy applies now to our website and any code we publish, and will apply to each product as it ships.

What is in scope?

  • The halfnine website and any halfnine-operated web service.
  • Source code and tools published under halfnine’s GitHub organisation.
  • halfnine hardware, firmware, runtime, local supervisor and cloud alarm service, once released. To be decided: list of products and versions in scope, with support end dates.

Out of scope:

  • Third-party services we use (report those to the vendor; we are happy to help coordinate if the issue affects our users).
  • Findings that need physical access to an unlocked device plus admin credentials, unless they bypass a protection we claim to provide.
  • Volume-based denial of service, spam, and social engineering of staff.
  • Reports from automated scanners with no demonstrated impact.

How do I report a vulnerability?

Email To be decided: security contact address
Encryption To be decided: OpenPGP key URL and fingerprint
Languages English To be decided: other languages
Machine-readable contact /.well-known/security.txt (see below)

If you cannot use email, To be decided: alternative channel, for example a web form. We do not require you to sign anything or to register for a bug bounty to report.

What should I include?

The more of this you can give, the faster we can act:

  • Product and version: hardware revision, firmware or software version, or the URL affected.
  • Type of issue: for example authentication bypass, remote code execution, information disclosure.
  • Steps to reproduce: exact requests, configuration, and any proof-of-concept code.
  • Impact: what an attacker could do, and under what conditions (network access, credentials, physical access).
  • Whether it is being exploited, if you know. This changes how fast we must act and whom we must notify (see the CRA section below).
  • How to reach you, and whether and how you want to be credited.

Please test only against systems you own or have permission to test, and use the minimum access needed to demonstrate the issue.

What will halfnine do, and how fast?

Step Target
Acknowledge your report To be decided: e.g. within N business days
Initial assessment and severity To be decided: e.g. within N days
Status updates while we work on it To be decided: e.g. at least every N days
Fix or mitigation for critical issues To be decided: target
Fix or mitigation for other issues To be decided: target
Public advisory When a fix is available, coordinated with you

These targets are placeholders until halfnine has a security team and products in the field; we will not publish numbers we cannot meet.

Security updates for supported products will be free of charge and will come with an advisory explaining what changed and what you need to do. To be decided: advisory location, for example a security advisories page and RSS feed; CVE assignment arrangement.

How does disclosure work?

We follow coordinated disclosure: we fix first, then publish, and agree the timing with you.

  • Our default is to publish an advisory once a fix is available. To be decided: maximum embargo, for example 90 days from report, after which you may publish even without a fix.
  • If we learn the vulnerability is being actively exploited, we may need to move faster and will tell you before we do.
  • We credit reporters by name or handle in the advisory unless you ask us not to. To be decided: acknowledgments page URL.

Safe harbour

If you make a good-faith effort to follow this policy, we will consider your research authorised, we will not pursue or support legal action against you for it, and if a third party takes action against you over research done under this policy, we will make it known that you acted with our authorisation.

Good faith means that you:

  • report the issue to us promptly and give us reasonable time to fix it before disclosing;
  • avoid privacy violations, destruction of data, and interruption or degradation of service, including on industrial equipment you do not own;
  • access only the data needed to demonstrate the issue, do not keep it, and do not share it;
  • do not use the issue for any purpose other than reporting it to us;
  • comply with applicable law.

If you are unsure whether something you plan to do is within this policy, ask us first at To be decided: security contact address.

To be decided: legal review of safe-harbour wording for each jurisdiction halfnine sells in.

How does the EU Cyber Resilience Act apply?

The Cyber Resilience Act, Regulation (EU) 2024/2847, sets cybersecurity duties for manufacturers of products with digital elements sold in the EU. Two parts bear directly on this page:

  • Vulnerability handling. Annex I, Part II requires manufacturers to put in place and enforce a coordinated vulnerability disclosure policy, to provide a contact address for reporting vulnerabilities, and to distribute security updates without delay and free of charge, with advisory information. Article 13 requires a single point of contact for users and a support period of normally at least five years.
  • Reporting to authorities. Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents affecting their products. Reports go through ENISA’s Single Reporting Platform to the national CSIRT of the manufacturer’s main establishment (ENISA, European Commission).

The deadlines for those reports, per the European Commission:

Report Deadline
Early warning Within 24 hours of becoming aware
Notification Within 72 hours of becoming aware
Final report, actively exploited vulnerability No later than 14 days after a corrective measure is available
Final report, severe incident Within one month of the notification

The CRA’s main requirements apply from 11 December 2027.

What this means for you as a reporter: if you tell us a vulnerability is being actively exploited, halfnine may have a legal duty to notify authorities within 24 hours. We will tell you when we do. To be decided: confirm policy on sharing reporter identity with authorities.

To be decided: confirm halfnine’s role (manufacturer) and which products are in CRA scope once they ship; main establishment and coordinating CSIRT; product support periods.

security.txt

We publish a machine-readable contact file at /.well-known/security.txt, following RFC 9116. The RFC requires the Contact and Expires fields, recommends an Expires date less than a year ahead, requires the file to be served over HTTPS as text/plain; charset=utf-8, and recommends an OpenPGP signature with a Canonical field.

Our file will look like this once the placeholders are filled:

Contact: mailto:[TBD: security contact address]
Expires: [TBD: date less than one year ahead, e.g. 2027-11-01T00:00:00.000Z]
Encryption: [TBD: https URL of OpenPGP key]
Preferred-Languages: en
Canonical: https://[TBD: domain]/.well-known/security.txt
Policy: https://[TBD: domain]/security
Acknowledgments: [TBD: https URL of acknowledgments page]

If the file’s Expires date has passed, treat its contents as stale and use the address on this page.

Changes to this policy

We will update this page as products ship and placeholders are filled, and record the date at the top. To be decided: changelog of policy versions.

Sources

  1. RFC 9116: A File Format to Aid in Security Vulnerability Disclosure, accessed 2026-11-19
  2. Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex, accessed 2026-11-19
  3. European Commission: CRA reporting obligations, accessed 2026-11-19
  4. ENISA: The CRA Single Reporting Platform is launched, accessed 2026-11-19