(In reply to Kathleen Wilson from comment #1)
Bug #1339292 requested EV treatment for this "IdenTrust Commercial Root CA 1" root certificate, but the request was denied due to Bug #1500593 during the public discussion:
Then I closed the bug/request with:
"This CA may re-apply for EV treatment for this root or for a new root by creating a new request"
Please explain the reason for re-applying for EV treatment for the same root.
IdenTrust is applying for extending our CA root “IdenTrust Commercial Root CA 1” to include EV SSL recognition with Mozilla browsers. We had previously submitted such request for the same root on March 2017, which was rejected on November 2018 with the conclusion: “This CA may re-apply for EV treatment for this root or for a new root by creating a new request”. The rejection of the previous application was due to failure by IdenTrust to disclose and remediate mis-issuance of 3 SSL certificates in February 2018 in a timely manner (https://groups.google.com/forum/#!msg/mozilla.dev.security.policy/fTeHAGGTBqg/ikgMfJeiAgAJ and Bug #1500593).
We are reapplying because we have successfully remediated the behavior that prompted denial of the previous application. Since February 2018, we have disclosed and remediated issues that demonstrates our commitment to disclosure and remediation in line with expectations of the CA/B Forum and Mozilla community. In addition, we have established improved controls including the performance of periodic internal audits to ensure CA/B Forum and Mozilla Root policy compliance. Examples of these are: (i) Bug #1526099; and Bug#1542082. It should be noted that all reported items will also be included in our annual audit findings scheduled to be published in September 2019.