You're reading from Hands-on Kubernetes on Azure, Third Edition Use Azure Kubernetes Service to automate management, scaling, and deployment of containerized applications

Product type Paperback

Published in May 2021

Publisher Packt

ISBN-13 9781801079945

Length 528 pages

Edition 3rd Edition

Languages

JavaScript

Tools

Azure

Concepts

Containerization

Authors (3):

Gunther Lenz

Nills Franssens

Shivakumar Gopalakrishnan

View More author details

Table of Contents (22) Chapters

Preface

Hands-on Kubernetes on Azure – Third Edition

Foreword

Section 1: The Basics FREE CHAPTER

1. Introduction to containers and Kubernetes

2. Getting started with Azure Kubernetes Service

Section 2: Deploying on AKS

3. Application deployment on AKS

4. Building scalable applications

5. Handling common failures in AKS

6. Securing your application with HTTPS

7. Monitoring the AKS cluster and the application

Section 3: Securing your AKS cluster and workloads

8. Role-based access control in AKS

9. Azure Active Directory pod‑managed identities in AKS

10. Storing secrets in AKS

11. Network security in AKS

Section 4: Integrating with Azure managed services

12. Connecting an application to an Azure database

13. Azure Security Center for Kubernetes

14. Serverless functions

15. Continuous integration and continuous deployment for AKS

Index

Neutralizing threats using Azure Defender

Now that you've explored the configuration best practices using Azure Security Center and Secure Score, you will explore how to investigate and deal with security alerts and active threats. Some of the workloads you created should have triggered security alerts by now, which you can investigate in Azure Defender.

Specifically, in the Deploying offending workloads section, you created three workloads that trigger security alerts in Azure Defender:

crypto-miner.yaml: By deploying this file, you created a crypto-miner on your cluster. This crypto-miner will generate two security alerts in Azure Defender as you will see in this section. One alert will be generated by monitoring the Kubernetes cluster itself, while another alert will be generated based on DNS traffic.
role.yaml: This file contained a cluster-wide role with very broad permissions. This will generate a security alert in Azure Defender notifying you of the risk...