Ensure each components can support encryptions (via https) for its interfaces For R3 all DCAE components require to data flow and control flow to be encrypted. 

Component that presents an API (DH, CBS, InventoryAPI, VESCollector, HV-VES) must present it via HTTPS, authenticating itself with its server cert (cert will be made available part of DCAE deployment setup) 

2-way Mutual SSL (which require that API clients present a TLS certificate) should be enabled via configuration (based on CADI client availability)

Support for RBAC via configuration (to allow integration with AAF later). Actual RBAC integration through AAF is tracked under DCAEGEN2-597