Users can be better protected if more thought was given to the default product configuration, Fraser Howard, principal virus researcher at SophosLabs, pointed out in a recent blog post.
Elaborating on Howard's argument, Paul Ducklin, Sophos' Asia-Pacific head of technology, said software and hardware vendors are sometimes too keen to show off the functionalities available in their products. "They turn that functionality on because it is there, rather than because it is necessary or important."
Default settings, he noted, are not a new problem. About a decade ago, the main vehicles for malware infection were macro viruses or Trojans in Microsoft Office files. This was partly due to "full-blown macro programming functionality" in every Office installation--a feature a user couldn't turn off even if that person wanted to, Ducklin pointed out.
"Presumably, Microsoft was afraid that if they allowed people consensually to [disable] Office's macro-handling capacity, some users might begin to think that macros weren't possible at all in Office, which might reduce the overall appeal of the product, or lead to bad reviews, or end up in unfavorable comparisons with competing products which did obviously have such a feature. So, in Office history, features won out over security for some years," said Ducklin.
"Eventually, Microsoft began to add operational restrictions to the macro system so that it retained almost all of its usefulness in real life, whilst breaking some key behaviors on which malware authors had relied," he continued. "Macro viruses then began to wither and die out. These days, they are rarely seen."
Firewalls and routers, added Ducklin, also come with default settings that make them easier to deploy but could be reconfigured by malware authors before the automatic settings are changed. "For example...default accounts and passwords on systems such as new routers and firewalls should work only for the purpose of setting non-default passwords, and the device shouldn't begin to function as a router or firewall until such changes have been made."
Features and ease-of-use or ease-of-deployment may often triumph over security, but prevention is nonetheless better than cure, said Ducklin. Vendors should turn "possibly dangerous features off by default" and monitor closely what happens when well-informed early adopters opt to activate those features.
This article was originally posted on ZDNet Asia.