Skip to main content

Reporting a security problem

If you think you have found a security problem in Hosting, tell us. This page is for anyone: a client, a client's tester or an independent researcher.

Our machine-readable contact is published at /.well-known/security.txt.

How to report​

Email support@haak.co with Security at the start of the subject. Include:

  • What you found and where: the address, page or API route.
  • How to reproduce it: the steps, requests or a short proof of concept.
  • What an attacker could do with it, as far as you know.
  • How to reach you, if not by replying to the same address.

Do not include another company's data in the report. If you came across some, say so and describe it instead of copying it.

What we commit to​

  • We acknowledge every report by email, and tell you whether we can reproduce it.
  • We keep you informed while we fix it, and tell you when it is fixed.
  • We credit you when the fix is announced, if you want to be credited.
  • We will not take legal action against you, or ask anyone else to, for research that follows this page in good faith: you stayed in scope, avoided harm to people and data, stopped once you had shown the problem, and gave us a reasonable time to fix it before telling anyone else. If somebody else takes action against you over such research, we will make it known that it was authorised.

In scope​

  • The Hosting panel at https://hosting.haak.co.
  • The Hosting API under https://hosting.haak.co/api/v1, and the OAuth sign-in it uses.
  • The hostingctl command-line client.
  • The platform we run your environments on: how one environment, company or account is kept apart from another, and the access we give you to your own environment (SSH, databases, storage, mail).

Test against your own account and your own company only. If you need a second company to test isolation between companies, ask us and we will set one up.

Out of scope​

  • Other clients' data and environments. Never access, change or keep another company's data. If a problem lets you see it, stop and report it.
  • Denial of service, load or stress testing, and anything that degrades the service for others.
  • Social engineering of our staff or clients, including phishing.
  • Physical attacks on any office or data centre.
  • The applications our clients run on the platform. Report those to the client who runs them.
  • Our providers' own infrastructure, such as the data-centre network the platform runs on.
  • Findings with no security impact on their own, such as a missing header with no demonstrated attack, or version banners.

A client testing their own applications follows Security testing your own environments instead.

No bounty​

We are a small company and do not pay for reports. We will credit you, and we will fix what you find.