The Federal Government is Pushing for Security-Aware Developers

Maskot/Getty Images

But do official recommendations work in their world?

In the past two years, we have seen the cybersecurity world forced to “grow up” quickly. The approach to security in the supply chain has been especially prominent, requiring fast-tracked solutions to successfully align with accelerating official mandates and recommendations. The SolarWinds and Log4j incidents certainly helped this along, but the truth is, this scrutiny was much-needed and a long time coming.

Mercifully, the U.S. government has taken multiple steps to zero in on several problem areas in the software supply chain, and continued focus on security has ensured it is a mainstay in the media, not to mention the minds of leaders in the space. One such area has been the issue of developer influence in the supply chain, and the need for their security skills to be verified if they’re working for a software vendor servicing the government. Make no mistake: vulnerabilities and misconfigurations affect the private sector just as much as any government department around the world, and these measures have the potential to make a positive impact on developer security awareness, if they are effective and widely adopted.

As someone who has dedicated much of their career to developer security enablement, a spotlight on an issue of this magnitude might seem cause for celebration, but I won’t be popping the champagne just yet. After all, instilling security best practices in the development cohort is much easier said than done, and the industrywide cultural change required for consistency to make it a new standard is simply not where it needs to be. Much like other general guidelines aimed at developer-driven security, they tend to lack the specifics needed to truly penetrate the traditional barriers that have made it a difficult sell in the first place.

Do the guidelines adequately consider a realistic developer workflow?

Many of the key obstacles in the way of developer-driven security practices directly relate to how they integrate with developers’ long-established workflow and ways of operating in a high-pressure environment. Simply plonking security responsibilities on top of every other goal they are required to achieve hasn’t resulted in success, and doing the same thing with security training—especially anything mandatory—is just another nail in the coffin for any affection a developer may have had towards secure coding in the first place.

We know from our own independent research that 86% of developers knowingly ship vulnerable code, and this is wildly at odds with what the U.S. government, at least, is attempting to declare as an acceptable level of security awareness and skill for a development team.

The guidelines state, “Developers should take regular and relevant security training, both for common topics and those deemed necessary for the individual role. Successful completion should be tracked for all engineers. Organizations should ensure individuals complete security training commensurate with the impact level of the system and software to which the individuals are assigned.” This is ideal, but naturally, easier said than done, especially in organizations where security maturity and culture are lacking. 

In the pressure cooker environment of modern software development, fast deployment of features reigns supreme, and, overwhelmingly, multiple studies—including our own—have revealed that developers simply have no time to train. The GitLab 2022 Global DevSecOps Survey showed that 35% of developers are releasing code twice as fast compared to three years ago, and demand shows no signs of slowing. 

Another concern is that, much like previous guidelines from NIST and others, there are few instructions on the types of training that would be effective. Many organizations struggle with finding right-fit security training and tools, and I don’t think this is any different. If training solutions eat away too much time—or time is not allocated in the work day in the first place—there is very little chance it will be embraced. Similarly, if it requires crazy context-switching to access, has no relevance to their actual work, and is easy to ignore, the effort to roll it out at all has to be questioned. 

Does this achieve security nirvana—i.e. security at speed?

If you asked any development team what their primary goal would be, “software delivery at speed” is likely priority one for most. Securing the software supply chain is not front-of-mind for developers, and realistically, it’s not entirely helpful for secure coding—or developer-led security best practices—to get quite that granular, when so many have so few opportunities to learn even the foundational basics. 

Introducing sweeping, restrictive security responsibilities for developers who don’t have the time, expertise or ongoing training needed to successfully mitigate common vulnerabilities will inevitably slow production to a crawl, and this will not fly in most government departments, let alone private enterprises. These recommendations need careful planning to implement, and organizations would do well to assess them in relation to their most pressing and relevant security issues.

A surprising element of the guidelines was that they detailed fairly complex areas of security that developers were expected to cover, such as insecure design principles and advanced threat modeling techniques, but they remained rather limited in the prescribed directions for code-level vulnerabilities, for example: “Software development group managers should ensure that the development process prevents the intentional and unintentional injection of malicious code or design flaws into production code.”

With security misconfigurations causing 80% of all data breaches, according to Gartner data, and API access control also a hot attack vector, this is somewhat simplistic, and teaching how to mitigate those scenarios alone won’t prepare a developer adequately for advanced threat modeling tasks, as an example. 

Steps for an enterprise-friendly approach

The bottom line is that we all need to care more about security, and these guidelines are a meaningful, commendable step in the right direction. While they are supply chain-centric, over time, it is likely that these recommendations will be cited increasingly in the private sector, dictating security awareness pathways for development teams, and it is at this point that many will find they need refinement to function in a realistic way. 

Organizations should first make an honest assessment of their security maturity, and I’d recommend the following pointers to start making these government suggestions work for you:

  • Find holistic training, and stay serious about it. Generic training that is not job-relevant, or even in the languages and frameworks used by the development cohort, will be next to useless in enabling developers to solve common security problems. The idea is to correct poor coding patterns, and they need hands-on, relevant, and engaging training. 
  • Don’t bombard the development team. A surefire way to upset the developers would be to make security part of their KPIs overnight, make them use disruptive tools and expect them to be ready to start preparing comprehensive threat modeling documentation in an instant. The guidelines don’t address skill-building and foundational learning very well, so it’s up to security professionals and managers to implement viable pathways where learning can occur in layers, build upon existing knowledge, and be continually assessed. 
  • Incentivize developers to build a security-first mindset. Security-aware developers are highly sought after, and provide the often unsung backbone to security best practices in an organization. They should be rewarded, shouted out to their peers and given ample opportunity to advance their careers.

Pieter Danhieux is the CEO and co-founder of Secure Code Warrior.

NEXT STORY: Zero Trust Doesn’t Come in a Box

X
This website uses cookies to enhance user experience and to analyze performance and traffic on our website. We also share information about your use of our site with our social media, advertising and analytics partners. Learn More / Do Not Sell My Personal Information
Accept Cookies
X
Cookie Preferences Cookie List

Do Not Sell My Personal Information

When you visit our website, we store cookies on your browser to collect information. The information collected might relate to you, your preferences or your device, and is mostly used to make the site work as you expect it to and to provide a more personalized web experience. However, you can choose not to allow certain types of cookies, which may impact your experience of the site and the services we are able to offer. Click on the different category headings to find out more and change our default settings according to your preference. You cannot opt-out of our First Party Strictly Necessary Cookies as they are deployed in order to ensure the proper functioning of our website (such as prompting the cookie banner and remembering your settings, to log into your account, to redirect you when you log out, etc.). For more information about the First and Third Party Cookies used please follow this link.

Allow All Cookies

Manage Consent Preferences

Strictly Necessary Cookies - Always Active

We do not allow you to opt-out of our certain cookies, as they are necessary to ensure the proper functioning of our website (such as prompting our cookie banner and remembering your privacy choices) and/or to monitor site performance. These cookies are not used in a way that constitutes a “sale” of your data under the CCPA. You can set your browser to block or alert you about these cookies, but some parts of the site will not work as intended if you do so. You can usually find these settings in the Options or Preferences menu of your browser. Visit www.allaboutcookies.org to learn more.

Sale of Personal Data, Targeting & Social Media Cookies

Under the California Consumer Privacy Act, you have the right to opt-out of the sale of your personal information to third parties. These cookies collect information for analytics and to personalize your experience with targeted ads. You may exercise your right to opt out of the sale of personal information by using this toggle switch. If you opt out we will not be able to offer you personalised ads and will not hand over your personal information to any third parties. Additionally, you may contact our legal department for further clarification about your rights as a California consumer by using this Exercise My Rights link

If you have enabled privacy controls on your browser (such as a plugin), we have to take that as a valid request to opt-out. Therefore we would not be able to track your activity through the web. This may affect our ability to personalize ads according to your preferences.

Targeting cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.

Social media cookies are set by a range of social media services that we have added to the site to enable you to share our content with your friends and networks. They are capable of tracking your browser across other sites and building up a profile of your interests. This may impact the content and messages you see on other websites you visit. If you do not allow these cookies you may not be able to use or see these sharing tools.

If you want to opt out of all of our lead reports and lists, please submit a privacy request at our Do Not Sell page.

Save Settings
Cookie Preferences Cookie List

Cookie List

A cookie is a small piece of data (text file) that a website – when visited by a user – asks your browser to store on your device in order to remember information about you, such as your language preference or login information. Those cookies are set by us and called first-party cookies. We also use third-party cookies – which are cookies from a domain different than the domain of the website you are visiting – for our advertising and marketing efforts. More specifically, we use cookies and other tracking technologies for the following purposes:

Strictly Necessary Cookies

We do not allow you to opt-out of our certain cookies, as they are necessary to ensure the proper functioning of our website (such as prompting our cookie banner and remembering your privacy choices) and/or to monitor site performance. These cookies are not used in a way that constitutes a “sale” of your data under the CCPA. You can set your browser to block or alert you about these cookies, but some parts of the site will not work as intended if you do so. You can usually find these settings in the Options or Preferences menu of your browser. Visit www.allaboutcookies.org to learn more.

Functional Cookies

We do not allow you to opt-out of our certain cookies, as they are necessary to ensure the proper functioning of our website (such as prompting our cookie banner and remembering your privacy choices) and/or to monitor site performance. These cookies are not used in a way that constitutes a “sale” of your data under the CCPA. You can set your browser to block or alert you about these cookies, but some parts of the site will not work as intended if you do so. You can usually find these settings in the Options or Preferences menu of your browser. Visit www.allaboutcookies.org to learn more.

Performance Cookies

We do not allow you to opt-out of our certain cookies, as they are necessary to ensure the proper functioning of our website (such as prompting our cookie banner and remembering your privacy choices) and/or to monitor site performance. These cookies are not used in a way that constitutes a “sale” of your data under the CCPA. You can set your browser to block or alert you about these cookies, but some parts of the site will not work as intended if you do so. You can usually find these settings in the Options or Preferences menu of your browser. Visit www.allaboutcookies.org to learn more.

Sale of Personal Data

We also use cookies to personalize your experience on our websites, including by determining the most relevant content and advertisements to show you, and to monitor site traffic and performance, so that we may improve our websites and your experience. You may opt out of our use of such cookies (and the associated “sale” of your Personal Information) by using this toggle switch. You will still see some advertising, regardless of your selection. Because we do not track you across different devices, browsers and GEMG properties, your selection will take effect only on this browser, this device and this website.

Social Media Cookies

We also use cookies to personalize your experience on our websites, including by determining the most relevant content and advertisements to show you, and to monitor site traffic and performance, so that we may improve our websites and your experience. You may opt out of our use of such cookies (and the associated “sale” of your Personal Information) by using this toggle switch. You will still see some advertising, regardless of your selection. Because we do not track you across different devices, browsers and GEMG properties, your selection will take effect only on this browser, this device and this website.

Targeting Cookies

We also use cookies to personalize your experience on our websites, including by determining the most relevant content and advertisements to show you, and to monitor site traffic and performance, so that we may improve our websites and your experience. You may opt out of our use of such cookies (and the associated “sale” of your Personal Information) by using this toggle switch. You will still see some advertising, regardless of your selection. Because we do not track you across different devices, browsers and GEMG properties, your selection will take effect only on this browser, this device and this website.