Standing on stage at the Facebook F8 developer's conference in September, founder and CEO Mark Zuckerberg boasted that the social media site he invented in his Harvard dorm room back in 2004 – the same site which now has more than 800 million users – recently hit a milestone: Half a billion people used Facebook in a single day.
There is no denying that the behemoth that is Facebook has become ingrained into users' everyday lives. But even giants can fall. If members believe the information they post on Facebook is unsafe, they will move on – plain and simple.
This reality is not lost on those who work for the company. In fact, it's quite the opposite. Within the walls of Facebooks's headquarters in Palo Alto, exists a culture dedicated to providing users with a secure experience, says Joe Sullivan, the company's chief security officer.
“Trust is fundamental,” Sullivan says. “That's something we think about every day. There is never a situation where the company trades off security for something else. If there is a security issue, we drop everything and deal with it.”
One of the necessities in running a web presence used by hundreds of millions of people each day is ensuring its code is free of errors – security vulnerabilities – that could allow an attacker to gain access to private accounts. By any measure, coding errors are extremely prevalent, not just in websites spanning the internet, but also in commercial computing products and custom-developed systems.
“Vulnerabilities are dangerous, and people outside of the [computer security] industry aren't aware of how many latent vulnerabilities there are in products they use every day,” says Dino Dai Zovi, an independent security consultant who started bug hunting to find such issues in 1999, and who has disclosed flaws in products made by Apple and Sun Microsystems (now owned by Oracle).
While Sullivan estimates that hundreds of employees across Facebook work on security issues, there are two primary groups dedicated to preventing, finding and fixing vulnerabilities. The platform integrity team, within the software engineering department, works to ensure that every single engineer in the company follows secure-coding practices. Then, the six-person product security team, which is part of the security department Sullivan manages, works to “poke holes” in the code that has been created, scouring it for vulnerabilities.
In addition to the internal holes, the company also calls on external auditors to review code for weaknesses before it is released online.
And, to ramp up its efforts to find holes that could be abused by attackers, Facebook recently followed the lead of several other major web companies – including Google and Mozilla – to launch a so-called “bug bounty” program. Such initiatives offer independent researchers monetary incentives for the private disclosure of vulnerabilities and exploits.
Since rolling out the program in July, Facebook has already doled out $70,000 to researchers around the world for the discrete disclosure of 72 vulnerabilities, all of which have since been fixed, Sullivan says.
“I think it is a good thing to have more people testing our site, and I believe that because we launched the program we have encouraged more people with expertise in security issues to help us,” he says.
The bug bounty programs of today represent a significant evolution in the historically fragile relationship between researchers who find security issues and companies whose products are affected. In the late 1990s and early 2000s, most large companies didn't have a defined process for dealing with reports of vulnerabilities coming in from the research community, Dai Zovi says.
“At best, they would ignore you,” he recalls. “At times, they were hostile and threatened researchers with lawsuits.”
The idea to begin paying researchers for vulnerabilities initially came from the vendor community. The first such initiatives were the Vulnerability Contributor Program (VCP), launched in 2002 by security firm iDefense (now owned by VeriSign), and the Zero Day Initiative (ZDI), founded in 2005 by TippingPoint (now owned by HP). These programs remain the top players in the commercial bug market today.
The most important shift in the vulnerability disclosure model occurred when software makers themselves started offering bug bounties, Dai Zovi says. “Vendors are switching from passively receiving reports to actively soliciting them,” he says.
Mozilla, maker of the popular Firefox web browser, began such a program in 2004. The company provides monetary rewards for the private disclosure of bugs classified as “critical,” or “high” – its most severe ratings designated for flaws that could allow an attacker to install malware without user interaction, obtain confidential data from a user's machine, or cause a denial of service requiring extensive cleanup or reinstallation of the operating system. Since launching the program, Mozilla has received somewhere between 150 and 160 bounty-eligible bugs, and thousands of others that are lower in severity, says Brandon Sterne, a Mozilla security engineer.
Considering some companies still try to deal with security flaws internally and don't welcome bug reports from the research community, Mozilla, along with a number of other companies with such programs, are undoubtedly ahead of the curve,.
Facebook, too, has traditionally encouraged researchers to notify the company directly about security problems.
“We haven't sued anyone or reported anyone to law enforcement who has reported a vulnerability to us, nor do we intend to,” Sullivan says.
In fact, the social networking site advanced its bug solicitation efforts after Sullivan's team spoke with professionals at other companies with established bug bounty programs and received positive feedback. Facebook now offers at least $500 for privately disclosed flaws that may “compromise the integrity or privacy of Facebook user data.” For a particularly bad flaw, the company has given $5,000.
Just two months after the project was launched, Sullivan says he is “astonished” by how impactful it has been. It has enabled Facebook to build relationships with researchers from all over the world. The top two bug finders so far have been a college student from the United States and an individual in Turkey, both of whom have already been paid at least five different times, totaling between $5,000 and $10,000 each, Sullivan says.
Further, the bugs that are being disclosed are flaws for which the company wouldn't normally have been looking. And, the initiative has proven to be an invaluable recruitment tool.
“We had one person who asked us if they could have admission to the F8 conference instead of receiving the bounty,” Sullivan says. “We flew them out to San Francisco and scheduled them for a series of engineering interviews the next day.”
Next: The flip side
Copyright © SC Magazine, US edition
Processing registration... Please wait.
This process can take up to a minute to complete.
A confirmation email has been sent to your email address - SUPPLIED GOES EMAIL HERE. Please click on the link in the email to verify your email address. You need to verify your email before you can start posting.
If you do not receive your confirmation email within the next few minutes, it may be because the email has been captured by a junk mail filter. Please ensure you add the domain @itnews.com.au to your white-listed senders.