# Security Policy

Although we strive to create the most secure products possible, we are not perfect. If you happen to find a security vulnerability in one of our services, we would appreciate letting us know and allowing us to respond before disclosing the issue publicly. We take security seriously, and we will try to review and reply to every legitimate security report personally within 24 hours. Other reports submitted will not be replied to.

## Supported Versions

### Web

Only the latest version of Calypso (that is, what is present in the `trunk` branch) is supported. Calypso is continuously deployed shortly after each merge to trunk, multiple times per day.

### WordPress Desktop

Only the latest version of WordPress desktop is supported. To receive security updates, please update to the latest available version of WordPress desktop.

## Reporting a Vulnerability

[Calypso](https://developer.wordpress.com/calypso/) is an open-source wp-admin replacement. Our HackerOne program covers the software.

<!--eslint ignore no-emphasis-as-heading-->

**For responsible disclosure of security issues and to be eligible for our bug bounty program, please submit your report via the [HackerOne](https://hackerone.com/automattic) portal.**

Our most critical targets are:

- wordpress.com
- cloud.jetpack.com

For more targets, see the `In Scope` section on [HackerOne](https://hackerone.com/automattic).

<!--eslint ignore no-emphasis-as-heading-->

_Please note that the **WordPress software is a separate entity** from Automattic. Please report vulnerabilities for WordPress through [the WordPress Foundation's HackerOne page](https://hackerone.com/wordpress)._

## Guidelines

We're committed to working with security researchers to resolve the vulnerabilities they discover. You can help us by following these guidelines:

- Follow [HackerOne's disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).
- Pen-testing Production:
  - Please **setup a local environment** instead whenever possible. Most of our code is open source (see above).
  - If that's not possible, **limit any data access/modification** to the bare minimum necessary to reproduce a PoC.
  - **_Don't_ automate form submissions!** That's very annoying for us, because it adds extra work for the volunteers who manage those systems, and reduces the signal/noise ratio in our communication channels.
  - To be eligible for a bounty, all of these guidelines must be followed.
- Be Patient - Give us a reasonable time to correct the issue before you disclose the vulnerability.

We also expect you to comply with all applicable laws. You're responsible to pay any taxes associated with your bounties.