load balancing - Use of KeyStore in SSL LoadBalancers -
i have service running on fleet of machines behind load balancer. load balancer binded ssl certificate. if use self-signed certificate on service, connection client load balancer still secured ?
if create keystore using certificate binded load balancer , ask service use keystore. how effect communication between client , service ?
since load balancer (lb) reverse proxy, external client wouldn't know difference on how communication between lb , backend done.
typically backend servers isolated internet via firewall, hence no ssl required. if need use ssl, yes self-signed certificate add security. colleague no longer able sniff packets , see information.
from security perspective, using self-signed certificate in scenario still poses risk. of colleague access private key , dns can still launch eavesdropping attack. furthermore can cumbersome having lbs trust public key of each backends (and everytime expires have redo it).
a better approach use internally managed certification authority (ca). each internally issued certs signed ca. lbs need trust internal ca , automatically trust chained certs.
this typically done in large corporation many business units potentially conflicting interest. since they're still 1 organization, business units on same network, if sniff information exchanged business can cause legal breach. if situation doesn't apply might re-think usage of ssl internal traffic.
Comments
Post a Comment