Security/Features/Roadmap: Difference between revisions

Security/Features/Roadmap (view source)

Revision as of 18:37, 30 August 2011

1,978 bytes removed , 30 August 2011

m

Redirected page to Security/Roadmap

Sidstamm

canmove, Confirmed users

1,537

edits

@@ Line 1: / Line 1: @@
-<section begin="summary" />{{RoadmapSummary
+#REDIRECT [[Security/Roadmap]]
-|icon=tbd.png|pagelocation=Security/Features/Roadmap
-|pagetitle=Security Features Roadmap
-|owner=[mailto:lucas@mozilla.com Lucas Adamski]
-|updated=May 2011
-|status=Draft
-|description=
-}}<section end="summary" />
-{{draft}}
-<br>
-= Vision  =
-Security is often seen as a fundamentally defensive discipline, where the goal is to minimize risk even if at the expense of functionality or usability.  In reality, security does not have to be a zero sum game, and creatively defined solutions can yield major benefits in security, usability AND functionality.  A well implemented password manager is an example of such a feature.
-Users care deeply about security.  It is one of the most important browser features users care about, behind convenience and roughly equal with speed.  They also want Mozilla to take an active role in keeping them secure, as we are seen as a trustworthy authority on the subject.
-= Overview  =
-Security features at Mozilla span a wide variety of products and purposes, but they could be perhaps separated into two main categories:
-*'''Risk reduction''':&nbsp;Features intended to reduce risk to users directly, often behind the covers by reducing attack surface, strengthening defenses and providing defense in depth.&nbsp; Often behind the scenes, and ideally invisible to users and web developers alike.<br>
-*'''Security functionality''':&nbsp;Meant to establish deploy new tools and mechnisms for developers, users and web administrators to protect themselves.&nbsp; These are high visibility changes requiring active participation by at least one of the participants.&nbsp; Potentially higher risk and more effort than risk reduction features, but conversely carry a much higher potential for impact.<br>
-We need to stay proactive in protecting our users directly, but also develop effective and usable mechanisms to help web developers and administrators protect users in scenarios where we cannot do so directly.
-= Roadmap  =