Open Bug 1449941 Opened 4 years ago Updated 4 months ago

Add "Fina Root CA" root certificate

Categories

(NSS :: CA Certificate Root Program, task, P4)

3.35

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: pma, Assigned: bwilson, NeedInfo)

Details

(Whiteboard: [ca-verifying] - BW Comment #8 2021-09-22)

Attachments

(2 files)

40.39 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document
Details
157.36 KB, application/pdf
Details
No description provided.
Acknowledging receipt of this root inclusion request. I have a huge backlog of CA updates/requests to review, so this has been added to my list. I will update this bug when I begin information verification of this request as per step #2 of our process:
https://wiki.mozilla.org/CA/Application_Process#Process_Overview

In the meantime, please attach your completed BR Self Assessment to this bug.

https://wiki.mozilla.org/CA/BR_Self-Assessment
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Whiteboard: [ca-verifying] - Need BR Self Assessment
Attached is the information that has been verified for this request. Within the document search for "NEED" to find where further information is needed from the CA.

In particular:

1) The Audit Statements do not properly specify the audit period start and end dates, and the SHA-256 fingerprints of each root and intermediate certificate that was in scope.

Audit period is NOT the same as the dates that the audit was performed.
Reference:
Sections 3.1.3 and 3.1.4 of
https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/
and
https://cabforum.org/wp-content/uploads/CA-Browser-Forum-BR-1.6.0.pdf
Audit Period: In a period-of-time audit, the period between the first day (start) and the last day of operations (end) covered by the auditors in their engagement. (This is not the same as the period of time when the auditors are on-site at the CA.) The coverage rules and maximum length of audit periods are defined in section 8.1.

2) If requesting the Email (S/MIME) trust bit, then the CP and/or CPS must explain how the CA confirms that the certificate requester owns/controls the email address to be included in the certificate.
https://wiki.mozilla.org/CA/Required_or_Recommended_Practices#Verifying_Email_Address_Control
Furthermore, In the Qualified and Non-Qualified CP/CPS documents, section 3.2.4 says that e-mail address is not verified. 

3) Need the URLs to the 3 test websites as per section 2.2 of the CA/Browser Forum's Baseline Requirements: "At a minimum, the CA SHALL host separate Web pages using Subscriber Certificates that are (i)valid, (ii) revoked, and (iii) expired."

4) Provide Test Results for
-- Revocation testing: http://certificate.revocationcheck.com/
-- BR Lint Test: https://github.com/awslabs/certlint
-- X.509 Lint Test: https://github.com/kroeckx/x509lint

5) Attach your CA's BR Self Assessment to this bug
https://wiki.mozilla.org/CA/BR_Self-Assessment
Whiteboard: [ca-verifying] - Need BR Self Assessment → [ca-verifying] - KW Comment #2 2018-08-17

The documentation supporting your application for root inclusion appears to be out of date and needs to be updated. The most current CP/CPS that we have is version 2.4, published June 10, 2019, and the most recent audit is dated June 24, 2019.

Flags: needinfo?(pma)
QA Contact: kwilson
Assignee: kwilson → bwilson
Whiteboard: [ca-verifying] - KW Comment #2 2018-08-17 → [ca-verifying] - BW Comment #3 2020-08-27

Also, CA needs to provision three test websites equipped with certificates - one valid, one expired, and one revoked.
If requesting enablement of the email trust bit, then CPS needs to describe how CA will verify the email address with a challenge-response mechanism.

The CA has provided the three test websites (verified) and their current CP/CPS (needs review). The ETSI accreditations on Fina's website have a date of 27/06/2019 (outdated) and do not include the SHA2 hash of the CA certificates and are not hosted on the Bureau Veritas website, as required. The CA will need to remediate this issue before we can proceed with our review.

Whiteboard: [ca-verifying] - BW Comment #3 2020-08-27 → [ca-verifying] - BW Comment #5 2020-08-31

Sent email to CA re: still waiting for updated attestation letter accessible from Bureau Veritas website.

Priority: -- → P4

In correspondence with Bureau Veritas regarding ALV processing, there was an issue with the audit dates in a table format that could not be processed by the ALV, so they are fixing the format of the attestation letter.

Do you have an estimate for when you'll be posting an updated CP and CPS to your repository?
https://www.fina.hr/en/legislation-documents-and-conformance-certificates
Are the last CP and CPS from 25 September 2020 (version 1.6)?
While updating your CP and CPS, please complete and submit the Compliance Self-Assessment - see https://wiki.mozilla.org/CA/Compliance_Self-Assessment and the template, here: https://docs.google.com/spreadsheets/d/1ExZE6PWIBM8rV9c6p6fFxOWmZyvf6X4ucMQRv7usHEk

Whiteboard: [ca-verifying] - BW Comment #5 2020-08-31 → [ca-verifying] - BW Comment #8 2021-09-22

(In reply to Ben Wilson from comment #8)

Do you have an estimate for when you'll be posting an updated CP and CPS to your repository?
https://www.fina.hr/en/legislation-documents-and-conformance-certificates
Are the last CP and CPS from 25 September 2020 (version 1.6)?
While updating your CP and CPS, please complete and submit the Compliance Self-Assessment - see https://wiki.mozilla.org/CA/Compliance_Self-Assessment and the template, here: https://docs.google.com/spreadsheets/d/1ExZE6PWIBM8rV9c6p6fFxOWmZyvf6X4ucMQRv7usHEk

On September 24, 2021 in in our repository https://www.fina.hr/en/legislation-documents-and-conformance-certificates we have published new versions of CP and CPS documents for OVCP certificates (Certificates for Website Authentication), version 1.7, effective date 25 September 2021 . Before that the last version of the documents was 1.6 from 25 September 2020.

We plan to conduct the compliance self-assessment during this week and send you the completed form in early October.

You need to log in before you can comment on or make changes to this bug.