Risk
2/5/2010
03:40 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

'Rugged' Initiative Brings Secure Software Development To The Masses

Rugged Software Development initiative an 'on-ramp' for all types of programmers to write resilient code

Security experts today officially launched a new effort to ensure software is written from the ground up with security in mind -- a philosophy and message they're aiming at people outside of the security industry.

The Rugged Software Development initiative is basically a foundation for creating resilient software that can stand up to attackers while performing its business or other functions, according to Joshua Corman, research director for the enterprise security practice at The 451 Group, who unveiled the program today at the SANS Application Security Summit in San Francisco.

Corman, along with Jeff Williams, chair of OWASP and CEO of Aspect Security, and David Rice, director of The Monterey Group and author of Geekonomics, came up with the idea for the initiative. It's more of "a value system" for writing secure software, versus a compliance program, according to its founders, who hope to incorporate the tenets of rugged code development into computer science programs at universities.

This isn't the first industry effort to push developers to bake security into their code: There's Homeland Security's Build Security In guidelines; Microsoft's Software Development Lifecycle (SDLC) framework and tools; Building Security In Maturity Model (BSIMM), where financial services firms are comparing notes and sharing their secure coding strategies and experiences; and OpenSAMM (Software Assurance Maturity Model), an open-source model aimed at becoming an industry standard for secure software development.

Rugged doesn't include any new frameworks for secure coding, however, and instead will serve as an "on-ramp" for secure software development, Corman says. Rugged is different because it's aimed at people outside of the security realm: "Most efforts have been isolated to people who care about security and preaching to the choir," he says. "[Rugged] is specifically targeted at people out of the security context."

Getting the secure software development message to the masses won't be easy, and the plan is to get some initial support and momentum from the application security industry.

"We're not trying to replace or undo [other secure coding efforts]," Corman says. "Our goal is to drive more people to it that otherwise would not have known how to become involved."

Chris Wysopal, CTO of Veracode, says developers must be part of the solution to security problems. "Unfortunately, most developers don't know what it means to write secure code, and worse they think they already write secure code if they write high quality code. Software security practitioners have struggled to get past this mindset," Wysopal says. "Rugged code is a way of breaking through and instilling a mindset that secure code should be a pride-of-ownership issue just as much as elegant, high performing, and high quality code is."

Corman, who says he's looking to set up an advisory board for Rugged, envisions everything from having programmers voluntarily pledge to be Rugged software developers to developing an Underwriters Laboratories (UL) label for measuring software for its "ruggedness."

The project is currently soliciting people to help define the "principles and technologies that will help others become Rugged, too. Our first project is to define how people and organizations can know if they are Rugged," the Rugged initiative Website says.

Meanwhile, the project even comes with its own manifesto, which reads, in part:

"I recognize that software has become a foundation of our modern world. I recognize the awesome responsibility that comes with this foundational role. I recognize that my code will be used in ways I cannot anticipate, in ways it was not designed, and for longer than it was ever intended. I recognize that my code will be attacked by talented and persistent adversaries who threaten our physical, economic, and national security. I recognize these things -- and I choose to be rugged. I am rugged because I refuse to be a source of vulnerability or weakness. I am rugged because I assure my code will support its mission. "

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.