A couple of weeks ago the geeky part of the mainstream media was reporting about a malware scam involving pop-up windows, bot-nets and rather dubious anti-virus software called Antivirus2009. The scam is not new, and in the instance I came across the attack vector was a piece of paid advertising on very reputable and well frequented news website. As is the Redmond way, Microsoft carefully analysed the trend and released their own response two weeks later after all the fuss has died down – an entry in their security blog yesterday. The piece referred to a study released on September 22nd (which of course pre-dates all the fuss) from North Carolina State University titled “New Study Highlights Risk of Fake Popup Warnings for Internet Users”.
The researchers found that most people are unable to distinguish fake warnings from real ones, but sshhh, don’t tell the criminals that. The professor of psychology and co-author of the study notes that:
companies and other credible entities may want to incorporate additional unique features into the real messages to allow people to differentiate between genuine warning messages and fake popups. However, he says, “I don’t know if you could develop a legitimate message that could not be duplicated and used illegitimately.”
This thinking is partly right but takes the wrong approach. A warning system that cannot be ‘faked’ does need to be developed. But rather than using ‘additional unique features’ the system should be simple, consistent, and probably open source.
Consider for a moment the warning systems in your car. Self contained, consistent (the low fuel light is always going to look the same) and reliable. It’s only when cars started getting complicated computer management systems that these warnings became oddly suspicious at times.
Computer alerts need to be extremely simple, reliable and trustworthy. Complexity is the enemy of security so additional features won’t work, not for long anyway before they are faked. As computer users we are trained to click OK or Close and the crims play on this.
So perhaps real warnings just need to say something like ‘I’ve detected a virus’. And that’s it. No options, no further warnings and no way to get rid of the message until the user takes some other action which is consistent and secure. Like perhaps a bios linked key stroke built into the secure kernel which fires up a trusted anti-malware product. Then even if the warning is faked, only the trusted product is run.
I’m no programmer so for all I know this may be impossible. But a system like this, which worked the same way on all platforms would be easy enough to train users to on.
Oh and by the way, I was a bit hard on the MSDN blog team earlier. There is actually some very good info on their Security at Home site.