...
- Kubernetes interface is REST. Exact supported version of kubernetes has to be specified by every ONAP release
- Database interface depends on DB type but only encrypted communication should be used
- xNF interface depends on particular xNF but all xNFs should support secure protocols for communication
- NFVI interface is REST (usually OpenStack or Kubernetes)
- IAM interface is Open ID Connect
- if operator already has OIDC compatible solution ONAP should just use it
- if operator has Identity Provider (LDAP/Kerberos/etc) external OIDC solution should be deployed (ie keycloak) with operator IdP configured as backend
- In testing environment external OIDC solution should be deployed and bootstraped with test users
- CA interface can be one of:
- Manual interaction by deployer that will retrieve certificates and the bootstrap ONAP instance with them
- One of automated certificate retrieval protocols (ACME, CMPv2 etc)
- In testing environment external CA (and ONAP should use automated certificate retrieval as described in b) solution should be deployed
Requirements towards used interfaces
Kubernetes
- Cluster should be configured according to CIS guideline
Databases
- Each DB should be configured according to corresponding CIS guideline
- All DB should be already created or ONAP should be provided with user that is capable of creating DB
- If ONAP creates a DB a dedicated user account with privileges limited to that DB should be created. Password used for this user cannot be hardcoded in ONAP source.
xNF
As defined in ONAP VNF security requirements
NFVI
As defined in CNTT Reference Architecture 1 & 2
IAM
- IAM has to support OpenID connect standard
CA
- If automated certificate retrieval is used on of .... has to be supported by the CA