Responsible disclosure: report a security vulnerability to Pilae

Found a vulnerability in a Pilae service? Write to security@pilae.com. We acknowledge every report, keep you informed while we fix it and do not take action against good-faith research.

Report a vulnerabilityRead the scope

In short

  • Report vulnerabilities to security@pilae.com. Acknowledgement within two business days, regular updates and safe harbour for good-faith research.
  • In scope are pilae.com, the Pilae console, the Pilae Agent, the gate of the private network and the infrastructure of Pilae Cloud.
  • Out of scope are denial-of-service testing, social engineering of our staff or customers, physical attacks, spam, and findings from automated scanners without a demonstrated impact.
Report to
security@pilae.com
Acknowledgement
Within two business days
Languages
English, French, German
security.txt
/.well-known/security.txt

Where to report, and what is in scope

One address, read by an engineer, in English, French or German.

security@pilae.com

Also published in /.well-known/security.txt, following RFC 9116.

No paid bug bounty. We do not run a paid programme today. Once the fix is out, the advisory credits you by name, if you wish.

Scope

Out of scope

  • Denial-of-service testing
  • Social engineering of our staff or customers
  • Physical attacks and spam
  • Automated scanner findings without a demonstrated impact
  • A customer’s apps and data: if you come across them, stop and tell us

A flaw in an open-source app itself, such as Nextcloud or n8n, belongs with its project. Report it there and tell us too: we protect our customers while the fix is prepared.

Safe harbour: research in good faith and within this policy is authorised. No complaint, no legal action.

What to put in the report

  • The affected URL, component or version
  • The steps to reproduce, in order
  • The impact you observed
  • Any proof of concept, screenshots or logs
  • How you would like to be credited

Found something? Tell us.

Write to security@pilae.com. An engineer reads every report and replies within two business days.

Report a vulnerability

  • Go deeperSecurityPrivate networking, hardened machines, named access, tracked advisories and a full audit log, built to ISO 27001 controls.
  • CompareWhere each alternative stopsTen alternatives and Pilae, across the thirteen jobs an open-source estate needs done.
  • CheckWhat each plan includesStarter, Business and Enterprise, side by side.

What happens after you report

  1. Acknowledge

    An engineer confirms receipt within two business days and gives you a reference.

  2. Assess

    Within five business days we confirm whether we can reproduce it and how severe it is.

  3. Fix

    We fix it, check whether any customer is affected and notify them as their contracts require. You receive an update at least every ten business days.

  4. Disclose

    We agree a publication date with you. Our default is ninety days from your report, or earlier once the fix is deployed.

  5. Credit

    The advisory names you, if you wish, and describes the issue and the fix.

How to report a vulnerability

Write to security@pilae.com. The same address is published in our security.txt file at /.well-known/security.txt, following RFC 9116. We read reports in English, French and German.

A useful report includes:

  • the affected URL, component or version;
  • the steps to reproduce, in order;
  • the impact you observed, such as data you could read or actions you could take;
  • any proof of concept, screenshots or logs;
  • how you would like to be credited, if at all.

Scope

In scope are pilae.com, the Pilae console, the Pilae Agent, the gate of the private network and the infrastructure of Pilae Cloud.

Out of scope are denial-of-service testing, social engineering of our staff or customers, physical attacks, spam, and findings from automated scanners without a demonstrated impact. A customer’s apps and data are not yours to test: if you come across them, stop and tell us.

A flaw in an open-source app itself, such as Nextcloud or n8n, belongs with its project. Report it through the project’s own process and tell us too. We protect our customers while the fix is prepared, and the Pilae Agent plans the patched release for every affected deployment once it exists. See security for how fixes reach customers.

Safe harbour

If you act in good faith and within this policy, we consider your research authorised. We do not file a criminal complaint or take legal action against you. In return, we ask you to:

  • access no more data than you need to show the issue, and delete what you obtained once it is reported;
  • avoid degrading our services or anyone else’s;
  • give us reasonable time to fix the issue before you publish, ninety days by default;
  • not use the issue for any other purpose.

We cannot waive the rights of third parties, such as customers or hosting providers. If you are unsure whether something is in scope, ask us at security@pilae.com first.

Our commitments

We acknowledge your report within two business days, send a first assessment within five business days and update you at least every ten business days until the issue is closed. Where a customer’s data is affected, we notify that customer as their data processing agreement requires. Once the fix is out, we publish an advisory and credit you if you wish.

Our commitments to researchers

Written into your contract with Pilae, under Swiss law.

  1. Acknowledgement

    Within two business days of your report.

  2. First assessment

    Within five business days: reproduced or not, and the severity we assign.

  3. Status updates

    At least every ten business days until the issue is closed.

  4. Coordinated disclosure

    A publication date agreed with you, ninety days from the report by default.

  5. Safe harbour

    No complaint and no legal action against good-faith research within this policy.

Who runs it

Questions

How do I report a security vulnerability to Pilae?

Write to security@pilae.com in English, French or German. Include the affected URL or component, the steps to reproduce, the impact you observed and any proof of concept. The address is also published in our security.txt file at /.well-known/security.txt.

How quickly will Pilae respond?

We acknowledge every report within two business days, send a first assessment within five business days and update you at least every ten business days until the issue is closed.

Does Pilae pay bug bounties?

We do not run a paid bug bounty programme today. We credit researchers by name in our advisories if they wish.

What if the vulnerability is in an open-source app Pilae operates?

Report it to the upstream project through its own security process, and tell us too. We help coordinate the fix, protect our customers while it is prepared and roll it out once it is released.

Found something? Tell us.

Write to security@pilae.com. An engineer reads every report and replies within two business days.