DigitalOcean looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

Create dedicated testing account

Important note: Please create dedicated testing accounts for any DO engagement. This allows our teams to know if any anomalous activity is associated with H1 or potential bad actors.

1. Create a dedicated account for testing by clicking here

2. Register the account using your H1 email address w/ the following format: yourh1username@ wearehackerone.com

3. Choose a username of similar format.

4. To avoid any undue consumption, spin down resources after you have finished testing.

If you are testing with an account that does not use a @wearehackerone.com email address, we may take action against it for perceived malicious activity (account locks, bans, etc).

Thanks and happy hacking!

Response Targets

DigitalOcean will make a best effort to meet the following SLAs for hackers participating in our program:

| Type of Response | SLA in business days |

| ------------- | ------------- |

| First Response | 2 days |

| Time to Triage | 2 days |

| Time to Resolution | depends on severity and complexity |

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

• Follow HackerOne's disclosure guidelines.

Some DOs and DON'Ts

===================

Violation of any of these rules may result in removal from the program.

• DO only test against your own accounts

• DO make a good faith effort to avoid privacy violations, destruction of data or service degradation

• DO NOT exploit vulnerabilities beyond a PoC. That means no SQL dumps, no pulling unnecessary files

• DO NOT perform any social engineering or physical attacks against DigitalOcean or our users

• DO NOT perform DoS or DDoS attacks

• DO NOT attack our end users or their resources (Droplets, databases, Spaces, or otherwise)

• DO NOT do any testing that creates support tickets

Acceptable PoCs

===============

• Command Execution: whoami, hostname, uname

• File Reads: /etc/hostname

• File Writes: /tmp/h1_<your HackerOne username here>

• SQL Injection: Basic evidence (e.g. ' OR 1='1 causes all rows to return and ' AND 0='1 causes zero rows to return) is fine, but feel free to extract the username of the database user as well

Out of Scope

============

For *.digitaloceanspaces.com

Security vulnerabilities in the contents of an individual user's spaces are out of scope

All other DigitalOcean domains or properties not listed are out of scope, including subdomains. All domains or properties hosted on DigitalOcean and controlled by third parties are out of scope (e.g. customer droplets, content stored in customer-owned spaces, etc.).

Additionally, we're not interested in the following types of results:

• Support tickets (due to the load on our support teams--please DO NOT perform any testing on, or create any, support tickets. Thanks!)

• Rate limit bypasses, with the exception of those that have a direct security impact

• Missing SPF/DMARC/DKIM settings on non-email DigitalOcean domains.

• Publicly known processor side-channel attacks

• Any physical attempts against DigitalOcean property or data centers

• Social engineering / phishing

• DigitalOcean corporate infrastructure

• Previously known vulnerable 3rd party software (such as old Apache server) without a working POC

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 on pages with no sensitive actions

• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions

• Attacks requiring MITM or physical access to a user's device.

• Previously known vulnerable libraries without a working Proof of Concept.

• Comma Separated Values (CSV) injection without demonstrating a vulnerability.

• Missing best practices in SSL/TLS configuration.

• Any activity that could lead to the disruption of our service (DoS).

• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

• Rate limiting or bruteforce issues on non-authentication endpoints

• Missing best practices in Content Security Policy.

• Missing HttpOnly or Secure flags on cookies

• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).

• Tabnabbing

• Open redirect - unless an additional security impact can be demonstrated

• Issues that require 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 DigitalOcean and our users safe!