Commentary

Wireless Security In A Sorry State, Mobile Viruses Feared By Many

Last week at Mobile World Congress, a new survey indicated that the public is afraid that their mobile devices will catch a rare virus. At the same time, a whitepaper from Codenomicon takes a look at the vulnerabilities of Bluetooth and Wi-Fi. Is the public -- and, more important, IT -- right to be afraid?

Last week at Mobile World Congress, a new survey indicated that the public is afraid that their mobile devices will catch a rare virus. At the same time, a whitepaper from Codenomicon takes a look at the vulnerabilities of Bluetooth and Wi-Fi. Is the public -- and, more important, IT -- right to be afraid?The first reports of mobile viruses appeared years ago, and specifically targeted smartphone operating platforms from Palm and Symbian. They used Bluesnarfing and Bluesharking techniques to break into smartphones by cracking open the Bluetooth connections. Although these instances have been very rare, the fear of infection persists.

McAfee polled 2,000 people in Britain, the United States, and Japan and found that 72% were concerned about the likelihood of an infection. Almost 12% said someone they knew had suffered through an infection, but only 2% had actually had a virus themselves. Still, that left a whopping 86% of respondents saying that they didn't know anyone who's phone had been sickened by a mobile virus.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

If we're to believe these numbers, instances of infection are rare. Details about which mobile operating systems were most affected weren't provided in the report, but it's not a big leap to imagine that the viruses are limited to smartphones. Phones running platforms from RIM, Microsoft, Symbian, and Palm, among others, provide the juiciest targets because of the nature of the information stored on such devices. Traditional consumer handsets, many of which run proprietary platforms, aren't as enticing a catch.

With Bluetooth and Wi-Fi coming standard on almost all smartphones at this point, IT should be concerned about protecting their corporation's assets.

Codenomicon recently published a whitepaper which suggest that 90% of all tested devices showed vulnerabilities. That is worrisome. What's worse is that rather than provide proactive defenses, most wireless security firms are providing reactive patches instead.

Reads the report, in part:

Despite boasts of hardened security measures, security researchers and black-hat hackers keep humiliating vendors. Security assessment of software by source code auditing is expensive and laborious. There are only a few methods for security analysis without access to the source code, and they are usually limited in scope. This may be one reason why many major software vendors have been stuck randomly fixing vulnerabilities that have been found and providing countless patches to their clients to keep the systems protected.

How is IT to protect against these viruses? And are they as much of a threat as people make them out to be?

True, lots of smartphone management programs allow IT to turn the Bluetooth and Wi-Fi radios off so the employee can't use them. This nullifies the threat. But what good is it to have those technologies if we're unable to make use of them?

There has to be a better way.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links