Cybersecurity Challenges in an Evolving Developer Landscape
Balancing security and innovation is crucial in the ever-evolving software landscape. Gary Orenstein, Bitwarden’s chief customer officer, shares how developers can adapt.
In the dynamic software development landscape, with a push for new ideas and on-time delivery, balancing security and innovation is the norm.
With advancements in areas like passkeys, AI, and more, the right guardrails help close security gaps. Safeguarding digital assets and sensitive information is paramount for developers but often overlooked.
What Developers Say
Developers struggle to manage a growing number of secrets throughout the software developer lifecycle (SDLC) and to safeguard that information against data breaches. The integration and growing use of generative AI among DevOps teams creates additional complexity, offering benefits and introducing unforeseen risks.
A recent survey from Bitwarden highlights developers’ concerns about escalating security threats associated with secrets management, cybersecurity habits, and generative AI. It also emphasizes the obstacles developers face, including technical complexities, staff limitations, and insufficient security training, which complicate cybersecurity posture.
Here are a few more compelling findings and how they play into the bigger picture for developers and the security community.
AI Security Challenges
The integration of AI in development processes introduces notable security challenges. The survey findings indicate a significant risk perception among developers, with 78% recognizing AI as a security concern. However, there is a contradictory trend in respondents’ behaviors, which sees developers frequently inputting sensitive information into generative AI platforms despite recognizing the dangers of doing so.
Thirty percent of respondents have input developer secrets into AI. In contrast, around a quarter of respondents have input privileged credentials (24%) and other highly sensitive personally identifiable information like social security numbers (25%) and banking and healthcare data (24%) into generative AI.
These results highlight the need for clearer AI policies within the developer community. They also signal the importance of enhancing cybersecurity awareness protocols and training to ensure developers’ actions are consistent with their understanding of AI-related risks.
See More: Can AI-Powered Tools End the Web Developer Shortage?
Training vs. Doing: Overlooked Security Risks
Despite growing recognition of the value of robust security habits, practical applications often fall short. There is often cognitive dissonance between how secure individuals think they are and how secure they are.
For example, 91% of developers have regular security training but their security habits continue to lag. Sixty-five percent of developers revealed that they hard-code secrets in source code, and 55% keep secrets in clear text, elevating the risk of data exposure and security breaches.
The risks associated with these practices are evident. Nearly three-quarters (72%) of developers have been impacted by a data breach, with 24% reporting substantial damage and disruption to their company. More than a fifth (21%) of respondents disclosed they use public computers to access work data, emphasizing the need for continuous education, robust security protocols, and organizational support to address cybersecurity threats.
This sentiment is backed by Kroll research, which found overconfidence to be a significant risk factor in an organization’s cybersecurity posture. The data also indicated that confidence in employees’ ability to deter a cyberattack was higher than trust in the effectiveness of cybersecurity tools.
Secure-by-Design Remains a Priority Despite Resource Shortages
The secure-by-design approach integrates security from the onset of software or product development, and it is gaining momentum in the private sector in the wake of continued government cybersecurity guidance. Ninety-four percent of developers acknowledge the critical role of secure-by-design principles, yet adoption remains a challenge.
The data shows that 26% of developers consider the implementation of a secure-by-design approach too time-consuming, while 18% report staffing shortages, leading to tighter deadlines. The lack of resources for development teams highlights a discrepancy between the recognized value of secure-by-design principles and daily behaviors, with 65% of developers regularly embedding secrets directly in source code or storing them in unencrypted formats (55%).
Passkeys: A Favorable Shift Still Moving Ahead
Continued development and adoption by larger tech companies like Google, Amazon, and Apple highlight the cybersecurity industry’s move toward passwordless authentication like passkeys. Passkeys are rooted in encrypted authentication protocols like WebAuthn and empower individuals and businesses with a more effective deterrent against ransomware attacks and phishing attempts by removing weak credentials from the attack surface altogether. They also prevent the reuse of passwords across services or platforms because they are created uniquely to each user and service while enabling fast and easy sign-in to websites and apps across user devices.
The benefits of passkeys and passwordless authentication are gaining momentum among developers, with 88% expressing a highly favorable or favorable attitude toward their benefits. More than two-thirds (68%) of respondents have used passkeys for work applications and 60% for accessing personal applications. Only 36% of developers believe passkeys will completely replace passwords, while 33% believe they will coexist with – and augment – other authentication methods. This indicates more room ahead to replace passwords while acknowledging the forward momentum of the industry’s preferred adoption of passwordless authentication solutions.
Modernizing Authentication Solutions
A significant shift is happening to modernize authentication solutions and harden security resilience among developers. This means continued adoption of passkeys in work applications and addressing vulnerability gaps associated with risky behaviors within the organization. This underscores a need for accessible tools to assist developers and businesses in securely managing secrets – or shifting left – alongside the implementation of stronger authentication measures and navigating risks associated with AI while pushing innovation forward.
How can developers effectively manage secrets amidst evolving AI risks? Let us know on Facebook, X, and LinkedIn. We’d love to hear from you!
Image Source: Shutterstock
