I explain what a firewall and a web application firewall do in hosting. I show where they sit and give a checklist you can use this week.
What a firewall and WAF do
A firewall limits which connections reach your server, and a web application firewall, or WAF, inspects web requests before your app runs. The firewall filters ports and addresses, and the WAF sits in front of your web server to filter HTTP and HTTPS.
A VPN is a private encrypted connection used for admin access. An IP address is the numeric address of a device on the internet.
Why this matters
Outages often start as small spikes in bad traffic. A WAF can stop common attack patterns like injection and cross-site scripting, and a firewall shrinks your attack surface so you get cleaner logs and fewer surprises.
How I place protections
I put the WAF in front so all website traffic passes through it first. I configure the server firewall to allow only the ports the site needs (usually 80 for redirects and 443 for HTTPS), and I restrict admin ports (like SSH or RDP) to known locations or put them behind a VPN. I enable rate limits on logins and forms, and I keep tested backups.
What to do this week
- Confirm you have a WAF in front of your site.
- Confirm a firewall is active on the server. Close all public ports you don't need. Keep ports 80 and 443 open for web traffic, and restrict admin ports (for example, SSH or RDP) to known IPs or place them behind a secure VPN. Before changing firewall rules, schedule a maintenance window and make sure you have console or out-of-band access in case you lock yourself out.
- Force HTTPS and redirect all HTTP traffic to HTTPS. Disable older protocols and ciphers if your host offers it.
- Turn on core WAF rules for injection and cross-site scripting. Add rate limits and bot checks on login, search, and contact forms.
- Enable logging and alerts for repeated blocks and firewall rule changes. Review weekly.
- Make a fresh backup, then perform a test restore. Write the steps so anyone on your team can follow them.
- Run a safe check. Request a nonsense URL with the word admin in it and expect a simple block page (for example, a 403), not a detailed error.
Ongoing monitoring
Watch blocked request and error trends, tie them to recent changes, and keep your CMS, plugins, and server packages updated.
How I can help
If you want steady protection and care, my Security and Compliance WAF and Firewall and Hosting and Infrastructure Web Hosting cover the setup. My Web Design and Development Maintenance Plans and Website Updates keep rules current, and AppWT Analytics reports AI referrals and AI crawlers separately.
Get the next one in your inbox
Pick your topics and how often, from weekly to quarterly. I send a confirmation email first, and you can change or stop it any time.
Get more like this by emailMore in Hosting, Maintenance & Website Care
Log rotation and storage
I show a practical log retention plan that keeps insight while controlling storage and risk.
Automate SSL renewals
I show how I set up automatic SSL renewals and add watchdogs to prevent outages.
CDN tuning for a live platform
I show how I tuned a CDN on a live platform and the checks you can reuse this week.
3-2-1 backups for peace of mind
I show how to set up 3-2-1 website backups with clear steps and a checklist to prove you can restore.









