Responsible Disclosure Policy



Read Time

4 min 39 sec



The information on this page is intended for security researchers interested in reporting security vulnerabilities to the NBX security team. If you are a customer and have a question about security or a password or account issue, please contact us through the support channels available for your product.


Security is core to our values, and we value the input of hackers acting in good-faith to help us maintain a high standard for the security and privacy for our users. This includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good-faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.


This policy covers all NBX services, or more technically defined as **

Excluded domains:

Please note that most reports we receive have little or no security impact or are already known. To avoid a disappointing experience when contacting us, please take a moment and consider if the issue you want to report actually has a realistic attack scenario.

More specifically, we ask you to not submit issues regarding:

  • Vulnerabilities requiring MitM, or the need for physical access to a user’s browser, phone, or email account, as well as issues on rooted or jailbroken smartphones.
  • Security hygiene issues, such as, but not limited to, SPF, DMARC, CAA, HTTP headers, SRI, cipher suites etc.
  • Cryptographic implementations, such as cipher suites.
  • Non-sensitive data disclosure, for example server version banners.
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions.
  • Rate limiting or bruteforce issues.
  • Session/token management.
  • Text injection.


As a contributor to making our platform and customer experience more safe and secure we will give you a reward in Bitcoin, and possibly a seat at our Wall of Fame. Our severity definitions can be seen below.

Critical: $2000 - $5000

Critical severity issues present a direct and immediate risk for our customers, NBX's infrastructure, operations or reputation. The ability to steal funds, bypass authentication or gather massive amounts of sensitive customer data, without user interaction, is defined as critical.

High: $500 - $2000

High severity issues are critical, but the difference could be the need for additional requirements or conditions, such as e.g. the need to manipulate users.

Medium: $25 - $100

Medium severity issues could be more theoretical and might result in a successful exploit at a future stage. Vulnerabilities regarding extracting lesser sensitive information about NBX or customers also goes into this severity level.

Low: $10 - $25

Low severity issues could be the ability to collect limited amounts of data, or may violate an expectation for how something is intended to work, but yields little to no direct advantage for an attacker.


When working with us according to this policy, you can expect us to:

  • Extend Safe Harbor for your vulnerability research that is related to this policy.
  • Work with you to understand and validate your report, including a timely initial response to the submission.
  • Work to remediate discovered vulnerabilities in a timely manner; and
  • Recognize your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change

Official Communications Channels

Our official communication channel is maintained within our security.txt file, located here:, alternatively, you may contact NBX by sending an email to [email protected]. The issues are triaged by a Security Analyst before being escalated to the appropriate team. If you feel that the email should be encrypted, our PGP key is available here.

Ground Rules

To encourage vulnerability research and to avoid any confusion between legitimate research and malicious attack, we ask that you attempt, in good faith, to:

  • Play by the rules. This includes following this policy and any other relevant agreements.
  • Report any vulnerability you’ve discovered promptly.
  • Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience.
  • Use only the Official Channels to discuss vulnerability information with us.
  • Handle the confidentiality of details of any discovered vulnerabilities according to our Disclosure Policy.
  • Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope.
  • If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a proof of concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information.
  • You should only interact with test accounts you own or with explicit permission from the account holder.
  • Do not engage in extortion.

Safe Harbor

When conducting vulnerability research according to this policy, we consider this research conducted under this policy to be:

  • Authorized in view of any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good faith violations of this policy.
  • Authorized in view of relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls.

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.

Disclosure Policy

  • Coordinated Disclosure: A researcher can share details of the vulnerability after a fix has been applied and the program owner has provided permission to disclose, or after 90 days from submission, whichever is sooner,
  • Discretionary Disclosure: The researcher or the program owner can request mutual permission to share details of the vulnerability after approval is explicitly received, or
  • Non-Disclosure: Researchers are required to keep vulnerability details and the existence of the program itself confidential.

NBX generally follows coordinated or discretionary disclosures based on the impact or involved third parties. Until a disclosure has been agreed upon, you are not allowed to publicly discuss or publish any vulnerabilities until having received explicit permission to do so. Depending on the discovered vulnerability, and if it involves a partner outside the control of NBX, a suitable disclosure method is chosen from these two options.

Security Team, NBX.

Cookie Consent

By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.