Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Learn Kubernetes Security

You're reading from  Learn Kubernetes Security

Product type Book
Published in Jul 2020
Publisher Packt
ISBN-13 9781839216503
Pages 330 pages
Edition 1st Edition
Languages
Authors (2):
Kaizhe Huang Kaizhe Huang
Profile icon Kaizhe Huang
Pranjal Jumde Pranjal Jumde
Profile icon Pranjal Jumde
View More author details

Table of Contents (19) Chapters

Preface 1. Section 1: Introduction to Kubernetes
2. Chapter 1: Kubernetes Architecture 3. Chapter 2: Kubernetes Networking 4. Chapter 3: Threat Modeling 5. Chapter 4: Applying the Principle of Least Privilege in Kubernetes 6. Chapter 5: Configuring Kubernetes Security Boundaries 7. Section 2: Securing Kubernetes Deployments and Clusters
8. Chapter 6: Securing Cluster Components 9. Chapter 7: Authentication, Authorization, and Admission Control 10. Chapter 8: Securing Kubernetes Pods 11. Chapter 9: Image Scanning in DevOps Pipelines 12. Chapter 10: Real-Time Monitoring and Resource Management of a Kubernetes Cluster 13. Chapter 11: Defense in Depth 14. Section 3: Learning from Mistakes and Pitfalls
15. Chapter 12: Analyzing and Detecting Crypto-Mining Attacks 16. Chapter 13: Learning from Kubernetes CVEs 17. Assessments 18. Other Books You May Enjoy

Chapter 13

  1. Cluster administrators keep track of CVE IDs to ensure that the Kubernetes cluster is not vulnerable to a publicly known issue. Security researchers study the references section to understand the technical details of the issue to develop mitigations for a CVE. Lastly, attackers study the references section to find unpatched variations or use similar techniques to discover issues in other parts of the code.
  2. Client-side issues often lead to data exfiltration or code execution on the client side. Build machines or machines of cluster administrators often contain sensitive data, and an attack on such machines can have a significant economic impact on the organization.
  3. DoS issues on api-server can lead to disruption of the availability of the entire cluster.
  4. Unauthenticated DoS issues are more severe than authenticated DoS issues. Ideally, unauthenticated users should not be able to communicate with api-server. If an unauthenticated user is able to send requests...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}