3-2-1 Backup Strategy: How to Never Lose Your Data
Learn what the 3-2-1 backup strategy is, how to apply it to your website, and how to confirm your backups actually work with a restore test.
View →Learn the essential defensive measures that protect your site, including updates, two-step verification, HTTPS, security headers, backups and monitoring, with a checklist.

Website security is not a single setting; it is the sum of measures that complement one another, such as keeping software updated, strong authentication, correct configuration, backups and monitoring. As a site owner, your goal is not to recognize every threat one by one, but to close the common weak points and be able to recover quickly when something goes wrong. This guide walks through the essential defensive measures that anyone running a corporate site, an online store or an admin panel can apply, in the form of a checklist.
A site that relies on a single measure is exposed the day that measure is skipped. In a layered approach, each layer covers the situation where the previous one fails: up-to-date software reduces the chance of a vulnerability, a strong password and two-step verification make account takeover harder, a firewall filters suspicious traffic, and a backup provides a way back in the worst case. For businesses with limited budget and time, the right order is to set up the basics first (updates, passwords, HTTPS, backups), then add monitoring and additional protection layers.
Most security vulnerabilities come from gaps that were published years ago and for which fixes already exist. Content management systems, plugins, themes, libraries, PHP and the server operating system should all be updated regularly. Delete the plugins and themes you do not use; removing them shrinks your attack surface better than merely deactivating them.
The healthiest approach is to make these updates part of a weekly or monthly maintenance routine rather than a one-time task.
Account takeover is one of the most common problems, even for small sites. The fix is simple, but it requires discipline.
Serving all pages over HTTPS encrypts the traffic between the visitor and the server. We explain what a certificate is and how to install one in our article what is an SSL certificate. Once a certificate is installed, permanently redirect HTTP requests to HTTPS, and make sure the certificate renews automatically.
Security headers that can be added to your server's responses make the browser behave more cautiously:
| Header | What it does |
|---|---|
| Strict-Transport-Security | Forces the browser to connect to the site only over HTTPS |
| Content-Security-Policy | Limits which sources the page may load scripts, images and styles from |
| X-Content-Type-Options | Prevents the browser from guessing the file type |
| X-Frame-Options or frame-ancestors | Restricts displaying your site inside frames on other pages |
| Referrer-Policy | Determines which address information is shared when going to other sites |
Using Secure, HttpOnly and an appropriate SameSite value on cookies is also important for session security. Roll out the content security policy gradually; otherwise a legitimate script may be blocked and the page may break.
Forms, search boxes, URL parameters and uploaded files are data that comes from outside, and they must always be validated. If you are developing or commissioning your own software, make sure these principles are applied:
include or require path; if needed, match it against a fixed whitelist.session.upload_progress.enabled turned off; if upload progress is needed, handle it on the browser side.These points also make a good checklist of questions for businesses that have software built: ask your developer about these principles.
A web application firewall (WAF) blocks known malicious request patterns before they reach your site. Rate limiting slows down bots that send a large number of requests in a short time. A CDN or DNS-based protection service provides both of these features as well as a buffer against heavy traffic. On the server side, a good foundation is to keep only the necessary ports open, allow SSH access only with keys and restricted access, and limit admin panels to specific IP addresses where possible.
No measure provides zero risk, which is why the final layer of security is the backup. A backup should not sit on the same server as your site, it should be taken regularly, and a restore should have been tested. For the detailed method, see our 3-2-1 backup strategy article.
When a problem occurs, you need log records to understand what happened. Record login attempts, administrative actions and server errors. It is safer to keep these logs somewhere separate from the site itself. File change monitoring, downtime monitoring and certificate expiry alerts also provide early warnings.
Prepare a short incident response plan in advance for a possible breach:
The server on which the site runs is at least as important as the application. Do not keep file and folder permissions unnecessarily broad: the fewer folders the web server can write to, the more limited the damage when a vulnerability appears. Configuration files, passwords and access keys should be kept outside the web root or somewhere not directly accessible. Version control folders, old backup files (.zip, .sql) and test files should not be left on the live server; they are often forgotten, and the information they contain can cause problems.
Every counter, chat box, map, advertising and analytics script on your site is someone else's code, and it runs on your page. Loading a script from an untrusted or abandoned source brings a risk into your page that is outside your control. For this reason, use only the external scripts you really need, remove those you no longer use, and where possible load them from trusted sources with a pinned version. A content security policy reduces this risk by clearly defining which sources are allowed. When buying a plugin or theme, check the developer's update history and support status; packages circulating as “free cracked versions” often contain malicious code, so stay away from them.
No matter how strong the technical measures are, a single employee clicking a link in a fake email and entering their password can get past the entire defense. For this reason, build a short awareness culture within your team:
| Priority | Measure | Effort |
|---|---|---|
| Immediately | Updates, two-step verification, backups, HTTPS | Low |
| This month | Simplifying permissions, security headers, removing unused plugins | Medium |
| This quarter | WAF and rate limiting, daily monitoring, incident response plan | Medium |
| Ongoing | Code review, dependency updates, awareness | Regular |
Security is not a one-time job but a regular habit: update, restrict permissions, verify, back up and monitor. If you would like to review your site's security status together, you can contact us.
Yes. Automated scanning bots look for vulnerabilities regardless of the site's size. That is why small sites too should take the basic measures such as updates, strong passwords and backups.
No single measure is enough on its own, but the ones that make the biggest difference are keeping software up to date, using two-step verification and having a working backup.
No. HTTPS encrypts traffic, but it does not prevent software vulnerabilities or weak passwords. It should be used together with the other measures.
It is not mandatory, but it is a useful additional layer, especially for e-commerce and panel-based sites, because it filters known malicious requests and slows down bots.
Put the site into maintenance mode, change all passwords, restore a clean backup, update the software and investigate how the intrusion happened using the logs.
Hosting, security, backups, SSL certificates and version upgrades.
Learn what the 3-2-1 backup strategy is, how to apply it to your website, and how to confirm your backups actually work with a restore test.
View →
Learn what SPF, DKIM and DMARC records do for business email, how to set them up correctly and how to test them so your messages stop landing in spam.
View →
What is an SSL certificate, and what types are there? A step-by-step HTTPS switch, common post-migration issues, HSTS and renewal tips for your site.
View →We would like to use Google Analytics cookies to understand how the site is used. If you decline, no statistics cookies are set. Details