Summary

In this chapter, we examined two primary security concerns for this development phase. First, we looked at ensuring a secure development environment or workspace. This means making sure that tools and platforms where coding occurs, such as IDEs, are safe from vulnerabilities. We also touched on the risks of malicious IDE extensions and the challenges when dealing with untrusted code. We highlighted the need for measures to counteract any potential IDE breaches. Second, we tackled common coding errors that can lead to security issues. We introduced tools such as secret scanning to detect exposed sensitive data, SAST to find code vulnerabilities, and SCA to check third-party components for security risks. With this knowledge, you’re now better equipped to handle security challenges before committing code in the DevOps process. Up to this point in the book, our DevSecOps discussion has not focused on Azure. That is because there has not been much Azure-specific content...