Confirmed users, Administrators
5,526
edits
CA/Responding To An Incident: Difference between revisions
m
Updated due to MDSP migration
m (Added link to a good example of an incident report) |
m (Updated due to MDSP migration) |
||
| Line 89: | Line 89: | ||
= Keeping Us Informed = | = Keeping Us Informed = | ||
Once the report is posted, you should respond promptly to questions that are asked, and in no circumstances should a question linger without a response for more than one week, even if the response is only to acknowledge the question and provide a later date when an answer will be delivered. You should also provide updates at least every week giving your progress, and confirm when the remediation steps have been completed - unless Mozilla representatives agree to a different schedule by setting a “Next Update” date in the “Whiteboard” field of the bug. Such updates should be posted to the | Once the report is posted, you should respond promptly to questions that are asked, and in no circumstances should a question linger without a response for more than one week, even if the response is only to acknowledge the question and provide a later date when an answer will be delivered. You should also provide updates at least every week giving your progress, and confirm when the remediation steps have been completed - unless Mozilla representatives agree to a different schedule by setting a “Next Update” date in the “Whiteboard” field of the bug. Such updates should be posted to the [https://groups.google.com/a/mozilla.org/g/dev-security-policy MDSP mailing list], if there is one, and the Bugzilla bug. The bug will be closed when remediation is completed. | ||
= Examples of Good Practice = | = Examples of Good Practice = | ||