Identity Security for Software Development

Chapter 3. The Value of a Secure Software Development Environment

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 4th chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

In an ideal world, identity security practices are included at every stage of the application development lifecycle. Every software component, tool, and process is secure by default and implemented using industry best practices. Your organization has bulletproof security controls in place to ensure updates, new code, and your software supply chain work safely as intended.

The problem is that our world isn’t ideal. No one would deny the importance of code security but every developer knows there’s a push-pull relationship between getting releases out fast and maintaining a secure code base. Usually, security is the one left behind.

Companies do better by establishing a secure software development environment – a shared set of tools, policies, and procedures that reduce the likelihood of vulnerabilities entering the development stream. This internal development platform (IDP) helps secure infrastructure with touch points across ...