Closed Bug 1773376 Opened 3 years ago Closed 3 years ago

Extend Root Inclusion Cases to Chrome

Categories

(CA Program :: Common CA Database, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kathleen.a.wilson, Assigned: poonam)

References

Details

https://www.chromium.org/Home/chromium-security/root-ca-policy/ says

The Chrome Root Program and corresponding Root Store will process applications and requests for changes through CCADB. This integration is ongoing, and is expected to be completed before September 2022. Before accepting applications, this policy will be updated with the steps for applying or updating existing included certificates, and CA operators will be contacted with more information using a CCADB message.

Much of the application process and information requested will be familiar to CA operators that participate in other public Root Programs; for example CA owner and operating organization details, and artifacts related to the CA and its operator’s policies, practices, and audit history. The Chrome Root Program application will require additional information, such as (but not limited to):

  • an architectural overview of the applicant PKI.
  • the dates and related audit artifacts pertaining to CA key material generation.
  • the collection of domain validation methods used during TLS certificate issuance.
  • the collection of a self-assessment concerning compliance with this policy and the Baseline Requirements.
Depends on: 1737866

Thank you, Kathleen!

We should be reaching out to you and Poonam with the specifics in a few weeks.

Assignee: nobody → poonam
Status: NEW → ASSIGNED
Whiteboard: [ccadb-roadmap] 2022-Q3 → [ccadb-roadmap] 2022-Q4
Product: NSS → CA Program

Went live on December 22.

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Whiteboard: [ccadb-roadmap] 2022-Q4
You need to log in before you can comment on or make changes to this bug.