| Use Case Name: | Remote Attestation Use Case 1- IoT Device Security and Authentication |
|---|
| Use Case Description: | Leveraging technics of Peraton Labs add Remote Attestation to existing lab infrastructure This Use Case may be combined with Remote Attestation Use Case 2- IoT Device Onboarding & Maintenance |
Epic Problem Statement and how is the problem solved: | Problem Statement: How to insure that IoT devices on a network are authentic and have not been tampered with. This is particularly sensitive in remote areas that are not often frequented by people. Resolution: |
User Stories | - [Placeholder] Remote Attestation Protocal (RAP) server is set to periodicaly "inspect" remote cameras IoT devices by checking there firmware fingerprint. Remote by confirming Evidence. Example, remote camera A is passively "inspected" by Remote Attestation server, the server confirms that the its evidence (ex; firmware fingerprint) is authentic and permits/allows the camera to stay on the network.
- [Placeholder] Remote Attestation Protocal server is set to periodicaly "inspect" remote cameras by checking there firmware fingerprintits evidence against pre-configured evidence. Remote camera B is passively "inspected" by Remote Attestation server, the server determines that the firmware fingerprint is not authenticevidence does not match evidence that has been pre-configured in the RAP server. The server then denies camera B access on the network and sends an alert.
- [Placeholder] Active alerting. Camera C sends an alert when its firmware fingerprint evidence has an unexpected change.
|
Demo Storyline (optional) |
|
Interaction with other open source projects and components | |
Links to existing documentation (Build Guide, Slideware, etc), if available (optional). | https://sediment-lfproject.github.io/ SEDIMENT Project Alignment |
Links to existing demo/video, if available (optional). |
|
Links to existing code/repos, if available (optional). | https://github.com/sediment-lfproject/remote-attestation |
