-
As we continue to mature our processes, it's crucial that our incident response plan includes an agreed to approach on how we communicate each incident by severity level so that we have a uniformed ap…
-
We should have a page and archive of known incidents so we can inform our community and coordinate within our team to troubleshoot and address them.
-
Per incident: [CCS Wallet Incident](https://github.com/monero-project/meta/issues/916)
After the disclosure of the stolen funds there has been a lot of questions of what exactly happened and how a…
-
It is still not clear what a good incident response framework and interfaces should be for cross-chain applications. [Some info in our recent paper ](https://www.techrxiv.org/users/687326/articles/691…
-
This is an issue for managing the discussion around the incident response workspace, providing a single thread to evolve what is going on in the workspace.
-
The scenario will include an attacker role and operator role, and will result in an incident response playbook.
@hannes-ucsc to update scenario document https://docs.google.com/document/d/1I5u56c4F7q…
-
-
_This initial comment is collaborative and open to modification by all._
## Task Summary
📅 Due date: N/A
🎯 Success criteria: Add these bits to handbook.
At the moment, we have no official gu…
-
[Objective](https://dash.gcp.marigold.dev/projects/MDEwOlJlcG9zaXRvcnkzNzM4MDc1NzM=/12)
Deadline: 2022-10-28 00:00:00
-
Hi there,
CSET would like to publish a large batch of incident annotations from the CSETv1 taxonomy at once. This involves changing one field ("Publish") from 'no' to 'yes' for ~250 incident annota…