Why security spans all services in Microservices - Why This Architecture

Problem Statement

When security is applied only at the edge or a few services, attackers can exploit weaker or unprotected internal services. This leads to unauthorized access, data leaks, or service disruptions inside the system, bypassing perimeter defenses.

Solution

Security must be integrated into every service to ensure consistent protection. Each service verifies identities, enforces permissions, and validates inputs independently, preventing attackers from moving laterally inside the system even if one service is compromised.

Architecture

Client

→API Gateway

↓

Service B

This diagram shows a microservices system where each service, including the API Gateway and internal services, independently enforces security checks on incoming requests.

Trade-offs

✓ Pros

→

Prevents attackers from exploiting weaker internal services after breaching the perimeter.

→

Limits damage scope by isolating security failures to individual services.

→

Supports zero-trust security models, improving overall system resilience.

→

Enables fine-grained access control tailored to each service's needs.

✗ Cons

→

Increases development complexity as security logic must be implemented in all services.

→

Can cause performance overhead due to repeated security checks.

→

Requires consistent security policies and updates across multiple teams and services.

Use when the system has multiple services communicating internally, especially in zero-trust environments or when sensitive data and operations are distributed.

Avoid if the system is a simple monolith or has very limited internal communication where perimeter security suffices and complexity overhead is unjustified.

Real World Examples

Netflix

Netflix applies security checks within each microservice to prevent compromised services from affecting others, supporting their zero-trust architecture.

Uber

Uber enforces authentication and authorization in every service to protect sensitive rider and driver data across their distributed microservices.

Amazon

Amazon implements security at each service layer to isolate faults and prevent lateral movement in their vast microservices ecosystem.

Code Example

The before code shows security only at the API Gateway, trusting internal services blindly. The after code adds authentication and authorization checks inside Service A, ensuring security spans all services.

Microservices

### Before: Security only at API Gateway
class APIGateway:
    def handle_request(self, request):
        if not self.authenticate(request):
            return "Unauthorized"
        return self.forward_to_service(request)

class ServiceA:
    def process(self, request):
        # No security checks here
        return "Processed by Service A"


### After: Security in every service
class APIGateway:
    def handle_request(self, request):
        if not self.authenticate(request):
            return "Unauthorized"
        return self.forward_to_service(request)

class ServiceA:
    def process(self, request):
        if not self.authenticate(request):
            return "Unauthorized"
        if not self.authorize(request):
            return "Forbidden"
        return "Processed by Service A"

    def authenticate(self, request):
        # Verify token or credentials
        return True

    def authorize(self, request):
        # Check permissions
        return True

    def forward_to_service(self, request):
        # Placeholder for forwarding logic
        pass

    def authenticate(self, request):
        # Placeholder for authentication logic
        return True

Alternatives

Perimeter Security Only

Security checks are only at the system edge or API gateway, trusting internal services implicitly.

Use when: Use when the system is small, internal network is fully trusted, and performance is critical.

Service Mesh Security

Uses a dedicated infrastructure layer to enforce security policies between services transparently.

Use when: Choose when you want centralized security enforcement without modifying each service's code.

Summary

Relying only on perimeter security leaves internal services vulnerable to attacks.

Applying security checks in every service prevents attackers from moving inside the system after breaching the edge.

This approach supports zero-trust models and improves overall system security and resilience.

Practice

1. Why is it important to include security measures in every microservice rather than just at the entry point?

easy

A. Because security slows down the system if applied everywhere.

B. Because only the first service handles sensitive data.

C. Because each service can be accessed independently and needs protection.

D. Because microservices do not communicate with each other.

Solution

1. Step 1: Understand microservice independence

   Each microservice can be called directly or by other services, so it can be a target for attacks.

2. Step 2: Recognize the need for protection at all points

   If only the entry point is secured, other services remain vulnerable to unauthorized access.

3. Final Answer:

   Because each service can be accessed independently and needs protection. -> Option C

4. Quick Check:

   Security must cover all services = C [OK]

Hint: Remember: every door needs a lock, not just the front door [OK]

Common Mistakes:

• Thinking only the first service needs security
• Assuming microservices don't communicate
• Believing security everywhere slows system too much

2. Which of the following is the correct way to enforce security in a microservice?

easy

A. Apply authentication only at the API gateway.

B. Disable auditing to reduce storage costs.

C. Skip authorization checks inside services to improve speed.

D. Use encryption for data in transit and at rest within each service.

Solution

1. Step 1: Identify proper security practices

   Encryption protects data both when moving between services and when stored inside each service.

2. Step 2: Evaluate other options

   Authentication only at gateway leaves internal services vulnerable; skipping authorization and auditing weakens security.

3. Final Answer:

   Use encryption for data in transit and at rest within each service. -> Option D

4. Quick Check:

   Encryption everywhere = B [OK]

Hint: Encrypt data everywhere, not just at the edges [OK]

Common Mistakes:

• Thinking authentication at gateway is enough
• Ignoring authorization inside services
• Disabling auditing to save space

3. Consider a microservice architecture where Service A calls Service B. If Service A authenticates the user but Service B does not verify the user's permissions, what is the likely outcome?

medium

A. Service B will reject all requests from Service A.

B. Service B may perform unauthorized actions on behalf of the user.

C. Service A will automatically enforce permissions on Service B.

D. The system will be faster and more secure.

Solution

1. Step 1: Analyze authentication vs authorization

   Authentication confirms identity; authorization checks permissions. If Service B skips authorization, it trusts Service A blindly.

2. Step 2: Understand security risk

   Without permission checks, Service B may allow actions the user is not allowed to perform, causing security breaches.

3. Final Answer:

   Service B may perform unauthorized actions on behalf of the user. -> Option B

4. Quick Check:

   Authorization missing in called service = A [OK]

Hint: Authenticate once, authorize everywhere [OK]

Common Mistakes:

• Assuming authentication covers authorization
• Believing Service A controls permissions for Service B
• Thinking skipping checks improves security

4. A developer forgot to add encryption for data stored in Service C, while all other services use encryption. What is the main security risk introduced?

medium

A. Data in Service C can be read if storage is accessed by attackers.

B. Service C will reject all incoming requests.

C. Encryption is not needed if network is secure.

D. Other services will stop working due to mismatch.

Solution

1. Step 1: Identify impact of missing encryption at rest

   Without encryption, stored data in Service C is vulnerable to theft if storage is compromised.

2. Step 2: Evaluate other options

   Service C will not reject requests just because of missing encryption; network security does not protect stored data; other services remain unaffected.

3. Final Answer:

   Data in Service C can be read if storage is accessed by attackers. -> Option A

4. Quick Check:

   Missing encryption at rest = D [OK]

Hint: Encrypt stored data to prevent leaks [OK]

Common Mistakes:

• Assuming network security protects stored data
• Thinking missing encryption breaks service functionality
• Believing other services fail due to one missing encryption

5. You are designing a microservices system handling sensitive user data. Which combination of security practices ensures comprehensive protection across all services?

hard

A. Authentication and authorization in each service, encryption in transit and at rest, and distributed auditing.

B. Authentication at gateway, no encryption inside services, centralized auditing.

C. No authentication, encryption only at database, auditing only on gateway.

D. Authentication only in some services, no authorization, encryption only in transit.

Solution

1. Step 1: Identify key security components

   Authentication and authorization must be enforced in every service to verify identity and permissions.

2. Step 2: Ensure data protection and monitoring

   Encryption protects data both moving and stored; auditing across services tracks actions for accountability.

3. Step 3: Evaluate options

   Authentication and authorization in each service, encryption in transit and at rest, and distributed auditing. covers all these best practices; others miss critical elements like authorization or encryption.

4. Final Answer:

   Authentication and authorization in each service, encryption in transit and at rest, and distributed auditing. -> Option A

5. Quick Check:

   Complete security coverage = A [OK]

Hint: Secure identity, data, and logs everywhere [OK]

Common Mistakes:

• Relying only on gateway security
• Skipping authorization checks
• Ignoring encryption at rest or auditing