Chapter 11: Exploring Istio Security Features

  1. True It is the end user's responsibility to rotate certificates and keys that have been defined for the Ingress gateway in order to secure traffic from external clients and send it to the edge microservice. Note that Istio's Citadel rotates certificates for microservices.
  2. True There can only be one MeshPolicy (with name as the default) that will apply mTLS mesh-wide.
  3. True Mutual TLS can be as granular as possible from the namespace level to the service level by defining a policy.
  4. True Mutual TLS can be enabled through destination rules or by using MeshPolicy.
  5. True Istio is capable of shielding modern microservices applications from running in a zero-trust network without any changes needing to be made to the application code.
  6. True Istio makes VPNs and firewalls redundant if security has been implemented properly.
  7. True It is the responsibility of the edge microservice to manage JWT for authorizations.
  8. True – Istio's Secret Discovery Service mounts secrets in pods automatically.
  9. True Istio's Citadel will rotate certificates and keys every 90 days by default.
  1. True  The Envoy sidecar checks the TTL of the certificates. The Istio node agent, if enabled, can request a new certificate from Citadel. It is Citadel that pushes certificates to Envoy, not the node agent.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.17.174.239