Mobile Security

30
Mobile Security “Bring war material with you from home but forage on the enemy” - Sun Tzu Xavier Mertens Beltug SIG Security - Jan 2013

description

Slides about mobile security presented during the BELTUG Security SIG ("Special Interest Group") in January 2013.

Transcript of Mobile Security

Page 1: Mobile Security

Mobile Security

“Bring war material with you from home butforage on the enemy” - Sun Tzu

Xavier MertensBeltug SIG Security - Jan 2013

Page 2: Mobile Security

Disclaimer

“The opinions expressed in this presentation are those of the speaker and do not necessarily reflect those of past, present employers, partners or customers.”

Page 3: Mobile Security

Agenda

• Introduction: Top-10 mobile risks

• Company owned devices

• Employee owned device (BYOD)

• Risks inherent in mobile devices

• Mobile applications development

Page 4: Mobile Security

Top-10 Mobile Risks• Insecure data storage

• Weak server side controls

• Insufficient transport layer protection

• Client side injection

• Poor authentication & authorization

• Improper session handling

• Secure decision via untrusted input

• Side channel data leakage

• Broken cryptography

• Sensitive information disclosure

(Source: OWASP)

Page 5: Mobile Security

Top-10 Mobile Risks• Insecure data storage

• Weak server side controls

• Insufficient transport layer protection

• Client side injection

• Poor authentication & authorization

• Improper session handling

• Secure decision via untrusted input

• Side channel data leakage

• Broken cryptography

• Sensitive information disclosure

(Source: OWASP)

Mobile devicesare

Computers!

Page 6: Mobile Security

Company Owned Devices

Page 7: Mobile Security

Easy? Really?

• Limited set of manufacturers/OS

• Full control of hell?

• People try to evade from jail (like laptops)

• Need procedures (backups, helpdesk)

Page 8: Mobile Security

Corporate Policy

• Must be communicated & approved before the device provisioning

• Communication channels: addendum to a contract, Intranet, a “check box”?

• Restrictions (SD cards, Bluetooth, camera)

• What about private data? (pictures, MP3, downloaded (paid!) apps?

Page 9: Mobile Security

Examples

• Document already available on beltug.be(Members section)

• Simple policy: http://www.security-marathon.be/?p=1466(Jean-Sébastien Opdebeeck)

Page 10: Mobile Security

Data Classification

• Another approach is implementing data classification

• Implementation of the “least privileges” principle

• Access to data is based on profiles

• Work with any device! (benefit broader than the scope of mobile devices)

Page 11: Mobile Security

Data ClassificationData

ClassificationCompany Owned

DevicesPersonal Devices

Top-Secret No No

Highly Confidential No No

Proprietary Yes No

Internal Use Only Yes Yes

Public Yes Yes

Page 12: Mobile Security

Employed Owned Devices

Page 13: Mobile Security

Why do people BTOD?

• Devices became cheaper and powerful

• The “Generation Y”

• Always online everywhere!

Page 14: Mobile Security

First Question?

• Are you ready to accept personal devices on your network?

• It’s a question of ... risk!

• Examples:

• Data loss

• Network intrusion

• Data ex-filtration

Page 15: Mobile Security

“MDM”?

• Do you need a MDM solution? (Mobile Device Management)

• Can you trust $VENDORS?

• Microsoft Exchange include ActiveSync for free

• Most security $VENDORS propose (basic) tools to handle mobile devices

Page 16: Mobile Security

Minimum Requirements

• Automatic lock + password

• No jailbroken devices

• Remote wipe

• Backups (who’s responsible?)

Page 17: Mobile Security

Risks Inherent InMobile Devices

Page 18: Mobile Security

Personal Hotspots

• Tethering allows mobile devices to be used as hotspots

• Corporate devices (laptops) could bypass Internet access controls

• Risks of rogue routers (if IP-forwarding is enabled

Page 19: Mobile Security

Rogue App Stores

• Mobile devices without apps is less useful

• Owners tend to install any apps

• Some apps may require much more rights than required

• People trust Apps stores and developers

• Developers must write good code

Page 20: Mobile Security

QR Codes

Page 21: Mobile Security

Geolocalization

Page 22: Mobile Security

NFC

Page 23: Mobile Security

Home & Cars

Page 24: Mobile Security

Mobile Application Development

Page 25: Mobile Security

OWASP Mobile Security Project

• Mobile testing guide

• Secure mobile development guide

• Top-10 mobile controls and design principles

https://www.owasp.org/index.php/OWASP_Mobile_Security_Project

Page 26: Mobile Security

Lack of/Bad Encryption

• Developers re-invent the wheel: do not write a new encryption algorithm

• Encrypt everything (data at rest, data in move)

Page 27: Mobile Security

Local VS. Remote Storage

Pros Cons

Local No network costsSpeed

Risk of lossOutdated

CentralAlways updatedNo risk of loss

Data network ($)Speed

Page 28: Mobile Security

Geolocalization

• Again! But this time for good purposes

• Do not allow some actions or apps (ex: opening a wallet) if GPS data shows the phone outside Europe

• Combine with passwords for stronger authentication/authorization

Page 29: Mobile Security

Enterprise Appstores

• Goal: Distribute, secure and manage mobile apps through your own company branded appstore.

• Application available in the appstore have been approved by a strong validation process.