[owasp-intrinsic-security] Microsoft Web Sandbox

Robert Hansen robert at sectheory.com
Wed Jan 28 23:57:46 EST 2009

Not to speak on behalf of MS on this one but the whole point of this project is to test the practicality of transporting the logic into a future version of the browser.  I talked with the head developer for this project (also one of the head devs for the original versions of all the major scripting versions within IE - that's no coincidence).  He's a smart dude.  This isn't at all about Silverlight or mashups, there's a much bigger picture here - think content restrictions.

**sent from cell phone**

Robert Hansen, CISSP
CEO -- SecTheory LLC
Cell: (530) 521-2542
FAX: (512) 628-6299

-----Original Message-----
From: Arshan Dabirsiaghi <arshan.dabirsiaghi at aspectsecurity.com>
Sent: Wednesday, January 28, 2009 8:13 PM
To: me at alexsmolen.com <me at alexsmolen.com>; owasp-intrinsic-security at lists.owasp.org <owasp-intrinsic-security at lists.owasp.org>
Subject: Re: [owasp-intrinsic-security] Microsoft Web Sandbox

I think this is a cool but wrong approach. I think we need to build a sandbox policy for JavaScript and anything else is a hack, frankly. Something standardized by ECMA.

Does anyone think a Silverlight plugin is going to solve mashup security? Not to pooh pooh this, I'm sure this research is generating a lot of awesome information, but we need a comprehensive solution.


From: owasp-intrinsic-security-bounces at lists.owasp.org on behalf of Alex Smolen
Sent: Wed 1/28/2009 7:57 PM
To: owasp-intrinsic-security at lists.owasp.org
Subject: [owasp-intrinsic-security] Microsoft Web Sandbox

Did you all see this?


It's an attempt to add a security layer onto the web platform and support mashups. It looks like it's driven through Silverlight.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/owasp-intrinsic-security/attachments/20090128/134d6307/attachment.html 

More information about the owasp-intrinsic-security mailing list