US security agencies define worst coding errors
LATEST NEWS
- Video will drive UFB uptake, but NZ lacks content choices: ComCom || 2
- TelstraClear's half-year revenue drops by 4 percent, but telco posts $1m profit
- Peter Finch leaves CIO post at Gen-i || 1
- 2degrees announces 875,656 customers
- NZ Fauna app fills 'crazy' lack of animal info || 4
- Megaupload interest a mixed blessing for Pirate Party || 2
SUBSCRIBE
Computerworld is New Zealand's only specialised information systems fortnightly. Subscribe now for $100 (23 issues) and save more than 37% off the cover price!
SIGN UP
The NSA helps define 25 dangerous programming errors
By Robert McMillan | San Francisco | Monday, 19 January, 2009
A group of more than 30 computer organisations has taken what some are calling a big step toward making software more secure.
Led by experts from the US National Security Agency, the Department of Homeland Security, Microsoft and Symantec, the group is set to publish a blueprint outlining the most dangerous software programming errors.
The list represents the first time the industry has reached consensus on the worst things that can happen when software is being written.
"The top-25 list gives developers a minimum set of coding errors that must be eradicated before software is used by customers," says Chris Wysopal, chief technology officer with Veracode, in a prepared statement.
More than just a list, however, the document could be used as a negotiating tool between buyers and software vendors, says Alan Paller, director of research with the SANS Institute, a security training group that spearheaded the work.
In fact, New York state is now developing procurement documents that could be used by state agencies to make their vendors certify that their code contains none of these programming errors. Ultimately that will make the vendor, not the state, responsible when buggy software leads to a security problem, Paller says. "When the software is found to be flawed... all of the economic liability shifts to them."
Paller expects this kind of certification, virtually unknown today, will become more common now that such a large part of the industry has agreed on what programming errors are most dangerous. But he expects it to be used in large custom-coding contracts, rather than in the software licensing agreements used for widely distributed software such as Microsoft Windows.
The flaws include things such as allowing for SQL injection or cross-site scripting attacks, sending sensitive information in clear text, which can be easily read, and hard-coding security passwords into programs, where they're hard to change if discovered.
Two of these bugs led to more than 1.5 million website breaches last year, SANS says. And that was just the start: often, these web breaches were used by online attackers to then launch more attacks against people who surfed the hacked sites.
MOST POPULAR
Social Media @Computerworld NZ
Computerworld NZ has now reached LinkedIn! Join to expand your networks and meet others interested in information systems.
