{"id":7462,"date":"2014-11-24T06:00:16","date_gmt":"2014-11-24T14:00:16","guid":{"rendered":"https:\/\/www.paloaltonetworks.com\/blog\/?p=7462"},"modified":"2015-10-07T15:26:17","modified_gmt":"2015-10-07T22:26:17","slug":"2015-predictions-mobility","status":"publish","type":"post","link":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/2014\/11\/2015-predictions-mobility\/","title":{"rendered":"2015 Predictions: Mobile Security"},"content":{"rendered":"

As 2014 comes to a close, our subject matter experts check in on what they see as major topics and trends for the new year. (You can read all of our 2015 predictions content here<\/a>.)<\/em>\u00a0<\/strong><\/p>\n

\"2015<\/span><\/div><\/p>\n

Looking to the year ahead, I see a number of signs that indicate a shift in the ways that organizations approach mobile security. Traditional measures are giving way to new thinking, the laissez-faire attitudes towards BYOD are melting away, and concerns about mobile threats are driving the need for stronger security measures.<\/p>\n

<\/p>\n

1. Death of Proprietary Containers On Mobile Devices<\/strong><\/p>\n

There was a time when the proprietary containers approach for managing company data was the only game in town. Companies deployed this technology because it delivered what they wanted for security by creating partitions for the data, but it drastically changed the user experience and in the process alienated the end user. \u00a0Talk to end users about what they think, and you\u2019ll find that most of them aren\u2019t happy.<\/p>\n

What\u2019s the solution? We\u2019re seeing far more elegant approaches to manage data coming from the operating system vendors. iOS 7 introduced an elegant method of managing business apps and data. Samsung Knox brought app and data management back to the function delivered by the operating system platform vendor, and the introduction of Android Lollipop continues down this same path. In 2015, I expect to see that proprietary approaches are going to disappear, with the market evolving to deliver enterprise management over security functions native to the mobile platform.<\/p>\n

2. Mobile Malware Will be a Slow Burn<\/strong><\/p>\n

There is clearly a gap between what we see in security research in terms of evolving techniques in mobile malware and the general public\u2019s understanding of the threat model. Mobile malware has not had the massive infection rate that desktops had in the past, so is it still problem?<\/p>\n

I don\u2019t think mobile malware is going down that road. There may never be an outbreak of mobile malware at the same infection rate as some of the Windows viruses of the past. That\u2019s because that play is dead. Blowing up millions of computers is pure 1999. Today, malware on the PC is highly targeted, because it\u2019s too easy to find if everyone, including the malware researchers, has a copy of it. Instead of trying to infect thousands of computers, the attackers only need to find one victim.<\/p>\n

Mobile malware is always going to be in lower in numbers, and 2015 will be no different. But finding it is very difficult if you don\u2019t have the capabilities to prevent or detect it, especially with all of the BYOD devices running on networks. And furthermore, when you do find infected devices, the malware packs a much stronger punch. There are far more resources (in addition to the data, there\u2019s always a network connection, access to out-of-band communication such as SMS for command & control, location data, and recording capabilities) to make the malware more potent than what you see on PCs.<\/p>\n

3. Less is More with\u00a0Enterprise Mobility Management (EMM)<\/strong><\/p>\n

Wait a minute, isn\u2019t more is more? Not with EMM, because the more you apply, the less your users will like it.\u00a0 Unfortunately, that\u2019s the challenge with thinking inside the box. If your only option for stopping threats is removing the application that can access the threat, then you\u2019re left with removing functionality as the only way to solve security issues.<\/p>\n

But in 2015, I think that the smart customer is going to think of more than EMM. In fact, they are going to skip a beat in the evolutionary chain. When faced with emerging security threats, the normal response is to rack and stack new security solutions on top of existing infrastructure. It\u2019s like buying a fast food value meal, buy more and get more, even though in the end it\u2019s still junk food.<\/p>\n

That\u2019s why the next step in EMM is not more EMM.\u00a0 It\u2019s also not going to be EMM plugged into other security solutions. The smart play is to evaluate all security needs and see what could be done when looking at mobile security requirements as a whole. That includes managing mobile devices, protecting mobile devices from threats, protecting your networks from bad devices, and most importantly, making sure your data is safe.<\/p>\n

 <\/p>\n

Mobile security\u00a0is among many focus topics at Ignite 2015<\/a>, where you will tackle your toughest security challenges, get your hands dirty in one of our workshops, and expand your threat IQ. Register now<\/a> to join us March 30-April 1, 2015 in Las Vegas -- the best security conference you'll attend all year.<\/em><\/p>\n

\"PAN_IC15_web_logo-1\"<\/span><\/div><\/a><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

As 2014 comes to a close, our subject matter experts check in on what they see as major topics and trends for the new year. (You can read all of our 2015 …<\/p>\n","protected":false},"author":19,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[76,229],"tags":[925,926,419],"coauthors":[788],"class_list":["post-7462","post","type-post","status-publish","format-standard","hentry","category-mobility","category-predictions","tag-2015-predictions","tag-emm","tag-mobile-malware"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/7462","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/comments?post=7462"}],"version-history":[{"count":7,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/7462\/revisions"}],"predecessor-version":[{"id":7495,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/7462\/revisions\/7495"}],"wp:attachment":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/media?parent=7462"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/categories?post=7462"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/tags?post=7462"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/coauthors?post=7462"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}