IE9's App Rep uses a file's hash -- which identifies the file contents -- and its digital certificate to determine whether it's a known application with an established reputation. If the App Rep algorithm ranks the file as unknown -- perhaps because the hash value hasn't been seen before -- IE9 throws up a warning when users try to run or save the file.
Wisniewski noted problems with that approach.
"The problem with code signing is that we regularly see it abused," Wisniewski said, using the Stuxnet worm as an example. One variant of Stuxnet, the worm that experts have concluded was created to wreak havoc on Iran's nuclear program, used a pair of stolen certificates to masquerade as legitimate software.
"One of the things that Zeus does is grab all the digital signatures on a [compromised] computer," Wisniewski added, talking about the pervasive crimeware kit responsible for a large percentage of financially motivated hacks.
Legitimate software that hasn't yet been "approved" by Microsoft could also confuse users into either rejecting the download -- bad for that product's developer -- or worse, "teach" IE9 users to ignore the warnings altogether.
"I love the idea of reputation-based blocking moving forward," acknowledged Wisniewski, who tipped his hat to Microsoft and IE9 for "trying to get ahead of the curve" with App Rep. "We're doing about all we can do in the reaction side.
But in his eyes, Microsoft's missed an opportunity by touting numbers that told only half the story.
"They made this PR move, showing us half the picture," he said. "They missed the mark."
Sign up for Computerworld eNewsletters.