Risk
1/29/2011
01:09 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Is Apple (Finally) Stepping Up Its Security Game?

Apple's reported recent hire of noted security author and expert, David Rice, is yet another step the company has made in the past year to help improve its sloppy security image.

Apple's reported recent hire of noted security author and expert, David Rice, is yet another step the company has made in the past year to help improve its sloppy security image.I know. I know. Macintoshes aren't attacked by malware to anywhere close to the extent of its rival Windows platform. And I also know that when it comes to security, most consumers and fanboys view Apple's record as untarnished, shiny, and red.

Well, that's not the image Apple necessarily has with the people who pay attention to enterprise IT security, such as security analysts, researchers, governments, and the security officers responsible for keeping their organization's data snug and reasonably safe.

One example would be the decision last spring by the UK's health minister who would not bless iPhones for use by government officials or civil servants. The reason, according to this Silicon.com story, is because of the lack of device encryption. It seems government departments were having trouble losing mobile devices with sensitive information onboard – and banned the use of devices without adequate encryption capabilities.

However, a story published later, Government iPhone ban blamed on Apple secrecy, places the reason for the ban on Apple's refusal to allow its source code to be reviewed by computing experts in the intelligence services.

Such secrecy is common with Apple. It's especially notable when it comes to software vulnerabilities. For a long time now Microsoft has (mostly) embraced the security researchers that vet its software for vulnerabilities. And, Microsoft is known for sharing much more information about the vulnerabilities in its software. Much of this information helps IT teams to better gauge the risk posed by the vulnerabilities, as well as decide how quickly they must patch. When it comes to Apple software vulnerabilities, the information provided is sparse. That is being kind.

Another trend in the IT industry designed to help improve system security (and perhaps as a PR exercise in some cases) has been bug bounties. Paying these bounties shows a willingness to build a relationship with security researchers. Software makers such as Google and Mozilla offer such bounties. Apple does not. To be fair, neither does Microsoft.

Last year the heat got so hot around how slowly Apple responded to vulnerabilities that one security expert and author called for Apple to be investigated by the FTC for its blatant disregard for software security.

Rich Mogul, security analyst, penned this response, and while he disagreed that it was time for an FTC investigation (which did strike me as over the top), he did agree that Apple has a less than admirable image when it comes to fixing vulnerabilities:

Apple has a poor history here, often failing to provide OS X security fixes for flaws fixed on other platforms days, weeks, or even months earlier. We've seen Mac users exposed to known vulnerabilities in WebKit (Safari), Samba (Windows file sharing), DNS (networking), MDNS (Bonjour), Apache (web server), Java, and more. This is an extremely serious problem, and one Apple is rightly criticized for.

To be fair, Macintosh systems are generally safer because they are targeted less. But make no mistake about it: if someone wanted to target a Mac user they'd have no trouble finding the software vulnerabilities that would make it easy to successfully do so.

And, if a report issued by security software maker Secunia [.pdf] last summer is accurate, Apple surpassed such software vulnerability generation heavy-weights as Oracle, Microsoft, HP, and Adobe Systems.

That ain't easy.

Which is why it's welcomed news to me that Apple has (reportedly) hired a security expert that knows more than most about the cost of insecure code. His book, Geekonomics, is one of the best attempts at quantifying how much insecure code costs businesses and the risk it creates for us all. Rice also worked as a global network vulnerability analyst for the NSA as well as a cryptologic officer in the United States Navy.

As Mathew J. Schwartz reported here, Rice isn't the first information security luminary to be recently hired by Apple. Last year Apple hired former security lead for Mozilla, Window Snyder, and the year prior, the company brought on board Ivan Krstic, former director of security architecture for the One Laptop Per Child project.

What does Apple have planned with all of this information security firepower? We have no idea. So far, Apple is being as obscure as it always is.

For my security and technology observations throughout the day, you can find me on Twitter.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

CVE-2014-9709
Published: 2015-03-30
The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.