Part 5. Secure development
by Wajjakkara Kankanamge Anthony Nuwan Dias,
Prabath Siriwardena
Microservices Security in Action
- Microservices Security in Action
- Copyright
- dedication
- brief contents
- contents
- front matter
- 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.5 Securing service-to-service communication
- Summary
- 2 First steps in securing microservices
- Part 2. Edge security
- 3 Securing north/south traffic with an API gateway
- 4 Accessing a secured microservice via a single-page application
- 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.3 Enforcing access-control policies at the API gateway with Open Policy Agent
- Summary
- 5.1 Throttling at the API gateway with Zuul
- Part 3. Service-to-service communications
- 6 Securing east/west traffic with certificates
- 7 Securing east/west traffic with JWT
- 8 Securing east/west traffic over gRPC
- 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.6 Using mTLS for authentication
- 9.7 Controlling access to Kafka topics with ACLs
- 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.3 Using Docker Content Trust to sign and verify Docker images
- 10.4 Running the Order Processing microservice on Docker
- 10.5 Running containers with limited privileges
- 10.6 Running Docker Bench for security
- 10.7 Securing access to the Docker host
- 10.8 Considering security beyond containers
- Summary
- 11 Securing microservices on Kubernetes
- 11.1 Running an STS on Kubernetes
- 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.4 Running the Order Processing microservice in Kubernetes
- 11.5 Running the Inventory microservice in Kubernetes
- 11.6 Using Kubernetes service accounts
- 11.7 Using role-based access control in Kubernetes
- Summary
- 12 Securing microservices with Istio service mesh
- 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.4 Running dynamic analysis with OWASP ZAP
- Summary
- 13.1 OWASP API security top 10
- 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.4 Grant types
- 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
- Appendix C. Single-page application architecture
- Appendix D. Observability in a microservices deployment
- Appendix E. Docker fundamentals
- E.1 Docker overview
- E.2 Installing Docker
- E.3 Docker high-level architecture
- E.4 Containerizing an application
- E.5 Container name and container ID
- E.6 Docker registry
- E.7 Publishing to Docker Hub
- E.8 Image name and image ID
- E.9 Image layers
- E.10 Container life cycle
- E.11 Deleting an image
- E.12 Persisting runtime data of a container
- E.13 Docker internal architecture
- 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.19 Moby project
- Appendix F. Open Policy Agent
- Appendix G. Creating a certificate authority and related keys with OpenSSL
- Appendix H. Secure Production Identity Framework for Everyone
- Appendix I. gRPC fundamentals
- Appendix J. Kubernetes fundamentals
- J.1 Kubernetes high-level architecture
- J.2 Basic constructs
- J.3 Getting started with Minikube and Docker Desktop
- J.4 Kubernetes as a service
- J.5 Getting started with Google Kubernetes Engine
- 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.14 Exploring the Kubernetes API server
- J.15 Kubernetes resources
- J.16 Kubernetes controllers
- J.17 Ingress
- J.18 Kubernetes internal communication
- J.19 Managing configurations
- Appendix K. Service mesh and Istio fundamentals
- K.1 Why a service mesh?
- K.1 The evolution of microservice deployments
- K.3 Istio service mesh
- K.4 Istio architecture
- K.5 Setting up Istio service mesh on Kubernetes
- K.6 What Istio brings to a Kubernetes cluster
- K.7 Setting up the Kubernetes deployment
- K8 Engaging Istio to STS and the Order Processing microservices
- K.9 Running the end-to-end sample
- K.10 Updating the Order Processing microservice with Istio configurations
- index
Speed to production is one of the key motivations behind the microservices architecture. Automating security testing in the development process helps you catch bugs as early as possible in the development cycle, and minimizes the effort in fixing them. This part of the book teaches you how to automate security testing of your microservices with SonarQube, Jenkins, and OWASP ZAP.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.