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.

Risk

6/24/2010
06:24 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

iPhone iOS 4 Security

Apple iPhone hit the streets today. I happened to be one of the lucky few who had his delivered by FedEx on Wednesday. So I had some time to kick around with it a bit, and took a look at its (lack) of new security features.

Apple iPhone hit the streets today. I happened to be one of the lucky few who had his delivered by FedEx on Wednesday. So I had some time to kick around with it a bit, and took a look at its (lack) of new security features.Fortunately, I managed to avoid the morning iPhone line madness that colleague Eric Zeman endured, bribes for a place in line and all. Luckily, I haven't suffered any problems with the glitch antenna that some report, either. And while the screen is bright and brilliant, FaceTime is nifty, and I like how this phone feels and fits in the hand more than the previous design - I'm still curious how to keep the data it holds secure.

And I'm not talking about the 65 security flaws Apple patched for the new iOS 4 operating system. Some of those were nasty, including the ability for attackers to grab control of infected devices. These types and numbers of security patches are just the state of application development today, and until development is treated more like an engineering discipline us users of gadgets and IT tools are just going to have to endure.

I'm more interested in how securely an iPhone (security flaws aside, all platforms have them) can slide into the enterprise or be used by someone who has data they need protected. With iOS 4, Apple takes a step in the right direction, but not quite enough.

The iPhone has always had the ability to secure the device by a screen passcode. But not the ability to natively secure specific files. Now, with iOS 4 users can encrypt data with a passcode to specifically protect e-mails and attachments stored on the phone. Apple boasts, in its marketing literature, that one can set "a long, complex passcode to make iPhone even more secure." If someone gets a hold of your phone, a single long passcode isn't going to get the job done if they really want at your data. In addition, with SSL VPN support, iPhone users can also access enterprise applications through an encrypted tunnel.

Good moves, no doubt. But many have commented on how easily iPhone encryption can be bypassed. I'd like to see Apple be more transparent about how the encryption is implemented. No doubt, we will get reports from security researchers in the weeks ahead. And I hope to see that the encryption scheme has improved.

I'd also like to see the ability to encrypt entire applications and other types of data on the phone. Encrypting e-mail and attachments is nice - but there's plenty of other applications that I may want to encrypt, too. And Apple currently provides no way to get that granular.

Apple has also made the API for its encryption available to developers. That's another great step. And I hope to see applications take advantage of the new security capabilities soon - but I don't want to have to rely on each application to provide its own type of security mechanisms. It's important Apple provide a number of these security enhancements as global capabilities.

The iPhone has been around for a few years now, it's way past time Apple step up its security game a bit more than it has so far.

for my security and technology observations throughout the day, find me on Twitter.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/13/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/2020
Russian Cyber Gang 'Cosmic Lynx' Focuses on Email Fraud
Kelly Sheridan, Staff Editor, Dark Reading,  7/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-10987
PUBLISHED: 2020-07-13
The goform/setUsbUnload endpoint of Tenda AC15 AC1900 version 15.03.05.19 allows remote attackers to execute arbitrary system commands via the deviceName POST parameter.
CVE-2020-10988
PUBLISHED: 2020-07-13
A hard-coded telnet credential in the tenda_login binary of Tenda AC15 AC1900 version 15.03.05.19 allows unauthenticated remote attackers to start a telnetd service on the device.
CVE-2020-10989
PUBLISHED: 2020-07-13
An XSS issue in the /goform/WifiBasicSet endpoint of Tenda AC15 AC1900 version 15.03.05.19 allows remote attackers to execute malicious payloads via the WifiName POST parameter.
CVE-2020-10986
PUBLISHED: 2020-07-13
A CSRF issue in the /goform/SysToolReboot endpoint of Tenda AC15 AC1900 version 15.03.05.19 allows remote attackers to reboot the device and cause denial of service via a payload hosted by an attacker-controlled web page.
CVE-2019-19338
PUBLISHED: 2020-07-13
A flaw was found in the fix for CVE-2019-11135, in the Linux upstream kernel versions before 5.5 where, the way Intel CPUs handle speculative execution of instructions when a TSX Asynchronous Abort (TAA) error occurs. When a guest is running on a host CPU affected by the TAA flaw (TAA_NO=0), but is ...