Versions Compared

Old Version 3

changes.mady.by.user LJ Illuzzi

Saved on

compared with

New Version 4

changes.mady.by.user Rajesh Krishnan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

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 server is set to periodicaly "inspect" remote cameras by checking there firmware fingerprint. Remote camera A is passively "inspected" by Remote Attestation server, the server confirms that the firmware fingerprint is authentic and permits/allows the camera to stay on the network.
  • [Placeholder] Remote Attestation server is set to periodicaly "inspect" remote cameras by checking there firmware fingerprint. Remote camera B is passively "inspected" by Remote Attestation server, the server determines that the firmware fingerprint is not authentic. 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 has an unexpected change

Demo Storyline (optional)


Interaction with other open source projects and components

  • a.
  • b.
  • c.

Links to existing documentation (Build Guide, Slideware, etc), if available (optional).

https://sediment-lfproject.github.io/

Links to existing demo/video, if available (optional).


Links to existing code/repos, if available (optional).

https://github.com/sediment-lfproject/remote-attestation