A "session" is like a conversation between two trusted workloads. It can be a series of API calls (from a client) and responses (from the API/server) needed to complete a service or function. Any number of API calls can occur in a session and the exact number depends on how an application is configured.
How is key generation for SEE™ synchronized?
Sidecars self-synchronize during secrets construction using their CHIPS™ algorithm. The client (the initiating workload) in a communication session builds its symmetric key first and the server (the workload receiving the encrypted client message) builds its symmetric key when the encrypted message is received (at nearly the same time as the client built its key).
At what network layer does encryption occur?
Sidecars can be configured to perform SEE™ at either layer 4 or layer 7 of the ISO network stack. Layer 4 supports network load balancers (NLB) and layer 7 supports application load balancers (ALB).
Stay in touch with us
Sign up for our awesome newsletter! No spam ever.
Thank you! Your subscription is confirmed.
Oops! Something went wrong while submitting the form.
