77 |
78 |
79 |
80 |
--------------------------------------------------------------------------------
/index.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | ---
4 |
5 | # Policy
6 |
7 | Thank you for helping us keep {{ site.company_name }} users safe! We ask that all researchers:
8 |
9 | * Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
10 | * Perform research only within the scope set out below;
11 | * Use the identified communication channels to report vulnerability information to us;
12 | * Report vulnerabilities as soon as you discover them;
13 | * Keep information about any vulnerabilities you’ve discovered confidential between yourself and {{ site.company_name }} until we’ve had 90 days to resolve the issue.
14 |
15 | If you follow these guidelines when reporting an issue to us, we commit to:
16 |
17 | * Not pursue or support any legal action related to your research;
18 | * Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission).
19 |
20 | ## Scope
21 | ### In-scope
22 |
23 | * [https://example.com](https://example.com)
24 | * [https://example.co](https://example.co)
25 |
26 | ### Out of Scope
27 |
28 | In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:
29 |
30 | * Findings from physical testing such as office access (e.g. open doors, tailgating).
31 | * Findings derived primarily from social engineering (e.g. phishing, vishing).
32 | * Findings from applications or systems not listed in the Scope section.
33 | * Vulnerability reports with video only PoCs.
34 | * Reports that state that software is out of date or vulnerable without a proof of concept.
35 | * Highly speculative reports about theoretical damage. Be concrete.
36 | * Vulnerabilities as reported by automated tools without additional analysis as to how they're an issue.
37 | * Reports from automated web vulnerability scanners (Acunetix, Vega, etc.) that have not been validated.
38 | * Recently disclosed zero-day vulnerabilities. We need time to patch our systems just like everyone else - please give us 30 days before reporting these types of issues.
39 | * Issues in third-party services should be reported to the respective team. Please take a look at the "Third-Party Services" section for more information.
40 |
41 | The following issue types are excluded from scope:
42 |
43 | * Network-level Denial of Service (DoS/DDoS) vulnerabilities.
44 | * Low severity issues that can be detected with tools such as [Hardenize](https://www.hardenize.com/) and [Security Headers](https://securityheaders.io/).
45 | * XSS issues that affect only [outdated browsers](http://outdatedbrowser.com/).
46 | * Content injection issues.
47 | * Cross-site Request Forgery (CSRF) with minimal security implications (Logout CSRF, etc.).
48 | * Missing cookie flags on non-security-sensitive cookies.
49 | * UI and UX bugs (including spelling mistakes).
50 | * [CSV and Excel injection](https://www.contextis.com/blog/comma-separated-vulnerabilities).
51 | * [401 page injection](https://security.stackexchange.com/a/135534).
52 | * Stack traces that disclose information.
53 | * Host header issues without an accompanying proof-of-concept demonstrating vulnerability.
54 | * Open ports without an accompanying proof-of-concept demonstrating vulnerability.
55 | * Banner grabbing issues (figuring out what web server we use, etc.).
56 |
57 | ## Reporting
58 |
59 | If you believe you’ve found a security vulnerability in one of our products or platforms, please send it to us via our [report form]({{ site.baseurl }}/report). Please provide detailed reports with reproducible steps. If a report is not detailed enough to reproduce the issue, it will not be eligible for a bounty.
60 |
61 | ## Rewards
62 |
63 | If you are the first to report an issue, and we make a code or configuration change based on the issue, we will award you:
64 |
65 | | Severity | CVSS | Award |
66 | |:---------|:----------:|:------|
67 | | Critical | 9.0 - 10.0 | $500 |
68 | | High | 7.0 - 8.9 | $100 |
69 | | Medium | 4.0 - 6.9 | $50 |
70 | | Low | 0.1 - 3.9 | $10 |
71 | | None | 0.0 - 0.0 | N/A |
72 |
73 | ## Third-Party Services
74 |
75 | {{ site.company_name }} uses the following third-party services. If you discover an issue in one of these services, please report it to the appropriate security team.
76 |
77 |
78 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 | # Project
9 |
10 | _SecurityTemplate_ is a static website template for security pages, powered by Jekyll. It's easy to get started. Clone this repo, edit the configuration files and content to your liking, and publish with [GitHub Pages](https://pages.github.com) or on your own server platform.
11 |
12 | You can [set up a local environment](https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/) to test your _SecurityTemplate_ static site, and [push to GitHub](https://help.github.com/articles/using-jekyll-as-a-static-site-generator-with-github-pages/) if desired.
13 |
14 | This project is a rapidly evolving work in progress. We value [contributions](https://github.com/EdOverflow/security-template/blob/master/CONTRIBUTING.md) from the public. Interested in checking out a live demo? Visit [securitytemplate.site](https://securitytemplate.site).
15 |
16 | # Structure
17 |
18 | The template directory structure is as follows:
19 |
20 | ```
21 | .
22 | ├── 404.html # 404 page.
23 | ├── advisories.md # Security advisories list.
24 | ├── assets # Page assets.
25 | │ ├── css
26 | │ │ └── styles.css
27 | │ └── images
28 | │ └── icon.png
29 | ├── _config.yml # Config file with all your variables.
30 | ├── _drafts
31 | ├── Gemfile
32 | ├── Gemfile.lock
33 | ├── hof.md # Hall of fame page.
34 | ├── _includes
35 | │ └── advisory-list.html
36 | ├── index.md # Security policy.
37 | ├── _layouts
38 | │ ├── default.html
39 | │ └── post.html
40 | ├── LICENSE
41 | ├── _posts
42 | │ └── 2017-07-22-cve-2017-0914.md # Example security advisory.
43 | ├── README.md
44 | └── report.md
45 | ```
46 |
47 | 
48 |
49 |
50 | ## `config.yml`
51 |
52 | * `company_name` — replace this with your organization name
53 | * `email` — replace this with your security contact address
54 | * `bugcrowd_id` — replace this with your [Bugcrowd ID](https://docs.bugcrowd.com/v1.0/docs/embedded-submission-form), if applicable
55 | * `hackerone_url` and `bugcrowd_url` — the /report URL will redirect to one of these, if specified.
56 |
57 | ## `index.md`
58 |
59 | The index file is where your security policy lives. To learn more about writing good security policies, please refer to https://support.hackerone.com/hc/en-us/articles/205624665-How-do-we-write-a-good-policy-.
60 |
61 | ## `advisories.md`
62 |
63 | This is where you can list your security advisories. The list is updated every time you add a security advisory to the `_posts` folder.
64 |
65 | ## `report.md`
66 |
67 | This file should contain contact information for security researchers to use when reporting a security vulnerability. If a HackerOne or Bugcrowd URL is specified in `config.yml`, users will be redirected automatically. You can also use an embedded Bugcrowd submission form. Just uncomment the form, and add your Bugcrowd embed token under `bugcrowd_id` in `_config.yml`.
68 |
69 | ## `hof.md`
70 |
71 | This is your security acknowledgements page. List the details of security researchers that reported valid security issues (and wish to be listed publicly).
72 |
73 | ## `.well-known/security.txt`
74 |
75 | `security-template` contains a security.txt template file. _security.txt_ defines a standard to help organizations define the process for security researchers to safely disclose vulnerabilities via a simple text file. For more on this, please refer to https://securitytxt.org/.
76 |
77 | # Contributing
78 |
79 | We welcome contributions from the public.
80 |
81 | ### Using the issue tracker 💡
82 |
83 | The issue tracker is the preferred channel for bug reports and features requests.
84 |
85 | ### Issues and labels 🏷
86 |
87 | The bug tracker utilizes several labels to help organize and identify issues.
88 |
89 | ### Guidelines for bug reports 🐛
90 |
91 | Use the GitHub issue search — check if the issue has already been reported.
92 |
93 | # Donations
94 |
95 | If you would like to support this project, you can use any of the addresses below:
96 |
97 | **Liberapay:** https://liberapay.com/EdOverflow
98 |
99 | **Bitcoin:** `1E2fZRNrrkCKPnWpKZAsJzByBoyoBURADN`
100 |
101 | **Ethereum:** `0xe98FC23fB4A8762d700c0354979dA5Db6c29Acc3`
102 |
--------------------------------------------------------------------------------