RFC: DCP Incident Response Plan #80
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
brianraymor
reviewed
Jun 8, 2019
brianraymor
reviewed
Jun 8, 2019
brianraymor
requested changes
Jun 8, 2019
Embed IRP content into 0000-Incident-Response-Plan.md
tjchen
reviewed
Jun 17, 2019
tjchen
reviewed
Jun 17, 2019
| 1. Date of discovery of the suspected or confirmed incident | ||
| 1. Brief description of suspected or confirmed incident | ||
| 1. If known, also include: | ||
| 1. Date incident occurred |
There was a problem hiding this comment.
I have seen before where the reporter can classify the ticket initially (event, incident, etc) and then the reviewer can downgrade/change as needed. In this situation, are all defaulting to a certain severity?
There was a problem hiding this comment.
I've updated to specifically called this out within today's updates
tjchen
reviewed
Jun 17, 2019
Updates based on TJ's comments: (1) request affected system and application versions + estimated incident severity rating during incident ticket creation and (2) allow IRT the opportunity to revise the incident severity rating after incident review
Bento007
reviewed
Jun 26, 2019
austinylin
reviewed
Jun 27, 2019
|
Approved during 7/25 PM meeting |
diekhans
pushed a commit
to barkasn/dcp-community
that referenced
this pull request
Aug 16, 2019
* Create 0000-Incident-Response-Plan.md * Update 0000-Incident-Response-Plan.md Embed IRP content into 0000-Incident-Response-Plan.md * Update 0000-Incident-Response-Plan.md Updates based on TJ's comments: (1) request affected system and application versions + estimated incident severity rating during incident ticket creation and (2) allow IRT the opportunity to revise the incident severity rating after incident review * Update 0000-Incident-Response-Plan.md * Update 0000-Incident-Response-Plan.md * Update 0000-Incident-Response-Plan.md
diekhans
pushed a commit
to diekhans/dcp-community
that referenced
this pull request
Oct 31, 2019
* Create 0000-Incident-Response-Plan.md * Update 0000-Incident-Response-Plan.md Embed IRP content into 0000-Incident-Response-Plan.md * Update 0000-Incident-Response-Plan.md Updates based on TJ's comments: (1) request affected system and application versions + estimated incident severity rating during incident ticket creation and (2) allow IRT the opportunity to revise the incident severity rating after incident review * Update 0000-Incident-Response-Plan.md * Update 0000-Incident-Response-Plan.md * Update 0000-Incident-Response-Plan.md
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.
The DCP needs to have a confirmed plan and procedures in place so that we are prepared to respond to an incident. This RFC proposes an Incident Response Plan for review.
June 14: Last call for community reviewJune 21: Last call for community review (extended 1 week)July 12: Last call for Oversight reviewReview closed; pending final approval.