From 025ad5f317433f27ee45b04c462f797a25d03d70 Mon Sep 17 00:00:00 2001 From: Natalie Chin Date: Thu, 11 Aug 2022 10:33:09 -0400 Subject: [PATCH 1/2] Updated IR plan recommendations --- development-guidelines/incident_response.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/development-guidelines/incident_response.md b/development-guidelines/incident_response.md index c48e24e2..6ec4e24d 100644 --- a/development-guidelines/incident_response.md +++ b/development-guidelines/incident_response.md @@ -18,4 +18,13 @@ Here, we provide recommendations around the formulation of an incident response - Consider adding more resilient solutions for detection and mitigation, especially in terms of specific alternate endpoints and queries for different data as well as status pages and support contacts for affected services. - [ ] **Combine issues and determine whether new detection and mitigation scenarios are needed.** - [ ] **Perform periodic dry runs of specific scenarios in the incident response plan to find gaps and opportunities for improvement and to develop muscle memory.** - - Document the intervals at which the team should perform dry runs of the various scenarios. For scenarios that are more likely to happen, perform dry runs more regularly. Create a template to be filled in after a dry run to describe the improvements that need to be made to the incident response. \ No newline at end of file + - Document the intervals at which the team should perform dry runs of the various scenarios. For scenarios that are more likely to happen, perform dry runs more regularly. Create a template to be filled in after a dry run to describe the improvements that need to be made to the incident response. + +## Incident Response Plan Resources + +- [ ] [How to Hack the Yield Protocol](https://docs.yieldprotocol.com/#/operations/how_to_hack) +- [ ] [Emergency Steps – Yearn](https://github.com/yearn/yearn-devdocs/blob/master/docs/developers/v2/EMERGENCY.md) + +## Well-handled IR Incidents + +- [ ] [Yield Protocol](https://medium.com/yield-protocol/post-mortem-of-incident-on-august-5th-2022-7bb70dbb9ada) From 79b3ebee1f41043b663921234acda88b5d9321cc Mon Sep 17 00:00:00 2001 From: Feist Josselin Date: Tue, 16 Aug 2022 13:34:17 +0200 Subject: [PATCH 2/2] Update incident_response.md --- development-guidelines/incident_response.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/development-guidelines/incident_response.md b/development-guidelines/incident_response.md index 6ec4e24d..89f66e70 100644 --- a/development-guidelines/incident_response.md +++ b/development-guidelines/incident_response.md @@ -22,9 +22,9 @@ Here, we provide recommendations around the formulation of an incident response ## Incident Response Plan Resources -- [ ] [How to Hack the Yield Protocol](https://docs.yieldprotocol.com/#/operations/how_to_hack) -- [ ] [Emergency Steps – Yearn](https://github.com/yearn/yearn-devdocs/blob/master/docs/developers/v2/EMERGENCY.md) +- [How to Hack the Yield Protocol](https://docs.yieldprotocol.com/#/operations/how_to_hack) +- [Emergency Steps – Yearn](https://github.com/yearn/yearn-devdocs/blob/master/docs/developers/v2/EMERGENCY.md) ## Well-handled IR Incidents -- [ ] [Yield Protocol](https://medium.com/yield-protocol/post-mortem-of-incident-on-august-5th-2022-7bb70dbb9ada) +- [Yield Protocol](https://medium.com/yield-protocol/post-mortem-of-incident-on-august-5th-2022-7bb70dbb9ada)