{"id":35110,"date":"2015-01-13T09:37:03","date_gmt":"2015-01-13T17:37:03","guid":{"rendered":"http:\/\/www.intego.com\/mac-security-blog\/?p=35110"},"modified":"2015-01-22T10:46:35","modified_gmt":"2015-01-22T18:46:35","slug":"apple-security-2014-year-in-review","status":"publish","type":"post","link":"https:\/\/www.intego.com\/mac-security-blog\/apple-security-2014-year-in-review\/","title":{"rendered":"Apple Security: 2014 Year In Review"},"content":{"rendered":"

\"Apple<\/a><\/p>\n

The computer security stories seemed to be virtually nonstop over the past year, so there’s a good chance you may have missed some stories. Make sure you haven’t missed anything important\u2014read on for a quick review of some significant Apple-related security stories of 2014.<\/p>\n

Perhaps the most widely publicized Apple security problem of 2014 was the celebrity photo leak<\/a> a few months ago, when a number of celebrities’ private photographs were posted online, apparently facilitated by a flaw in iCloud security. (It’s worth mentioning that although Apple’s iCloud got the brunt of the blame, some of the leaked photos were evidently taken on Android devices and webcams.) Apple admitted that it had identified a way that attackers could brute-force iCloud passwords and stated that the issue had been rectified. Just last week, however, a hacker tool was released that again allowed attackers to brute-force iCloud passwords, but Apple fixed the problem<\/a>\u00a0early this week. In case similar flaws are found in the future, be sure to use a very strong password for your iCloud account and enable two-step\u00a0verification<\/a>.<\/p>\n

\"bug<\/a>Apple also had a bit of public embarrassment when a developer revealed that he had discovered a way to obtain, by means of a bug in Apple’s developer site<\/a>, the personal contact information of all Apple employees (all the way up to executives such as Tim Cook and Phil Schiller) and all registered developers (including, potentially, Flappy Bird developer Dong Nguyen, who was distressed by all the personal attention he received due to his iOS game’s unanticipated popularity). Apple quickly patched the bug.<\/p>\n

There were quite a few new samples of OS X malware that were discovered in 2014. Apple’s built-in Safe Downloads List (aka XProtect, the rudimentary unsafe-download blocker built into Snow Leopard and later) was updated 12 times throughout the year. Somewhat surprisingly, Apple has (for now) continued to release XProtect updates for Snow Leopard and Lion even though both OS X versions are no longer receiving security patches to the operating system itself. (Perhaps Apple is trying to prevent headlines about armies of Mac botnets<\/a>; after all, Lion and earlier versions of OS X\u00a0comprise roughly one-fifth of the Mac installed base, as I reported here<\/a>.)<\/p>\n

\"New<\/a>

Image credit: The Safe Mac<\/p><\/div>\n

Independent security researcher Thomas Reed recently wrote up a list of the biggest malware threats<\/a> he observed in 2014, if you’re interested in reading some technical details. While XProtect and standalone malware removal tools can certainly be\u00a0helpful, they don’t provide the active security protection\u00a0offered by\u00a0full-fledged Mac antivirus<\/a> products; might we recommend some\u00a0options for your Mac<\/a>?<\/p>\n

The past year also seemed to follow\u00a0a trend of nicknaming major security exploits, for example Heartbleed<\/a>, Shellshock<\/a>, and POODLE<\/a>. The main thing you need to do in order to stay safe is to make sure you’re running a supported version of OS X and a fully updated Web browser. You may also need to change your passwords\u2014if you haven’t already done so\u2014on sites that may have been vulnerable to Heartbleed; you can find a partial list of sites here<\/a>. As a follow-up note on Shellshock:\u00a0Snow Leopard and older versions of OS X did not get an official patch from Apple, but you can patch it yourself<\/a>.<\/p>\n

Just before Christmas, Apple patched a widely publicized critical NTP vulnerability<\/a>. This led to what some saw as a milestone in Apple OS security: it was the first time Apple has automatically patched a vulnerability on all supported versions of an OS without first prompting the user (unless you count XProtect, which updates in the background and, in addition to the aforementioned download blocking, also prevents highly exploited versions of Flash Player and Java from running in your Web browsers).<\/p>\n

\"Apple<\/p>\n

Last year also marked the mysterious death of TrueCrypt<\/a>, which had been a cross-platform whole-drive encryption product that was available as\u00a0freeware. Mac users of TrueCrypt can switch to FileVault 2, which is\u00a0built into Lion and later versions of OS X.<\/p>\n

With the recent release of OS X Yosemite (version 10.10<\/a>), Apple stopped releasing security updates for Lion (10.7)\u2014including the Lion version of OS X Server. Most Macs running Lion can be upgraded to Yosemite, which is a free* upgrade available from the Mac App Store; see my guide to which Macs can (and can’t) run Yosemite<\/a>.<\/p>\n

*Note that if you’re upgrading a Mac server, OS X Server is a paid upgrade ($19.99 in the Mac App Store<\/a>) after upgrading the base operating system to Yosemite.<\/p>\n

\"FadedSnowLeopard\"Apple also stopped releasing iTunes updates for Mac OS X Snow Leopard (version 10.6), which had already stopped receiving base OS security updates when Mavericks (10.9) was released in 2013. Although the cessation of iTunes updates for Snow Leopard doesn’t have any immediate security implications, if future versions of iTunes include security fixes, they most likely\u00a0won’t be made available to Snow Leopard users. However, if you’re still using Snow Leopard as a client OS at this point, it’s really time to move on, if at all possible; XProtect updates and antivirus software can’t always protect you from unpatched vulnerabilities in your core operating system. Again, see our upgrade guide<\/a>\u00a0if you’re not sure whether your Mac can be upgraded, and for tips on what to do if you can’t upgrade to a supported version of OS X.<\/p>\n

There was also a plethora of password database breaches in 2014, which in some cases prompted companies to ask its users to change their passwords. I mentioned a few such occurrences<\/a> back in May. As a standard best practice, it’s wise to use a unique password for each site. If you have accounts at a lot of sites and can’t memorize every password, consider using a reputable password management program; we shared some Mac and iOS options<\/a>\u00a0a couple years ago. (For thoughts about why storing your passwords in a single secure program might not be a bad idea, see this article<\/a>, or you can take a look at\u00a0our past articles on password security<\/a>.)<\/p>\n","protected":false},"excerpt":{"rendered":"

The computer security stories seemed to be virtually nonstop over the past year, so there’s a good chance you may have missed some stories. Make sure you haven’t missed anything important\u2014read on for a quick review of some significant Apple-related security stories of 2014. Perhaps the most widely publicized Apple security problem of 2014 was […]<\/p>\n","protected":false},"author":14,"featured_media":35200,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[190,13,5],"tags":[775,1807,66,174,86],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\n\n\n\t\n\t\n\t\n