Site Sponsor:

mcafee_logo.gif
line

Now Available:

Featured Resource:

line

Newsletter

Email Address:


line

Ask the Expert

Have a question for our resident expert? Email your questions to Dan or post a comment to the blog.

« Web Application Firewalls Complement - Don't Replace - Secure Coding | Main | Secure Data, Not Just Devices »

Smartphone Security Threatened by J2ME and Application Challenges

Currently, 80% of smartphones use the Java 2 Micro Edition (J2ME) platform so the security of this platform should be of concern to enterprise network managers and security professionals. Smartphones, like Blackberries before them, will creep into widespread use from the grassroots, not from controlled IT initiatives. If it hasn't happend already, soon some executive will want access to the enterprise network from his or her smartphone, IT will have to make it happen, and a whole lot of security issues will come with it. For this reason, a study of smartphone and J2ME application security from the University of Bergen is worth a look. (Published in IEEE Computer, subscription or fee required to access the paper).

The authors point out several challenges to securing J2ME applications:

1. The quality of J2ME implementations vary and developer's time can be consumed with adapting code to different J2ME platforms.

2. J2ME devices do not behave consistently so broad testing is required.

3. Smartphone software is not patched frequently enough leading to what the authors call "permanent bugs."

4. Defensive programming is required to deal with resource limitations.

5. The MIDP 2.0 security framework, used for securing applications and communications, have critical functions that are optional and may not function on some devices.

6. Signed applications did not always install correctly in the smartphones tested by the researchers, requiring the use of unsigned devices.

7. Too much trust is placed in client software that can be used to spread malware and attack servers.

There is more in the article including a discussion of how the Security and Trust services API can help improve the security profile of smartphones. I'd recommend it to anyone responsible for a network that might have smartphone clients.

None of this should be read as bashing smartphones or J2ME. These devices are early in the lifecycle and getting security right takes time. The issue is managing expectations about what will and will not be allowed to access the network, what kinds of policies need to be in place before smartphones can access network resources, and how control over personal devices that access the network will have to be shared between the owner of the device and the owner of the network. That last one might be a bitter pill for some to swallow.

TrackBack

TrackBack URL for this entry:
http://www.realtime-websecurity.com/type/mt-tb.cgi/222

Post a comment

(All comments are approved by site leader before appearing here. Thanks for commenting!)

line

Dan Sullivan's Bio:

Dan Sullivan is a systems architect with 20 years of IT experience that includes engagements in enterprise security, application design, and systems architecture. His experience includes a broad range of industries, including financial services, manufacturing, government, retail, gas and oil production, power generation, and education. Dan’s security-related project work has ranged from requirements analysis for enterprise information security to designing and implementing security for database applications and enterprise portals. Dan has written about information security and other enterprise information management topics for Business Security Advisor, DM Review, Intelligent Enterprise, and E-Business Advisor. You can contact Dan at: dan_sullivan@realtimepublishers.net