The 5 Faces of Development Risk

Which of these development risks do you recognize?

Delivering cloud-native applications, quickly, is an existential requirement for most businesses. Security, Risk Management, and DevSecOps leaders are tasked with ensuring cloud misconfigurations do not lead to breach, disruption, or non-compliance events. But agile development and delivery practices including infrastructure as code and automated pipelines have made this increasingly difficult.

74% of organizations do not effectively validate Infrastructure as Code security and compliance, leaving them highly vulnerable to data breach and disruption in cloud.

Gaining visibility and control of cloud security and compliance starts with an understanding of where development risk comes from. Some risks are the result of simple human error, while others are related to ignorance or malfeasance. Read on to get to know the five faces of cloud development risk.

Overloaded Developer

They continually face pressure from deadlines that force them to work fast. As businesses push to do more in less time and tasks multiply, Overloaded Developers make more mistakes that put your reputation and cloud at risk. As a result, 65% of organizations had active cloud storage services without encryption turned on.1

Lead Developer

They are needlessly slowed or derailed by irrelevant and last-minute security tickets. Lead Developers often feel frustrated by security delays which are unnecessary. “Why does security break my build with policies that don’t apply to my code? Consider that 73% of developers have thought about quitting their job due to security-related stresses.2

Unaware Developer

They have not been given a clear and up-to-date set of standards to comply with. Unlike the Overloaded Developer, the Unaware Developer doesn’t really know which security and compliance checks they should be using to test their code. This is a systemic problem with 41% of developers citing unclear security benchmarks as a barrier to testing their infrastructure as code.3

Third-Party Developer

They build code you integrate, but it may not be developed with your standards in mind. Most organizations rely heavily on third-party developers, or the marketplace and open-source code they build. These developers don’t know your environment nor your security and compliance policies. Yet less than 50% of organization scan their open-source libraries.4

Nefarious Developer

They can change or ignore controls and circumvent your security without you ever knowing. Did you hear the one about the Nefarious Developer who allegedly stole gigabytes of confidential data, and then tried to sell it back to his then current employer? It’s no surprise that 62% of data breaches are financially motivated.5

Read The 5 Faces of Development Risk Infographic to learn why these risks are all too common and what steps you can take to prevent them from putting your cloud and your reputation at risk.    

1 Sophos, Cloud Security Report 2020

2 Invicti, AppSec Indicator, Fall 2021

3 Snyk, IaC Security Insights, 2020

4 Veracode, State of Software Security

5 Verizon, Data Breach Investigations Report, 2020

Related Resources

Learn more about one policy architecture and Concourse Labs.