Skip to content

Commit

Permalink
VRS policy changes and updates
Browse files Browse the repository at this point in the history
  • Loading branch information
@OllieJC
OllieJC committed Sep 22, 2023
1 parent 9cd6e3b commit 58ca862
Show file tree
Hide file tree
Showing 6 changed files with 64 additions and 56 deletions.
2 changes: 1 addition & 1 deletion cdn/s3_bucket/acknowledgements.html.tmpl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@
</div>
%{ endfor ~}
</div>
<a href="/" role="button" draggable="false" class="govuk-button back-button" data-module="govuk-button">Back</a>
<a href="/" role="button" draggable="false" class="govuk-button back-button govuk-button--secondary" data-module="govuk-button">Back</a>
</main>
</div>

Expand Down
2 changes: 1 addition & 1 deletion cdn/s3_bucket/assets/js/main.js
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ element.onclick = function() {
var emails = document.getElementsByClassName('email');
for (var i = 0; i < emails.length; i++) {
var email = emails[i].innerText.replace("[at]", "@");
emails[i].innerHTML = '<a href="mailto:'+ email +'">'+ email +"</a>";
emails[i].innerHTML = '<a class="govuk-link" href="mailto:'+ email +'">'+ email +"</a>";
}

function hackerone_onerror() {
Expand Down
20 changes: 5 additions & 15 deletions cdn/s3_bucket/config.html.tmpl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -71,29 +71,19 @@
<h1>Configuration</h1>
<div>
<p>This guidance is for all UK government organisations to configure the Vulnerability Reporting Service (VRS) for their websites and web services.</p>
<p>Step 1 describes configuring the security.txt signpost, and step 2 is for submitting contact details so the VRS team know where to direct reports against different assets.</p>

<hr><br/>

<h3 class="govuk-heading-m" id="securitytxt">Step 1: implement a security.txt</h3>
<p>There is a central deployment of the security.txt file to make it easier for you to implement on your systems and services.</p>
<p>You can find more about how to implement a signpost, including example code, here: <a href="https://github.com/co-cddo/implement-security.txt">https://github.com/co-cddo/implement-security.txt</a></p>
<p>There is a central deployment of the <a class="govuk-link" href="https://vulnerability-reporting.service.security.gov.uk/.well-known/security.txt">security.txt</a> file to make it easier for you to implement on your systems and services.</p>
<p>You can find more about how to implement a signpost, including example code, here:<br/><a class="govuk-link" href="https://github.com/co-cddo/implement-security.txt">https://github.com/co-cddo/implement-security.txt</a></p>

<hr><br/>

<h3 class="govuk-heading-m" id="contacts">Step 2: submit contact details</h3>

<p>If you have any issues with the form, contact <span class="email">vm[at]gccc.security.gov.uk</span></p>
<h3 class="govuk-heading-m" id="contacts">Step 2: submit contact and system details</h3>

<div>
<div class="config-container">
<iframe src="https://docs.google.com/forms/d/e/1FAIpQLSez1i1nR0lp9nkszlsIcvb6nAaT0w49qsARuRUjJO4zGjKAQw/viewform?embedded=true" marginheight="0" marginwidth="0" frameborder="0">
Loading…
</iframe>
</div>
</div>
<p>Let GC3 know you have configured the security.txt by emailing you and your team's contact details and configured domains and URLs to <span class="email">vm[at]gccc.security.gov.uk</span></p>
</div>
<a href="/" role="button" draggable="false" class="govuk-button back-button" data-module="govuk-button">Back</a>
<a href="/" role="button" draggable="false" class="govuk-button back-button govuk-button--secondary" data-module="govuk-button">Back</a>
</main>
</div>

Expand Down
9 changes: 2 additions & 7 deletions cdn/s3_bucket/feedback.html.tmpl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -69,14 +69,9 @@

<main class="govuk-body" id="main-content" role="main">
<div>
<p>If the form doesn't load correctly, you can contact <span class="email">vm[at]gccc.security.gov.uk</span>.</p>
<p>You can contact <span class="email">vm[at]gccc.security.gov.uk</span>.</p>
</div>
<div class="feedback-container">
<iframe src="https://docs.google.com/forms/d/e/1FAIpQLSdz_K5tS7T6Q_Y_i9b32sIvSUEoqvCWhg_O7OmrpIcT-2eWGA/viewform?embedded=true" marginheight="0" marginwidth="0" width="700" frameborder="0">
Loading…
</iframe>
</div>
<a href="/" role="button" draggable="false" class="govuk-button back-button" data-module="govuk-button">Back</a>
<a href="/" role="button" draggable="false" class="govuk-button back-button govuk-button--secondary" data-module="govuk-button">Back</a>
</main>
</div>

Expand Down
85 changes: 54 additions & 31 deletions cdn/s3_bucket/index.html.tmpl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -59,54 +59,75 @@
</div>

<main class="govuk-body" id="main-content" role="main">
<h1>Vulnerability Reporting</h1>
<h1>Vulnerability Reporting Service</h1>
<div>
<p>
A vulnerability is a technical issue with a government website or domain that attackers or hackers could use to exploit the service and its users.
You will not be paid a reward for reporting a vulnerability (known as a ‘bug bounty’).
Government Cyber Coordination Centre (GC3) is the UK government’s focal point for cross government collaboration on operational cyber security. We have a vital purpose to coordinate the cyber security efforts across the public sector. GC3 will accept reports on behalf of other UK government system owners where you have been unable to contact them and we will attempt to contact them on your behalf as part of our vision to “Defend As One”.
</p>
<p>
This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to us (the "Organisation"). We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.
</p>
<p>
We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures.
</p>

<h3 class="govuk-heading-m">How to report a vulnerability</h3>
<p>If you believe you have found a security vulnerability, please submit your report to us using the following link:</p>

<div>
<a href="/submit" role="button" class="govuk-button" data-module="govuk-button">
Submit report
</a>
</div>

<h3 class="govuk-heading-m">Scope</h3>
<p>In your report please include details of:</p>
<ul>
<li>“In scope” vulnerabilities must be original, previously unreported, and not already discovered by internal procedures.</li>
<li>Volumetric vulnerabilities are not in scope; this means that simply overwhelming a service with a high volume of requests is not in scope.</li>
<li>Reports of non-exploitable vulnerabilities are not in scope.</li>
<li>Reports indicating that our services do not fully align with “best practice” (for example, missing security headers) are not in scope.</li>
<li>TLS configuration weaknesses, for example, “weak” cipher suite support or the presence of TLS 1.0 support, are not in scope.</li>
<li>the website, IP or page where the vulnerability can be observed</li>
<li>a brief description of the type of vulnerability, for example; “XSS vulnerability”</li>
<li>steps to reproduce. These should be a benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers</li>
</ul>

<h3 class="govuk-heading-m">What to expect</h3>
<p>After you have submitted your report, we will respond to your report within five working days and aim to triage your report within ten working days. We’ll also aim to keep you informed of our progress.</p>

<p>Priority for remediation is assessed by looking at the impact, severity and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire on the status but should avoid doing so more than once every 14 days. This allows our teams to focus on the remediation.</p>

<p>We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately.</p>

<p>Once your vulnerability has been resolved, we welcome requests to disclose your report. We’d like to unify guidance to affected users, so please do continue to coordinate public release with us.</p>

<h3 class="govuk-heading-m">Guidelines for reporting a vulnerability</h3>

<p>When you are investigating and reporting the vulnerability on a government website or domain, you must not:</p>
<p>You must <b>NOT</b>:</p>

<ul>
<li>break the law</li>
<li>access unnecessary or excessive amounts of data</li>
<li>modify data</li>
<li>use high-intensity invasive or destructive scanning tools to find vulnerabilities</li>
<li>try a denial of service - for example overwhelming a service with a high volume of requests</li>
<li>disrupt services or systems</li>
<li>tell other people about the vulnerability you have found until we have disclosed it</li>
<li>social engineer, phish or physically attack our staff or infrastructure</li>
<li>demand money to disclose a vulnerability</li>
<li>break any applicable law or regulations</li>
<li>access unnecessary, excessive or significant amounts of data.</li>
<li>modify data in the Organisation's systems or services.</li>
<li>use high-intensity invasive or destructive scanning tools to find vulnerabilities.</li>
<li>attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests</li>
<li>disrupt the Organisation's services or systems</li>
<li>submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with “best practice”, for example missing security headers</li>
<li>submit reports detailing TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.0 support</li>
<li>communicate any vulnerabilities or associated details other than by means described in the published security.txt</li>
<li>social engineer, ‘phish’ or physically attack the Organisation's staff or infrastructure</li>
<li>demand financial compensation in order to disclose any vulnerabilities</li>
<li>share, redistribute or fail to properly secure data retrieved from the systems or services</li>
</ul>

<h3 class="govuk-heading-m">How to report a vulnerability</h3>
<p>Include in your report:</p>

<p>You must:</p>

<ul>
<li>the IP address and/or URL of the page where you found the vulnerability</li>
<li>a description of the type of vulnerability - for example, XSS vulnerability</li>
<li>details of the steps we need to take to reproduce the vulnerability</li>
<li>screenshots or logs if you have them</li>
<li>always comply with data protection rules and must not violate the privacy of the Organisation’s users, staff, contractors, services or systems</li>
<li>securely delete all data retrieved during your research as soon as it is no longer required or within one month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law)</li>
</ul>

<div>
<a href="/submit" role="button" class="govuk-button" data-module="govuk-button">
Submit report
</a>
</div>
<h3 class="govuk-heading-m">Legalities</h3>

<p>This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause the Organisation or partner organisations to be in breach of any legal obligations.</p>

<p>However, if legal action is initiated by a third party against you and you have complied with this policy, we can take steps to make it known that your actions were conducted in compliance with this policy.</p>

<h3 class="govuk-heading-m">Acknowledgements</h3>

<p>We appreciate people reaching out with valid vulnerabilities and are more than happy to include them on an acknowledgement page for their efforts.</p>
Expand All @@ -118,6 +139,8 @@
Go to acknowledegments
</a>
</p>

<p>&nbsp;</p>
</div>
</main>
</div>
Expand Down
2 changes: 1 addition & 1 deletion cdn/s3_bucket/submit.html.tmpl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@
<div id="submit-secondary-form" class="hidden">
<a href="https://hackerone.com/${hackerone_form_id}/embedded_submissions/new" role="button" draggable="false" class="govuk-button" data-module="govuk-button" target="_blank" rel="nofollow noreferrer noopener">Submit via HackerOne here</a>
</div>
<a href="/" role="button" draggable="false" class="govuk-button back-button" data-module="govuk-button">Back</a>
<a href="/" role="button" draggable="false" class="govuk-button back-button govuk-button--secondary" data-module="govuk-button">Back</a>
</main>
</div>

Expand Down

0 comments on commit 58ca862

Please sign in to comment.