All,

The update to the CCADB, which adds an Audit Team Qualifications document
upload field to the AUDITS tab of  “Add/Update Root Request” cases, is now
complete. (This is mainly for audits that do not include this information
directly in audit statements.)  Under the AUDITS tab of  “Add/Update Root
Request” cases, there are now sections for "Audit Firm" and "Audit Team".

Instructions for this new upload functionality in the CCADB are available
here
<https://docs.google.com/document/d/12U4az-hjYDC_aWsVn8-Y5vVmJ10inVziAxrQoxP-hfI/edit#bookmark=id.q9frfps8jur5>.


As noted in a separate email
<https://groups.google.com/a/ccadb.org/g/public/c/hvhra7upKMU/m/zItEhBVLBgAJ>,
on October 25, 2023, we expect to add a new section 5.2 to the CCADB Policy
(Audit Firm and Audit Team Qualifications), which recounts the expected
contents of a statement of Audit Team Qualifications. Until then, please
refer to each separate root store policy for its audit team qualification
requirements.

Thank you

- Ben, on behalf of the CCADB Steering Committee



On Sun, Oct 15, 2023 at 11:26 AM Ben Wilson <bwil...@mozilla.com> wrote:

> All,
>
> Tomorrow, Monday, October 16, 2023, we will be updating the AUDITS tab of
> “Add/Update Root Request” Cases in the CCADB to provide upload
> functionality for Audit Team Qualifications documents (mainly for WebTrust
> audits, as ETSI audit teams already include this information directly in
> audit statements).
>
> CA Owners should not be impacted during this update and can perform
> routine CCADB functions as expected.
>
> We will send a separate email when the update is complete.
>
> Thank you,
>
> Ben, on behalf of the CCADB Steering Committee
>

-- 
You received this message because you are subscribed to the Google Groups 
"CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to public+unsubscr...@ccadb.org.
To view this discussion on the web visit 
https://groups.google.com/a/ccadb.org/d/msgid/public/CA%2B1gtaZVzsqBB4FT0-kO0myt-KQd7U%3Dzchdpxbjt3TQjwaFzuA%40mail.gmail.com.

Reply via email to