IdenTrust request to enable EV for Identrust Commercial Root CA 1 was reviewed and closed

This case was an IdenTrust request to enable EV treatment for the "IdenTrust Commercial Root CA 1" root certificate. The request was opened by IdenTrust after it attached EV checker results and audit materials, and Mozilla asked for a CA information verification review and a BR self-assessment. During review, Mozilla raised questions about the CA hierarchy, audit scope, CPS language, and whether the Booz Allen Hamilton BA CA 01 intermediate was properly covered. IdenTrust provided clarifications, updated its CPS, and supplied additional audit statements and self-assessment attachments. In public discussion, Wayne Thayer noted remaining concerns, including a liability-limit issue and a reported .INT domain certificate in bug 1500593, and recommended denial. Mozilla then closed the request to enable EV treatment and stated that IdenTrust could re-apply with a new request.

1. 2017-02-14 IdenTrust requested EV treatment for the Identrust Commercial Root CA 1 root certificate.
2. 2018-04-06 Mozilla moved the request into detailed CP/CPS review.
3. 2018-09-19 Public discussion began on the EV-enablement request.
4. 2018-11-27 Mozilla closed the request to enable EV treatment for the root certificate.

1. 2017-02-14 IdenTrust Services, LLC — IdenTrust opened the bug, attached EV checker test results and an EV SSL audit report, and pointed to the original inclusion request and CP/CPS URLs.
2. 2017-03-21 Mozilla representative — Aaron requested responses to Mozilla's recommended practices and problematic practices questions.
3. 2017-04-18 Mozilla representative — Aaron asked IdenTrust to complete a BR self-assessment and attach it to the bug.
4. 2017-12-28 IdenTrust Services, LLC — IdenTrust attached a self-assessment for the IdenTrust Commercial Root CA A1 to resume SSL/TLS EV certificates.
5. 2018-03-26 Mozilla representative — Kathleen Wilson attached a status document and asked for clarification on the CA hierarchy, cross-certification, and delegated third parties.
6. 2018-04-02 IdenTrust Services, LLC — IdenTrust said it would review the feedback and provide the required clarifications.
7. 2018-04-06 Mozilla representative — Kathleen Wilson said the request was ready for the Detailed CP/CPS Review phase and assigned it to Wayne.
8. 2018-07-19 Fastly representative — Wayne Thayer raised questions about prior audit statements, CPS domain validation language, and EV audit scope for the Booz Allen Hamilton BA CA 01 intermediate.
9. 2018-08-03 IdenTrust Services, LLC — IdenTrust said it would review and respond, then provided prior audit reports and said it would update the CPS.
10. 2018-09-15 Fastly representative — Wayne asked for the CPS link and for 2013-2014 audit statements because the root was created in January 2014.
11. 2018-09-17 IdenTrust Services, LLC — IdenTrust provided the CPS link and said the 2013-2014 WebTrust audit reports had been added.
12. 2018-09-19 Fastly representative — Wayne started public discussion and listed his assessment, including concerns about audit scope, CPS language, and several compliance issues.
13. 2018-09-25 IdenTrust Services, LLC — IdenTrust replied to Wayne's comments and agreed to update CPS language on domain validation, CPS update timing, and a typo.
14. 2018-10-31 Fastly representative — Wayne said most CPS concerns were addressed in the newer version but asked for an explanation of the section 9.8 liability language.
15. 2018-11-02 Fastly representative — Wayne recommended denying the request due to bug 1500593 and linked the public discussion.
16. 2018-11-16 IdenTrust Services, LLC — IdenTrust proposed revised liability wording for CP section 9.8.
17. 2018-11-27 Mozilla representative — Kathleen Wilson closed the request and said IdenTrust could re-apply by creating a new request.