You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: development-guidelines/incident_response.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ How you respond during an incident is a direct reflection of your efforts to pre
24
24
## Process
25
25
26
26
-**Conduct periodic training and incident response exercises**. Regularly organize training sessions and incident response exercises. Such measures ensure that employees remain updated and can help highlight any flaws in the current incident response protocol.
27
-
-**Remember to consider off-chain components when planning**. While much of this document is concerned with on-chain code, compromised frontends or social media accounts are also common sources of incidents.
27
+
-**Remember to consider off-chain components when planning**. While much of this document is concerned with on-chain code, compromised frontends or social media accounts are also common sources of incidents.
28
28
-**Identify incident owners, with at least**:
29
29
-**A technical lead**. Responsible for gathering and centralizing technical data.
30
30
-**A communication lead**. Tasked with internal and external communication.
0 commit comments