add vulnerability disclosure policy

3 files changed, 52 insertions, 2 deletions

diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 000000000..37ed19246
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,50 @@
+**Introduction**
+
+Security is core to our values, and we value the input of hackers acting in good faith to help us maintain a high standard for the security and privacy for our users. This 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.
+
+**Expectations**
+
+When working with us according to this policy, you can expect us to:
+- Extend Safe Harbor (see below) for your vulnerability research that is related to this policy;
+- Work with you to understand and validate your report
+- Work to remediate discovered vulnerabilities in a timely manner; and
+- Recognize your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change.
+
+**Safe Harbor**
+
+When conducting vulnerability research according to this policy, we consider this research to be:
+- Authorized in accordance with the law, and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
+- Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls;
+- Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy;
+- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
+
+You are expected, as always, to comply with all applicable laws.
+
+If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
+
+**Ground Rules**
+
+To encourage vulnerability research and to avoid any confusion between good-faith hacking and malicious attack, we ask that you:
+- Play by the rules. This includes following this policy, as well as any other relevant agreements. If there is any inconsistency between this policy and any other relevant terms, the terms of this policy will prevail.
+- Report any vulnerability you have 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.
+- Keep the details of any discovered vulnerabilities confidential until they are fixed, according to the Disclosure Terms in this 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 data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information.
+- You should only interact with test accounts you own or with explicit permission from the account holder.
+- Do not engage in extortion.
+
+**Official Channels**
+
+To help us receive vulnerability submissions we use the following official reporting channels:
+- chocobozzz@cpy.re (GPG: [583A612D890159BE](https://keybase.io/chocobozzz/pgp_keys.asc?fingerprint=c44aad638367912ca93edd57583a612d890159be))
+
+If you think you have found a vulnerability, please include the following details with your report and be as descriptive as possible:
+- The location and nature of the vulnerability,
+- A detailed description of the steps required to reproduce the vulnerability (screenshots, compressed screen recordings, and proof-of-concept scripts are all helpful), and
+- Your name/handle and a link for recognition.
+
+If you would like to encrypt the information, please use our GPG key.
+
+We may modify the terms of this program or terminate this program at any time. We will not apply any changes we make to these program terms retroactively.
diff --git a/config/default.yaml b/config/default.yaml
index e95fa3ec7..40458bb38 100644
--- a/config/default.yaml
+++ b/config/default.yaml
@@ -129,7 +129,7 @@ instance:
     Disallow: ''
   # Security.txt rules. To discourage researchers from testing your instance and disable security.txt integration, set this to an empty string.
   securitytxt:
-    "# If you would like to report a security issue\n# you may report it to:\nContact: https://github.com/Chocobozzz/PeerTube\nContact: mailto:"
+    "# If you would like to report a security issue\n# you may report it to:\nContact: https://github.com/Chocobozzz/PeerTube/blob/develop/SECURITY.md\nContact: mailto:"
 
 services:
   # Cards configuration to format video in Twitter
diff --git a/config/production.yaml.example b/config/production.yaml.example
index edc774e6b..d032e4a0c 100644
--- a/config/production.yaml.example
+++ b/config/production.yaml.example
@@ -143,7 +143,7 @@ instance:
     Disallow: ''
   # Security.txt rules. To discourage researchers from testing your instance and disable security.txt integration, set this to an empty string.
   securitytxt:
-    "# If you would like to report a security issue\n# you may report it to:\nContact: https://github.com/Chocobozzz/PeerTube\nContact: mailto:"
+    "# If you would like to report a security issue\n# you may report it to:\nContact: https://github.com/Chocobozzz/PeerTube/blob/develop/SECURITY.md\nContact: mailto:"
 
 services:
   # Cards configuration to format video in Twitter