We created this Green Belt path for Web Application Security Testers and their teams. 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.
Web Application Security Testing
Green Belt Path
Introduction to Web Application Security Testing
In this module, we describe security testing. We also list security testing truths, techniques, tools, and processes. We explain the differences between client-side and server-side testing.
In this module, we explain the truths of security testing
and how to apply them.
Security Testing Techniques
In this module, we list the different techniques for performing security tests, the advantages of each security testing approach, and explain how to create a balanced approach to testing security.
Web Application Penetration Testing Tools
In this module, we describe Kali Linux fits in with web application security testing. We also explain how to use ZAP, Burp Suite, and sqlmap.
Software Security Testing Lifecycle
In this module, we list the phases of the Software Security Testing Lifecycle. We also, explain how SWSTL relates to the SDLC and the SDL.
Secure Requirements & Threat Modeling for Testers
In this module, we examine the different categories of security requirements and review the steps of threat modeling for testers.
Building a Security Testing Strategy
In this module, we review the scope of a threat model and how to build a security testing strategy.
In this module, we explain how to create security unit tests and fuzz targets. We explain the importance of doing security testing peer reviews.
Automate Security Tests | Part 1
In this module, we emphasize the importance of automating security testing. We describe how DAST tools fit in the toolchain.
Automate Security Tests | Part 2
In this module, we discuss how to automate fuzzing tools and the best approach to include IAST in your testing toolchain.
Validating Security Findings and Controls
In this module, we list the steps to take when validating security findings and controls. We also explain how to remediate security findings.
Client-Side Testing for DOM-XSS
In this module, we describe web application security client-side testing techniques and how to test for DOM-XSS.
Server-Side Testing for Authentication Bypass
In this module, we describe web application security server-side testing techniques and how to test for authentication bypass.