[Brian Salcedo] made headlines a few years ago as a hacker who attempted to break into Lowe's corporate network. He is currently serving a nine-year prison sentence, one of the longest sentences for a computer hacking offense. Recent events surrounding a different hacking case have revealed that the buyer he worked for, [Albert "Segvec" Gonzalez], was a Secret Service informant. [Salcedo] claims that were it not for [Gonzalez]'s threats, he would not have committed the hacking offense. While the Secret Service may not have even been aware of [Gonzalez's] activity with other hackers, [Salcedo] could make a case of entrapment by arguing that [Gonzalez] threatened him as a government agent in order to make him plant the sniffer in Lowe's network.

Mozilla security chief [Window Snyder] made some surprising announcements about Firefox Next, Mozilla's next major browser overhaul. In her chat at the Black Hat security conference, she introduced three new initiatives that focused on threat modeling, training, and vulnerability metrics. For the threat modeling initiative, she's hired Matasano Security consultants to review Firefox's code for weaknesses and recommend mitigation tactics to protect the browser from hacker attacks. This isn't inherently unusual; what is abnormal is that the information, once the work is done, will be revealed to the public. The training initiative will have IOActive trainers working with Mozilla engineers on secure computer programming practices. At the end, according to [Snyder], online versions of the classes will be released to the public, along with the class materials. The last initiative revolves around security metrics, and is already in progress. Essentially, the project will ideally take the focus off of patch-counting and provide a better assessment of security and vulnerability issues. [Snyder] says "We're in the early phase, working on incorporating feedback from the rest of the industry." She also reveals some more Firefox developments, including possibly incorporating NoScript into the core browser and implementing protected mode, but they're still a long way from becoming standard features.