The security architecture for your mobile application depends on the requirements for mobile banking application in general. I would start the following investigations
- What are the mobile banking requirements on a mobile device ---> required radio interface for your transaction (wifi is not as secure as cellular) ---> what is needed if you are on wifi? ---> Which security mechanisms are involved for a banking transaction? (investigate IP connectivity requirements up to security requirements on application level - What is supported on Android? (for example there a limitations on WPA2 support in Android SDK in case of Wifi) ---> which protocols are supported for a secure connection? ---> which security framework is available or can be ported ---> in case of slow performance, what is available on native level ---> does it make sense to change the framework/platform code and run certain software as root only? This are only some basic questions which I came up with. But may be it helps to get started. -- Roman Baumgaertner Sr. SW Engineer-OSDC ·T· · ·Mobile· stick together The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Sep 7, 2:12 am, Sudeep Jha <[email protected]> wrote: > Hi all, > Can anybody tell me something about the security architecture > required to build a mobile banking solution in android? > Warm Regards, > Sudeep > > -- > Warm Regards, > Sudeep --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
