How to Avoid Writing Insecure Code

This training is about writing secure software. We chose to deliver secure coding practices using a perspective where widespread coding security mistakes are classified into understandable chunks. We hope that this will make more sense and be more helpful to hardcore developers and analysts.

Security should be an intrinsic part of any software production methodology and its implementation. That being said, development is a complex process and it is extremely hard to keep a software secure as it ages. Although there are numerous security tools (LLMs included), methodologies and knowledge to produce a secure software, still vast number of applications include critical security bugs. Most of these bugs stem from bad coding patterns that we call software security anti-patterns or in simpler term, mistakes.

An anti-pattern is a common response to a recurring problem that is usually ineffective or worse carry risks. In other words, anti-patterns are commonly reinvented bad solutions to problems.

For example, one of the most famous anti-patterns in software development is the Spaghetti Code. In early phases of being a developer, we are usually not familiar with the importance of modularity or find little time to design first. So, we tend to produce extremely complicated, hard to understand unstructured software. This way of coding produces Spaghetti Code which is hard to maintain and write test code, however, the end product may still run perfectly and serve well in production. But then it is extremely hard to adapt to any possible new changes and add new features.

Similarly, there are bad design or coding choices that repeatedly lead to security bugs. It is important to be aware of these software security anti-patterns in order not to fall prey to hackers. This course will try to explain eight core mistakes. Some are more prevalent than the others, however, all of them produce deadly results. In each lesson, we will first try to explain what the specific anti-pattern is all about. Then, we will move on giving one or more demos on what can go wrong when that mistake is made. At the end of each lesson, we will look at different sound and widely acknowledged solutions against insecure design or coding choices. You will also have the opportunity to apply what you have learned by solving hands-on coding exercises prepared for various programming languages.

Note: Unfortunately, in udemy, all coding exercises should be completed before getting a certificate of completion. Due to negative feedbacks, semantically same coding exercises using different programming languages are barred down by keeping only one exercise per section.