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 *.nbx.com/*
Excluded domains:
ravn.nbx.com
signicat.nbx.com
custody.nbx.com
auth.nbx.com
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:
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 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 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 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 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:
Our official communication channel is maintained within our security.txt file, located here: https://app.nbx.com/.well-known/security.txt, 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.
To encourage vulnerability research and to avoid any confusion between legitimate research and malicious attack, we ask that you attempt, in good faith, to:
When conducting vulnerability research according to this policy, we consider this research conducted under this policy to be:
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.
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.
