Microservices Security in Action
Prabath Siriwardena and Nuwan Dias
  • July 2020
  • ISBN 9781617295959
  • 616 pages
  • printed in black & white

A complete guide to the challenges and solutions in securing microservices architectures.

Massimo Siani, FinDynamic
Unlike traditional enterprise applications, Microservices applications are collections of independent components that function as a system. Securing the messages, queues, and API endpoints requires new approaches to security both in the infrastructure and the code. Microservices Security in Action teaches you how to address microservices-specific security challenges throughout the system. This practical guide includes plentiful hands-on exercises using industry-leading open-source tools and examples using Java and Spring Boot.

About the Technology

Integrating independent services into a single system presents special security challenges in a microservices deployment. With proper planning, however, you can build in security from the start. Learn to create secure services and protect application data throughout development and deployment. As microservices continue to change enterprise application systems, developers and architects must learn to integrate security into their design and implementation. Because microservices are created as a system of independent components, each a possible point of failure, they can multiply the security risk. With proper planning, design, and implementation, you can reap the benefits of microservices while keeping your application data—and your company's reputation—safe!

About the book

Microservices Security in Action is filled with solutions, teaching best practices for throttling and monitoring, access control, and microservice-to-microservice communications. Detailed code samples, exercises, and real-world use cases help you put what you've learned into production. Along the way, authors and software security experts Prabath Siriwardena and Nuwan Dias shine a light on important concepts like throttling, analytics gathering, access control at the API gateway, and microservice-to-microservice communication. You'll also discover how to securely deploy microservices using state-of-the-art technologies including Kubernetes, Docker, and the Istio service mesh. Lots of hands-on exercises secure your learning as you go, and this straightforward guide wraps up with a security process review and best practices. When you're finished reading, you'll be planning, designing, and implementing microservices applications with the priceless confidence that comes with knowing they're secure!
Table of Contents detailed table of contents

Part 1: Overview

1 Microservices security landscape

1.1 How security works in a monolithic application

1.2 Challenges of securing microservices

1.2.1 The broader the attack surface, the higher the risk of attack

1.2.2 Distributed security screening may result in poor performance

1.2.3 Deployment complexities make bootstrapping trust among microservices a nightmare

1.2.4 Requests spanning multiple microservices are harder to trace

1.2.5 Immutability of containers challenges how you maintain service credentials and access-control policies

1.2.6 The distributed nature of microservices makes sharing user context harder

1.2.7 Polyglot architecture demands more security expertise on each development team

1.3 Key security fundamentals

1.3.1 Authentication protects your system against spoofing

1.3.2 Integrity protects your system from data tampering

1.3.3 Nonrepudiation: Do it once, and you own it forever

1.3.4 Confidentiality protects your systems from unintended information disclosure

1.3.5 Availability: Keep the system running, no matter what

1.3.6 Authorization: Nothing more than you’re supposed to do

1.4 Edge security

1.4.1 The role of an API gateway in a microservices deployment

1.4.2 Authentication at the edge

1.4.3 Authorization at the edge

1.4.4 Passing client/end-user context to upstream microservices

1.5 Securing service-to-service communication

1.5.1 Service-to-service authentication

1.5.2 Service-level authorization

1.5.3 Propagating user context among microservices

1.5.4 Crossing trust boundaries

Summary

2 First steps in securing microservices

2.1 Building your first microservice

2.1.1 Downloading and installing the required software

2.1.2 Clone samples repository

2.1.3 Compiling the Order Processing microservice

2.1.4 Accessing the Order Processing microservice

2.1.5 What is inside the source code directory?

2.1.6 Understanding the source code of the microservice

2.2 Setting up an OAuth 2.0 server

2.2.1 The interactions with an authorization server

2.2.2 Running the OAuth 2.0 authorization server

2.2.3 Getting an access token from the OAuth 2.0 authorization server

2.2.4 Understanding the access token response

2.3 Securing a microservice with OAuth 2.0

2.3.1 Security based on OAuth 2.0

2.3.2 Running the sample

2.4 Invoking a secured microservice from a client application

2.5 Performing service-level authorization with OAuth 2.0 scopes

2.5.1 Obtaining a scoped access token from the authorization server

2.5.2 Protecting access to a microservice with OAuth 2.0 scopes

Summary

Part 2: Edge security

3 Securing north/south traffic with an API gateway

3.1 The need for an API gateway in a microservices deployment

3.1.1 Decoupling security from the microservice

3.1.2 The inherent complexities of microservice deployments make them harder to consume

3.1.3 The rawness of microservices does not make them ideal for external exposure

3.2 Security at the edge

3.2.1 Understanding the consumer landscape of your microservices

3.2.2 Delegating access

3.2.3 Why not basic authentication to secure APIs?

3.2.4 Why not mutual TLS to secure APIs?

3.2.5 Why OAuth 2.0?

3.3 Setting up an API gateway with Zuul

3.3.1 Compiling and running the Order Processing microservice

3.3.2 Compiling and running the Zuul proxy

3.3.3 Enforcing OAuth 2.0-based security at the Zuul gateway

3.4 Securing communication between Zuul and the microservice

3.4.1 Preventing access through the firewall

3.4.2 Securing the communication between the API gateway and microservices by using mutual TLS

Summary

4 Accessing a secured microservice via a single-page application

4.1 Running a single-page application with Angular

4.1.1 Building and running an Angular application from the source code

4.1.2 Looking behind the scenes of a single-page application

4.2 Setting up cross-origin resource sharing

4.2.1 Using the same-origin policy

4.2.2 Using cross-origin resource sharing

4.2.3 Inspecting the source that allows cross-origin requests

4.2.4 Proxying the resource server with an API gateway

4.3 Securing a SPA with OpenID Connect

4.3.1 Understanding the OpenID Connect login flow

4.3.2 Inspecting the code of the applications

4.4 Using federated authentication

4.4.1 Multiple trust domains

4.4.2 Building trust between domains

Summary

5 Engaging throttling, monitoring, and access control

5.1 Throttling at the API gateway with Zuul

5.1.1 Quota-based throttling for applications

5.1.2 Fair usage policy for users

5.1.3 Applying quota-based throttling to the Order Processing microservice

5.1.4 Maximum handling capacity of a microservice

5.1.5 Operation-level throttling

5.1.6 Throttling the OAuth 2.0 token and authorize endpoints

5.1.7 Privilege-based throttling

5.2 Monitoring and analytics with Prometheus and Grafana

5.2.1 Monitoring the Order Processing microservice

5.2.2 Behind the scenes of using Prometheus for monitoring

5.3 Enforcing access-control policies at the API gateway with Open Policy Agent

5.3.1 Running OPA as a Docker container

5.3.2 Feeding the OPA engine with data

5.3.3 Feeding the OPA engine with access-control policies

5.3.4 Evaluating OPA policies

5.3.5 Next steps in using OPA

Summary

Part 3: Service-to-service communications

6 Securing east/west traffic with certificates

6.1 Why use mTLS?

6.1.1 Building trust between a client and a server with a certificate authority

6.1.2 Mutual TLS helps the client and the server to identify each other

6.1.3 HTTPS is HTTP over TLS

6.2 Creating certificates to secure access to microservices

6.2.1 Creating a certificate authority

6.2.2 Generating keys for the Order Processing microservice

6.2.3 Generating keys for the Inventory microservice

6.2.4 Using a single script to generate all the keys

6.3 Securing microservices with TLS

6.3.1 Running the Order Processing microservice over TLS

6.3.2 Running the Inventory microservice over TLS

6.3.3 Securing communications between two microservices with TLS

6.4 Engaging mTLS

6.5 Challenges in key management

6.5.1 Key provisioning and bootstrapping trust

6.5.2 Certificate revocation

6.6 Key rotation

6.7 Monitoring key usage

Summary

7 Securing east/west traffic with JWT

7.1 Use cases for securing microservices with JWT

7.1.1 Sharing user context between microservices with a shared JWT

7.1.2 Sharing user context with a new JWT for each service-to-service interaction

7.1.3 Sharing user context between microservices in different trust domains

7.1.4 Self-issued JWTs

7.1.5 Nested JWTs

7.2 Setting up an STS to issue a JWT

7.3 Securing microservices with JWT

7.4 Using JWT as a data source for access control

7.5 Securing service-to-service communications with JWT

7.6 Exchanging a JWT for a new one with a new audience

Summary

8 Securing east/west traffic over gRPC

8.1 Service-to-service communications over gRPC

8.2 Securing gRPC service-to-service communications with mTLS

8.3 Securing gRPC service-to-service communications with JWT

Summary

9 Securing reactive microservices

9.1 Why reactive microservices?

9.2 Setting up Kafka as a message broker

9.3 Developing a microservice to push events to a Kafka topic

9.4 Developing a microservice to read events from a Kafka topic

9.5 Using TLS to protect data in transit

9.5.1 Creating and signing the TLS keys and certificates for Kafka

9.5.2 Configuring TLS on the Kafka server

9.5.3 Configuring TLS on the microservices

9.6 Using mTLS for authentication

9.7 Controlling access to Kafka topics with ACLs

9.7.1 Enabling ACLs on Kafka and identifying the clients

9.7.2 Defining ACLs on Kafka

9.8 Setting up NATS as a message broker

Summary

Part 4: Secure deployment

10 Conquering container security with Docker

10.1 Running the security token service on Docker

10.2 Managing secrets in a Docker container

10.2.1 Externalizing secrets from Docker images

10.2.2 Passing secrets as environment variables

10.2.3 Managing secrets in a Docker production deployment

10.3 Using Docker Content Trust to sign and verify Docker images

10.3.1 The Update Framework

10.3.2 Docker Content Trust

10.3.3 Generating keys

10.3.4 Signing with DCT

10.3.5 Signature verification with DCT

10.3.6 Types of keys used in DCT

10.3.7 How DCT protects the client application from replay attacks

10.4 Running the Order Processing microservice on Docker

10.5 Running containers with limited privileges

10.5.1 Running a container with a nonroot user

10.5.2 Dropping capabilities from the root user

10.6 Running Docker Bench for security

10.7 Securing access to the Docker host

10.7.1 Enabling remote access to the Docker daemon

10.7.2 Enabling mTLS at the NGINX server to secure access to Docker APIs

10.8 Considering security beyond containers

Summary

11 Securing microservices on Kubernetes

11.1 Running an STS on Kubernetes

11.1.1 Defining a Kubernetes Deployment for the STS in YAML

11.1.2 Creating the STS Deployment in Kubernetes

11.1.3 Troubleshooting the Deployment

11.1.4 Exposing the STS outside the Kubernetes cluster

11.2 Managing secrets in a Kubernetes environment

11.2.1 Using ConfigMap to externalize configurations in Kubernetes

11.2.2 Defining a ConfigMap for application.properties file

11.2.3 Defining ConfigMaps for keystore.jks and jwt.jks files

11.2.4 Defining a ConfigMap for keystore credentials

11.2.5 Creating ConfigMaps by using the kubectl client

11.2.6 Consuming ConfigMaps from a Kubernetes Deployment

11.2.7 Loading keystores with an init container

11.3 Using Kubernetes Secrets

11.3.1 Exploring the default token secret in every container

11.3.2 Updating the STS to use Secrets

11.3.3 Understanding how Kubernetes stores Secrets

11.4 Running the Order Processing microservice in Kubernetes

11.4.1 Creating ConfigMaps/Secrets for the Order Processing microservice

11.4.2 Creating a Deployment for the Order Processing microservice

11.4.3 Creating a Service for the Order Processing microservice

11.4.4 Testing the end-to-end flow

11.5 Running the Inventory microservice in Kubernetes

11.6 Using Kubernetes service accounts

11.6.1 Creating a service account and associating it with a Pod

11.6.2 Benefits of running a Pod under a custom service account

11.7 Using role-based access control in Kubernetes

11.7.1 Talking to the Kubernetes API server from the STS

11.7.2 Associating a service account with a ClusterRole

Summary

12 Securing microservices with Istio service mesh

12.1 Setting up the Kubernetes deployment

12.1.1 Enabling Istio autoinjection

12.1.2 Clean up any previous work

12.1.3 Deploying microservices

12.1.4 Redeploying Order Processing and STS as NodePort Services

12.1.5 Testing end-to-end flow

12.2 Enabling TLS termination at the Istio Ingress gateway

12.2.1 Deploying TLS certificates to the Istio Ingress gateway

12.2.2 Deploying VirtualServices

12.2.3 Defining a permissive authentication policy

12.2.4 Testing end-to-end flow

12.3 Securing service-to-service communications with mTLS

12.4 Securing service-to-service communications with JWT

12.4.1 Enforcing JWT authentication

12.4.2 Testing end-to-end flow with JWT authentication

12.4.3 Peer authentication and request authentication

12.4.4 How to use JWT in service-to-service communications

12.4.5 A closer look at JSON Web Key

12.5 Enforcing authorization

12.5.1 A closer look at the JWT

12.5.2 Enforcing role-based access control

12.5.3 Testing end-to-end flow with RBAC

12.5.4 Improvements to role-based access control since Istio 1.4.0

12.6 Managing keys in Istio

12.6.1 Key provisioning and rotation via volume mounts

12.6.2 Limitations in key provisioning and rotation via volume mounts

12.6.3 Key provisioning and rotation with SDS

Summary

Part 5: Secure development

13 Secure coding practices and automation

13.1 OWASP API security top 10

13.1.1 Broken object-level authorization

13.1.2 Broken authentication

13.1.3 Excessive data exposure

13.1.4 Lack of resources and rate limiting

13.1.5 Broken function-level authorization

13.1.6 Mass assignment

13.1.7 Security misconfiguration

13.1.8 Injection

13.1.9 Improper asset management

13.1.10 Insufficient logging and monitoring

13.2 Running static code analysis

13.3 Integrating security testing with Jenkins

13.3.1 Setting up and running Jenkins

13.3.2 Setting up a build pipeline with Jenkins

13.4 Running dynamic analysis with OWASP ZAP

13.4.1 Passive scanning vs. active scanning

13.4.2 Performing penetration tests with ZAP

Summary

Appendixes

Appendix A: OAuth 2.0 and OpenID Connect

A.1 The access delegation problem

A.2 How does OAuth 2.0 fix the access delegation problem?

A.3 Actors of an OAuth 2.0 flow

A.3.1 The role of the resource server

A.3.2 The role of the client application

A.3.3 The role of the resource owner

A.3.4 The role of the authorization server

A.4 Grant types

A.4.1 Client credentials grant type

A.4.2 Resource owner password grant type

A.4.3 Refresh token grant type

A.4.4 Authorization code grant type

A.4.5 Implicit grant type

A.5 Scopes bind capabilities to an OAuth 2.0 access token

A.6 Self-contained access tokens

A.7 What is OpenID Connect?

A.8 More information about OpenID Connect and OAuth 2.0

Appendix B: JSON Web Token

B.1 What is a JSON Web Token?

B.2 What does a JWT look like?

B.2.1 The issuer of a JWT

B.2.2 The subject of a JWT

B.2.3 The audience of a JWT

B.2.4 JWT expiration, not before and issued time

B.2.5 The JWT identifier

B.3 JSON Web Signature

B.4 JSON Web Encryption

Appendix C: Single-page application architecture

C.1 What is single-page application architecture?

C.2 Benefits of a SPA over an MPA

C.3 Drawbacks of a SPA compared with an MPA

Appendix D: Observability in a microservices deployment

D.1 The need for observability

D.2 The four pillars of observability

D.2.1 The importance of metrics in observability

D.2.2 The importance of tracing in observability

D.2.3 The importance of logging in observability

D.2.4 The importance of visualization in observability

Appendix E: Docker fundamentals

E.1 Docker overview

E.1.1 Containers prior to Docker

E.1.2 Docker adding value to Linux containers

E.1.3 Virtual machines vs. containers

E.1.4 Running Docker on non-Linux operating systems

E.2 Installing Docker

E.3 Docker high-level architecture

E.4 Containerizing an application

E.4.1 What is a Docker image?

E.4.2 Building the application

E.4.3 Creating a Dockerfile

E.4.4 Building a Docker image

E.4.5 Running a container from a Docker image

E.5 Container name and container ID

E.6 Docker registry

E.6.1 Docker Hub

E.6.2 Harbor

E.6.3 Docker cloud platforms and registries

E.7 Publishing to Docker Hub

E.8 Image name and image ID

E.8.1 Docker images with no tags (or the latest tag)

E.8.2 Docker images with a tag

E.8.3 Working with third-party Docker registries

E.8.4 Docker Hub official and unofficial images

E.8.5 Image ID

E.8.6 Pulling an image with the image ID

E.9 Image layers

E.10 Container life cycle

E.10.1 Creating a container from an image

E.10.2 Starting a container

E.10.3 Pausing a running container

E.10.4 Stopping a running container

E.10.5 Killing a container

E.10.6 Destroying a container

E.11 Deleting an image

E.12 Persisting runtime data of a container

E.12.1 Using Docker volumes to persist runtime data

E.12.2 Using bind mounts to persist runtime data

E.13 Docker internal architecture

E.13.1 Containerd

E.13.2 Containerd-shim

E.13.3 Runc

E.13.4 Linux namespaces

E.13.5 Linux cgroups

E.14 What is happening behind the scenes of docker run?

E.15 Inspecting traffic between Docker client and host

E.16 Docker Compose

E.17 Docker Swarm

E.18 Docker networking

E.18.1 Bridge networking

E.18.2 Host networking

E.18.3 No networking

E.18.4 Networking in a Docker production deployment

E.19 Moby project

Appendix F: Open Policy Agent

F.1 Key components in an access-control system

F.2 What is an Open Policy Agent?

F.3 OPA high-level architecture

F.4 Deploying OPA as a Docker container

F.5 Protecting an OPA server with mTLS

F.6 OPA policies

F.7 External data

F.7.1 Push data

F.7.2 Loading data from the filesystem

F.7.3 Overload

F.7.4 JSON Web Token

F.7.5 Bundle API

F.7.6 Pull data during evaluation

F.8 OPA integrations

F.8.1 Istio

F.8.2 Kubernetes admission controller

F.8.3 Apache Kafka

F.9 OPA alternatives

Appendix G: Observability in a microservices deployment

F.1 The need for observability

F.2 The four pillars of Observability

F.2.1 The importance of metrics in observability

F.2.2 The importance of tracing in observability

G.1 Creating a certificate authority

G.2 Generating keys for an application

Appendix I: Secure Production Identity Framework for Everyone

H.1 What is SPIFFE?

H.2 The inspiration behind SPIFFE

H.3 SPIFFE ID

H.4 How SPIRE works

H.5 SPIFFE Verifiable Identity Document

H.5.1 X.509-SVID

H.5.2 JWT-SVID

H.6 A trust bundle

Appendix J: gRPC fundamentals

I.1 What is gRPC?

I.2 Understanding Protocol Buffers

I.3 Understanding HTTP/2 and its benefits over HTTP/1.x

I.3.1 Request/response multiplexing and its performance benefits

I.3.2 Understanding binary framing and streams in HTTP/2

I.4 The different types of RPC available in gRPC

I.4.1 Understanding channels

I.4.2 Understanding request metadata

I.4.3 What is unary RPC?

I.4.4 What is server streaming RPC?

I.4.5 What is client streaming RPC?

I.4.6 What is bidirectional streaming RPC?

Appendix K: Kubernetes fundamentals

J.1 Kubernetes high-level architecture

J.1.1 Master nodes

J.1.2 Worker nodes

J.2 Basic constructs

J.2.1 A Pod: The smallest deployment unit in Kubernetes

J.2.2 A node: A VM or physical machine in a Kubernetes cluster

J.2.3 A Service: an abstraction over Kubernetes Pods

J.2.4 Deployments: Representing your application in Kubernetes

J.2.5 A namespace: Your home within a Kubernetes cluster

J.3 Getting started with Minikube and Docker Desktop

J.4 Kubernetes as a service

J.5 Getting started with Google Kubernetes Engine

J.5.1 Installing gcloud

J.5.2 Installing kubectl

J.5.3 Setting up the default setting for gcloud

J.5.4 Creating a Kubernetes cluster

J.5.5 Deleting a Kubernetes cluster

J.5.6 Switching between multiple Kubernetes clusters

J.6 Creating a Kubernetes Deployment

J.7 Behind the scenes of a Deployment

J.8 Creating a Kubernetes Service

J.9 Behind the scenes of a Service

J.10 Scaling a Kubernetes Deployment

J.11 Creating a Kubernetes namespace

J.12 Switching Kubernetes namespaces

J.13 Using Kubernetes objects

J.13.1 Managing Kubernetes objects

J.14 Exploring the Kubernetes API server

J.15 Kubernetes resources

J.16 Kubernetes controllers

J.17 Ingress

J.18 Kubernetes internal communication

J.18.1 How kubectl run works

J.18.2 How Kubernetes routes a request from an external client to a Pod

J.19 Managing configurations

J.19.1 Hardcoding configuration data in the Deployment definition

J.19.2 Introducing ConfigMaps

J.19.3 Consuming ConfigMaps from a Kubernetes Deployment and populating environment variables

J.19.4 Consuming ConfigMaps from a Kubernetes Deployment with volume mounts

Appendix L: Service mesh and Istio fundamentals

K.1 Why a service mesh?

K.1 The evolution of microservice deployments

K.2.1 The Service Mesh architecture

K.2.2 Service mesh implementations

K.2.3 Service mesh vs. API gateway

K.3 Istio service mesh

K.4 Istio architecture

K.4.1 Istio data plane

K.4.2 Istio control plane

K.4.3 Changes introduced to Istio architecture since Istio 1.5.0 release

K.5 Setting up Istio service mesh on Kubernetes

K.5.1 Setting up Istio on Docker Desktop

K.5.2 Setting up Istio on GKE

K.5.3 Limitations of Istio on GKE

K.6 What Istio brings to a Kubernetes cluster

K.6.1 Kubernetes custom resource definitions

K.6.2 The istio-system namespace

K.6.3 Control plane components

K.6.4 The istio-ingressgateway Service

K.6.5 The istio-ingressgateway pod

K.6.6 Istio’s MeshPolicy

K.7 Setting up the Kubernetes deployment

K.8 Engaging Istio to STS and the Order Processing microservices

K.8.1 Sidecar auto injection

K.8.2 Setting up iptables rules

K.8.3 Envoy sidecar proxy

K.9 Running the end-to-end sample

K.10 Updating the Order Processing microservice with Istio configurations

K.10.1 Redeploying STS and the Order Processing microservices

K.10.2 Creating a Gateway resource

K.10.3 Creating a VirtualService resource for the Order Processing and STS microservices

K.10.4 Running the end-to-end flow

K.10.5 Debugging the Envoy proxy

What's inside

  • Microservice security concepts
  • Edge services with an API gateway
  • Deployments with Docker, Kubernetes, and Istio
  • Security testing at the code level
  • Communications with HTTP, gRPC, and Kafka

About the reader

For experienced microservices developers with intermediate Java skills.

About the authors

Prabath Siriwardena is the vice president of security architecture at WSO2. Nuwan Dias is the director of API architecture at WSO2. They have designed secure systems for many Fortune 500 companies.

placing your order...

Don't refresh or navigate away from the page.
print book $69.99 pBook + eBook + liveBook
Additional shipping charges may apply
Microservices Security in Action (print book) added to cart
continue shopping
go to cart

eBook $55.99 3 formats + liveBook
Microservices Security in Action (eBook) added to cart
continue shopping
go to cart

Prices displayed in rupees will be charged in USD when you check out.
customers also reading

This book 1-hop 2-hops 3-hops

FREE domestic shipping on three or more pBooks