Fix broken IR process #2429
Merged
Fix broken IR process #2429
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
markdboyd
reviewed
Nov 2, 2023
markdboyd
reviewed
Nov 2, 2023
| - Is there evidence of compromise or attack? | ||
| - Has the system been unable to maintain our [service level objectives]({{ site.baseurl }}{% link _docs/overview/customer-service-objectives.md %})? | ||
| - An availability issue impacting a single customer is likely _not_ an incident | ||
| - Is an attack imminent or suspected (e.g. a Log4J type vulnerability) |
There was a problem hiding this comment.
Suggested change
| - Is an attack imminent or suspected (e.g. a Log4J type vulnerability) | |
| - Is an attack imminent or suspected (e.g. a Log4J type vulnerability)? |
markdboyd
reviewed
Nov 2, 2023
Comment on lines
+80
to
+92
| When a TTS staff member (the *reporter*) notices and reports a cloud.gov-related incident using the [TTS incident response process](https://handbook.tts.gsa.gov/general-information-and-resources/tech-policies/security-incidents/) they should then notify the cloud.gov team in [`#cg-support`](https://gsa-tts.slack.com/archives/C09CR1Q9Z) | ||
|
|
||
| When a cloud.gov team member is the first person to notice an incident, they should | ||
| join [`#cg-incidents`](https://gsa-tts.slack.com/archives/GTNBK2L9K), and use the "Declare Incident" Workflow. | ||
|
|
||
| When a cloud.gov team member is the first person to notice an incident, they should also begin reporting it by using the [TTS incident response process](https://handbook.tts.gsa.gov/general-information-and-resources/tech-policies/security-incidents/) and posting about it in [`#cloud-gov`](https://gsa-tts.slack.com/messages/cloud-gov/) using `@cg-team` (including notifying the cloud.gov leads). | ||
| Declaring an incident results in further guidance to: | ||
| - Designate an Incident Commander and Scribe | ||
| - Claim an incident folder in our "Incident Response" [Google Drive folder](https://drive.google.com/drive/folders/1WtLFiZuxLmKR4mrztEE9YtS78nGxC--P) | ||
| - We try to populate incident folders in advance based on existing templates | ||
| - Share the URL of the incident document | ||
| - Update incident doc in that folder with comms and key findings. | ||
| - Gather in a Google Meet | ||
| - Set reminders to send comms updates, and to rotate key roles every 6 hours. |
There was a problem hiding this comment.
This section feels broadly repetitive of https://github.com/cloud-gov/cg-site/pull/2429/files#diff-8b21e674168ee96c2cb0966300d0c51b63e5fd2389228d91f3d3cf45df23d510R39-R48
Is there any way to avoid that?
There was a problem hiding this comment.
The IR document is still very duplicative. I’d like to do another round and leverage somthing like https://gist.github.com/scmx/eca72d44afee0113ceb0349dd54a84a2 to expand/collapse the details.
There was a problem hiding this comment.
Fair. As a first pass, this is a big improvement
markdboyd
approved these changes
Nov 2, 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.
Changes proposed in this pull request:
This is still a less-than-ideal document but is significantly better. I'd like to merge it once we correct what's still clearly wrong even we may still have some omissions.
Security Considerations
The IR process has already been open-source.