Chapter 4. Preventing Risk Early
Oh, East is East and West is West, and never the twain shall meet.
Rudyard Kipling
The twain shan’t meet, but collaborate.
Anonymous
An ounce of prevention is worth a pound of cure.
Benjamin Franklin
Never was so much owed by so many to so few.
The Right Honorable Sir Winston Churchill
“More meetings?” came the cry. “Please, no more meetings!”
It was a valid plea. The call had gone out for the development teams to work more closely with the security teams, and our work calendars had just been filled with architecture and design reviews, security audits, code security reviews, gates, and requests for our planned future release plans. There was starting to be very little time left to actually write any code.
We all knew security was important, critical even. But how security happened, how it was brought to and actioned by development teams, was the question. More meetings couldn’t be the way. Nor could a cacophony of new reviews. There had to be a better way. There had to be.
And there is. In this chapter, you’re going to see how your CNAPP is the collaborative glue between your development teams and your security-focussed teams, helping you get ahead of the game from the very first moments of your software development lifecycle, as shown in Figure 4-1.
Figure 4-1. The focus of this chapter is on how your CNAPP can bring security awareness ...
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