Loading summary
Rick Howard
You're listening to the Cyberwire Network powered by N2K.
Nyla Genoi
What's the common denominator in security incidents? Escalations and lateral movement. When a privileged account is compromised, attackers can seize control of critical assets with bad directory hygiene and years of technical debt. Identity attack paths are easy targets for threat actors to exploit, but hard for defenders to detect. This poses risk in active directory, entra ID and hybrid configurations. Identity leaders are reducing such risks with attack path management. You can learn how attack path management is connecting identity and security teams while reducing risk with Bloodhound Enterprise powered by Spectrops. Head to Spectrops IO today to learn more. Spectrops See your attack paths the way adversaries do.
Rick Howard
The word is OWASP insecure design spelled O for open, W for Web, A for application S for security P for project Insecure as in having vulnerabilities that can be exploited and design as in to plan and fashion skillfully. Definition a Broad OWASP Top 10 Software Development Category representing missing, ineffective and unforeseen security measures. Example sentence to avoid creating an application with insecure design, developers must think about security during the planning and design stage of the software development life cycle. Origin in Context Dave Wickers and Jeff Williams, working for Aspect Security, a software consultancy company, published an education piece in 2003 on the top software security coding issues of the day that eventually turned into the OWASP top 10, a reference document describing the most critical security concerns for web applications. Today, OWASP is an international team of security professionals led by the foundation executive director and top 10 project leader Andrew van der Stock, dedicated to enabling organizations to develop, purchase, and maintain applications and APIs that can be trusted. Today there are tens of thousands of members and hundreds of chapters worldwide. In 2021, OWASP published an updated top 10 list where a new category appeared insecure Design ranking at number four on the most critical vulnerabilities to fix insecure design results when there are flaws in thinking about the security of the development process, this is not to be confused with insecure implementation that has a different root cause and remediation. According to owasp, a secure design can still have implementation defects leading to vulnerabilities that may be exploited. An insecure design cannot be fixed by a perfect implementation, as by definition needed. Security controls were never created to defend against specific attacks. According to owasp, the security of the software development process is never done. The landscape requires constant monitoring for newly discovered vulnerabilities and and continuous updating as new flaws come to light. The only way to stay ahead of the game is to embrace secure design patterns, reference architectures, and deployment frameworks. In other words, automate the development process in a DevSecOps kind of way. Once deployed, assign Red teams the task of deploying known attack scenarios against the landscape and make adjustments to newly discovered flaws in the design. OWASP specifically recommends looking for changes in data flows, access controls, or other security controls, as well as automating the validation of assumptions on a regular basis. Nerd reference in the 2001 movie Ocean's Eleven, starring George Clooney, Brad Pitt and the late great Carl Reiner and a host of favorite that Guy actors and actresses Danny Ocean, played by Clooney and his 10 accomplices run a heist to rob three Las Vegas casinos. Simultaneously, they run into a security system designed and I'm using air quotes here to be impenetrable by the casino owner. In this scene, Clooney describes the insecure design with the help of Pitt and Reiner. The design is insecure because, spoiler alert, the Ocean's Eleven team successfully steals the money.
George Clooney
This is the vault at the Bellagio. It's located below the strip beneath 200ft of solid earth. It safeguards every dime that passes through each of the three casinos above it. This place houses a security system that rivals most nuclear missile silos. First, we have to get within the casino cages, which anybody will tell you takes more than a smile. Next, through these doors, each of which requires a different six digit code changed every 12 hours. Past those lies the elevator. This is where it gets tricky. The elevator won't move without authorized fingerprint identification, which we can't fake, and vocal confirmation from both the security system within the Bellagio and and the vault below.
Brad Pitt
Which we won't get.
George Clooney
Furthermore, the elevator shaft is rigged with motion detectors, meaning if we were to.
Brad Pitt
Manually override the lift, the shaft's exit would lock down automatically and we'd be trapped.
George Clooney
Now, once we get down the shaft, though, then it's a piece of cake. Just two more guards with Uzis and the most elaborate vault door ever conceived by man.
Brad Pitt
No tunneling is out. There's sensors monitoring the ground 100 yards in every direction from if a groundhog were to nest there, they'd know about it.
Carl Reiner
I have a question. Say we get into the cage and through the security doors there and down the elevator. We can't move. And past the guards with the guns and into the vault we can't open.
Brad Pitt
Without being seen by the cameras.
George Clooney
Oh yeah, sorry, I forgot to mention that.
Carl Reiner
Yeah, well, say we do all that, we're just supposed to walk out of there with $150 million in cash on us with. Without getting stopped.
George Clooney
Yeah.
Rick Howard
Wordnotes is written by Nyla Genoi, executive produced by Peter Kilpe, and edited by John Pettrick and me, Rick Howard. The mix, sound, design and original music have all been crafted by the ridiculously talented Elliot Peltzman. Thanks for listening.
Nyla Genoi
Bad actors don't break in. They log in. Attackers use stolen credentials in nearly nine out of 10 data breaches. Once inside, they're after one thing your data. Varonis AI powered data security platform secures your data at scale across las SaaS and hybrid hybrid cloud environments. Join thousands of organizations who trust Varonis to keep their data safe. Get a free data risk assessment@veronis.com.
Podcast Summary: Hacking Humans - Episode: OWASP Insecure Design (noun)
Host/Author: N2K Networks
Release Date: April 22, 2025
In this episode of Hacking Humans, hosted by Rick Howard, the discussion centers around the concept of "OWASP Insecure Design," a critical category within the OWASP Top 10 list of software security vulnerabilities. Rick Howard kicks off the episode by clearly articulating the term:
Rick Howard [01:12]: "The word is OWASP insecure design spelled O for open, W for Web, A for application S for security P for project Insecure as in having vulnerabilities that can be exploited and design as in to plan and fashion skillfully."
This segment sets the stage for an in-depth exploration of how insecure design principles can lead to significant security vulnerabilities in software applications.
The discussion traces the origins of the OWASP Top 10, highlighting its evolution from a 2003 educational piece by Dave Wickers and Jeff Williams of Aspect Security. The OWASP foundation, now a global leader in application security, continuously updates its Top 10 list to reflect the most pressing security concerns. Rick emphasizes:
Rick Howard [01:12]: "In 2021, OWASP published an updated top 10 list where a new category appeared insecure Design ranking at number four on the most critical vulnerabilities to fix."
This addition underscores the growing recognition of design flaws as a primary risk factor in application security.
A significant portion of the episode delves into distinguishing between secure and insecure design. Rick Howard explains that while secure design aims to anticipate and mitigate potential vulnerabilities during the planning and architecture phases, insecure design results from flawed thinking and oversight:
Rick Howard [01:12]: "An insecure design cannot be fixed by a perfect implementation, as by definition needed security controls were never created to defend against specific attacks."
This highlights the importance of integrating security considerations from the very beginning of the software development lifecycle, rather than attempting to bolt on security measures post-development.
Rick underscores the necessity of ongoing vigilance in the software development process:
Rick Howard [01:12]: "The security of the software development process is never done. The landscape requires constant monitoring for newly discovered vulnerabilities and continuous updating as new flaws come to light."
He advocates for the adoption of secure design patterns, reference architectures, and deployment frameworks, suggesting a DevSecOps approach to automate and streamline security integration.
Employing the recommendations from OWASP, the episode highlights strategies to combat insecure design:
Red Team Engagement: Assigning specialized teams to simulate attack scenarios helps in identifying and rectifying design flaws before they can be exploited.
Automated Validation: Regular automation of security checks ensures that assumptions about security controls remain valid over time.
Rick Howard [01:12]: "OWASP specifically recommends looking for changes in data flows, access controls, or other security controls, as well as automating the validation of assumptions on a regular basis."
To illustrate the real-world implications of insecure design, the podcast references the 2001 film Ocean's Eleven. In a pivotal scene, the characters discuss the supposedly impenetrable security system of the Bellagio vault, which ultimately succumbs to their heist. Key dialogues include:
George Clooney [05:24]: "This is the vault at the Bellagio. It's located below the strip beneath 200ft of solid earth. It safeguards every dime that passes through each of the three casinos above it. This place houses a security system that rivals most nuclear missile silos..."
Brad Pitt [06:07]: "Which we won't get."
Carl Reiner [06:35]: "I have a question. Say we get into the cage and through the security doors there and down the elevator. We can't move. And past the guards with the guns and into the vault we can't open."
George Clooney [07:04]: "Yeah."
This dialogue serves as a cautionary tale about over-reliance on perceived secure systems. Despite the elaborate security measures, the vault was ultimately compromised due to inherent design vulnerabilities—mirroring real-world scenarios where sophisticated defenses fail due to fundamental design flaws.
Early Integration of Security: Incorporating security measures during the design and planning phases is crucial to prevent vulnerabilities that cannot be mitigated later.
Continuous Security Monitoring: The dynamic nature of threats necessitates ongoing surveillance and adaptation of security strategies.
Collaborative Approach: Bridging the gap between identity and security teams through attack path management enhances an organization's resilience against potential breaches.
Practical Application: Real-world examples, such as the Ocean's Eleven heist, illustrate the tangible risks of insecure design and the importance of robust security planning.
Rick Howard concludes the episode by reinforcing the importance of adopting secure design principles to safeguard against evolving cyber threats. By understanding and addressing insecure design, organizations can significantly reduce their vulnerability to attacks, ensuring the integrity and trustworthiness of their applications and systems.
Notable Quotes with Timestamps:
Rick Howard [01:12]: "OWASP insecure design... representing missing, ineffective and unforeseen security measures."
Rick Howard [01:12]: "An insecure design cannot be fixed by a perfect implementation..."
Rick Howard [01:12]: "The security of the software development process is never done..."
George Clooney [05:24]: Detailed description of the Bellagio vault's security system.
Carl Reiner [06:35]: "Say we get into the cage and through the security doors there and down the elevator. We can't move..."
These quotes encapsulate the essence of the discussion, providing listeners with clear insights into the critical nature of insecure design within the realm of cybersecurity.