Sectigo's F5 partnership expands to F5 Distributed Cloud Services: What this means for you

When Sectigo and F5 announced their partnership earlier this year, the goal was straightforward: bring automated certificate lifecycle management directly into F5 environments, so teams could stop chasing renewals manually and start trusting their infrastructure to stay current. That partnership began with support for the F5 Application Delivery and Security Platform (ADSP), giving organizations a way to automatically issue, deploy, and renew certificates across on-premises, hybrid, cloud, and edge deployments.

Now that partnership is expanding. With the launch of Sectigo Orchestration Gateway (SOG), Sectigo Certificate Manager (SCM) customers can extend the same automation to F5 Distributed Cloud, F5's SaaS-native solution for securing and delivering applications and APIs across multi-cloud and edge environments.

Why this matters now
How this integration works
The bigger picture

By Henry Lam, Product Management DirectorSeptember 3, 20263 min read

Why this matters now

Certificate lifecycles keep getting shorter, and the operational surface keeps getting bigger. Teams using F5 Distributed Cloud to proxy internet-facing applications are managing certificates across load balancer configurations that, until now, often required manual intervention every renewal cycle. As validity periods shrink, that manual work becomes repetitive and becomes a real source of risk.

SOG closes that gap for Distributed Cloud environments the same way it does across the rest of the F5 ecosystem: by automating the parts of the process that used to depend on someone remembering to do them.

How this integration works

Does the integration use F5 Distributed Cloud APIs? Yes. SOG connects to Distributed Cloud using its APIs, giving it a direct, secure line into the tenant rather than relying on manual export/import workflows.
Does SOG establish a secure connection directly to the F5 Distributed Cloud tenant? Yes. The API-based connection means SOG can act on certificates within the Distributed Cloud environment directly, without a person moving files between systems by hand.
What manual steps does this eliminate? Previously, keeping a Distributed Cloud managed application current meant submitting a certificate request to a CA, waiting for and collecting the issued certificate, and then manually loading it into the console. Every renewal cycle, for every application. SOG removes that entire chain. It handles issuance coordination and deployment into the console automatically, so engineers aren't the ones closing the loop.
What does that look like in practice? Consider a customer running Distributed Cloud to proxy internet-facing applications. Certificates renew in SCM as usual, but instead of stopping there, SOG automatically deploys the updated certificate to the Distributed Cloud load balancer configuration. Engineers no longer need to manually import and bind a new certificate every time one renews.

The bigger picture

This expansion is part of a broader pattern in how Sectigo and F5 are working together: reducing the manual surface area where certificate-related outages tend to start and giving joint customers one less thing to track by hand as renewal cycles accelerate industry-wide. Support for F5 Distributed Cloud through SOG means that automation now follows applications wherever they're delivered, not just within traditional ADSP/BIG-IP deployments, but across the multi-cloud and edge footprint that Distributed Cloud is built for.

For teams already running SCM alongside Distributed Cloud, the integration is available now as part of the Sectigo Orchestration Gateway rollout. If you're managing certificates across Distributed Cloud today and want to see what automated deployment looks like in your environment, reach out to your Sectigo team.