Versions Compared

Key

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

Proposal scope

The data security  for eve software module EVE, will be driven through configuration published to the EVE software from the controller, using REST APIs. The scope of this document is to define the security policy details, which will be exchanged between the controller module and Eve softwareEVE. And, this configuration will be user-driven through UI module of the controller.

Data Security on

...

EVE Software

The data security for the Eve ModuleEVE, can be of the following types,

...

Data in transit security, is applicable for controller and Eve EVE Module data exchange. The data in transit security for Application instance data traffic will be prerogative of the application software and, is out of scope for the current proposal.

Currently, TLS 1.2 is used for data in transit security, for configuration/status/information exchange between the controller and Eve ModuleEVE. Additionally, sensitive configuration information, viz. data store credentials,  will be secured between the controller and the end-user of the information, inside Eve software EVE (downloader), by using the device cert/key pair.

Data at rest security is applicable for the Application Instance mutable business sensitive data and  storage for Eve Module EVE sensitive configuration information.

...

The sensitive configuration for Eve ModuleEVE, will be stored in encrypted form (cypher text), till it is ready for use by the end user. viz., data store access credentials.

Security policy Details

Data security policy, will consist of the following,

  • Data in transit security policy
  • Data at rest security policy

Data in transit policy

Currently, the data in transit is secured through TLS 1.2 framework,  between the controller software and Eve moduleEVE.

The data in transit security policy, will be applicable for the sensitive configuration data in transit between the controller software and the end user (downloader) inside Eve moduleEVE.

Data at Rest Policy

The data at rest security policy will be applicable to application business sensitive data, covering the following aspects,

  • policy activation flag
  • encryption algorithm
  • data handling policy
  • offline activation policy
  • key rotation policy
  • key Information

Encryption Algorithm

This specifies, the encryption algorithm to be used for data at rest security. [Ref. 1].

  • NONE
  • AES256
  • ADIANTUM

Data handling policy

This specifies the sensitive data handling across encryption algorithm change or, security breach detection.

...

some user defined policy in the controller module.

Off-line Security Policy

When is the Eve software WhenEVE is not able to contact communicaate the controller module, it will keep operating, using the last configuration received.On power cycle, if the device EVE is not able to connect to the controller, the following options are available for the user. And it may require physical access to the device and/or user intervention. 

...

The user has to ensure that, proper configuration is stored in the USBKEY Usb Stick or, inputs them through to KEYBOARD for the Eve softwareKeyboard.

Key rotation policy

This will define the key rotation activation. The key rotation poilcy will be in controller module and will not be intimated to Eve softwareEVE.

Keys

This consists of  set of Keys information( max. 2). For a key rotation scheme, a maximum of two keys will be intimated to the Eve software. The controller module EVE. Controller will store and publish, the last published key it has published to the Eve module along with the most current key, to the Eve module. This will cover the cases for the Eve module cases, when EVE not able to communicate with the controller module.

Implementation

A new API (EdgeDevPolicy) will be used for handling security policy configuration. The security policystatus/information detail will be added to device status message APIs. 

On Eve software, the The security policy configuration will be handled by vault manager in EVE. [Ref. 1].

Vault manager will poll for security policy configuration. Vault manager will not store the security key configuration in permanent storage/disk  at any time.

References


  1. https://wiki.lfedge.org/display/EVE/Encrypting+Sensitive+Information+at+Rest+at+the+Edge