Skip to content
ENS.EG

Protecting a Company Website from Being Hacked: What to Actually Ask

17 Nov 2026

Most websites are not breached by a clever attack. They fall to an outdated plugin, a reused password, or an admin panel open to the world. A guide for the business owner, not the programmer: what actually protects a site, what to ask your developer or host for, and what to do if the site has already been hacked.

You usually find out a website was hacked in an embarrassing way: a customer sends a screenshot of a strange advertising page, Google shows a warning next to your name in search results, or company email starts landing in spam because the server is sending messages you know nothing about. In every case the damage hits trust first.

The good news is that most of the breaches we see on company websites in Egypt did not need sophisticated protection to prevent. They needed simple habits that nobody kept.

Where breaches usually come from

  • Plugins or themes that have not been updated in years, especially on WordPress sites.
  • A weak admin password, reused elsewhere, or shared between several people.
  • A former developer’s account that still works after the relationship ended.
  • A form on the site that accepts file uploads without checking their type.
  • Cheap shared hosting where your site is exposed to other sites on the same server.

What actually protects a site

Regular updates

Every platform and every plugin needs security updates. The question is not “is the site secure today?” but “who is responsible for updating it every month?” If there is no named person, the answer is nobody.

Separate accounts and two-step sign-in

Each person signs in with their own account and the least access they need. Two-step verification on admin accounts stops most attempts to log in with stolen passwords. When an employee or developer leaves, their account is closed the same day.

Backups stored off the server

A backup on the same server is lost with the server. You need automatic backups kept somewhere else, and at least one real restore test. A backup that has never been restored is a hope, not a plan.

SSL and server settings

The padlock in the browser is now a baseline, but it is not enough on its own. Server configuration, keeping the admin panel hidden or protected, and limiting the size and type of uploaded files all belong to the same picture.

What to ask your developer or host

  • Who is responsible for security updates, and how often?
  • Where are backups kept, and when was a restore last tested?
  • Who can access the server and the admin panel right now?
  • How will you know the site was breached or went down, before a customer tells you?
  • What happens in the first hour after a breach?

If the site has already been hacked

Do not delete files yourself, and do not simply restore an old backup. The hole the attacker used is still there, and they will come back. The right order: change every password, keep a copy of the current state for investigation, find how they got in and close it, clean or rebuild, then ask Google to review the site so the warning is removed.

Customer data on the website

If the site collects customer data, such as quote requests, bookings or accounts, a breach is no longer only about appearances. Start by finding out what is actually stored on the site and why. Many sites keep every message a visitor ever sent, for years, in a database reachable from the same admin panel. It is better for enquiries to flow into your CRM or email and for the site to keep the minimum. Where storage is unavoidable, limit who can read it to a few accounts, with a log of who opened what.

Monitoring: knowing before the customer does

Simple monitoring that checks the site every few minutes and alerts when it goes down, plus a notice when site files change unexpectedly, is the difference between a problem fixed in an hour and one customers discover a week later. Make sure alerts reach a named person in your company, not an inbox nobody reads.

Choosing the host is part of security; read business website hosting in Egypt, and if the site runs WordPress, see WordPress vs a custom website. Ongoing monitoring is part of our support and maintenance service.

For a security review of your current site, or a recovery after a breach, send the link from start your project.

Have an idea or a system that needs building?

Tell us about your project in three short steps. We will review it and contact you to agree on the next step.

Start a project