Skip to content
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.

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

create an incident response checklist #833

Closed
2 tasks done
afeld opened this issue Jul 27, 2022 · 0 comments · Fixed by #1300
Closed
2 tasks done

create an incident response checklist #833

afeld opened this issue Jul 27, 2022 · 0 comments · Fixed by #1300
Assignees
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc) security Changes to improve or maintain the availability and resilience of the app

Comments

@afeld
Copy link
Contributor

afeld commented Jul 27, 2022

Acceptance Criteria

  • The team should know the general steps of what to do if there's a incident of some kind (security, downtime, etc.)

Additional context

Things this should include:

  • Where to look for logs/metrics
  • Doing a post-mortem
  • Writing up an incident report
  • When/how to notify the ISO/DevSecOps teams
  • When/how to notify relevant transit agencies
  • If/how to notify users

Various steps should direct the reader to the troubleshooting page for more details.

Examples:

What is the definition of done?

  • There is a checklist of steps
@afeld afeld added security Changes to improve or maintain the availability and resilience of the app deliverable Work that ends with a non-code deliverable (e.g. Google doc) labels Jul 27, 2022
@afeld afeld added this to the Reliability milestone Jan 9, 2023
@afeld afeld self-assigned this Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc) security Changes to improve or maintain the availability and resilience of the app
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant