Skip to end of metadata
Go to start of metadata

Project Name:

  • Proposed name for the project: Certificate and Secret Management Service
  • Proposed name for the repository : csm

Meetings

           

Project description:

This project proposal address two areas in the ONAP deployment structure from a security perspective.

  1. Secure Communication between microservices.
    • Current state and need
      • ONAP consists of multiple micro services which talk to each other.
        There are two types of communication. 

        1. REST API based communication.
        2. DMAAP publish/subscriber based communication.

        Since the communication is mostly over HTTP, there is a need to protect services from:

        • Bad actors stealing the data on the wire.
        • Receiving messages from bad actors
    • Requirement:
      • Enable TLS1.2+ for securing communication among the services. Java and Python libraries do support this functionality, but easy certificate provisioning is required for Mutual TLS. This project aims to simplify PKI - certificate provisioning via a simple and secure CA service that stores private keys (CA private key at CA and user certificate private keys) securely using hardware security.
  2. Storage of sensitive information such as passwords.
    • Current state and gaps
      • Many services in ONAP use password based authentication. Eg: Database servers, publish/subscribe brokers etc.
      • Passwords are stored in plain text files in many services.
      • With multiple instances of these services, the attach surface area becomes very big.
      • Hence there is a need to ensure that attack surface related to password exposure is reduced.
    • Requirement:
      • Need for secure secret management. Services are expected to get the secret only on needed basis using secret reference and remove the secrets once they are used up. 

This project aims to provide solutions to the above needs by:

  1. Provide Certificate Management Service (CA Service)  to provision signed certificates required for Mutual TLS.
  2. Provide Certificate Request Agent SDK
  3. Provide hardware security plugin for storing private keys and for performing crypto operations that require private keys.
  4. GUI/CLI for Certificate Management Service
  5. Provide Secret Management Service for adding/deleting/updating/reading secrets.
  6. Provide Secret Client Agent SDK 
  7. GUI/CLI for Secret Management Service.

Scope:

Certificate Management Service

The proposed project will provide a Certificate Management Service which will be used for certificate enrollment by micro services. The ultimate goal is to make sure that all micro services communicate securely between each other using the CA for enrollment and then use TLS to establish secure communication channels between each other.

The Certificate Management Service will support the following:

  • RESTful API support for Certificate Request Operations by micro services
    • Generate Certificate
    • Revocation of Certificate
    • Usage report updates
    • Token Authentication
  • An Admin interface
    • That will generate a self signed CA
    • Upload any admin generated CA Cert + Private Key pair
    • Usage usage reports on each key
    • Revoke certificates
    • Get CA Certificate in PEM/DER format
    • Token service to provide temporary tokens

There will also be a Client that will be part of the project written in either Python or Java that will be used to communicate with the CA Broker Service to enroll certificates.
It will have the following roles/abilities:

  • Generate RSA/ECDSA key pair using PKCS11
  • Securely store the private key.
    • Store the private key using TPM if it is available
  • PKCS10 CSR generation
  • Communicates with the previously described Certificate Management Service over REST API
  • Periodically generates a usage report
  • Certificate Renewal
  • Discovery of Certificate Management Service

The below diagram illustrates Best Practices of Certificate Enrollment that is end-point initiated.

The below diagram illustrates Certificate Enrollment that is Middle Man initiated

This diagram shows mapping of Certificate Provisioing in ONAP context.

The below diagram details the architechture blocks used previously in detail:

The below diagram the same architecture blocks as above with a Sidecar service:

Use Case Sequence Diagrams





Secret Management Service

The project will also provide a Secret Management Service with the following features and capabilities:

  • Support multiple Secret domains
    • Each domain can be used to multiple secrets
    • Each domain is associated with various policies
  • Each secret can have multiple key value pairs
  • Certificate based authentication
  • Authenticate users with AAF
  • Token based authentication
  • Securely store secrets using AES encryption
    • Use TPM/SGX for key storage if available
  • RESTful API support for ADD, UPDATE, DELETE of secrets

The below diagram illustraces the Secret Service High Level Flow in an ONAP Context


The below diagram illustrates how a micro service will use the Secret Client Agent to talk to the Secret Service to store or retrieve passwords.

SoftHSMv2 +TPM2-Plugin

This project provides SoftHSMv2 with an extended capabilities to leverage TPM2.0 hardware capabilities to generate RSA/ECC keypairs and import keys generated outside of TPM2.0 module. This is achieved by modifying SoftHSMv2, adding an adapter layer between SofhHSMv2 and TPM2-Plugin. 

Bullseys coverage tool is used to measure the codes coverage: 


Architecture Alignment:

CSM is a common service across ONAP components.

Other Information:

Key Project Facts:

Primary Contact : Srinivasa Addepalli

Facts

Info

PTL (first and last name)
Jira Project NameTBD
Jira KeyTBD
Project IDTBD
Link to Wiki SpaceTBD

Release Components Name:

Note: refer to existing project for details on how to fill out this table

Components Name

Components Repository name

Maven Group ID

Components Description

smsaaf/smsorg.onap.aaf.smsSecret Management Service that will contain the webservice as well as client code for managing and accessing secrets.
sshsmaaf/sshsmorg.onap.aaf.sshsmA repository for softhsm modifications and hardware security plugin

Resources committed to the Release:

Note 1: No more than 5 committers per project. Balance the committers list and avoid members representing only one company.

Note 2: It is critical to complete all the information requested, that we help to fast forward the onboarding process.

Role

First Name Last Name

Linux Foundation ID

Email Address

Location

PTLKiran Kaminenikirankaminenikiran.k.kamineni@intel.comSanta Clara, CA
CommittersKiran Kaminenikirankaminenikiran.k.kamineni@intel.comSanta Clara, CA

Girish Havaldargirihg0071052@techmahindra.com

Bangalore, India

ContributorsVamshi Namilikondavamshi.nemalikondavn00480215@techmahindra.comPune, India

Manjunath Ranganathaiahmranganamanjunath.ranganathaiah@intel.comSanta Clara, CA, USA

Ning Sun

ningsun

ning.sun@intel.comSanta Clara, CA, USA



  • No labels

5 Comments

  1. How does this fit in with the AAF certificate management service ?

    1. Hi Brian,  That is something we started to discuss with Ram. 

  2. Slides that were presented today at F2F meeting in Santa Clara

  3. Thanks for this proposal. We've had many discussions via the mailing list, but a couple more questions:

    • What is the outcome on syncing with AAF?  Would it be possible to have a single security project to include this proposal as well as AAF?  I see a lot of synergy here.
    • Have you discussed how to work with MSB which looks to be implementing a sidecar model in Beijing?
  4. Hi Jason,

    We had a discussion with AAF team.  AAF group is willing to extend the scope of the AAF project to include certificate management & secret management with HW level security. Ram Koya (PTL for AAF) project said that scope details need to be worked out in coming week.  Since it is important security feature for ONAP,  we are in two minds on whether it is best done as a separate project with its own focus or combine the efforts in one security project. We and TechMahindra is okay with either way and we would leave the decision to TSC.

    On Sidecar:  As you see in the presentation deck, we would like to ensure sidecar (based on OpenRusty + NGINX OR Envoy proxy) initiated Mutual TLS is also supported with certificate provisioning and also ensure that private key of certificate is secured in HW based TEEs (TPM, SGX etc...)

    Thanks

    Srini