Most of the organizations I work with do not have an IT department. They have a person, and the person has a day job, a full calendar, and a website that somebody once said "just needs to stay up." Security advice written for enterprises assumes a team, a budget, and a vocabulary; none of the three is available to that person. Episode 9 of The Web Managers Podcast is security for them, with no dread and no jargon.

This post is the episode's companion: the four enemies small sites actually face, the afternoon of defenses that turns them away, the walls and alarms worth the free toggles, the calm script for the bad day, and the two-minute answer to the board chair who says nobody would bother hacking you.

The bot that read a version number

The episode opens with a site I cleaned up this year, where a single outdated plugin handed the attacker a file manager: open any file, save changes, write straight to the database. What the attacker knew about that organization before striking was nothing. A bot read a version number, and that was the whole crime. Every lesson in the episode follows from that fact.

Four enemies, and permission to ignore the rest

Four attacks account for nearly everything a small site faces. Brute force is automated password guessing against every login page on the internet, around the clock. Malware arrives through outdated software, often within hours of a vulnerability being published. Phishing works on people, and AI has retired the misspelled giveaway; the modern fake reads like the real notice. Form spam is the least dangerous and the most constant, and it buries the inquiries your mission depends on.

Scope discipline is itself a security practice. Nation-state actors and exploits with cinematic names are aimed at other targets, and an organization that chases them buys anxiety while the four ordinary enemies walk through ordinary doors. The episode also names the one setting that retires form spam for the year: Cloudflare Turnstile or hCaptcha on every public form.

The baseline is an afternoon and a schedule

The National Institute of Standards and Technology (NIST) Cybersecurity Framework groups security into five functions: identify, protect, detect, respond, and recover. The inventory was identify. The baseline is protect, and nearly all of it is free.

Updates come first, because the update cadence from Chapter 7 is the single highest-value security control you hold; Monday's post walked the order. Credentials come next: a unique, vault-generated password for every account, and two-factor authentication (2FA) on every account that could cause an incident, with seeds and backup codes in organizational custody. The phishing habit that survives a perfect fake is one sentence: never log in through a link in a message. If the notice was real, it will be waiting when you type the address yourself.

Least privilege closes the baseline. Hold administrator accounts to as few as the work allows and never fewer than two; no shared logins anywhere, because a shared credential can be revoked for nobody and audited for nobody; and publish from editor-level accounts, so a phished content password cannot delete the site. Offboarding is a security event: disable the accounts, transfer what they owned, and recover the 2FA custody the day access ends.

Walls, alarms, and the noise problem

Two free layers do most of what a consultant would bill for at this scale. Cloudflare's free tier filters traffic in front of everything and includes an under-attack mode worth locating before you need it. On WordPress, Wordfence's free tier adds a firewall, login attempt limits, and alerts for administrator logins, file changes, and outdated components. The failure mode of alerting is noise rather than silence. Route the blocked-attempt chatter to a weekly digest and reserve immediate email for the events that always deserve eyes; an alert can only stop you if it is rare.

The day the alarm is real

Confirm something is actually wrong and write down what you see, with times and screenshots. Contain: maintenance mode, or a request to the host, if the site is serving malware to visitors. From a device you trust, rotate the passwords that matter, hosting, CMS administrators, registrar, and email, in that order. Open a ticket and say the words "my site is compromised." Restore from the backup that predates the compromise onto a fully updated platform, so the same hole does not come back with it. Then write the log entry: what happened, how it got in, what changed. Last week's post on the incident log explains why that entry is the cheapest insurance you own.

Also in this episode

The Question Line takes the board chair's objection, "we're a tiny nonprofit, nobody is going to bother hacking us," and answers it in two minutes: bots attack platforms, not brands, and your size does not appear in the search. The Tool Minute covers Have I Been Pwned, the free breach check that makes the argument concrete.

Quick win: count the administrators

  1. Open the website's users list and count the administrator accounts.

  2. Demote every one that does not strictly need administrator access to editor or below.

  3. Delete every account belonging to someone who has left, after noting anything it owned.

  4. Turn on 2FA for the accounts that remain, and keep at least two.

Done looks like a short, named list of administrators, every one with 2FA, and nobody on it who has left.

Get the worksheet. The M8.1 Security Baseline Checklist and Incident Response One-Pager scores your site on fifteen pass-or-fail items with the fix for each, and puts the bad-day script on one printable page with your host's contact lines filled in. It is free with a Web Managers account at https://webmanagers.com/register, and it arrives with the weekly Web Managers letter.

Categories

Cybersecurity  

Terms