Skip to content

Commit

Permalink
Merge branch 'master' of https://github.com/d-leigh/vulnerability-dis…
Browse files Browse the repository at this point in the history 
…closure-policy
  • Loading branch information
@jsulinski
jsulinski committed Jan 10, 2020
2 parents 2e5e979 + 0443250 commit f3f8877
Showing 1 changed file with 72 additions and 70 deletions.
142 changes: 72 additions & 70 deletions README.md
View file
Original file line number Diff line number Diff line change
@@ -1,67 +1,72 @@
# Vulnerability Disclosure Policy

Keeping user information safe and secure is of the utmost importance and a
core company value, and we can't feasibly accomplish that without the help of
external security researchers. Consequently, we have formalized a
vulnerability disclosure policy and reward program in order to be able to show
appreciation for their effort, skill and dedication.
Security is core to our values, and we appreciate the input of security researchers acting in good-faith to help us maintain a high standard for the security and privacy of our users, which 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.

## Rewards
## Expectations

We provide rewards to vulnerability reporters at our discretion. In order to
be eligible for a bounty, your submission must be accepted as valid.
When working with us, according to this policy, you can expect us to:

The guidelines we use to determine the validity of requests and the reward
compensation offered are listed in our awards table.
* Extend Safe Harbor for your vulnerability research that is related to this policy;
* Work with you to understand and validate your report, including a timely initial response to the submission; and
* Work to remediate discovered vulnerabilities in a timely manner.

## Official Channels

Any vulnerability deemed to be in-scope, according to this policy, should be reported directly to this program through the Federacy platform. All communications between the researcher and program team regarding any reported vulnerability should be confined to the comments section of the corresponding report.

## Awards

| Severity | Description | Examples |
|---|---|---|
| Critical | Systemic compromise | XXE Injection and SQL Injection with significant impact; <br/>RCE and Vertical Authentication Bypass. |
| High | Full access to other user's private data | IDOR, Stored XSS and CSRF with significant impact; <br/>Internal SSRF and Lateral Authentication Bypass. |
| Medium | Limited access to other user's private data | IDOR, Reflective XSS and CSRF with impact. |
| Low | Configuration issues and other <br/>vulnerabilities with limited impact | SSL misconfigurations; <br/>XSS and CSRF with limited impact. |

We award vulnerability reports at our discretion. In order to be eligible for a bounty, your submission must be accepted as in-scope and valid.

The guidelines we use to determine the validity of reports are outlined below.

### Reproducibility

Our engineers must be able to reproduce the vulnerability you have reported.
Reports that include clearly written explanations and a working proof of
concept are more likely to receive awards.
Our engineers must be able to reproduce the vulnerability you have reported. Reports that include clearly written explanations and a working proof of concept are more likely to be awarded.

### Severity and Priority

Our focuses for security research are listed as 'in-scope' with their priority
indicated. More impactful bugs will be receive larger awards.
Generally, more impactful bugs will receive higher awards. Review the chart above for examples of award levels for similar vulnerabilities.

### Rewards
### Award Factors

Reward amounts may vary depending upon the severity of the vulnerability
reported and quality of the report. If we receive multiple reports of the same
vulnerability, the first clear, reproducible report will be rewarded.
The amount awarded may vary depending upon the severity of the vulnerability reported and quality of the report. If we receive multiple reports of the same vulnerability, the first clear, reproducible report will be awarded.

We may decide to pay higher rewards for clever or severe vulnerabilities,
decide to pay lower rewards for vulnerabilities that require unusual user
interaction, decide that a single report constitutes multiple bugs, or that
multiple reports are so closely related that they only warrant a single
reward.
We may decide to award higher for clever or more impactful vulnerabilities, decide to award lower for vulnerabilities that require unusual user interaction, decide that a single report constitutes multiple bugs or that multiple reports are so closely related that they only warrant a single award.

## Disclosure

We would very much like to highlight the incredible work that external
researchers do for us and one way we can do that is to publicly disclose
vulnerabilities in a timely manner with proper attribution. To facilitate
this, please:
**Discretionary Disclosure:** Researchers may only share vulnerability details with third parties after requesting and receiving explicit permission from the Program.

* Share the security issue with us in detail
* Give us a reasonable time to remediate the issue before making any information about it public.
* When we have remediated the issue, remain in communication to coordinate public disclosure timelines.
## Guidelines

## Guidelines for investigating and reporting bugs
To encourage vulnerability research and to avoid any confusion between legitimate research and malicious attack, we ask that you attempt, in good faith, to:

* Be clear and succinct, a short proof-of-concept link is invaluable. Visit the Bug Hunter University articles to learn more about sending good vulnerability reports.
* Be respectful of our existing applications. Respect their Terms of Service and avoid scanning techniques that are likely to cause degradation of service to other customers.
* Do not access or modify our data or our users' data, without explicit permission of the owner. Only interact with your own accounts or test accounts for security research purposes.
* Contact us immediately if you do inadvertently encounter user data. Do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability.
* Act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services (including denial of service).
* **Otherwise comply with all applicable laws.**
* **Play by the rules.** Adhere to this policy and any other relevant agreements, e.g., Terms of Service;
* Report any vulnerability you’ve discovered promptly;
* Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
* Use only the Official Channels to discuss vulnerability information with us;
* Handle the confidentiality of details of any discovered vulnerabilities according to our Disclosure Policy;
* Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
* If a vulnerability provides unintended access to user data, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information: Cease testing and submit a report immediately;
* Only interact with accounts you own unless given explicit permission by the account holder;
* Do not engage in extortion.
* Be clear and succinct—a short proof-of-concept link is invaluable;
* Never attempt non-technical attacks—such as social engineering, phishing, or physical attacks—against our employees, users, or infrastructure; and
* Do not view, alter, save, store, transfer, or otherwise access our data or the data of our users without explicit permission.

## In Scope
We may modify the terms or terminate this program at any time.

The applications listed under 'in-scope' are explicitly eligible for the bounty program.
## In-Scope

Any design or implementation issue that substantially affects the confidentiality or integrity of user data is likely to be in scope for the program. Common examples include:
Any design or implementation issue that substantially affects the confidentiality or integrity of user data is likely to be considered in-scope. Common examples include:

* Cross-site scripting.
* Cross-site request forgery.
Expand All @@ -70,63 +75,60 @@ Any design or implementation issue that substantially affects the confidentialit
* Server-side code execution bugs.
* Circumvention of our permissions model.
* SQL injection.
* XML external entity Attacks.
* XML external entity attacks.

While this list represents our primary focus for security research, we are interested in reports for all of our software and dependencies especially if it impacts reasonably sensitive user data. This can include any open source libraries, software, or third-party components. At our discretion, we will issue rewards for reports not included in the in-scope list.
While this list is reflective of the research we prioritize, it should not be considered exhaustive. Any report that concerns the possible compromise of sensitive user data or our systems is of interest. By extension, this includes the reporting of serious security weaknesses in any dependency—such as open source libraries, software, or third-party components—actively used in the development of our properties and/or products shared below.

## Out of Scope
## Out-of-Scope

The applications listed under 'out of scope' are explicitly ineligible. We will not disclose vulnerabilities reported regarding out of scope applications, nor will we issue rewards for them.

In addition, the following issues are outside of the scope of our rewards program:
The following issues are explicitly outside the scope of this program:

* Policies on presence/absence of SPF/DMARC records.
* Password, email and account policies, such as email id verification, reset link expiration, and password complexity.
* Password, email and account policies, such as email id verification, reset link expiration, and password complexity.
* Logout cross-site request forgery.
* Attacks requiring physical access to a user's device.
* XSS on any site other than those listed as 'in scope'.
* Attacks that require attacker app to have the permission to overlay on top of our app (e.g., tapjacking).
* Vulnerabilities that require a potential victim to install non-standard software or otherwise take active steps to make themselves be susceptible.
* XSS on any site other than those listed as 'in-scope'.
* Attacks that require an exploitation tool to overlay on top of our app (e.g., tapjacking).
* Vulnerabilities that require a potential victim to install non-standard software or otherwise take active steps to make themselves susceptible.
* Vulnerabilities affecting users of outdated browsers or platforms.
* Social engineering of our employees or contractors.
* Any physical attempts against our property or data centers.
* Presence of autocomplete attribute on web forms.
* Missing cookie flags on non-sensitive cookies.
* Any access to data where the targeted user needs to be operating a rooted mobile device.
* Any access to data where the targeted user needs to be operating a rooted mobile device.

The following issues are outside the scope of our rewards program unless they are accompanied by evidence of exploitability:
The following issues are outside the scope of our program, unless they are accompanied by evidence of exploitability:

* Use of a known-vulnerable library.
* Missing best practices.
* Insecure SSL/TLS ciphers.
* Missing security headers which do not lead directly to a vulnerability.
* Lack of CSRF tokens (unless there is evidence of actual, sensitive user action not protected by a token).
* Missing security headers, which do not directly lead to a vulnerability.
* Lack of CSRF tokens, except when there is evidence of a sensitive user-action not protected by a token.
* Host header injections.
* Reports from automated tools or scans that haven't been manually validated.
* Presence of banner or version information unless correlated with a vulnerable version.

For more additional information about issues that are commonly out of scope, refer to Google Bughunter University.
* Presence of banner or version information, unless a vulnerable version.

## Known Issues

Any issues already known to us will be published as a Known Issues list. These vulnerabilities are considered out of scope, but additional reports of them may qualify for awards if they are new instances which were not previously observed.

## Consequences of Complying with This Policy
Any issues already known to us will be published as a separate Known Issues list. These vulnerabilities are also considered out-of-scope, though new reports of a known issue may be accepted if the instances described were not previously observed.

We will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy.
## Safe Harbor

We consider activities conducted consistent with this policy to constitute 'authorized' conduct under the Computer Fraud and Abuse Act.
When conducting vulnerability research according to this policy, we consider the research conducted under this policy to be:

To the extent your activities are inconsistent with certain restrictions in our Acceptable Use Policy, we waive those restrictions for the limited purpose of permitting security research under this policy.
* Authorized in view of any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
* Authorized in view of relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
* Exempt from restrictions in our Acceptable Usage Policy that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
* Lawful, helpful to the overall security of the Internet, and conducted in good faith.

We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.
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 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.

Please submit a report to us before engaging in conduct that may be inconsistent with or unaddressed by 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 before going any further.

## The Fine Print

This is not a competition, but rather an experimental and discretionary rewards program. We may modify the terms of this program, terminate this program at any time, or not pay a reward entirely at our discretion.
This is not a competition, but rather an experimental and discretionary program.

You are solely responsible for any applicable taxes, transaction fees, or other withholdings that arise from or relate to your participation in this program.

We won't apply any changes we make to these program terms retroactively. Reports from individuals who we are prohibited by law from paying are ineligible for rewards. You are responsible for paying any taxes associated with rewards. Any rewards that are unclaimed after 12 months will be donated to a charity of our choosing.
Reports from individuals we are prohibited by law from paying are ineligible for awards.

0 comments on commit f3f8877

Please sign in to comment.