Episode 5. Secure Coding — Understanding Software Risks
→ Whenever software is released, we should always focus on high-risk areas and determine where to get the most rewards.
→ Testing high mitigation areas in each release
→ When we truly identify risks early in the development stage, your entire team, your project and your budget benefit.
→ When we become security-minded developers, we will always question the security aspects of development, designs and production releases.
→ Hence we can provide more tangible feedback on code reviews.
→ Understanding risks is important. We should not only understand code in functionality, but also the environment around us.
→ Every day new risks to the software come to software, as we try to build code, it’s someone’s job to break code.
→ We as a team should always plan for these:
→ The goal of Secure coding — Is not just about the bytes. It's about the overall culture we are trying to create.
→ Understanding risks will help you improve the security culture in your organization.
When it comes to the IT world, we should plan for security risks in the initial software requirement/architecture stage.
In the next article, we will explore documenting risks — Risk number, test name.
Thank you for reading till the end 🙌 . If you enjoyed this article or learned something new, support me by clicking the share button below to reach more people and/or give me a follow on Twitter and subscribe Happy Learnings !! to see some other tips, articles, and things I learn about and share there.