- Scope & Frequency
-
Perform these checks at least once a month.
-
Additional checks may be necessary if urgent security advisories are released.
- Environments
-
Production: ColdFusion, WordPress, PHP, Python, and Chrome.
-
Development: ColdFusion, WordPress, PHP, Python, and Chrome, plus the Revive Adserver script using Chromedriver (the script itself only runs on Dev).
-
Update Checks
-
ColdFusion
-
Log in to the ColdFusion Administrator panel (for both Production and Dev).
-
Check the “Server Updates” section for new patches.
-
Download and install any available security updates following official Adobe instructions.
-
Confirm server functionality post-update.
-
-
WordPress
-
Log in to the WordPress admin dashboard (Production and Dev).
-
Check for core, plugin, and theme updates.
-
Apply updates in Dev first; verify site stability.
-
Repeat the updates on Production once verified.
-
-
PHP
-
Check your server’s package manager (e.g.,
yum,apt, or other) for available PHP updates. -
Apply updates in Dev; ensure applications function normally.
-
Repeat on Production if tests pass.
-
-
Python
-
Check your server’s package manager or Python release notes for security patches.
-
Update Python in Dev; test any Python-dependent scripts.
-
Apply updates in Production after successful testing.
-
-
Chrome
-
Use your server’s package manager to check for Chrome updates (e.g.,
yum update google-chrome-stable). -
Update Chrome on Dev first; verify it doesn’t break any browser-based tasks.
-
Update Production once confirmed stable.
-
-
Chromedriver
-
The Revive Adserver nightly dashboard report in Dev uses a library that automatically checks and installs the latest Chromedriver version.
-
No manual update needed unless library checks fail or there is a known security issue.
-
If manual updates are ever required, obtain the latest Chromedriver from the official site, replace the binary on Dev, and re-test the Revive script.
-
(Note: This script is only on Dev—no action needed for Production.)
-
-
Testing & Verification
-
After applying any update, restart relevant services (ColdFusion, web server, etc.) if required.
-
Confirm applications, sites, and scripts run without errors on Dev before applying the same updates to Production.
-
Log any issues and resolutions in Confluence for future reference.
- Documentation
-
Record update versions and dates in Confluence under the monthly maintenance log.
-
Note any changes or unusual steps needed during the update process.
- Sign-Off
-
Once all updates have been confirmed stable in Dev and Production, finalize the process for the month in Confluence.
-
Notify relevant stakeholders if any critical security patches or major version upgrades were applied.
