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

1/15/2008
11:52 AM
George V. Hulme
George V. Hulme
Commentary
50%
50%

A Couple More Things Apple Needs To Do To Become IT (Security) Friendly

As Macworld kicks off, more companies, especially SMBs, are bound to be eyeing the possibility of displacing Microsoft in favor of Apple. And there are plenty of good reasons why: Vista has been a disappointment, and OS X is simply more elegant and easier to use than anything Microsoft has to offer. And if my personal experience with OS X is any indicator, OS X is a lot more stable. But when it comes to security, Apple has some work to do.

As Macworld kicks off, more companies, especially SMBs, are bound to be eyeing the possibility of displacing Microsoft in favor of Apple. And there are plenty of good reasons why: Vista has been a disappointment, and OS X is simply more elegant and easier to use than anything Microsoft has to offer. And if my personal experience with OS X is any indicator, OS X is a lot more stable. But when it comes to security, Apple has some work to do.In his excellent article, What Apple Needs To Do To Become More IT Friendly, John C. Welch outlined nearly a dozen things the champion-of-slick-design needs to do if it's to succeed in gaining business market share. They're good points all -- but Welch forgot one: Apple would need to improve how it approaches security.

That's right. Apple would need to improve how it approaches security.

Here's why I say this:

Scheduled Patch Releases. OS X updates and security patch releases would need to be released on a standard schedule, much as Microsoft has done. It was just handful of years ago when Microsoft would release patches willy-nilly: a couple patches on Monday, another late Friday afternoon, and on it went. This drove IT departments nuts. It was impossible to plan or ready resources to push the patch to their 50, or 5,000 desktops. So it took companies longer to deploy patches. They were less secure as a result. Patch Tuesday has helped to (somewhat) calm that madness. Apple would need to follow suit, if it's to succeed in enterprises of any size.

Develop Better Automated Patch Deployment and Patch Validation Options. Updating patches on 10 to 20 client systems can be a chore. In fact, using the built-in Software Update gets the job done just fine. But manually updating 1,000 endpoints is a story with a frustrating and costly ending. In this highly regulated environment, companies not only have to deploy patches, but they need to be able to prove that the patches have been deployed.

Enterprise-Class Security Software Management. That's right. The firewall built in to OS X, as well as third-party firewalls, anti-malware, anti-spam, and other types of security software, needs better centralized management. While you can manually support 10 MacBook Pros, no one wants to endure the pain, or cost, of manually supporting 1,000.

But we're talking about Apple ... Macs are inherently more secure, you say . . .

No, they're not. At least I don't think so.

And even if they are, that's a moot point in the enterprise. My assumption is that any application and operating system is breakable. And any security professional worth her firewall policies needs to make that assumption when protecting the IT infrastructure.

I think, because of the relatively smaller market share, OS X and Apple software has been targeted less. That's a condition that's likely to change with each new percentage bump upward.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/9/2020
Russian Cyber Gang 'Cosmic Lynx' Focuses on Email Fraud
Kelly Sheridan, Staff Editor, Dark Reading,  7/7/2020
Why Cybersecurity's Silence Matters to Black Lives
Tiffany Ricks, CEO, HacWare,  7/8/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-2012-6486
PUBLISHED: 2020-07-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2012. Notes: none.
CVE-2012-6487
PUBLISHED: 2020-07-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2012. Notes: none.
CVE-2012-6488
PUBLISHED: 2020-07-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2012. Notes: none.
CVE-2012-6489
PUBLISHED: 2020-07-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2012. Notes: none.
CVE-2012-6490
PUBLISHED: 2020-07-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2012. Notes: none.