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.

Comments
6 Ways Apple Is Polishing Mac Security
Newest First  |  Oldest First  |  Threaded View
MROBINSON000
50%
50%
MROBINSON000,
User Rank: Apprentice
7/12/2012 | 8:10:34 AM
re: 6 Ways Apple Is Polishing Mac Security
This article does a great job of summarizing the aspects regarding Mac security. Recently, Kaspersky said that Apple is 10 years behind Microsoft in terms of security. But, we think itGs more significant to look at the software, not the operating system when thinking about security.
As security professionals, we expect Apple to be more transparent and change the way they deal with security researchers.
For more information on our vision, check out this article http://blog.securityinnovation...
Andrew Hornback
50%
50%
Andrew Hornback,
User Rank: Apprentice
7/3/2012 | 2:39:50 AM
re: 6 Ways Apple Is Polishing Mac Security
I think the biggest takeaway here is that Apple is trying to do what it can to protect the user from their own actions which is the primary attack vector on the OS X platform.

The theory goes that if you keep your Mac updated (i.e. all of the relevant OS updates, all of the security updates, all of the application updates), that you'll be much better off with regards to defending against threats in the wild.

However, keeping updated is part of proper system hygiene - and there aren't too many people that are diligent about it because Macs are supposed to be easier to work with and impervious, so users don't think twice about "set it and forget it". That's the bane of the security pro's existence and the best case scenario for the malware crowd.

Andrew Hornback
InformationWeek Contributor
ANON1237925156805
50%
50%
ANON1237925156805,
User Rank: Apprentice
6/29/2012 | 9:19:34 PM
re: 6 Ways Apple Is Polishing Mac Security
It's hard to inject viruses into any UNIX-based system, whether it be Mac OS, Android, Linux, or any of the original flavors of UNIX. This publication has clearly explained why that is more than once. That why since Apple released OS X they have legitimately made the claim that Windows viruses can't hop over to the Mac.

At this point malware other than viruses has become the dominant threat, particularly via the interet. Plenty of malware that is OS agnostic can wreak as much havoc on a Mac as it could on a Windows box; the UNIX advantage has diminished. Flashback is emblematic of this situation.

Apple is wisely reframing its strategies and its marketing language to reflect this changing reality. This is what they should do, so no need for outsized praise. On the other hand finding fault with a strategy that was more than adequate several years ago is not useful.

It would be nice if Apple did a better job of explaining patches but what's most important to me is frequency and efficacy of patches and ease of installing. Apple seems to be heading down the right path on that front. Now let's just turn on the security features rather than ignoring them. . .
ANON1251568162539
50%
50%
ANON1251568162539,
User Rank: Apprentice
6/29/2012 | 7:11:59 PM
re: 6 Ways Apple Is Polishing Mac Security
The essential question is GǣWho gets hurt here?Gǥ

Novice Mac users want a walled garden. Especially, those who fled from Windows.

Power users get vetted third party apps. And a means of automatically removing accidentally installed malware.

Expert Mac users and Linux advocates get to take the level of risk they choose.

Malware writers donGt lose, because they were never on Macs anyway. You canGt lose what you never had.

The only losers I see are the Windows Anti-virus venders who have been fraudulently coercing people into buying their worthless software. They were the oneGs who corrupted the word Gǥ virusGǥ into meaning any malware regardless of type or function.

Apple doesnGt lose when they give up a contention which no one believed.
ANON1251568162539
50%
50%
ANON1251568162539,
User Rank: Apprentice
6/29/2012 | 6:58:10 PM
re: 6 Ways Apple Is Polishing Mac Security
YouGd have to prove that you own it.
Tronman
50%
50%
Tronman,
User Rank: Apprentice
6/29/2012 | 5:10:46 PM
re: 6 Ways Apple Is Polishing Mac Security
Want to buy a bridge?
hlubinv8l
50%
50%
hlubinv8l,
User Rank: Apprentice
6/29/2012 | 4:49:21 PM
re: 6 Ways Apple Is Polishing Mac Security
It's easy to understand why Apple had to change the statement that Macs don't get viruses. Since some Mac owners run Windows on their Macs (either in Boot Camp or in emulation), those users can get Windows viruses infecting their Windows installations.

Even though Windows viruses have no effect on OS X, they still count as viruses. So for those people running Windows on a Mac, the statement would not be true.

The statement should have read that Mac OS X (the operating system) has never been susceptible to viruses.... simply because there has never been an OS X virus.

There have been a few examples of malware for OS X in the past, like the recent Flashback Trojan, but nothing that spreads to other users without user interaction (as Windows viruses do).


COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...