We created this Green Belt path for developers coding in the PHP. It includes our standard 13 Green Belt Secure Development lesson with the addition of 14 new PHP lessons. 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.
Introduce PHP, its prevalence and popularity, and the basics of PHP security.
Identify the threats to PHP such as Remote File Inclusion, Cross-site Scripting, and Outdated Components.
Discuss some dangerous PHP functions and how to mitigate them.
Functions vulnerable to Injection Attacks in PHP
Introduce the basics of injection attacks and discuss the functions that are vulnerable to them.
PHP Security Best Practices
Outline some best practices that help you to secure your PHP applications such as securing your file uploads, restricting file and directory access, and using safe SQL practices.
Introduce the basics of input validation within PHP, the three basic rules of input validation, and the difference between semantic and syntactic input validation.
Discuss how to secure sessions within PHP, we touch on timestamp-based session management as well as how to configure your security.ini file.
Static Application Security Testing (SAST)
In this module, we review tools and processes for discovering vulnerabilities in source code. We explore the uses of a SAST tool, the SAST tool workflow for a developer, and survey the available SAST offerings. SAST is a spell checker for security problems. You may have these tools, but not understand how they work or what they do.
Authentication and Authorization in Laravel
Introduce the Laravel and discuss how to utilize its built-in security capabilities to do authentication and authorization.
Input Validation in Laravel
Discuss how to use Laravels built-in input validation tools in order to secure your application.
PHP Security in Codeigniter
Introduce Codeigniter and discuss the different security tools built in it that can help to protect your application from CSRF and XSS attacks.
Input Validation in Codeigniter
Discuss the built-in tools Codeigniter provides in order to do input validation.
Authentication and Authorization in Symfony
Introduce Symfony and discuss the tools the framework provides for us to do authorization and authentication.
Input Validation in Symfony
Discuss the different tools Symfony provides to assist us in validating input.