Security Month is behind you, and the busiest weeks of the year are ahead. Between now and December your website will take more orders, more donations, and more first impressions than at any other time, so this month's web checks are about readiness. The first is the least glamorous: applying the updates waiting right now, in an order that keeps a routine Monday from becoming an emergency.

An unapplied update is a published invitation. When a vulnerability is announced, the fix ships the same day, and so does a description of the hole; bots begin scanning for sites still running the old version within hours. The one honest argument against updating, the fear that an update will break something, is answered by sequence rather than by waiting.

Why the order matters

Chapter 7 of the book fixes the sequence: plugins first, then the theme, then the platform core. Plugins go first because they are the most numerous, the most often abandoned, and the most common way a small site is compromised; bringing each one current settles the likeliest suspects before anything beneath them moves. The theme comes next, because it depends on those plugins and is the component most likely to change what visitors see. The core goes last, so a platform update lands on a site where everything built on it is already current, and a problem at that step has one suspect. Readers on hosted platforms can skip the mechanics; the subscription applies updates invisibly.

The sequence, in twenty minutes

Confirm the backup before anything else. Open the host's backup panel or the backup plugin and look at the date of the most recent copy with your own eyes; never update a site whose last backup you have not seen. If the host offers one-click snapshots, take one now.

Work through the plugin list, checking the site after each one or each small batch. Then apply the theme update and load the homepage. Then the core. A site with staging runs the sequence there first.

Click through the five pages that matter: the homepage, the contact page, the donation or checkout page, and the two pages visitors use most, with the homepage loaded on your own phone. Submit the contact form and confirm the message arrives.

Write one line in the maintenance log: the date, what updated, anything odd. Most weeks it reads "all clear," and that is the product.

Automatic or manual

The policy depends on what a broken update would cost by morning. A brochure site can auto-update everything, backed by the backups above and this weekly glance. A site that takes orders, processes donations, or runs memberships should update manually on this schedule, with security-only updates left automatic, because the gap between a published vulnerability and its exploitation is measured in hours. In the peak week itself, apply security patches only and let feature updates wait seven days.

When an update breaks the site

Stop updating. The instinct is to update everything else in case that fixes it, which turns one suspect into eleven. The most recent update is the culprit. Deactivate it from the admin panel, or, if the panel is gone too, rename its folder from the host's file manager; support will walk you through that. If the site does not recover, restore the snapshot you took at the start. Should the restore fail, put up a holding page and call the helper on your emergency contact card. Log the incident, report the update to its maker, and put any component that breaks on routine updates on the replacement list. Staying outdated to avoid the annoyance trades a visible, recoverable problem for the invisible kind.

Done looks like a dated log line, every waiting update applied, a backup you saw before you touched anything, and a test message from the contact form in the inbox.

Pin the card beside the desk. The M7.3 Monday Web Check Card is the six-step check above on one printable sheet, with an eight-week log and the recovery steps for a broken update. It is free with a Web Managers account at https://webmanagers.com/register, and it arrives with the weekly Web Managers letter.

Categories

Cybersecurity  Management