We created this Green Belt path for developers coding in the AWS and the cloud. It includes our standard 12 Green Belt Secure Development modules with the addition of 12 new Secure Coding with Ruby 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.
Cloud Security: AWS
Green Belt Path
Introduction to AWS Security
This module explains why mastering cloud security is crucial, the differences between traditional and cloud security, and presents the elements of a strong security methodology.
AWS Five Cloud Security Disciplines
This module introduces five cloud security disciplines, explains how each one can be bolstered, and describe the most common points of cloud security failure.
This module, teaches the top ten AWS security actions, how to choose the best approaches to security, and how to promote security culture and discipline for cloud services.
AWS Secure Access Control
This module reviews IAM fundamentals, explains the best use cases for users, groups, and roles, dive deeper into policies, application of security strategies and controls to curate access, and detection of misconfigured or misbehaving entities using AWS tools.
This module, teaches S3 access control, how to set up and associate S3 buckets with VPC endpoints, how to select the best approach to encryption, how to enforce object persistence, and detect misconfigured buckets and malicious access.
This module explains how to select a reliable OS distribution, why hands-off updates are crucial, how to manage policies and role assignment securely, how to protect instances using VPCs and security groups, and how to protect configuration values.
In this module, we explain the benefits of centralized and structured logging, how to setup life cycle policies and replication for logs, and how to analyze and issue log-sourced alerts with AWS tools.
In this module we introduced AWS Secrets Manager, explaining how to distribute secrets granularly and securely, how secrets encryption and rotation works, how to audit access to secrets using Cloud Trail, and how to provide secrets to legacy applications without re-writing.
This module introduces several security tools for each cloud security discipline, teaches how to divide and conquer elements of offending infrastructure, and explains how to select the most important tools and integrate them into your DevOps workflow.