Confirmed users
529
edits
Security/FirefoxOperations: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 165: | Line 165: | ||
* [ ] Apply sensible limits to user inputs, see [input validation](https://wiki.mozilla.org/WebAppSec/Secure_Coding_Guidelines#Input_Validation) | * [ ] Apply sensible limits to user inputs, see [input validation](https://wiki.mozilla.org/WebAppSec/Secure_Coding_Guidelines#Input_Validation) | ||
* POST body size should be small (<500kB) unless explicitly needed | * POST body size should be small (<500kB) unless explicitly needed | ||
* [ ] When allowing users to upload or generate content, make sure to host that content on a separate domain (eg. firefoxusercontent.com, etc.). This will prevent malicious content from having access to storage and cookies from the origin. | |||
* Also use this technique to host rich content you can't protect with a CSP, such as metrics reports, wiki pages, etc. | |||
* [ ] When managing permissions, make sure access controls are enforced server-side | * [ ] When managing permissions, make sure access controls are enforced server-side | ||
* [ ] If | * [ ] If an authenticated user accesses protected resource, make sure the pages with those resource arent cached and served up to unauthenticated users (like via a CDN). | ||
* [ ] If handling cryptographic keys, must have a mechanism to handle quarterly key rotations | * [ ] If handling cryptographic keys, must have a mechanism to handle quarterly key rotations | ||
* Keys used to sign sessions don't need a rotation mechanism if destroying all sessions is acceptable in case of emergency. | * Keys used to sign sessions don't need a rotation mechanism if destroying all sessions is acceptable in case of emergency. | ||