Mobile application securitry risks ISACA Silicon Valley 2012
The document discusses mobile app security risks, identifying the top three concerns as side channel data leakage, insecure transport/server controls, and insecure data storage. It outlines various countermeasures for risk management and highlights the necessity of mobile information management (MIM), mobile application management (MAM), and mobile device management (MDM) in addressing security challenges. Expert speakers Kartik Trivedi and Lenin Aboagye emphasize the importance of secure practices in mobile application development and management.
More Related Content
Similar to Mobile application securitry risks ISACA Silicon Valley 2012
![Vibe Coding vs. Spec-Driven Development [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/vibecodingvsspecdrivendevelopment-251209105622-43f455e7-thumbnail.jpg?width=640&height=640&fit=bounds)
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
Mobile application securitry risks ISACA Silicon Valley 2012
- 1. Mobile Apps SecurityRisk Assessment Kartik Trivedi / Lenin Aboagye
- 2. For the Demo… pleasedownload and install the following apps on your mobile device and create an account 2
- 3. Who are we? •Kartik Trivedi – Co-founder of Symosis – Author / Speaker / Interviews - Forbes, Security Focus, Tech world, Security News, etc – Golfer (Advanced Amateur? ) • Lenin Aboagye – Security Architect Apollo group – Cloud / Mobile security expert – Media & Television, Education, Health, Real Estate and Energy industries experience 3
- 4. Agenda Introduction Growth / Revenue Security Concerns Mobile Apps Top 3 Risks Countermeasures & Risk Management 4
- 5. There is anApp for that! 5
- 6. There is anApp for that! • Pay bills • Small Business Payroll • File income taxes • Pay invoice • Pay property tax • Location based check in • Scan & Shop • Personal finance • Deposit checks • Investments & 401k • Transfer money • Health & Fitness • Store medical records • Productivity • Refill prescription • Facebook / twitter • Manage health information • Place bets on sports • Remember your meds • Utilities • Book flight / hotel • Store passwords • Medscape / pharmacopia • Document storage 6
- 7.
- 8. 53% of Fortune500 companies have mobile apps 8
- 9. Business Case forMobile Presence • Networking / communication - unprecedented level of connectivity between employees, vendors, and/or customers • Instant Feedback - sharing information through this medium allows businesses to get immediate feedback on products and services from customers. • Marketing - SMS (text) messaging, mobile websites, mobile applications, banner ads, QR codes, IVR messaging and more. • Commerce – Mobile ticketing, vouchers, coupons, loyalty cards, content purchase, delivery, location based services, Information services, mobile banking, mobile brokerage, mobile purchase 9
- 10. Security Concerns • Side Channel Data Leakage • Activity monitoring and data retrieval • Insufficient Transport Layer Protection • Unauthorized dialing, SMS, and payments • Weak Server Side Controls • Unauthorized network connectivity (data exfiltration or command & control) • Insecure Data Storage • UI (unique identifier) impersonation • Client Side Injection • System modification (rootkit, APN proxy • Poor Authorization and configuration) Authentication • Mobile Malware • Improper Session Handling • Criminals Target and Infect App Stores • Security Decisions Via Untrusted Inputs • Social-Engineering • Geolocation compromise • Broken Cryptography • Security Regulatory Compliance • Sensitive Information Disclosure • Device Risk • Hardcoded password/keys • BYOD / MDM • Privacy compliance • Application management • Identity exposure • Installation of un-verified / unsigned 3rd party apps 10
- 11. Agenda Introduction Growth / Revenue Security Concerns Mobile Apps Top 3 Risks Side Channel Leakage Insecure Transport / Server Controls Insecure Data Storage Countermeasures & Risk Management 11
- 12. Side Channel DataLeakage Data leakage via platform defaults, use of third party libraries, logging, etc • SnapShot (ie- iOS backgrounding) • Plist files Sometimes result of programmatic flaws
- 13. Demo 13
- 14.
- 15.
- 16. Agenda Mobile Platform Risks MobileApps Top 3 Risks Side Channel Leakage Insecure Transport / Server Controls Insecure Data Storage Countermeasures & Risk Management 16
- 17. Insecure Transport/Server Controls Failingto encrypt sensitive network traffic consisting of sensitive data Insecure server controls - web, application and backend API - can lead to security compromise
- 18. Demo 18
- 20.
- 21. TOC Mobile Platform Risks MobileApps Top 3 Risks Side Channel Leakage Insecure Transport / Server Controls Insecure Data Storage Countermeasures & Risk Management 21
- 22. Insecure Data Storage Locallystored data both on native and browser based apps that includes • SQLite / Cache files • Keychain – Is this really secure? 22
- 23. Demo 23
- 24.
- 25. Risk & Impact:High Sensitive Data exposure • Username & password • PII, SSN, Health Information • Device ID, Application configuration • Account Number, Credit Card, Financial Information Loss of Data Confidentiality & Integrity Data Tempering Man-in-the-Middle (MITM attack) Impersonation Unauthorized access to application data or functionality Privacy Violations / reputation damage
- 26. Agenda Introduction Mobile Apps Top3 Risks Insecure Data Storage Insecure Transport / Server Controls Side Channel Leakage Countermeasures & Risk Management Tactical Strategic 26
- 27. Secure Programming /Education Disable Cache - Set the autocorrectionType property to UITextAutocorrectionNo for UITestField Disable Snapshot – Use applicationWillResignActive delegate method Disable Logs – Disable NSLog and NSAssert Disable Insecure HTTP - Use NSURLConnection along with canAuthenticateAgainstProtectionSpace 27
- 28. Encrypt Data Data ProtectionAPI - set the NSFileProtectionKey on an existing file Keychain – Apple recommends storing Sensitive data like passwords and keys in the Keychain CCCrypt - provides access to AES, DES, 3DES SQLCipher (IOS & Android) - transparent 256-bit AES encryption of database files 28
- 29. Secure Design /Architecture • Do not trust the client. Store sensitive data on the server • Perform server side data validation and canonicalization • Only collect and disclose data which is required for business use of the application • Define and deploy secure configuration • Establish common set of security requirements • Perform periodic security scans and audits • Protect sensitive data using HTTPS & SSL • Do not log credentials, PII and other sensitive data • Review all third party libraries before use 29
- 30. Agenda Mobile Platform Risks MobileApps Top 3 Risks Security Controls & Risk Management Tactical Strategic 30
- 31. Mobile Strategy &Challenges • The are 3 major components of a mobile strategy that most organizations have to apply – Mobile Information Management(MIM) – Mobile Application Management(MAM) – Mobile Device Management(MDM) 31
- 32. MIM • MIM refersto cloud-based services that syncs files and documents across different devices • MIM allows for sharing data of varying security classification across devices with varying degrees of trust • MIM intersects Cloud and Mobile Security • Public MIM services are Dropbox, Box, Microsoft SkyDrive, GoogleDrive • Corporate MIM solutions include Monodesk, WatchDox, Citrix ShareFile, Vmware Octopus • NFC technologies could be classified as MIM 32
- 33. Security Challenges -MIM •BYOD in corporate environments • Potential synching of corporate data across both corporate and non-corporate issued endpoints • Sensitive bi-directional data leakage from user’s private and personal data into corporate and vice-versa • Access and Identity Management • Data classification , identification and protection • Difficult to apply and enforce any corporate security configurations across mobile devices • No existing virtual segregation capabilities for corporate/user components to allow for different security policies to be applied based on risk 33
- 34. MDM • MDM involvesdownloading software that allows users/organizations to lock down • MDM allows controls like monitoring, encryption, policy enforcement , remote wiping etc.. • Addresses security at the device level as opposed to the application level • Especially challenging in BYOD era • One policy regardless of varying classification levels of applications on device – Policies like remote wiping could adversely affect user personal /private data 34
- 35. Security Issues-MDM • Addressessecurity of device only • Has little insight into security health of applications • Treats all applications and all data at the same classification level • Difficulties in adoption in corporate environments that allows BYOD • Does not affect or improve the security of applications 35
- 36. MAM • MAM solutionsallow users and organizations to control the security of specific applications that are deployed on mobile endpoints • MAM can allow an organization to deliver applications like secure email, calendar, expense reporting • Allows security policies to be applied exclusively on specific applications based on their security classification – Encryption, remote wipe, remote application kill etc.. 36
- 37. Security Issues-MAM • MAMseems to have the answer for MIM’s security challenges • MAM should solve the BYOD challenges since it allows for security policies to be applied to corporate applications and their data and allows for non-visibility into personal user information • MAM solutions have several challenges: – Rewrite secure versions of vendor applications(functionality challenges) – Allow vendors plug into their security platform – Currently works only an a few apps – Create a wrapper around vendor applications (most vendors will not provide original packaged files to wrap with MAM tools) 37
- 38. Mobile Security Convergence MDM All mobile security strategies converge on these MIM approaches MAM Mobile Application Security 38
- 39. Thanks for listening… kartik@symosis.com/ Lenin.Aboagye@apollogrp.edu Email info@symosis.com for a free seat to the Mobile Apps Top 10 Security Risk Training Course 39
Editor's Notes
- #5 Please make a selection by clicking on the
- #6 Mobile App Growth
- #8 How consumers are evolving and changing their mobile behaviorhttp://www.pwc.com/us/en/industry/entertainment-media/publications/assets/consumer-research-series-smartphones.pdf
- #9 Mobile AppGrowth - http://www.appconomist.com/2011/08/01/fortune-500-apps-a-50-update/TransactionMarketingSMS / TXT MarketingNews AlertsTake a picture QR codes
- #10 http://www.strategicgrowthconcepts.com/growth/increase-productivity--profitability.html
- #12 Please make a selection by clicking on the
- #13 Side channel data leakage applies to data leakage via platform defaults, use of third party libraries, logging, etc. In order to provide the visual iOS has been proven to capture and store snapshots.This occurs when a device suspends (rather than terminates), when either the home button is pressed, or a phone call or other event temporarily suspends the applicationPlist is a structured text file that contains essential configuration information for a bundled executable
- #15 A PLIST (Property List) file is an XML file that holds application properties. Some applications store sensitive information in the plist files including authentication credentials, PIN and oAUTH tokensPlist files can be found in several location in the application directory . An example location and plist file content storing sensitive authentication credentials are shown on the screen
- #16 http://garethwright.com/blog/facebook-mobile-security-hole-allows-identity-theft#
- #17 Please make a selection by clicking on the
- #18 Web sites and servers sometimes have improperly configured SSL certificates. This causes warning messages which are often ignored by the users. This results in users Phishing attacks where users end up providing personal information and private data to malicious websites that look like legitimate applicationsApplications that fall back or can be forced out of an encrypting mode can also be abused by attackers resulting in insecure communication. This is common on sites that operate on both HTTP and HTTPS services, or by the implementation of older versions of SSL on the web server that are vulnerable to downgrade attacks.
- #20 In 2011, it was discovered that Android devices transmitted data and AuthToken session cookie via insecure HTTP. AuthToken is not bound to any session or device and thus would allow an adversary to access any personal data which is made available through the service API. This includes Google calendar, picasa and contact information for that user. For more Reference: http://www.uni-ulm.de/in/mi/mitarbeiter/koenings/catching-authtokens.htmlThe issue here is the use of insecure HTTP channel which allows network eavesdropping of the authToken and user data
- #21 http://www.theverge.com/2012/2/14/2798008/ios-apps-and-the-address-book-what-you-need-to-know
- #22 Please make a selection by clicking on the
- #23 InsecureData Storage applies to the locally stored data by the mobile applications. There are two types of mobiles apps - native apps and browser based apps. Native apps are apps that is installed in the handset, processes data locally and may connect to the internet for updates or sending user specific information to the server. Example: Gaming apps, News apps, etc. Browser based apps are apps that are accessible via mobile browser. This vulnerability applies to both categories of apps.Most apps stores user specific information on mobile devices. This data may be stored in clear text and may includeUsername and passwordPII, SSN, Health InformationDevice ID, Application configurationAccount Number, Credit Card, Financial Information
- #25 http://blog.agilebits.com/2012/04/06/oauth-dropbox-and-your-1password-data/
- #26 Insecure transport layer protection is considered a high risk security vulnerabilityThe impact could includeLoss of Data Confidentiality & Integrity when sensitive information is revealed to the attackerData Tampering when attacker modifies application traffic and force user accept itMan-in-the-Middle (MITM attack) if an attacker diverts all traffic through an insecure channelImpersonation if the attacker hijacks user account
- #27 Please make a selection by clicking on the
- #28 Disable the auto-correct feature for any sensitive information, not just for password fields. Since the keyboard caches sensitive information, it may be recoverable. For UITextField, look into setting the autocorrectionType property to UITextAutocorrectionNo to disable caching. Set UITextField to OFF to prevent caching altogetherAdd an enterprise policy to clear the keyboard dictionary at regular intervals. This can be done by the end user by simply going to the Settings application, General > Reset > Reset Keyboard Dictionary
- #31 Please make a selection by clicking on the