Legal

Besso Energy: Coordinated Vulnerability Disclosure (CVD) Policy

Besso Energy takes the security of its systems and its clients' data seriously. If you are a security researcher and you believe you've found a vulnerability in one of our systems, we'd like to hear from you and we'll work with you to fix it. This policy explains how to report, what we ask of you, and what you can expect from us.

How to report

Email [email protected] with:

  • a description of the vulnerability and its potential impact;
  • clear steps to reproduce it (a proof-of-concept, affected URL or component);
  • your name or handle, and how you'd like to be contacted (and credited, if you wish).

You can report in English or Dutch. If you need to send sensitive details encrypted, ask us for a PGP key.

Scope

In scope: besso.be, the Besso web application and API, and infrastructure operated by Besso.

Out of scope (please don't test these, and report them to the relevant provider instead):

  • third-party services we use (e.g. Google Workspace, Cloudflare, Supabase, TigerData, GitHub, Vercel); report to that provider's own disclosure programme;
  • denial-of-service (DoS/DDoS), volumetric or brute-force attacks;
  • social engineering, phishing, or physical attacks against Besso staff or offices;
  • reports from automated scanners without a demonstrated, exploitable impact;
  • missing best-practice hardening (e.g. header tweaks) with no concrete vulnerability.

What we ask of you (rules of engagement)

  • Act in good faith and avoid privacy violations, data destruction, or service disruption.
  • Access only the minimum needed to demonstrate the issue. Do not view, copy, store, modify or exfiltrate data that isn't yours, and do not access other users' data.
  • Give us a reasonable chance to fix it before disclosing publicly, and coordinate any public disclosure with us (see timeline).
  • Comply with applicable law, including the Belgian coordinated-vulnerability-disclosure framework (see below).

What you can expect from us (our commitment)

  • Safe harbour: if you make a good-faith effort to comply with this policy, we will not pursue or support legal action against you for your research, and we'll treat your report as authorised access.
  • We'll acknowledge your report within 3 business days, give you an initial assessment within about 10 business days, and keep you informed as we work on a fix.
  • We'll remediate as quickly as the risk warrants and, with your permission, credit you once the issue is resolved.

Coordinated disclosure timeline

We aim to agree public disclosure with you once a fix is in place, typically within 90 days of the report. If a fix is taking longer, we'll stay in touch and agree a reasonable timeline together.

Belgian legal framework (CCB / CERT.be)

Belgium has a legal framework for coordinated vulnerability disclosure, overseen by the Centre for Cybersecurity Belgium (CCB). To benefit from its legal protection, a researcher must act without fraudulent intent or intent to cause harm, must not go beyond what is necessary to report the issue, and should notify the CCB (CERT.be) in addition to notifying us. We support researchers who follow this framework. (This is a general summary, not legal advice. The current conditions are published by the CCB at ccb.belgium.be / cert.be.)

Contact

Security owner: Frederik Vanmaele. Reports: [email protected].

Version 1.0, 2026-08-17. Reviewed annually and on any change to systems or contacts.