Building Secure Windows Phone 8 Apps – The Platform

April 7, 2013 — 2 Comments

Application security for developers is a very large topic, but Windows Phone does make adding security to an app easier for developers and also to help keep an end users data safe. With an article recently published on Building Secure Windows Store Apps, pretty much all of those concepts can be used on Windows Phone 8. I thought it fitting to describe some of the security features available on Windows Phone that developers get for free and what is available to use within their apps.

Trusted Boot & Code Signing

Secure_BootWindows Phone 8 is based on the ARM version of Windows 8 so a lot of the security features available on the desktop come for free on the phone such as Trusted Boot and Code Signing. What are these for? Basically these features help protect the phone boot process and operating system from malware attacks (ie rootkits) by making sure only validated software components execute. The Trusted Boot technology validates Windows Phone firmware images and all boot components have digital signatures that are cryptographically validated. This helps ensure that only authorized code can execute to initialize the device and load the operating system, Windows Phone.

This helps protect the integrity of the phone and also the end user from potential malware.

 

App Platform Security

security110628151442As the Windows Phone platform is pretty well protected with Trusted Boot and Code Signing, there is still the opportunity for other forms of malware that could make its way to the end users phone that could potentially disclose or capture user’s data or even corporate data.  There are a few things Microsoft does to prevent this which developers should be aware of.

  • Chambers – Introduced with Windows Phone 7 security model, you can think of a chamber as your app running within its own sandbox or silo not having any access to other apps chambers. Every app, including Microsoft apps, OEM Apps and Third Party Apps will run in their own chamber and have to declare their capabilities.
  • Capabilities – A chamber will disclose what operating system capabilities an app is required to use to function. A capability can be accessing user location using GPS, camera access, sensor access, and microphone access as well as others.

The following is a list developers should know when developing for Windows Phone

  • If an app attempts to use an operating system capability without declaring it, an exception will be thrown at runtime.
  • If you are building multiple apps, you won’t be able to communicate between the applications or share data between the apps unless you use the cloud
  • If you are building multiple apps and you want to get a device ID using Windows.Phone.System.Analytics.HostInformation.PublisherHostId, this will return a different value in each app.
  • If you are building web apps, Internet Explorer also runs in its own chamber preventing web apps from accessing other app resources or operating system features.

Protecting Your IP

kblockAs developers, we work hard to create our software and want to make sure it’s protected when users start downloading it and using it. Once your app passes certification requirements, the app will be digitally signed on behalf of the developer and made available in the Windows Phone store.

To help protect a developers hard work, a valid license that is issued by the Windows Phone Store must be present on the users phone to be able to run.  So if someone does figure out how to download the app and load it onto their phone, Windows Phone will not allow the app to run since the license is not available.

As a developer this is great as it helps curb someone pirating your app and since all XAP files are encrypted, it helps prevent a lot of casual snooping of your app code files but things to remember are

  1. Obfuscate your code if you are using .NET to make it harder to decompile your app
  2. Use C++ to make it more difficult to hack your app or protect critical pieces of code
  3. Use Windows Phone Enterprise Distribution if it’s an enterprise type application

Links and Resources

Here are a list of resources used for this article which contain more information

What’s Next?

This is not an exhaustive list of the security features available in Windows Phone 8, but this introduction and resources should get you started if you want to learn more about it.

Up next, some of the APIs and techniques to help secure your apps and help your users feel safe when using your apps.

Trackbacks and Pingbacks:

  1. Building Secure Windows Phone 8 Apps – APIs and Techniques | Mark Arteaga - April 9, 2013

    […] your code, they may get access to the password and be able to decrypt the database. With the Windows Phone platform security features put in place, this will be more challenging, but you may still want to not hardcode this password […]

  2. Building Secure Windows Phone 8 Apps – The Platform - Canadian Developer Connection - Site Home - MSDN Blogs - April 10, 2013

    […] This post is cross-posted from Mark Arteaga’s blog. […]

Leave a Reply