# Security Information

{% hint style="info" %}
If you wish to report any security-related issues, please email us directly at **<info@nodeset.io>**
{% endhint %}

### Penetration Testing

The NodeSet Dashboard undergoes regular penetration tests by leading independent security professionals. However, nodeset.io does not interact with any assets and is therefore closed-source for maximum security. Due to this and the sensitive nature of these security reports, these reports will not be released publicly. However, for the sake of transparency, we will list the firms engaged in penetration testing here.

### Bug Bounties

Note that, in order to be eligible for a bug bounty, you must provide a proof of concept and, if necessary, work with our developers to successfully demonstrate the issue.

Rewards for successfully replicated issues in the NodeSet Dashboard are awarded according to severity as classified by the [Immunefi Vulnerability Severity Classification System](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/) for websites and apps:

<table><thead><tr><th width="121">Severity</th><th width="142">Amount (USD)</th></tr></thead><tbody><tr><td>Critical</td><td>$20,000</td></tr><tr><td>High</td><td>$10,000</td></tr><tr><td>Medium</td><td>$5,000</td></tr></tbody></table>

In addition, because NodeSet currently must retain pre-signed exit messages from our Ethereum node operators, the NodeSet Dashboard has a special level of bug bounty set at $50,000 USD specifically for exploits which demonstrate full access to this data.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nodeset.io/nodeset-dashboard/security-information.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.