We created this Green Belt path for developers coding in the Ruby on Rails framework. 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.
Secure Coding with Ruby on Rails
Green Belt Path
Discuss the importance of security in the Ruby ecosystem, how modern Ruby on Rails applications
are structured, the threats that exist with Ruby and Rails applications, and how security practices can protect your applications.
Describe the different types of threats that impact Ruby and the consequences of a successful attack scenario for each specific threat.
Secure Coding with Ruby | Part 1
Discuss defensive programming, secure coding, and the five failures of defensive programming. We introduce the Zen of Ruby, the Ruby Style Guide, style automation, RBS, line-of-sight functions, and self-documenting code.
Secure Coding with Ruby | Part 2
Continue the exploration of safe coding tips for Ruby, including using proper operators, exception pitfalls, dangerous functions, and immortal symbols.
Input Validation with Ruby
Explain the importance of validating input from untrusted resources. We also describe the role of Active Record in validation within Ruby on Rails and list the different methods that can be used to validate untrusted input.
In this module, we review Injection, Broken Authentication, and Sensitive Data Exposure. We examine a description of each item, the risk to products and applications, applicable languages, and how to mitigate each risk. The OWASP Top 10 is the most popular application security document and contains the definitive industry list of security risks.
In this module, we review XML External Entity, Broken Access Control, Security Misconfiguration, and Cross-Site Scripting. We examine a description of each item, the risk to products and applications, applicable languages, and how to mitigate each risk. The OWASP Top 10 is the most popular application security document and contains the definitive industry list of security risks.
In this module, we review Insecure Deserialization, Using Components with Known Vulnerabilities, and Insufficient Logging & Monitoring. We examine a description of each item, the risk to products and applications, applicable languages, and how to mitigate each risk. The OWASP Top 10 is the most popular application security document and contains the definitive industry list of security risks.
Secure Software Supply Chain
Define how to secure the software supply chain for Ruby applications. We also, list the classes of Ruby supply chain threats, Describe the different types of attacks against the Ruby supply chain, and explain the different ways to mitigate supply chain attacks.
List which Static Application Security Testing (SAST) tools to use for Ruby applications. We also describe how SAST tools fit into a proper development tool-chain and explain the use cases and advantages of modern SAST tools.
Secure Coding with Ruby | Part 3
Continue the exploration of safe coding tips for Ruby, exploring deserialization of untrusted data, proper use of Regex, and how to securely use Distributed Ruby.