Hi Pedro, All CAs in the Apple Root Program are required to complete an audit based on either WebTrust Principles and Criteria for Certification Authorities or ETSI EN 319 411-1 LCP, NCP, or NCP+ per Section 1.1.1 of the ARP Policy. For clientAuth-only CAs, these are currently the only audit criteria.
I appreciate the comment regarding TLS CAs; I’ll look at improving this language, but this specifically is referencing CAs capable of asserting the serverAuth EKU as clientAuth is not required for TLS. That is, the serverAuth EKU is required at a protocol level to establish a secure TLS connection, while the clientAuth EKU is only used in specific contexts, such as mTLS — which is almost always a use-case better (or perhaps more ideally) solved by Enterprise or Private PKIs. Thanks! -Clint > On May 17, 2024, at 2:32 AM, Pedro FUENTES <[email protected]> wrote: > > I also oversaw that… > > Anyhow… @Clint, what are the audit requirements for these clientAuth CAs? > In your program you mention WTBR as a requirement for "TLS CAs”, but there’s > no distinction between clientAuth or serverAuth… while both are used to > secure TLS handshakes. > >> On 17 May 2024, at 11:22, Dimitris Zacharopoulos (HARICA) >> <[email protected]> wrote: >> >> >> >> On 16/5/2024 10:29 μ.μ., Clint Wilson wrote: >>>> AFAIK Apple and Mozilla also don't have a specific "trust bit" for Client >>>> Authentication. Only Microsoft does. >>> FWIW, Apple does indeed have a specific trust bit for id-kp-clientAuth EKU >>> and allows for (and ships) dedicated clientAuth Root CAs in the Apple Root >>> Program (as outlined in 2.1.3 of the ARP Policy). >>> >> >> Thanks for the correction Clint. I had the impression that you shipped only >> Apple Roots for clientAuth. My bad. >> >> Dimitris. >> >> >> > > > WISeKey SA > Pedro Fuentes > CSO - Trust Services Manager > Office: + 41 (0) 22 594 30 00 > Mobile: + 41 (0) 791 274 790 > Address: Avenue Louis-Casaï 58 | 1216 Cointrin | Switzerland > Stay connected with WISeKey <http://www.wisekey.com/> > > THIS IS A TRUSTED MAIL: This message is digitally signed with a WISeKey > identity. If you get a mail from WISeKey please check the signature to avoid > security risks > > CONFIDENTIALITY: This email and any files transmitted with it can be > confidential and it’s intended solely for the use of the individual or entity > to which they are addressed. If you are not the named addressee you should > not disseminate, distribute or copy this e-mail. If you have received this > email in error please notify the sender > > DISCLAIMER: WISeKey does not warrant the accuracy or completeness of this > message and does not accept any liability for any errors or omissions herein > as this message has been transmitted over a public network. Internet > communications cannot be guaranteed to be secure or error-free as information > may be intercepted, corrupted, or contain viruses. Attachments to this e-mail > are checked for viruses; however, we do not accept any liability for any > damage sustained by viruses and therefore you are kindly requested to check > for viruses upon receipt. >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Servercert-wg mailing list [email protected] https://lists.cabforum.org/mailman/listinfo/servercert-wg
