Versions Compared

Key

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

Use this template to submit Use Cases for submission to the 5G Super Blueprint Use Case & Requirements Advisory Group. All input is required unless marked "(optional)"



Use Case Name:

ONE Summit Demo of Cryptographic Approach to Securing Network Slices.

DoD- Micheal August. Based on ONAP SABRE?

Use Case Description:

Demonstration of mechanism for securing Network Slices using Proxy Re-encryption.

Secure distribution of AES keys used to decrypt streaming video

(currently a 5-minute video).

Problem Statement and how is the problem solved:

Problem Statement: 

Currently, there is no mechanism for the secure distribution of critical information, such as private keys and control channel data, throughout the 5G core network and across administrative domains.

How the problem is solved: 

Lattice-based Proxy Re-encryption (PRE) can be used to securely forward ciphertext from a producer to a consumer by way of a Broker and Key Authority server.

Users Stories

  • Alice wants to forward Charlie an encrypted video so that he can watch it. Alice is not able to decrypt and re-encrypt the video using Charlie’s public key, so she delegates the forwarding process to Bob.  She doesn’t completely trust Bob, but she wants him to forward her encrypted video, along with its encrypted decryption key, to Charlie. Delegating the secure forwarding process to Bob means that Alice does not have to decrypt and then re-encrypt the video in order for Charlie to securely receive a copy of it.

Demo Storyline (optional)

Post-Quantum secure distribution of keys can be done via Proxy Re-encryption.  The demonstration consists of a streaming video whose decryption key is distributed securely via a transitive, or multi-hop, PRE scheme.

Interaction with other open source projects and components

  • ONAP
  • Free 5GC?

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


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


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