Skip To Content

Website Security: A Monthly Checklist

Web Design & Development | Adam Post Friday, September 18, 2026

Overview

If someone changed one line of code on your website this morning, how long would it take you to notice?

 

For a lot of organizations, the honest answer is that a customer would eventually mention it. That’s not negligence. It’s what happens when a site gets built, launched, and then runs quietly for four years while everyone gets on with the business. It works. Nobody’s complaining.

 

October is Cybersecurity Awareness Month, as good an excuse as any to look, and there’s a specific reason this year. In late September, Chrome turned on Always Use Secure Connections by default, so it now asks permission before loading a public page over plain HTTP. It’s a prompt the visitor can click through, and Chrome won’t keep pestering a regular. But a first-time visitor gets a security question about you before your homepage.

 

Most business sites already run on HTTPS and won’t blink. It’s the leftovers that trip the warning.

A manager helping a worker by pointing someone out to them on a monitor.

Why Is Your Website a Different Security Problem Than Your Network? 

Your internal network sits behind a firewall, and someone has to get through it. Your website is deliberately exposed to everyone on earth, which is the entire point of having one. 

Almost nobody is picking your business out of a directory and mounting a targeted attack on your brochure site. What happens is automated: software crawls the internet for known weaknesses in common web platforms, finds one, and exploits it without knowing whose site it landed on. You don’t get compromised because someone wanted your data. You get compromised because your version number matched a pattern. 

Which is oddly reassuring, because it makes the fix a maintenance problem. The same discipline that keeps your network credentials from being harvested applies here, but the surface is different, and it usually belongs to a different person. Sometimes to nobody in particular. 

What Belongs on a Website Security Checklist? 

Who Can Log In, and What Happens If Someone Guesses? 

Start with the account list. It’s usually where the surprises are. Every content management system accumulates logins: the agency that built the site, the marketing hire who posted three Blog articles in 2022, the contractor who needed access “just to check something.” The bigger the company, the longer that list and the less anyone remembers approving it. Pull the account list from your site and review it. Most accounts should be gone, and several probably hold administrator rights they never needed. 

Then turn on multi-factor authentication for whoever’s left. CISA’s position is blunt: any MFA is better than no MFA, and phishing-resistant MFA is the standard to work toward. An authenticator app on your admin panel is a large improvement over nothing, though a hardware key is what CISA would actually point you at. A CMS login is exactly the credential-phishing target it has in mind. On most sites that means adding a plugin. The next section applies. 

Is Anything Running That Nobody Updates? 

WordPress runs a large share of the web, and the core software, the part WordPress itself builds and maintains, is genuinely well looked after. The trouble is rarely there. Patchstack, a security vendor tracking vulnerabilities across the WordPress ecosystem, reported that in 2025 roughly nine in ten new vulnerabilities came from plugins and nearly all of the rest from themes. Core had six all year. Treat the exact figure the way you’d treat any vendor dataset, but the shape is right: one professionally maintained core, tens of thousands of plugins from developers of varying diligence. 

Here’s the part that catches people. Plugins and themes almost never update themselves unless somebody turned that on, one at a time. WordPress’s security team can push a fix for a critical vulnerability, and some managed hosts enable updates fleet-wide, but neither is something to count on. Minor core updates install automatically on essentially every site, major ones only on sites set up on WordPress 5.6 or later. So, core mostly looks after itself. The plugins wait for a human. 

Look at the plugin list. Anything you don’t recognize, anything the developer hasn’t updated in over a year, anything you installed to test once and left sitting there. 

Then stop before you click Update All. Plugin updates are the most common way a working site suddenly isn’t one. Two that got along fine yesterday stop getting along, or a theme leans on a function that just changed. The page that breaks is rarely the one you were looking at, and tracking it down afterwards, with no way back, turns a ten-minute job into a bad afternoon and a bill nobody wanted. 

So take a restore point before you touch anything. That’s how we run updates on the sites we manage: snapshot first, updates second, and a bad one goes back with one click. 

Underneath it all sits the language the site runs on. PHP 8.1 and older stopped receiving security fixes at the end of 2025, and PHP 8.2 reaches end of life on December 31, 2026. Your host can tell you which version you’re on in about thirty seconds. 

Does Every Address You Own Actually Load Over HTTPS

It’s rarely the main site that fails this one. 

It’s the old subdomain from a campaign three years ago. The staging site nobody took down. The hardcoded HTTP :// link in a directory listing you don’t control. The QR code printed on last year’s trade show banner. 

Every hostname you own should serve HTTPS , and every HTTP request should redirect at the server rather than leaving it to the browser. Then the harder half: your address in print, on signage, in other people’s databases. Those still say whatever they said when somebody typed them. 

Building that inventory is the fiddly part, and the step most people skip. If you don’t know what’s out there, or who set it up, ask us and we’ll send you the list of every address still answering under your domain. 

Who Renews Your Certificate, and How? 

Certificate lifetimes are shrinking on a published schedule, and the number most people have heard is the wrong one. 

The CA/Browser Forum agreed on a phased reduction in April 2025. Since March 15, 2026, a new certificate can be issued for at most 200 days. That drops to 100 days in March 2027 and 47 in March 2029. The 47-day figure made the headlines and is still two and a half years away. The one that matters today is 200 days, shorter than a year. 

So the real question is whether anyone renews your certificate by hand. On the sites we host, renewal runs automatically, and the handful of certificates that can’t renew that way are tracked and handled before they lapse. If your site sits elsewhere, ask whoever runs it the same question. A certificate that has expired over a weekend once will do it again, and the fix is permanent. 

Can You Actually Restore From Your Backup? 

Having a backup and having a tested backup are different states. CISA’s 3-2-1 rule for small and mid-sized business is three copies of important files, two types of storage, one copy off-site. It also asks you to test the restore. NIST has said the same for a decade: test immediately after generating the backup, so you know it worked. 

Restore it somewhere harmless (a test copy of the site, not the live one) and see what you get. You’ll learn whether the database came along, whether the uploads did, and how many hours it takes. A Tuesday afternoon is a better time to find that out than an outage. There’s more on where backup responsibility actually falls if your host and your contract disagree. 

If You Take Payments, Have You Asked Your Processor One Question? 

PCI DSS added two requirements covering payment pages, 6.4.3 and 11.6.1, mandatory since March 2025. One governs the scripts on the page; the other requires you to detect unauthorized changes to it. If you take payments through a hosted page or an embedded iframe from Stripe, Square or similar, you may qualify for the simplified questionnaire, which dropped both in January 2025. 

What it didn’t drop is a criterion you still attest to: that your site isn’t susceptible to script attacks affecting the payment flow. The cheapest way to satisfy it is written confirmation from your processor that their solution covers it. Get it in writing and keep it. Then check you actually qualify for that questionnaire. If you don’t, 6.4.3 and 11.6.1 are yours to implement in full. 

How Often Should You Run Through This? 

Monthly is the honest answer for the plugin and account items, because that’s roughly how fast they drift. Quarterly is fine for the rest. 

One more thing. If a checklist you find online tells you to add an X-XSS-Protection header, close it and find a different one. That header is deprecated and non-standard, and Mozilla’s documentation warns it can create the very vulnerability it claimed to prevent. Chrome pulled the filter in 2019. A checklist still recommending it is old enough that I wouldn’t trust the rest of it either. Content-Security-Policy is what replaced it. 

Should You Run This Yourself, or Hand It Over? 

Two or three of these you can do yourself this week. The rest need someone with server access and somewhere safe to test, which may or may not be you. The harder part either way is remembering to do it again in three months. 

That’s what ongoing management is for. On our website bundle plans the monthly pass is somebody’s job: updates applied with a restore point in place, certificates watched, backups tested, and an account manager who notices when something changes. 

If you’d rather see where you stand first, ask our development team to review the site and we’ll send a written list of what we found and what we’d fix first. Taking that list back to whoever built the site is a perfectly good outcome. 

Call (570) 321-7370 or use the contact form at intradatech.com. If something has already gone wrong, open a helpdesk ticket and we’ll work through it with you. 

Frequently Asked Questions About Website Security 

Isn’t my website security handled by my hosting company? 

Partly, and it depends who hosts you. A host secures the server, the network and usually the certificate. What runs on top — the CMS , plugins, themes, user accounts and forms — is normally yours. If you’re hosted with us on a bundle or management plan, most of this list is covered on your behalf. 

We don’t store customer data. Are we really a target? 

Not being a target is the point. Attacks on small and mid-sized business sites are automated and indiscriminate. A compromised site is useful for sending spam, hosting phishing pages or quietly injecting links, none of which needs anything worth stealing. 

What does the Chrome change actually do to my site? 

Nothing, if every address you own loads over HTTPS . If a visitor reaches an HTTP address, Chrome asks whether they want to continue. They can click through, and it won’t keep asking a regular. A first-time visitor gets the question before your page. 

Should I install a security plugin? 

It can help, though it’s no substitute for the basics. A security plugin on a site with three unused admin accounts and a plugin last updated in 2021 is treating the symptom. Do the cleanup first. And when you do add one, remember it’s still a plugin: security plugins take deeper access than most, and a conflict with something already running can take the whole site down. Same rule as any other install: snapshot first, or let us do it. 

How do I know if my site has already been compromised? 

Common signs: unexpected admin accounts, pages you didn’t create, sudden ranking drops, browser warnings, or your host getting in touch about outbound spam. If you suspect it, don’t just delete what you find. The way in is usually still open. 

Adam Post - Head Shot

ABOUT THE AUTHOR

Adam is a core member of the Intrada team, working in software engineering, Linux system administration, and web development. He splits his time between writing code and helping keep projects, and the people working on them, moving in the right direction. He likes staying close to the technical work while also being someone the team can lean on to keep things organized.

Learn More

Share this article:

Many small business owners carry a quiet assumption about cybersecurity. They believe their company is too small to matter, that criminals go after banks and large corporations, and that no one would waste time on a modest operation with a handful of employees. It is an understandable way to think, ...

Most of a website’s attention goes to the part people can see. Underneath sits a layer of infrastructure that makes the visible part work, and it keeps its own calendar:The security certificate, which produces the padlock in the address barThe programming language version, which runs the site’s code...

Our website uses cookies and analytics to enhance our clients browsing experience. Learn More /