Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

6/18/2008
02:45 AM
50%
50%

Could a Smartphone Solve the Notebook Security Problem?

Maybe instead of looking at them as a new problem, we should consider smartphones as a potential security solution

One of the big trends I’m watching for the next several years is the move to next-generation smartphones instead of laptops as the primary means of mobile access to increasingly cloud-based IT solutions. With the launch of the second-generation iPhone – as well as high-profile competitors based on Google and Microsoft technologies from vendors ranging from HP to Palm to RIM’s own Bold and Thunder – maybe it’s time we took a look at whether a smartphone could be part of the security solution.

Granted, up until recently the smartphone was seen as an unprotected problem. But with improvements to security and centralized management tools from a variety of players, it no longer needs to be. But could a laptop user really live on a smartphone – and what would be the security advantages?

Recently, I’ve been playing with a unique accessory called the Redfly Mobile Companion. What makes this accessory really interesting is that it's a laptop hardware emulator that works with a Windows Mobile phone. It doesn’t run an OS and doesn’t have any persistent storage. It simply re-displays what is on the phone on a laptop-sized screen, which is coupled with a laptop-like keyboard and touch pad. In effect, it turns your Windows Mobile-based smartphone into a laptop-sized device.

What's fascinating is that when you take the Windows Mobile user interface and blow it up to PC size, you actually get a much more livable experience. And although it is limited, the number of things you can do on a smartphone today exceeds what you could do on early laptops. If you are like me and mostly live on email, you can almost live on the result – the only real problems are the limitations of the browser and the bandwidth, both of which are improving rapidly.

There are performance issues with the current generation of smartphones. But both Apple’s new iPhone and Nvidia’s recently announced Tegra promise to address these shortcomings.

But how could smartphones be more secure than laptops? In a word: capacity – or the lack of it. One of the big problems with laptops is that people keep putting large databases of customer information on them – then find them lost or stolen, resulting in a public relations nightmare. And no matter how well this information is encrypted or protected, if we can’t certify that it has been destroyed, we are still pretty much screwed.

Smartphones, on the other hand, don’t have the capacity to hold that sort of data, so the exposure is vastly lower. And, unlike laptops, which are only occasionally connected to the network, smartphones are virtually always connected when they are turned on. They can more easily, and more assuredly, be wiped if they are lost or stolen.

Granted, this last point requires the use of relatively sophisticated management tools. But these tools are readily available, and they are very similar to tools that were developed for PCs. The combination of low memory and more persistent connectivity potentially makes smartphones much more secure than laptop computers.

There are drawbacks with currently available smartphones. I still think most current models are still too heavily reliant on password-based security. They should use biometrics or some other more secure access method.

In the end, though, I think it is past time we started looking at smartphones differently. We have to secure them and pay for them anyway. As the technology gets better – and it will, with Apple's introduction of the new iPhone later this year – we should see them as new, and possibly more secure, alternatives to laptops.

— Rob Enderle is President and Founder of Enderle Group . Special to Dark Reading

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.