chore: add incident response checklist #1300
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
afeld
commented
Feb 28, 2023
afeld
force-pushed
the
chore/incident-response-checklist
branch
from
e5d1e78
to
a444f4e
Compare
afeld
force-pushed
the
chore/incident-response-checklist
branch
from
a444f4e
to
e425759
Compare
afeld
commented
Feb 28, 2023
| ### Medium/High incidents | ||
|
|
||
| - [ ] Notify [#benefits-general][benefits-general]. | ||
| - [ ] If the incident is lasting more than 60 minutes or their customers' data has been breached, notify the impacted transit agencies. |
There was a problem hiding this comment.
Open to feedback on what this threshold should be.
thekaveman
requested changes
Feb 28, 2023
angela-tran
reviewed
Feb 28, 2023
thekaveman
approved these changes
Mar 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #833.
I kept it somewhat minimal, leaving out formalities such as the assigning of roles. I also tried to keep instructions in the issue and short, rather than creating yet another page that needs to be read.