Confirmed users
491
edits
WebAppSec/Security Review Request: Difference between revisions
Jump to navigation
Jump to search
WebAppSec/Security Review Request (view source)
Revision as of 17:53, 29 September 2010
, 29 September 2010→Questions to Address within Request Body
| Line 20: | Line 20: | ||
#What is the worst case scenario that could happen with this system, data or connected systems? (This is used to help understand the criticality of this server.) | #What is the worst case scenario that could happen with this system, data or connected systems? (This is used to help understand the criticality of this server.) | ||
#This review will be scheduled amongst other requested reviews. What is the urgency or needed completion date of this review?<br> | #This review will be scheduled amongst other requested reviews. What is the urgency or needed completion date of this review?<br> | ||
== Additional Comments== | |||
* Standard lead time on security review requests is minimum 4-6 weeks | |||
* Once the review is started it takes 1-2 weeks to complete | |||
* Critical reviews can be expedited. Please contact us directly as soon as possible | |||
* Using standard frameworks such as django will decrease the security review time | |||
* Also reference the [https://wiki.mozilla.org/WebAppSec/Secure_Coding_Guidelines secure coding guidelines] to self evaluate and eliminate security issues prior to the security review | |||