Create documents on how the repository for ceremonies should be set up #32

Open
opened 2024-12-20 16:31:56 +00:00 by anton · 2 comments
Owner
No description provided.
anton added this to the Vaulting Framework Documentation milestone 2024-12-20 16:31:56 +00:00
anton added this to the Custody Framework project 2024-12-20 16:31:56 +00:00
Member

Few questions I have here around a ceremony log.txt:

  1. What should be logged?
  2. Who should be doing the logging?
  3. From what device should the logging be performed?
Few questions I have here around a ceremony `log.txt`: 1. What should be logged? 2. Who should be doing the logging? 3. From what device should the logging be performed?
anton added the
qvs
label 2025-01-04 15:31:29 +00:00
Author
Owner

Few questions I have here around a ceremony log.txt:

  1. What should be logged?
  2. Who should be doing the logging?
  3. From what device should the logging be performed?
  1. We should log details such as: who is performing some task, when they are doing it, where they are doing it, what equipment they are using etc. I will specify these more explicitly with a template we can use. The log is also where we would note anything out of the ordinary, including a incident response initialization.
  2. The logging should be done by one of the individuals whose role it is to perform the process, and another to witness. The idea is that these logs will go into the "ceremonies" repo, and be git signed.
  3. The logs can be done on a computer after the ceremony is done, so they could be taken on paper during the ceremony, because we want to minimize the amount of hardware we bring into the space unless it's necessary (level 2 doesn't require minimizing hardware present in the ceremony room, but its not a bad idea do this if possible)
> Few questions I have here around a ceremony `log.txt`: > > 1. What should be logged? > 2. Who should be doing the logging? > 3. From what device should the logging be performed? 1. We should log details such as: who is performing some task, when they are doing it, where they are doing it, what equipment they are using etc. I will specify these more explicitly with a template we can use. The log is also where we would note anything out of the ordinary, including a incident response initialization. 2. The logging should be done by one of the individuals whose role it is to perform the process, and another to witness. The idea is that these logs will go into the "ceremonies" repo, and be git signed. 3. The logs can be done on a computer after the ceremony is done, so they could be taken on paper during the ceremony, because we want to minimize the amount of hardware we bring into the space unless it's necessary (level 2 doesn't require minimizing hardware present in the ceremony room, but its not a bad idea do this if possible)
Sign in to join this conversation.
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/docs#32
No description provided.