On 28/09/2017 18:11, Gervase Markham wrote:
On 22/09/17 00:12, Ryan Sleevi wrote:
Based on the number of reports reviewed recently, I suspect we've got
opportunities for improvement, but I'm not quite sure yet what the concrete
suggestions on that should look like. A few thoughts below:
Here's a set of changes which attempt to capture some of what you are
requesting. Further input, from you or others, is welcome.
https://wiki.mozilla.org/index.php?title=CA%2FResponding_To_A_Misissuance&diff=1181405&oldid=1179230
Suggested minor additional improvements to this excellent document:
1. Title should also reflect that this is now about various kinds of
incidents.
2. Opening paragraph should be split in two just before the definition
of "misissuance". A third paragraph should be added with a similar
spirit definition of "Other examples of incidents include ...".
3. In the definition of "misissuance" it may be prudent to add wording
to the effect that "revocation" at the request of the certificate
subject due to events entirely under the the subjects control are
typically not considered "misissuance", just routine revocation work.
4. Under "Follow-Up actions", second bullet, perhaps change "rigorous"
to "frequent/rigorous".
5. Under "Incident Report", item 1, add "internal self-audit" as another
example of discovery. (I think the recent DigiCert reissue incident
might be a good example of that happening).
6. Under "Incident Report", item 3, remove the word "TLS/SSL" to make
the bullet point equally applicable to e-mail certs, OCSP certs etc.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy