canmove, Confirmed users
1,220
edits
SecurityEngineering: Difference between revisions
Added "what we work on" section.
Ptheriault (talk | contribs) |
Ptheriault (talk | contribs) (Added "what we work on" section.) |
||
| Line 21: | Line 21: | ||
For more details, check out our [[SecurityEngineering/Strategy|strategy]]. | For more details, check out our [[SecurityEngineering/Strategy|strategy]]. | ||
==What we work on== | |||
The core security guarantee of the web is that it’s safe to browse. You can run a web browser and connect to any web server on the planet, and whatever that server sends you, it won’t be able to harm you. | |||
Delivering on this promise requires many layers of assurance: | |||
That the browser itself is safe to run -- that no malicious code has been introduced, and that we find and fix vulnerabilities before they can be exploited. | |||
That the browser is protecting web content as it’s delivered over the network. | |||
That that web content is forced to play by our rules, including assuring that privacy-sensitive actions that web pages take are gated on a user’s permission. | |||
That we’re providing a user experience that helps people understand the risks and how they can stay safe. | |||
For more details see our [[Security/Roadmap|security roadmap]]. | |||
==Major Efforts== | ==Major Efforts== | ||