Reporting security vulnerabilities

Last updated: 11 October 2026

This English version is a convenience translation. Only the German version is legally binding: Deutsche Fassung.

What this is about

RegStack is used by supervised financial institutions for their outsourcing, risk and compliance management. If you believe you have found a security vulnerability in RegStack, please report it to us confidentially so that we can fix it before it is exploited. We thank everyone who helps us in this way.

How to report a vulnerability

Write to info@regstack.de with the subject “Security”. Reports in German or English are welcome. Helpful information includes:

  • the affected URL or component,
  • a description and the steps to reproduce the issue,
  • your assessment of the potential impact,
  • how we can reach you with questions.

Please do not send us any data you came across — only describe where it was visible. We do not currently offer encrypted submission (PGP). If your report contains particularly sensitive details, first send us a short message without those details; we will then agree on a secure way to transmit them.

Scope

This policy applies to regstack.de, www.regstack.de and app.regstack.de and to the associated RegStack interfaces (APIs).

Third-party systems, such as those of our hosting, database or email providers, are not covered: please report vulnerabilities in their services directly to the respective provider. A misconfiguration of these services on our side, however, does belong here.

Please agree penetration tests on behalf of a customer institution, for example under contractual audit and testing rights, with us in advance through the contractually agreed contacts. This policy does not replace a testing agreement.

What we expect from you

  • Do not access, copy, modify or delete data of customer institutions or their users beyond what is strictly necessary to demonstrate the vulnerability. If you come across other people’s data, stop, report it to us and delete anything of it you have stored.
  • Only test with accounts that belong to you or have been released for you, and do not use anyone else’s credentials. There is no open registration; without your own account, please limit yourself to the publicly accessible parts.
  • No attacks on availability (denial of service, load or mass tests), no brute forcing of passwords or 2FA codes and no automated scans with a high request volume.
  • No social engineering (such as phishing), no physical attacks and no attacks on our employees, customers or service providers.
  • No malware, no backdoors and no permanent changes. Do not exploit a vulnerability further than necessary to demonstrate it, for example for privilege escalation or to move into other systems.
  • Keep the vulnerability confidential until it has been fixed or we have agreed on a date for disclosure.

What we commit to

  • We acknowledge receipt of your report within five business days.
  • We review the report, share our assessment with you and keep you informed until the issue is fixed.
  • We fix confirmed vulnerabilities as quickly as their risk requires and agree the timing of any disclosure with you: as a rule after the fix, at the latest 90 days after your report, unless we agree otherwise.
  • We do not pass your contact details on to third parties without your consent, unless we are legally obliged to do so.
  • On request, we credit you as the discoverer after the fix.
  • We do not currently offer a bug bounty programme with monetary rewards.

Legal

If you act in good faith and comply with this policy, we will not file a criminal complaint, submit a request for prosecution or pursue civil claims against you because of your research. This does not apply if you evidently act with harmful intent, for example by exfiltrating data, impairing systems or demanding something in return for not publishing the vulnerability.

This commitment is given by Lumera Technologies (see legal notice). It does not bind third parties — neither customer institutions nor our service providers nor law enforcement authorities. If you are unsure whether an action is covered by this policy, ask us beforehand.