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

Tamper Evidence Procedures #5

New Issue
Closed
opened 2024-11-20 22:53:09 +00:00 by anton · 4 comments
anton commented 2024-11-20 22:53:09 +00:00
Owner
Copy Link
  • Each tamper proof setup explains the threat model and procedure of how it's used

https://git.distrust.co/public/docs/pulls/10/files#diff-fc113b43a349f341e16df0a68689564f47c1986d

* Each tamper proof setup explains the threat model and procedure of how it's used https://git.distrust.co/public/docs/pulls/10/files#diff-fc113b43a349f341e16df0a68689564f47c1986d
lrvick added this to the Custody Framework project 2024-11-21 04:51:25 +00:00
anton commented 2024-11-26 18:11:37 +00:00
Author
Owner
Copy Link

The 3 tamper evidence methods I'm currently documenting are:

  • Vacuum Sealing + Colored Filler
  • Glitter
  • Heads/Pure Boot
The 3 tamper evidence methods I'm currently documenting are: * Vacuum Sealing + Colored Filler * Glitter * Heads/Pure Boot
anton commented 2024-11-26 19:19:51 +00:00
Author
Owner
Copy Link

Currently figuring out the most practical and reliable way to photograph sealed objects and compare photographs. There are several considerations here:

  • The device taking photographs should not be internet connected, and ideally not have radio cards in it. This is because devices inside of the vault should not have the ability to transmit data by wireless means.

  • There should be an easy way to transfer photographs, to a local computer/phone for image comparison, and to an online computer for signing and uploading photographs.

  • There should be a practical way to take photos in a consistent manner regarding the lightning, distance, and image fidelity

Currently figuring out the most practical and reliable way to photograph sealed objects and compare photographs. There are several considerations here: * The device taking photographs should not be internet connected, and ideally not have radio cards in it. This is because devices inside of the vault should not have the ability to transmit data by wireless means. * There should be an easy way to transfer photographs, to a local computer/phone for image comparison, and to an online computer for signing and uploading photographs. * There should be a practical way to take photos in a consistent manner regarding the lightning, distance, and image fidelity
anton commented 2024-11-28 22:52:32 +00:00
Author
Owner
Copy Link

Using polaroid + digital camera offers an analog and digital option, adding additional resiliency to the system

Using polaroid + digital camera offers an analog and digital option, adding additional resiliency to the system
anton self-assigned this 2024-11-29 16:21:05 +00:00
anton added the due date 2024-12-10 2024-12-05 21:51:50 +00:00
anton modified the due date from 2024-12-10 to 2024-12-11 2024-12-05 21:52:00 +00:00
anton started working 2024-12-05 23:37:00 +00:00
anton stopped working 2024-12-05 23:59:20 +00:00
22 minutes 20 seconds
anton added this to the Vaulting Framework Documentation milestone 2024-12-06 01:33:09 +00:00
anton commented 2024-12-17 19:30:09 +00:00
Author
Owner
Copy Link

This document has reached poc status.

This document has reached poc status.
anton closed this issue 2024-12-17 19:30:10 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
feat/tamper-proofing-chain-of-custody
coding-standards
feat/quorum-kms
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Vaulting Framework Documentation
Projects
Clear projects
No project
Custody Framework
Assignees
Clear assignees
No Assignees
anton
1 Participants
Notifications
Total Time Spent: 22 minutes 20 seconds
anton
22 minutes 20 seconds
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

2024-12-11

Dependencies

No dependencies set.

Reference: public/docs#5
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?