Introduction

Tenable supports responsible disclosure of security vulnerabilities, and we are committed to working with researchers to fully understand and resolve them. Tenable believes in responding quickly to reports, maintaining communication with researchers, and providing a solution in short order.

Response Targets

Tenable will make a best effort to meet the following response targets for hackers participating in our program:

• Time to first response/acknowledgment (from report submit) - 5 business days
• Time to triage (from report submit) - 10 business days
• Time to resolution - depends on severity and complexity

The team will keep you informed about our progress throughout the process.

Disclosure Policy

• Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
• Follow HackerOne's disclosure guidelines.

Program Rules

• Submit one vulnerability per report
• Include a description of the issue explaining the vulnerability, including the impact to the user(s) or system. This should clearly describe how the issue crosses privilege boundaries. The affected product or resource (e.g., Tenable.io, Nessus, Tenable.sc, web site), the software version, and the platform you are using (e.g., Windows 10, Debian Linux).
• A proof-of-concept or functional exploit that demonstrates the issue. If a proof-of-concept is not available, please include any relevant logs generated from your testing.
• Any caveats or conditions required to exploit the issue. Indicate if there are any non-default system settings, custom configurations, required user interaction, or anything else that would limit the attack.
• Social engineering of any type (e.g. phishing, vishing, smishing) is strictly prohibited.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• Clickjacking or lack of Framing protection in headers
• Unauthenticated/logout/login CSRF
• Previously known vulnerable libraries without a new working Proof of Concept
• Missing best practices in SSL/TLS and Header configuration.
• Any activity that could lead to the disruption of our services (i.e., DoS, DDoS, etc).
• Recently disclosed zero day vulnerabilities
• Headers which disclose versioning information
• Issues related to email spoofing
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• Tabnabbing
• Physical or social engineering attempts (this includes phishing attacks against Tenable employees)
• Missing Cookie Flags
• Self XSS or similar vulnerabilities
• Bugs requiring exceedingly unlikely user interaction

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Tenable and our users safe!