Silverlight Security Cheat Sheet

Over the last week we took a look at the new Silverlight security model.  When you're writing a Silverlight application though, there's a lot of information there that you may not want to wade through to get yourself unblocked.  Here's a quick cheat sheet highlighting the important points that you'll need to know when working with the Silverlight security model:

• All applications written for Silverlight are security transparent.  This means that they cannot: [details]
  • Contain unverifiable code
  • Call native code directly
• Silverlight applications can access public methods exposed by platform assemblies which are either: [details]
  • Security transparent (neither the defining type nor the method has any security attributes)
  • Security safe critical (the method has a SecuritySafeCriticalAttribute)
• Silverlight applications may contain types which derive from: [details]
  • Other types defined in the application
  • Unsealed, public, security transparent types and interfaces defined by the platform
• Silverlight applications may contain types which override virtual methods and implements interface methods which are: [details]
  • Defined in the application itself
  • Defined by the platform and are transparent or safe critical

Comments

• Anonymous
  May 15, 2007
  Shawn over on the MSDN blogs has put up a series of posts on the Silverlight security model. The...

• Anonymous
  May 15, 2007
  Shawnfa over at MSDN Blogs has a series of posts on the Silverlight Security model. Anyone interested

• Anonymous
  May 20, 2007
  Another week has shot by. Didn't have any time to look at Silverlight although I have managed to download

• Anonymous
  October 13, 2009
  That seems to be interesting and useful, i need to secure but i don't ever know such a solution is possible, thanks for speaking about it ! Very helpful for me !

• Anonymous
  January 21, 2010
  The comment has been removed