[Servercert-wg] Draft ballot SC-XX: Profiles cleanup ballot

Wed Aug 2 18:08:19 UTC 2023

Tim -
These are not TLS certificates so they cannot easily adhere to the TLS
serverAuth profile. They do not contain the serverAuth EKU
They are currently allowed in the BRs under
6.1.7
#3  Certificates for infrastructure purposes (administrative role
certificates, internal CA operational device certificates)

Which this "cleanup ballet" is proposing to remove.

thanks

Wendy

Wendy Brown

Supporting GSA

FPKIMA Technical Liaison

Protiviti Government Services
703-965-2990 (cell)

On Wed, Aug 2, 2023 at 2:00 PM Tim Hollebeek <tim.hollebeek at digicert.com>
wrote:

> Do these automatically issued certificates have the serverAuth EKU, and is
> it necessary for them to chain to a publicly-trusted root?  If not, they’re
> out of scope for the server certificate baseline requirements.  If so, why
> can they not be in full compliance with the standard TLS profiles?  Which
> fields / requirements are causing problems?
>
>
>
> -Tim
>
>
>
> *From:* Servercert-wg <servercert-wg-bounces at cabforum.org> *On Behalf Of *Wendy
> Brown - QT3LB-C via Servercert-wg
> *Sent:* Wednesday, August 2, 2023 1:52 PM
> *To:* Corey Bonnell <Corey.Bonnell at digicert.com>
> *Cc:* CA/B Forum Server Certificate WG Public Discussion List <
> servercert-wg at cabforum.org>
> *Subject:* Re: [Servercert-wg] Draft ballot SC-XX: Profiles cleanup ballot
>
>
>
> Corey -
>
> For at least 1 CA product that I am aware of, issuance of these
> certificates is automatic, and we don't believe that issuance can be
> disabled, or that a separate private PKI can be used to issue these
> certificates instead.  In the event a separate, private PKI is used for CA
> infrastructure, it would be important that the private PKI at a minimum
> meets the same security and monitoring requirements of the CA for which it
> issues infrastructure certificates.  In a situation where a CA requires
> these certificates, it would be more secure to have optional Baseline
> profiles than stand up a separate private PKI to avoid the certificates.
>
> While the issuance is automatic, the profiles can be adjusted prior to
> issuance.  The profiles required would be for a Trusted Role authentication
> certificate (unless the two factor authentication requirement is waived and
> password authentication is used instead), audit log signing certificate,
> OCSP signing certificate, TLS certificate (for the local web interface of
> the CA), and a subsystem certificate so the certificate manager subsystem
> can communicate with the CA subsystem for issuance/revocation/Trusted Role
> authentication, etc.
>
>
>
> In addition, for an offline Root CA - requiring the use of a separate
> internal PKI might also require network capability each time the Root is
> activated so the Root CA can validate the current status of those
> externally issued certificates.
>
>
>
> thanks,
>
> Wendy
>
>
>
> Wendy Brown
>
> Supporting GSA
>
> FPKIMA Technical Liaison
>
> Protiviti Government Services
>
> 703-965-2990 (cell)
>
>
>
>
>
> On Tue, Aug 1, 2023 at 2:27 PM Corey Bonnell <Corey.Bonnell at digicert.com>
> wrote:
>
> Hi Wendy,
>
> Do you know if the automatic issuance of such certificates can be
> disabled, and a private PKI be used for infrastructure purposes instead?
> Based on the discussions during the development of the profiles ballot, it
> was clear that private PKI should be used for CA infrastructure. However,
> prohibiting such use on a short timeframe would likely cause migration
> issues, so such issuance may need to continue to be permitted for at least
> some time.
>
>
>
> I’m wondering whether it’s feasible to create a “infrastructure
> certificate" profile in the BRs that can allow for the continued issuance
> of these types of certificates while also establishing some guard rails. Do
> you happen to know whether these certificates share a profile that is
> roughly like one another? I personally haven’t used CA software that
> exhibits this “automatic issuance” behavior, so I’ll lean on others who do
> have experience.
>
>
>
> Thanks,
>
> Corey
>
>
>
> *From:* Wendy Brown - QT3LB-C <wendy.brown at gsa.gov>
> *Sent:* Friday, July 21, 2023 8:24 AM
> *To:* Corey Bonnell <Corey.Bonnell at digicert.com>
> *Cc:* CA/B Forum Server Certificate WG Public Discussion List <
> servercert-wg at cabforum.org>
> *Subject:* Re: [Servercert-wg] Draft ballot SC-XX: Profiles cleanup ballot
>
>
>
> Corey -
>
> not according to some CA products - these additional certificates are
> created automatically at the time a new CA is established - so if they are
> not excluded those products are no longer eligible for use as Root CAs.  It
> was my understanding that the original language that you are proposing to
> eliminate was put there so these products could continue to be used.
>
>
> Wendy
>
>
>
> Wendy Brown
>
> Supporting GSA
>
> FPKIMA Technical Liaison
>
> Protiviti Government Services
>
> 703-965-2990 (cell)
>
>
>
>
>
> On Fri, Jul 21, 2023 at 8:19 AM Corey Bonnell <Corey.Bonnell at digicert.com>
> wrote:
>
> Hi Wendy,
>
> The intent behind the certificate profiles ballot was that the profile of
> all allowed certificate types issued from a BR-compliant CA were completely
> specified within the BRs. Adding a carve-out to allow the issuance of
> certificates whose profile is not specified and not intended for use
> outside the CA’s infrastructure would seem to go against that goal.
>
>
>
> Is the use of a private PKI not feasible for these internal infrastructure
> certificates?
>
>
>
> Thanks,
>
> Corey
>
>
>
> *From:* Wendy Brown - QT3LB-C <wendy.brown at gsa.gov>
> *Sent:* Wednesday, July 19, 2023 3:54 PM
> *To:* Corey Bonnell <Corey.Bonnell at digicert.com>; CA/B Forum Server
> Certificate WG Public Discussion List <servercert-wg at cabforum.org>
> *Subject:* Re: [Servercert-wg] Draft ballot SC-XX: Profiles cleanup ballot
>
>
>
> I would not like to see #3 exclusion for Root CAs removed
>
>
>
> Some CA products when a new CA is established, automatically create some
> internal certificates that are necessary for the operation of the CA
> including possibly a key pair used to sign audit logs with a certificate
> signed by the Root CA that can be used to verify the integrity of the logs
> by verifying the signature. In addition to enabling cert-based
> authentication for trusted roles needing to access the CA, including for
> actions like manually instigating the issuance of a subordinate CA
> certificate or manually issuing a new CRL when there has not been a
> revocation.
>
>
>
> This change would make it so those products could not be compliant with
> the BRs, even though such certificates would never be seen outside the
> supporting infrastructure.
>
>
>
> If the rationale is there are no profiles for internal certificates, then
> I suggest a better fix would be to add the word public in the conflicting
> language in 7.1.2, as the internal certificates that have no BR profile
> should never be seen outside the CA's infrastructure. But removing the
> allowance would potentially trigger a non-compliance during an audit.:
>
> “If the CA asserts compliance with these Baseline Requirements, all
> *public *certificates that it issues MUST comply with one of the
> following certificate profiles, which incorporate, and are derived from RFC
>
> 5280.”
>
>
>
> Thanks,
>
> Wendy
>
>
>
> Wendy Brown
>
> Supporting GSA
>
> FPKIMA Technical Liaison
>
> Protiviti Government Services
>
> 703-965-2990 (cell)
>
>
>
>
>
> On Wed, Jul 19, 2023 at 10:16 AM Corey Bonnell via Servercert-wg <
> servercert-wg at cabforum.org> wrote:
>
> Hello,
>
> While adding support for SC-62 linting for TLS certificates in pkilint, a
> few issues were identified with the current language in section 6 and 7 of
> the BRs. To address these issues, I created a draft ballot on Github. The
> draft ballot text can be viewed here:
> https://github.com/cabforum/servercert/compare/SC63..CBonnell:servercert:sc62-cleanup
> <https://url.avanan.click/v2/___https:/github.com/cabforum/servercert/compare/SC63..CBonnell:servercert:sc62-cleanup___.YXAzOmRpZ2ljZXJ0OmE6bzpkNmRlMmQ1ZDU1ZDIyYThiNDc1ZjJmNTg3YzJjZDczZTo2OmE3YTg6OTQzODNmYmRkMjcyM2U5ODYwMmY5YWNkMjA5MWU1MDcxMTM4OWIwZDA1OWUxODYxOTFmMDE1OTIyOWM3ZWQ3NzpoOkY>
> .
>
>
>
> Chris Clements of the Chrome team reviewed and offered to endorse, so
> we’re looking for one more endorser to push this ballot forward.
>
>
>
> Please let me know if you have any feedback on the proposed language or if
> you’d be willing to endorse.
>
>
>
> Thanks,
>
> Corey
>
> _______________________________________________
> Servercert-wg mailing list
> Servercert-wg at cabforum.org
> https://lists.cabforum.org/mailman/listinfo/servercert-wg
> <https://url.avanan.click/v2/___https:/lists.cabforum.org/mailman/listinfo/servercert-wg___.YXAzOmRpZ2ljZXJ0OmE6bzpkNmRlMmQ1ZDU1ZDIyYThiNDc1ZjJmNTg3YzJjZDczZTo2OmZmMTI6NTg5ZDE2ZjkyNDJjODZjOTdjNTYwOGFhMDBlNGY3OWFjMTAyNDU5NzViMmE5ZWQ5NTBjMDMwZTZkZWNjOTA4YTpoOkY>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/servercert-wg/attachments/20230802/7fb1a210/attachment.html>