On Wednesday, March 29, 2017 at 2:00:05 PM UTC-7, Jeremy Rowley wrote: > ... > An extension on this could be to have CAs annually file an updated mapping > with their WebTrust audit. That way it's a reminder that the CA needs to > notify Mozilla of changes in their process and keeps the CAs thinking about > updating practices to stay in-line with the baseline requirements. Plus, a > practice like that would provide better notice to the public on CA policy > changes and how CAs are responding to new threats. >
Oh! I like that idea! The timing is good, as we are just now switching over to the new annual process: https://wiki.mozilla.org/CA:CommonCADatabase#How_To_Provide_Annual_Updates I could also say something about it in the CA Communication we are getting ready to send. Does anyone see a reason why we should *not* require a new BR-self-assessment annually from every CA with the Websites trust bit enabled? I think CAs could just attach it to their original root inclusion bug each year. Kathleen _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy

