Skip to content

Update incident process #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update incident process #116

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions source/security/incidents.html.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,7 @@ Additionally, consider if a given issue needs to be solved immediately or if the
- Malicious code being shipped in govuk-frontend
- Linking to a malicious resource in our documentation eg: a port of govuk-frontend that contains malicious code
- A serious accessibility bug is shipped/discovered in govuk-frontend
- A majority of our GitHub PRs are failing

### Examples of things that are not incidents

Expand Down Expand Up @@ -58,6 +59,8 @@ You should assign 2 roles to help manage the incident:

Incidents are varied and can require different roles to resolve. You also may discover exactly which roles you need as the incident progresses. It's recommended to request roles on the team as you need them.

It is almost always helpful to hop on a video call with each other while dealing with an incident.

### Start an incident report

The incident team at this point should start an incident report so that they can keep track of the incident, its impact, its severity, a timeline of events and, once resolved, a list of actions taken out of an incident review. You can find a template for incident reports, as well as a record of all previous incidents by year, [in the INCIDENTS folder in the team drive](https://drive.google.com/drive/u/0/folders/1plXDUGFIoyzWubWNC9J_IjMiEN8eh9pO).
Expand Down