Hosting & Maintenance 9 min read

Website Security & Managed Hosting: Infrastructure Guide

Website security works in layers: TLS encryption, a firewall and CDN, fast patching, least-privilege access with 2FA, malware scanning, site isolation, monitoring, and an incident plan. A managed host covers most server-level layers. You still own user accounts, passwords, and which plugins go on your site.

Shield illustration showing the layers of website security on managed hosting

Key takeaways

  • Website security is 8 layers, not one tool: TLS, a WAF and CDN, patching, access control, malware scanning, isolation, monitoring, and incident response.
  • 91% of the 11,334 new WordPress vulnerabilities found in 2025 were in plugins, according to Patchstack. Your plugin list is your attack surface.
  • For heavily targeted flaws, Patchstack puts the weighted median time to first exploit at 5 hours. Monthly patching alone is too slow for those.
  • A managed host secures the server. You still own your passwords, your user list, and which plugins you install.

Most website security advice is a shopping list: get SSL, install a security plugin, done. That covers maybe two of the layers that matter, and it skips the uncomfortable question of who’s responsible when something gets through.

This guide walks through each layer, what it actually stops, and where the line sits between what a managed host handles and what stays on your side of the table.

What are the layers of website security?

Website security works in layers, so a failure in one doesn’t hand an attacker the whole site. The eight that matter for most business sites are encryption, edge filtering, patching, access control, malware scanning, isolation, monitoring, and incident response.

No single layer is enough. A firewall won’t save a site whose admin password is “Spring2024,” and perfect passwords won’t help if a plugin has an unpatched hole that doesn’t require logging in at all. The point of stacking them is that each one covers for gaps in the others.

1. TLS encryption

TLS (the “S” in HTTPS) encrypts traffic between the visitor’s browser and your server, so logins, form submissions, and payment details can’t be read in transit. It’s the baseline. Certificates should renew automatically, and every page, not just checkout, should force HTTPS.

2. Web application firewall and CDN

A web application firewall (WAF) sits in front of your site and blocks known attack patterns, like SQL injection attempts and bad bots, before they reach your server. A CDN in the same layer absorbs traffic spikes and floods. Together they filter out a lot of automated noise. They’re also how hosts can block a newly disclosed exploit with a rule while the real patch is still being written.

3. Updates and patching

Patching is where most sites are won or lost. Patchstack’s research makes the point plainly:

91%

Of the 11,334 new vulnerabilities found in the WordPress ecosystem in 2025, 91% were in plugins and only 6 were in WordPress core.

Patchstack, State of WordPress Security in 2026

The same report found that 46% of vulnerabilities weren’t fixed in time for public disclosure, and that roughly half of high-impact vulnerabilities were exploited within 24 hours of being disclosed. That changes how you should think about updates. A monthly update window is fine for most patches, but critical fixes need to go out the day they’re released, and a WAF rule has to cover the gap when no patch exists yet.

Patching covers more than plugins. The server’s operating system, PHP version, and database software all need updates too. Fewer plugins also means fewer things to patch, which is why plugin discipline is a security decision, not just a performance one.

4. Least-privilege access and 2FA

Least privilege means every account gets only the access it needs. Your blog writer doesn’t need administrator rights, and the freelancer who finished a project last year doesn’t need an account at all. Two-factor authentication on every admin login stops most stolen-password attacks cold. Server access should use SSH keys, not shared passwords, and be limited to the people who actually manage the server.

5. Malware scanning

Scanning checks your files and database for injected code, unexpected changes, and known malicious patterns. It won’t prevent an infection, but it shortens the time between “we got hit” and “we know we got hit,” which is often the difference between a quick cleanup and weeks of spam pages indexed under your domain.

6. Isolation

Isolation means one compromised site can’t reach another. On cheap shared hosting, sites often share a user and file system, so an infected neighbor can spread to you. Good managed hosting runs each site in its own container or account, with separate credentials and file permissions that stop a hacked plugin from writing outside its own folder.

7. Monitoring

Monitoring is how you notice something’s wrong before your customers do. Uptime checks catch outages. Log monitoring catches the things that come before an attack: a spike in failed logins, a new admin user nobody created, files changing at 3 a.m.

8. Incident response

Incident response is the plan for when a layer fails. Who gets alerted, who takes the site offline if needed, how it gets cleaned or restored from a backup, and how the hole gets closed so it doesn’t happen again. Without a plan, the first hour of an incident is spent figuring out who to call.

Want someone to check your site’s security?

Free 30-minute call. No pitch, no pressure.

Book a free call

What does a managed host handle, and what do you still own?

A good managed hosting provider handles the infrastructure layers: the server, its patches, network filtering, isolation, and server monitoring. You still own the decisions only you can make, like who gets an account, what passwords they use, and which plugins go on the site.

The exact split depends on the plan, but this is the typical shape:

LayerManaged host typically handlesSite owner still owns
TLSIssuing and renewing certificatesNot embedding insecure third-party scripts
WAF and CDNRunning the firewall and its rule setReporting unusual traffic or blocked legitimate users
PatchingServer OS, PHP, database softwareApproving plugins and removing ones you don’t use
AccessServer access and SSH keysSite user accounts, roles, passwords, and 2FA
Malware scanningServer-level scansActing on findings in your own content and uploads
IsolationSeparating sites and file permissionsNot reusing credentials across sites
MonitoringServer uptime and resource alertsKeeping contact details current so alerts reach someone
Incident responseServer recovery and backupsBusiness decisions, customer communication, legal duties

The patching row hides a gap. Plenty of hosts patch the server and leave plugin and theme updates to you. Since plugins are where most vulnerabilities live, that leaves the biggest risk with the person least likely to have time for it. That’s the job ongoing maintenance is meant to cover.

How does ongoing maintenance fit into website security?

Ongoing maintenance closes the gap between server security and site security. They cover plugin and theme updates, user account cleanup, and the monitoring that tells someone a form broke or a file changed. Hosting alone usually stops at the server.

Our ongoing support and retainers bundle the two so there’s no handoff in the middle. Every plan includes managed hosting, maintenance, and security. The Basic plan covers security and plugin updates, uptime monitoring, and monthly backups. Standard and Pro add monthly dev hours for fixes, and Pro adds performance optimization and a dedicated point of contact.

Security also starts earlier than hosting. A site built with a short, deliberate plugin list and clean custom code has less to patch for its whole life. That’s part of how we approach WordPress development: fewer moving parts to update over the life of the site.

What should you ask a host about website security?

Ask them to name what they handle at each layer, in writing. Vague answers like “enterprise-grade security” don’t tell you whether they update your plugins, isolate your site, or have a plan for a breach.

  • Do you update plugins and themes, or only the server?
  • How fast do you apply critical security patches after release?
  • Is there a WAF, and who maintains its rules?
  • Is my site isolated from other customers’ sites?
  • Where are backups stored, and how often have you tested a restore?
  • If my site is hacked, what do you do, and what does it cost?

If they can answer those clearly, you’ll know exactly what’s still on your list.

The bottom line

Website security is a stack of layers, and a managed host can carry most of the infrastructure ones for you. The plugin updates, user accounts, and day-to-day judgment calls still need an owner, and since most vulnerabilities live in plugins, that owner matters most. Pick a setup where every layer has someone’s name on it.

If you’d like hosting, updates, and security handled by one team, look at our support and retainer plans, or book a free call and we’ll walk through your current setup. If you’re an agency looking for a partner to keep client sites patched and secure under your brand, book a call and we’ll talk through white-label work.

Common questions

How do you check website security?

Start by confirming every page loads over HTTPS, then check that the CMS, plugins, and themes are current and that no admin accounts are unused or missing 2FA. Run a malware scan with a free scanner like Sucuri SiteCheck or a security plugin, and ask your host, in writing, what it handles at each layer.

Is managed hosting more secure than shared hosting?

Usually, yes. Managed hosting typically isolates each site, patches the server for you, and runs a firewall and monitoring. Cheap shared hosting often puts many sites under one account, so one infected site can affect others. The real difference depends on the plan, so ask what each layer includes.

Who is responsible for website security?

Both the host and the site owner. The host is responsible for the server, network, and isolation between sites. The owner is responsible for user accounts, passwords, and which plugins are installed and updated, unless a maintenance plan takes that on. Get the split in writing so nothing falls between the two.

What is a website security certificate?

A website security certificate is an SSL/TLS certificate, a small data file that proves a site’s identity and lets the browser encrypt traffic to it. It’s what puts HTTPS and the padlock in the address bar. It protects data in transit, but it doesn’t stop outdated plugins, weak passwords, or malware.

Have something to build? Let's talk.

Free 30-minute call with no pitch and no pressure. We'll talk honestly about what you need and whether we're the right fit.

Book a free call

Our Work

All Work

Riesgo Pro

SaaS / Apps

A KYC compliance platform for financial institutions. It covers watchlist screening, real-time risk scoring and remote client onboarding.

View more

Realtor Pro

SaaS / Apps

A SaaS platform for real estate developers. It has sales tracking, payment plans, Stripe payments, e-sign documents and accounting integrations.

View more

RREAF Holdings

WordPress

A real estate investment firm site with flexible property templates and custom filtering. The agents manage it themselves.

View more