public
/
docs
5
0
Fork 0
Code Issues 5 Pull Requests Packages Projects Releases Wiki Activity

Define Chain-Of-Custody Standards #3

New Issue
Open
opened 2024-11-20 22:50:45 +00:00 by anton · 0 comments
anton commented 2024-11-20 22:50:45 +00:00
Owner
Copy Link
  • Laptop Acquisition: Use tamper-evident, randomly acquired laptops that have never left the supervision of a two-person team.
  • Dual-Operator Compliance: Document each chain-of-custody step witnessed and certified by two team members to prevent unauthorized actions.
- [ ] Laptop Acquisition: Use tamper-evident, randomly acquired laptops that have never left the supervision of a two-person team. - [ ] Dual-Operator Compliance: Document each chain-of-custody step witnessed and certified by two team members to prevent unauthorized actions.
lrvick added this to the Custody Framework project 2024-11-21 04:51:25 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
feat/quorum-kms
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Custody Framework
Assignees
Clear assignees
No Assignees
1 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#3
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?