Apple CT Log Program: call for 2028 log shards

[Dustin Hollenback]

Hello,

The Apple Certificate Transparency Log Program is inviting applications to include 2028 log shards.

Please submit 2028 log shards by 2026-09-05. This allows time for compliance monitoring, rollout, and processing. Later submissions will still be evaluated, but the delay reduces redundancy and issuance capacity across the ecosystem until the logs are Usable.

Send applications to certificate-tran...@group.apple.com . The full requirements are published at https://github.com/apple/apple-root-program/blob/main/ct/ct-log-program.md .

If you run a Qualified or Usable log and do not plan to operate a 2028 shard, please tell us early so we can account for it.

Thank you,

Dustin

Apple Certificate Transparency Log Program

[Andrew Ayer]

Hi Dustin,

I see that Apple still requires at least one SCT from an RFC6962 log, and still requires static-ct-api logs to follow an old version of the spec. Is Apple planning to update either requirement?

I think it would be very beneficial to the ecosystem if there were no RFC6962 logs past 2027. The static-ct-api protocol and implementations have proven themselves and there are now more operators willing to operate static-ct-api logs than RFC6962 logs. Meanwhile the RFC6962 read endpoint continues to pose challenges for multiple operators, and the challenges will only get worse as certificate lifetimes become shorter.

Updating to static-ct-api v1.1.0 would allow log implementations to drop error-prone code for handling Precertificate Signing Certificates.

Regards,
Andrew


On Thu, 23 Jul 2026 14:44:37 -0700
"'Dustin Hollenback' via Certificate Transparency Policy"

<ct-p...@chromium.org> wrote:

> Hello,
>
> The Apple Certificate Transparency Log Program is inviting
> applications to include 2028 log shards.
>
> Please submit 2028 log shards by 2026-09-05. This allows time for
> compliance monitoring, rollout, and processing. Later submissions
> will still be evaluated, but the delay reduces redundancy and
> issuance capacity across the ecosystem until the logs are Usable.
>
> Send applications to certificate-tran...@group.apple.com

> <mailto:certificate-tran...@group.apple.com> . The full

> requirements are published at
> https://github.com/apple/apple-root-program/blob/main/ct/ct-log-program.md .
>
> If you run a Qualified or Usable log and do not plan to operate a
> 2028 shard, please tell us early so we can account for it.
>
>
> Thank you,
>
>
> Dustin
> Apple Certificate Transparency Log Program
>
>
>

> --
> You received this message because you are subscribed to the Google
> Groups "Certificate Transparency Policy" group. To unsubscribe from
> this group and stop receiving emails from it, send an email to
> ct-policy+...@chromium.org. To view this discussion visit
> https://groups.google.com/a/chromium.org/d/msgid/ct-policy/DCE85586-DD37-4C5A-9FF3-CF7675F76C6F%40apple.com.

[Dustin Hollenback]

Hi Andrew,

Thank you for the feedback on these two points.

Both changes you described are already incorporated in our upcoming policy updates, which are in internal review.

We expect to publish both updates soon... ahead of 2028 log shards becoming Usable.

Thank you,

Dustin

Apple Certificate Transparency Log Program