Api Gateway medium
If you terminate SSL at the Gateway and use plain HTTP for internal traffic (Gateway -> Service), what critical security risk are you introducing?
- A The 'Man-in-the-Side' attack, where internal microservices can steal each other's database passwords.
- B You are violating the 'Zero Trust' principle. If the internal network is breached, unencrypted traffic between services can be sniffed or intercepted by an attacker.
- C You are making the system 10x more vulnerable to SQL Injection attacks.
- D It will prevent the Gateway from being able to perform rate limiting or authentication.
Answer: B. You are violating the 'Zero Trust' principle. If the internal network is breached, unencrypted traffic between services can be sniffed or intercepted by an attacker.
Modern security assumes the perimeter is already compromised ('Zero Trust'). For high-compliance systems, you should use 'Mutual TLS' (mTLS). The Gateway terminates public SSL but then re-encrypts the request using a private certificate to talk to the backend, ensuring encryption 'In-Transit' across the entire chain.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Your Gateway communicates with backends via HTTP/1.1 connections. A slow backend service causes 'Head-of-Line Blocking'. How does switching to HTTP/2 as the Gateway-to-Backend transport mitigate this?
- What is the primary architectural role of an API Gateway in a microservices environment?
- Why is 'Stateless Token Validation' (e.g., using JWTs) significantly more scalable at the Gateway level than 'Stateful Validation' (e.g., using Opaque/Reference Tokens)?
- Your Gateway is configured to cache any URL ending in `.css` or `.jpg`. An attacker tricks a victim into visiting `https://api.com/v1/profile/info/style.css`. How can this lead to an 'Account Takeover'?
- An API is receiving a sudden surge of 10,000 requests per second from a single IP address. How does an API Gateway preserve the stability of the backend services?
- How can an API Gateway help prevent 'Double Charging' in a payment system when a mobile client retries a failed request due to a poor connection?