Software firms team to fight bug leaks
Organisation for Internet Safety - very Orwellian
Scott Blake, chair of OIS's communications committee, told ComputerWire the guidelines will give security researchers and software developers responsibilities for being discreet and taking warnings seriously respectively. The key proposal is a 30-day waiting period between a patch release and details of the bug being released.
"We want to give the good guys a 30-day head-start on the bad guys," Blake said. "Demo code for [vulnerability] exploits won't be published by anybody without some assertion that it will not be used for unlawful purposes... We don't want researchers putting loaded guns in the hands of script kiddies."
The OIS was the brainchild of Steve Christey of the MITRE Corp and Chris Wysopal of @Stake Corp, who published a best practices document as an Internet Draft with the Internet Engineering Task Force in February. Founding members also include Oracle, Microsoft, Symantec, NAI, Guardent, ISS, SCO Group and BindView.
In recent years, there has been friction between vendors and professional and hobbyist bug-hunters. The periods between notifying a vendor of a bug and releasing the information to the public have been variable, and vendors, notably Microsoft, have been criticized for ignoring warnings or threatening legal action against the discoverer.
"It's been a very long time since anyone has had a legitimate complaint against Microsoft for not responding to a security issue," said Blake, who works for BindView Corp. "More often it's someone who wants to embarrass Microsoft, or other software companies, because they have a bone to pick."
"We'll probably get more traction with the professionals at first," he added. "But we're hoping to set a good example for the rest." The hope is that ultimately anybody, including the hobbyist bug-hunter, releasing vulnerability information without conforming to the guidelines will be frowned upon.
Two weeks ago, US senior presidential advisor Richard Clarke published a document outlining a strategy for securing American interests on the internet. Responding to the fact that most successful attacks are due to unpatched systems, among the proposals was the notion of an industry-led clearinghouse for vulnerability and patch information.
But Blake said there's no chance OIS will become that organization. "We're very specifically going to stay out of that kind of thing," he said. The OIS will merely create and maintain the guidelines and approve new members.
Companies wishing to join need only seek approval from the OIS board. There will be no enforcement of the guidelines, no certification seal to boast, and no membership fees. "We're using the honor system," Blake said.