Confirmed users
717
edits
SecurityEngineering: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 1: | Line 1: | ||
=Security Engineering= | ==Security Engineering== | ||
Our mission is to design and implement evolutionary and revolutionary features to manifestly improve the privacy and security of all web users, in a Mozilla way that engages the community in our design and implementation decisions. These priorities are reflected in the [[Privacy/Roadmap_2011|Privacy]] and [[Security/Roadmap|Security]] roadmaps | Our mission is to design and implement evolutionary and revolutionary features to manifestly improve the privacy and security of all web users, in a Mozilla way that engages the community in our design and implementation decisions. These priorities are reflected in the [[Privacy/Roadmap_2011|Privacy]] and [[Security/Roadmap|Security]] roadmaps | ||
this team manages, public evangelism and participation in relevant standards bodies to maximize adoption of new privacy & security mechanisms. | this team manages, public evangelism and participation in relevant standards bodies to maximize adoption of new privacy & security mechanisms. | ||
=Who is involved= | ==Who is involved== | ||
Security Engineering is led by Lucas Adamski, who is focused on security features along with Ian Melven and Tanvi Yvas. Sid Stamm is leading the Privacy development efforts, along with Camilo Viecco. | Security Engineering is led by Lucas Adamski, who is focused on security features along with Ian Melven and Tanvi Yvas. Sid Stamm is leading the Privacy development efforts, along with Camilo Viecco. | ||
=Modi Operandi= | ==Modi Operandi== | ||
The Security Engineering team works publicly like other Mozilla engineering teams. | The Security Engineering team works publicly like other Mozilla engineering teams. | ||
| Line 26: | Line 26: | ||
We are not always the best team to implement a given privacy or security feature, so another important role we play is to champion privacy and security features throughout the Mozilla organization. | We are not always the best team to implement a given privacy or security feature, so another important role we play is to champion privacy and security features throughout the Mozilla organization. | ||
=How to participate= | ==How to participate== | ||
We hang out on #security on irc.mozilla.org, and our primary mailing list is mozilla.dev.security. Milestone reviews and other meetings will be announced on mozilla.dev.security. | We hang out on #security on irc.mozilla.org, and our primary mailing list is mozilla.dev.security. Milestone reviews and other meetings will be announced on mozilla.dev.security. | ||
=Security Reviews= | ==Security Reviews== | ||
For information about participating in our security review process, please see [[Security/Reviews|here]] | For information about participating in our security review process, please see [[Security/Reviews|here]] | ||
=Security Bugs= | ==Security Bugs== | ||
If you've found a security bug please see http://www.mozilla.org/security/#For_Developers | If you've found a security bug please see http://www.mozilla.org/security/#For_Developers | ||
For information regarding our security bug bounty, check out http://www.mozilla.org/security/bug-bounty.html | For information regarding our security bug bounty, check out http://www.mozilla.org/security/bug-bounty.html | ||