We created this Green Belt path for developers coding in Kubernetes with nine learning modules. Each of our lessons are short and conclude with a brief ten question assessment. The learning module length is purposeful – they are perfect for filling gaps in a developer’s day while code is deploying.
Secure Development Core Lesson Modules
Intro to Secure Development
The definition of secure development and it’s pieces. Each developer has secure development responsibilities. Secure development starts and ends with the developer. Your software, hardware, and infrastructure are only as safe as you make them. Developers are the first line of defense.
The need for secure coding, what are secure coding standards and how does a developer use them, and the potential dangers of Stack Overflow. Languages are complex. Secure coding is about creating code that is correct and secure.
Secure Coding Best Practices: Part 1
Explore the OWASP Proactive Controls, including Define Security Requirements, Leverage Security Frameworks and Libraries, Secure Database Access, Encode and Escape Data, and Validate All Inputs. OWASP Proactive Controls is security information written for developers, by developers.
Secure Coding Best Practices: Part 2
Explore the OWASP Proactive Controls, including Enforce Access Control, Protect Data Everywhere, Implement Security Logging and Monitoring, and Handle All Errors and Exceptions. OWASP Proactive Controls is security information written for developers, by developers.
In this module, we explain how a languages type system is categorized and what the main categories are. We discuss the difference between static and dynamic languages as well as weak and strongly typed languages.
Securing the Development Environment
The threats that your development environment faces, how to reduce development environment risk, and the ten tips to secure your development environment. Development environment threats are real and following simple tips to secure your development environment can significantly reduce your exposure.
Protecting your Code Repository
Why you need to protect your code repository, the security challenges in choosing a repository, the impact of not protecting access credentials and separating secrets in the source code. Your code is your product or application. If it is left unsecured, it could fall into the hands of a competitor.
Producing a Clean, Maintainable, & Secure Code Culture
The sources of complexity in software that led to security vulnerabilities and the twelve laws that act as the foundation for a clean, maintainable, and secure code culture. Developers must strive for secure code. Secure code is both clean and maintainable.
Potential security threats are impacting your release and deployment process and ways to improve the security of your release and deployment process. The release and deployment process is how our code gets delivered to our customers. The introduction of an unauthorized piece of code by an attacker could be devastating.
Designing a Secure App or Product
The four pillars of a secure application or product, secure application or product decisions, and the categories of the design of a secure application or product. A new application or product deserves a secure design. Security becomes a reality through careful design choices.
Thinking Like A Penetration Tester
The tools and methodologies to help a developer think like a penetration tester, how penetration testers use browsers and intercepting proxies, testing, fuzzing, and reverse engineering, and applying the knowledge of these topics to your world as a developer. Developers generally focus on the build; to better secure your applications, products, and systems, think like one who breaks.
Secure Design Principles in Action: Part 1
The economy of mechanism, secure the weakest link, establish trust boundaries, defense in-depth, don’t reinvent the wheel, usable security and default deny. Secure design principles require action to achieve “secure by design.”
Secure Design Principles in Action: Part 2
In this module, we explore secure design principles such as minimizing the attack surface, fail securely, least privileged, separation of duties, do not trust services/ infrastructure, and secure defaults. Employing a common understanding of secure design principles encourages secure design, and secure design equals fewer vulnerabilities.
Green Belt Path
Introduction to Kubernetes Security
The Kubernetes high-level architecture and introduce the various Kubernetes security features and functionality.
Kubernetes: Attack Surface
The attack surface that a Kubernetes installation exposes and how to implement a secure Kubernetes architecture that minimizes attack surface.
Kubernetes: Threat Landscape
Various security threats that exist against Kubernetes, including host compromise, malicious node, malicious container, compromise of credentials, other containers via the network, other resources via the network, stealing secrets, DoS, and data exfiltration and recognize how these threats could be used to compromise Kubernetes hosts, nodes, containers, and the network. We also impart an appreciation for why you need to harden Kubernetes containers and container infrastructure.
Kubernetes: Network Policy
This module covers the concept of fields in a Network Security Policy and how to use To/From Selectors. This module also includes a walk-through on how to set up a Kubernetes Network Security Policy.
Kubernetes: Pod Security Policy
Introduce the concept of a Pod Security Policy and examine the steps to incorporate a Pod Security Policy, including understanding the options, building a working policy, deploy/test the policy, adjust, and deploy to production. We also explore the various pieces of a Pod Security Policy, including privileged, host namespaces, volumes/filesystems, users/groups, privilege escalation, capabilities, SE Linux/AppArmor, SecComp, and Sysctl.
Kubernetes: Best Practices, Part One
Security best practices including secure the base OS, upgrade to the latest version, design with a private topology, firewall inbound traffic, utilize a bastion host for SSH access, harden according to the CIS Kubernetes Benchmark, control access to the Kubernetes API, restrict access to etcd, and disable default service account and dashboard.
Kubernetes: Best Practices, Part Two
Security best practices including enable authentication using OIDC or X.509 certificates and use service account tokens for applications and workloads, use namespaces to establish security boundaries, limit resource usage on the cluster using quotas, and separate sensitive workloads to reduce the risk of sensitive applications being accessed by less secure applications that share a container runtime or host.
Kubernetes: Best Practices, Part Three
Security best practices include turning on audit logging, enacting an audit policy, sending audit records to log, webhook, or dynamic backends, encrypting secrets at rest and protecting the data stored in your etcd database, and detecting misconfigurations in your running Kubernetes clusters and nodes.
Kubernetes: Role Based Access Control (RBAC)
Learn how authorization works within Kubernetes, the request verbs and attributes that make up Kubernetes RBAC policies, the categories of pre-defined roles within Kubernetes, and
the tools for testing Kubernetes RBAC.