Perimeter
2/10/2009
06:15 PM
Sara Peters
Sara Peters
Commentary
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Could Slimmer OSes Lead To Better Mobile Device Security?

Maybe I'm stretching a bit, but let's say that operating system developers slimmed down their standard OSes enough so that eventually they'd be skinny enough to have a career in fashion and, more important, run on mobile devices. And, if so, would this be a good thing for mobile device security?

Maybe I'm stretching a bit, but let's say that operating system developers slimmed down their standard OSes enough so that eventually they'd be skinny enough to have a career in fashion and, more important, run on mobile devices. And, if so, would this be a good thing for mobile device security?I pondered this today while reading Ephraim Schwartz's story on ComputerWorld, "The incredible shrinking operating system."

I've spoken before about how delightful it would be if Microsoft, Apple, and their colleagues would cool it with the window dressing and frenetic adding of new features, and, instead, take some time to make their current OSes slimmer. In fact, I was a bit giddy when Mac announced this was precisely its plan for Mac OS X "Snow Leopard." A trim OS moves more quickly than a massive, bloated OS. Plus, less code generally means more security.

Another compelling reason Schwartz mentioned for putting operating systems on a diet is because "a smaller OS can run on a greater variety of devices, and as netbooks, smartphones, and new devices like the iPod Touch gain traction, the benefit of a smaller OS becomes hard to ignore."

OK, so let's say your Apple comes out with the new, slim-and-sexy Mac OS X Snow Leopard, and it can run on your iPhone.

Good thing? Bad thing?

From an interoperability, ease-of-use standpoint, it sounds good. From a security standpoint--well, it could be good because the mobile platform would have gone through the same scrutiny as other operating systems. (Maybe Mac's a bad example, here, but you get my point.)

Similarly, the iPhone's Snow Leopard operating system could theoretically run the same well-scrutinized applications as an iMac's Snow Leopard. (Realistically, though, the applications, themselves, would have to lose a lot of tonnage if they want to dance with an iPhone's comparatively puny RAM.) If, for example, the security industry ever succeeds in developing a secure Web browser that actually works,, I'd love to see it work on my BlackBerry.

On the other hand, narrowing the number of OSes to pen test and exploit might make attackers' job easier.

I'm just beginning to ponder this. I'm eager to gain the benefit of your thoughts.

Sara Peters is senior editor at Computer Security Institute. Special to Dark Reading. Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3407
Published: 2014-11-27
The SSL VPN implementation in Cisco Adaptive Security Appliance (ASA) Software 9.3(.2) and earlier does not properly allocate memory blocks during HTTP packet handling, which allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCuq68888.

CVE-2014-4829
Published: 2014-11-27
Cross-site request forgery (CSRF) vulnerability in IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allows remote attackers to hijack the authentication of arbitrary users for requests tha...

CVE-2014-4831
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to hijack sessions via unspecified vectors.

CVE-2014-4832
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to obtain sensitive cookie information by sniffing the network during an HTTP session.

CVE-2014-4883
Published: 2014-11-27
resolv.c in the DNS resolver in uIP, and dns.c in the DNS resolver in lwIP 1.4.1 and earlier, does not use random values for ID fields and source ports of DNS query packets, which makes it easier for man-in-the-middle attackers to conduct cache-poisoning attacks via spoofed reply packets.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?