Apple's patch process a mess, say researchers

Apple's patching process proves that the company isn't serious about moving Macs into the enterprise, security researchers said Monday.

One dissenting expert, however, said it was unfair to compare Apple's patching procedures with, say, Microsoft's.

"You have to evaluate the patching performance of the company if you're looking at Macs," said Andrew Storms, director of security operations at vendor nCircle Network Security Inc. "And the last two weeks hasn't been a gold star for Apple."

Unlike its operating system rival Microsoft, which schedules security updates for the second Tuesday of each month and typically limits other updates to twice monthly, Apple releases updates, security fixes included, on any day of the month. Apple, for example, has rolled out updates on five of the 10 business days since September 9.

"You get an update from Apple and it's always a surprise," Storms said. "The first thing you do is sit down with your team, look at the update, set priorities and assign resources. And then the next day, another update arrives, and you have to do it all over again.

"If you can't properly plan for this, you're in a constant firefighting mode," Storms continued. "Now it's affecting the management of the IT team."

And that has to spook businesses, whose administrators are used to pinning Microsoft's updates to specific dates on the calendar. "Even if you realize that the Mac may be an effective tool, it's going to have a greater impact on the infrastructure because of the way Apple patches," Storms said. "The question is, can your infrastructure withstand it?"

Charlie Miller, a researcher at Independent Security Evaluators who is well-known for his Mac and iPhone vulnerability work, agreed that Apple's patching process makes it tough on corporate IT staffers. "Administrators rely on knowing what will happen," Miller said. "If they know, they can plan their week around it."

Posting patches without a schedule, Miller said, is an invitation for businesses to simply not patch. "For someone like me, it's no big deal, but for professionals, it's a whole different story," he said. "The last they want is a patch that just shows up. They can't patch without testing. So this is one more reason for them to go, 'I just won't patch.' "

• Bookmark this page
• Share this article
  •  
  • facebook
  • slashdot
  • digg
  • Reddit
  • stumbleupon
  • linkedin
  • twitter
• Got more on this story? Email TechWorld
• Follow TechWorld on twitter

• Share
  Share this article

  •  google+
  • facebookfacebook
  • slashdotslashdot
  • diggdigg
  • RedditReddit
  • stumbleuponstumbleupon
  • linkedinlinkedin
  • twittertwitter
• print
• email
• Bookmark