CA/Information Checklist

Information checklist for CAs applying for inclusion in Mozilla

In order to support cryptographic applications, such as those that make TLS connections to web and other servers, and those that sign and encrypt/decrypt email, Firefox and other Mozilla-based products contain digital certificates and related metadata for multiple Certification Authorities (CAs). By including the CA certificates and various associated pre-set metadata values Mozilla-based products can recognize as valid the end entity certificates that are issued under such CAs and are associated with, e.g., web servers, and email senders.

Example and Template

The example and template below list the information that must be provided by the CA in their root inclusion or update request as per step 1 of Mozilla's Application Process.

• Example -- This is what it will look like when you create a Root Inclusion Case directly in the CCADB.

Mozilla's process is public-facing, so all information that will be taken under consideration during the root inclusion request must be publicly available and provided by the CA via a Case in the CCADB and in a Bugzilla bug report. (Both must be created as they will reference each other.)

Adding Root Certificates and Creating Root Inclusion Cases

Access the CCADB

If your CA does not yet have access to the CCADB, then you may request access here:

• https://ccadb.org/cas/request-access

Information and instructions for CAs about the CCADB are here:

• https://www.ccadb.org/cas/

Create an "Add/Update Root Request" case

CAs provide information about their CA organization and root certificates by creating an "Add/Update Root Request".

1. Create an "Add/Update Root Request" case in the CCADB
   • Detailed Instructions: Create an Add/Update Root Request
2. Add new root certificates to the case.
   • In the ROOT INFORMATION tab, click on the "Add/Select Root Certificates" button. Then click on the "Add Root Certificate to CCADB" button and paste the certificate PEM into the window and click on "Validate PEM". If validation is successful, click on the "Create Root Certificate in CCADB" button.
3. Completely fill in the information in the five tabs of the "Add/Update Root Request" case: CA OWNER, AUDITS, POLICY DOCUMENTS, ROOT INFORMATION, and TEST WEBSITES.
4. Click on the "Submit to Root Store" button.

Important:

• Audit statements must meet the requirements listed in section 5.1 of the CCADB Policy and in section 3 of the Mozilla Root Store Policy.
  • Also see Mozilla's audit lifecycle requirements
• CCADB automatically converts WebTrust Seal URLs into PDF URLs when you click on ‘Save’
• In each audit statement section in the AUDITS tab, be sure to select "Applicable Root Certificates".
  • Click on the inverted triangle ("Edit") to select all of the root certificates covered by the audit.
• If you are requesting that the Websites (TLS) trust bit be enabled for your root certificate(s), then be sure to provide the 3 test websites (valid, expired, revoked) in the TEST WEBSITES tab.
  • Click on the 'Test Websites Validation' button, resolve all failures, then click on 'Re-run Validation'
• Add records to the CCADB for all existing intermediate certificates chaining up to the new root certificate(s).
  • https://www.ccadb.org/cas/intermediates

Create a "Root Inclusion Request" Case

After you have provided information to the CCADB about your CA organization and root certificates, you may use a "Root Inclusion Request" case to request that your root certificate(s) be included in Mozilla's root store, update trust bit settings, and/or enable EV treatment.

1. Create a "Root Inclusion Request" Case in the CCADB
   • Detailed Instructions: Create a Root Inclusion Request
   • Example: https://ccadb.my.salesforce-sites.com/mozilla/PrintViewForCase?CaseNumber=00000341

• Fill in all of the fields in the MOZILLA tab

1. Click on the "Submit to Root Store" button.

Important:

• In the MOZILLA tab, click on the "Print View" button to see the data that will be shared publicly about your request.
• Click on the "Get URLs" button (which may be in the button overflow – upside down triangle) and copy the line that begins with “Mozilla Root Inclusion Case Information:” into a Comment in your Bugzilla Bug. The line to copy and paste into the Bugzilla Bug looks like:
  • Mozilla Root Inclusion Case Information: https://ccadb.my.salesforce-sites.com/mozilla/PrintViewForCase?CaseNumber=00000341
• Whenever you update data in your Root Inclusion Case in the CCADB, be sure to add a comment to your Bugzilla Bug to let folks know to re-check the information.

CA Primary Point of Contact (POC)

In addition to the information listed in the template and example above, CAs must provide the contact information for at least one person filling the role of Primary Point of Contact (POC), and may use a contractor as one of the POCs. The CA must have one or more people within the CA’s organization who jointly have authority to speak on behalf of the CA, and to direct whatever changes the review process or Mozilla’s CA Communications require. At least one of the CA’s POCs should also be in a position to make commitments for the CA and be held accountable by the CA.

The Primary POCs will:

• Provide annual updates of CP/CPS documents, audit statements, and test websites.
• Respond to CA Communications
• Input and maintain the CA’s data in the Common CA Database (CCADB)
• Inform Mozilla when there is a change in the organization, ownership, CA policies, or in the POCs that Mozilla should be aware of, as per
  • Common CCADB Policy
  • [https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy#8-ca-operational-changes Mozilla's Root Store Pne number to a specific individual within the CA (must be one of the POCs).
• CA Email Alias: An email alias is being requested so that more than one person in your organization will receive notifications in case the primary contact is out of the office or leaves the organiolicy]
• Provide Mozilla with updated contact information if a new person becomes a POC.

Required contact information:

• Direct E-mail address, full name (first and last name), and phozation. Mozilla CA Communications will be sent to both the POC direct email address(es) and the email alias.
• CA Phone Number: A main phone number from which Mozilla can reach the organization responsible for root certificates for the CA.
• Title / Department: If Mozilla needed to call your main phone number, what Title/Department should the Mozilla representative ask for?

If the CA uses a contractor as an additional POC, then someone at the CA must be CC’d on the root inclusion Bugzilla bug, CA Communications, and the CA’s responses to CA Communications.

• An individual within the CA must also get a Bugzilla account and comment in the bug to say that they will be a POC for the CA, and that the contractor has indeed been hired by the CA to act as one of the POCs.

To ensure that the POC(s) has the authority to perform the tasks listed above, a representative of Mozilla may do the following.

1. Use the CA’s website to contact a person at the CA to confirm that at least one of the POCs that have been provided does indeed have the authority to perform the responsibilities listed above on behalf of the CA.
2. Use the CA’s website, to confirm that the domain in the email address of at least one of the POCs is owned by the CA (e.g. @CAname.com).
3. If a contractor is also used as a POC, then contact the POC that was previously verified to confirm that the CA has indeed enlisted the help of the contractor.