As members of the group will be aware, last month GoDaddy filed an incident report concerning a problem with their domain validation system.
Domain validation is the most important task a CA can undertake, any any flaws in it are serious. This is why the CAB Forum has been working for some time on carefully documenting best practice in domain validation, and passed ballot 169 to incorporate them into the Baseline Requirements. The problem experienced by GoDaddy is one explicitly foreseen by the drafters of those best-practice validation methods. That is why, despite some IPR-related tangles, Mozilla will be requiring in its next CA Communication that all CAs move to using only those documented methods in a fairly short timeframe, regardless of what the BRs say. CAs may wish to not wait for that communication to arrive before starting to adapt their systems. We note that GoDaddy's response to this issue was delayed because it was not submitted through their expected channels. We will be working in the CAB Forum to get the CAB Forum to host a master list of CA security contacts, open both to CAs who are and are not members of the Forum, to try and reduce the likelihood of this happening in future. We asked GoDaddy for a list of domains where they revoked the cert because they could not re-do the validation, and compared them to the Alexa top 1M domains. There were no hits in the top 10,000, and only 15 in the top 100,000. As attackers tend to target popular domains, we feel it is _unlikely_ that any certs ended up in the wrong hands as a result of this problem. So we do not plan to add any of the 8951 certs to OneCRL. Here is our proposed remediation plan for GoDaddy. 1) As with all CAs, update all their domain validation code to use one of the 10 approved methods; 2) Implement comprehensive automated testing for their domain validation code for all issuance systems; 3) Make sure those tests automatically run when any change is made to the code, before deployment, such that deployment is gated on a pass; 4) Get a statement from their auditors that these tests have been created and positioned correctly in the deployment workflow. All steps to be completed within 3 months. Comments on this plan are welcome, including from GoDaddy. Gerv _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy

