Every Friday, this blog takes one chapter of Strategic Web Management and argues its central idea, paired with the podcast episode and worksheet built from it. This week is Chapter 8, Security for Non-Security People, and its idea fits in one sentence: the attacks that reach small websites are aimed at software versions, never at organizations, so the defense is a schedule rather than a specialty.
That sentence answers the objection I hear most often, in boardrooms and at kitchen tables: nobody would bother hacking us. It is true, and it is beside the point. Nobody bothers. A bot does, and the bot never read the About page.
Two sites from this year
The chapter opens with cases from my own calendar. In one, a single outdated plugin handed an attacker a file manager: open any file, save changes, execute code straight into the database. By the time anyone noticed, the damage had reached the site's structure, its search standing, and the trust the organization had spent years earning. In another, no malware was involved at all; a plugin installed years earlier was registered under a former developer's personal account, and when the organization brought management in house, the site stayed locked until that developer released it, for a fee. Neither organization was targeted. One had an unapplied update; the other had an ownership gap nobody had written down.
Four enemies and a framework
Chapter 8 names four attacks and gives you permission to ignore the rest: brute-force password guessing, malware through outdated software, phishing that now reads like the real notice, and form spam. The National Institute of Standards and Technology (NIST) Cybersecurity Framework supplies the chapter's order: identify, protect, detect, respond, recover. The inventory from Chapter 2 was identify. The baseline is protect. The walls and alarms are detect. The incident script is respond and recover, with the tested backup from Chapter 4 playing the role it was rehearsed for.
The baseline costs an afternoon
While the security industry sells depth, the chapter argues for a floor, and the floor is short. Updates on a weekly schedule, because an unapplied update is a published invitation. A unique, vault-generated password for every account, and two-factor authentication (2FA) on every account whose compromise would be an incident, with the codes in organizational custody. Least privilege: as few administrators as the work allows and never fewer than two, no shared logins, publishing from editor-level accounts, and offboarding treated as a security event. One habit that defeats phishing even when the fake is perfect: never log in through a link in a message. Nearly all of it is free, and nearly all of it was already on the maintenance calendar Chapter 7 built. Security at this scale is the maintenance calendar wearing a helmet.
The bad day, scripted
Preparation makes a compromise unlikely and cannot make it impossible, so the chapter ends with a calm script for the day the alarm is real: confirm and document, contain, rotate the passwords that matter in order, tell the host "my site is compromised," restore the pre-compromise backup onto a fully updated platform, and write the log entry that closes the hole. The chapter also supplies a decision rule for paying a professional: when the site handles commerce or personal data, when there is no clean backup, or when reinfection recurs. Otherwise, the tested backup and the script handle the common case, and the fee stays in the mission's pocket.
The mission tie-back
Every form submitted, every card entered, every address handed over is a small act of trust, and in the coming weeks your site will receive more of them than at any other time of year. The baseline is how that trust is honored on the nights and weekends when nobody is watching. A secure site is quiet, and the quiet is earned. Episode 9 of The Web Managers Podcast walks the same ground, with the board chair's objection answered in two minutes.
Get the chapter worksheet. The M8.1 Security Baseline Checklist and Incident Response One-Pager is the worksheet for Chapter 8 and Episode 9, free with a Web Managers account at https://webmanagers.com/register. The full chapter, with the four enemies, the baseline, and the incident script, is in Strategic Web Management: First Steps for the Accidental Web Manager.

