canmove, Confirmed users
1,220
edits
Security/B2G/PermissionReview: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Ptheriault (talk | contribs) (Created page with "The basic problem is that web content is completely untrustworthy, so our APIs are too dangerous to expose to such content. APIs can need to be made safer through a combinatio...") |
Ptheriault (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
The basic problem is that web content is completely untrustworthy, so our APIs are too dangerous to expose to such content. APIs can need to be made safer through a combination of: | The basic problem is that web content is completely untrustworthy, so our APIs are too dangerous to expose to such content. APIs can need to be made safer through a combination of: | ||
* only exposing safe parts of APIs | |||
* adding mitigating controls to APIs | |||
* creating more specific APIs to safely solve use cases | |||
* creating more sophisticated security UI | |||
* mandating adoption of existing web security controls (TLS, CSP etc) | |||
== General Security Requirements == | == General Security Requirements == | ||