I'm dealing with a Fortinet patch, PHP cleanup, and certificate revocation work involving GoDaddy-managed systems. How would you prioritize the work without breaking services?
How should I prioritize certificate cleanup after a Fortinet patch?
Answers
First, identify which certificates actually need to be revoked and where they're installed. Don't assume the Fortinet patch means every GoDaddy certificate is affected. Check the relevant notices and your inventory.
For each affected certificate, map the services that use it, arrange a replacement, install it, and verify the service presents the new certificate. Coordinate the revocation timing with the reason for revocation. A suspected compromised key may need faster action, even if that risks interruption.
Check load balancers, reverse proxies, appliances, and any other places a certificate might have been copied. Track owners and deadlines so a forgotten endpoint doesn't surprise you later.
Reply to this answer
Split the work into separate queues. The Fortinet patch, PHP updates, and certificate revocations may overlap on the same systems, but they aren't automatically the same incident.
Prioritize exposed systems and any explicitly affected certificates, then check PHP versions and bundled applications against their own advisories. Test changes where practical and have a rollback plan for the patching work.
Reply to this answer
For hosted websites, check the contract and hosting controls before assuming the provider handles all of this. A third party might manage the server while leaving the PHP version or certificate configuration to you. Find out who owns each change and who verifies it afterward.
Reply to this answer
If renewal is part of the cleanup, look at how each service proves domain control. Some setups temporarily open a port for automated renewal, but the site is still publicly reachable during that window. Treat that exposure as a security decision, not just a scheduling trick.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_y64+socketmixer.3:
That distinction matters for bundled PHP too. An application can bring its own runtime, separate from the version configured for the main site.