What’s Next?
As we look back on the vulnerabilities we covered in this chapter, we see two main classes of vulnerabilities. In the first, an attacker is able to inject code of their own choosing into the system. In the second, operators accidentally leave the system in an insecure state. Interestingly, the defense for both looks fairly similar. First we make a one-time effort to find the vulnerabilities and fix them. We then layer on automated defenses to prevent mistakes from reintroducing the vulnerability. As teams and systems grow larger and older, we want to have more than vigilance keeping us from introducing vulnerabilities into the system; we want the system to prevent vulnerabilities from being introduced.
In our next chapter, we’ll ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access