Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
Website hacking has become a common occurrence. Within the past few months, hackers have penetrated websites of businesses and agencies as disparate as the Venezuelan army, the UK National Lottery, the Hungarian Human Rights Foundation, KFC, and Tesco Bank.
If you run an e-commerce site, you run the risk of hackers trying to steal your customer’s personal data to commit identity theft. You may think you’re not at risk because your site does not contain any sensitive data, but that is not a good assumption. Hackers are increasing breaching sites to get access to servers they can use to send spam or attract visitors to buy their products. For example, if you search Google for the phrase “buy meds online,” the top-ranked result is a link to a London-based specialty book publisher. It’s unlikely the company is selling pharmaceuticals, but it is almost certain that hackers have compromised the site.
While there are no measures that can provide 100% protection against hackers, you can take steps to discourage them and send them looking elsewhere for a target.
Keep your software and systems updated
It is essential that all software you use on your site is current. Outdated software is one of the easiest ways hackers can use to gain access to your site by using known flaws. If you have a dedicated server, also be sure you are using the latest version of its operating system.
If you use plug-ins from a third party, be sure you apply any updates or security patches as soon as they are available. Before you install any new plug-ins, do your research to ensure they are trustworthy. Promptly remove any outdated plug-ins from your server when you no longer use them.
Use strong passwords
Hackers often try to gain access to the administrative areas of a website by trying to guess various combinations of usernames and passwords – don’t make it easy for them. Always use a combination of lower and uppercase letters, numbers and special characters when you create passwords and be sure to change them frequently. As ridiculous as it sounds, many individuals and companies still use passwords that are easy to guess, including 123456, qwerty, abcdefg and password!
Do not use the same password for every administrative function, and change your passwords regularly. Always encrypt your passwords when you store them for further protection against hackers.
Limit file uploads
Use great care if you allow users to upload files to your site, as a hacker may use this function to upload an executable file to try to get access. Prevent users from direct access to any files they upload by storing them in a location separate from the root directory and changing the permissions associated with those files to prevent users from executing them.
Conduct penetration tests
There are both free and paid tools available that you can use to conduct penetration tests to simulate hacking attacks. Consider conducting penetration tests on a regular basis to see if your site has vulnerabilities that need correcting before potential hackers find them.
Slow page loading time can be a symptom of a hacked website, so consider using a website monitoring service to detect any performance degradation promptly. You can also use this type of service to alert you when content on a page unexpectedly changes.
StatusCake Team
Share this
More from StatusCake
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026