Security

Website security: ten basic measures that stop most break-ins

Most website break-ins are automated and exploit known holes. A guide to ten basic measures, the signs of a break-in and what to do when an incident happens.

Updated

Website security is often discussed as if it were a concern only for large companies. In reality, small business websites are the most common targets, because there are so many of them and they are often poorly maintained. Attacks are almost always automated: bots crawl the internet looking for known vulnerabilities, weak passwords and outdated software.

The good news is that most break-ins are prevented by a few basic measures handled consistently.

How are websites broken into?

The most common ways in are:

  1. Outdated plugins and themes. Once a vulnerability is published, automated scanners look for it quickly.
  2. Weak or leaked passwords. Username–password pairs leaked from other services are tried automatically (credential stuffing).
  3. Excessive permissions. Administrator accounts of former employees and suppliers are still active.
  4. An outdated server environment. A PHP version or operating system that is out of support.
  5. Abandoned test and development environments. A forgotten copy of the site on a subdomain that nobody updates.
  6. Scams and phishing. Administrator credentials are phished with a fake login page or a "domain renewal" message.

Ten basic measures

1. Update regularly

A weekly update rhythm for the CMS, plugins and themes is the single most important security measure. See the instructions in WordPress website maintenance.

2. Trim plugins and themes

Remove everything that is not used. A deactivated plugin leaves its code on the server.

3. Two-factor authentication

Turn on two-factor authentication for all administrator accounts in the CMS, the hosting control panel and the domain service. It stops the vast majority of password-based attacks.

4. Individual accounts and password management

Everyone has their own account. Shared "admin" accounts do not show who did what, and they cannot be removed when one person leaves. Passwords are kept in a password manager.

5. Least privilege

A content producer does not need administrator rights. Review users and roles every six months, and remove accounts as soon as the cooperation ends.

6. HTTPS and security headers

The whole site must run over HTTPS, and HTTP requests are redirected to HTTPS. The server should also send security headers such as Strict-Transport-Security, X-Content-Type-Options and Content-Security-Policy. Read more in Domain, DNS and SSL.

7. Web application firewall and login protection

A web application firewall (WAF) filters known attack patterns, and limiting login attempts stops password guessing. These can be provided by the hosting provider, a CDN service or a plugin.

8. Backups kept separately

If an attacker gets into the website, they must not get into the backups as well. Keep at least one copy with a different service and different credentials. See the backup guide.

9. Monitoring

Uptime monitoring, malware scanning, Search Console security notifications and file change tracking tell you about problems before customers notice them.

10. Forms and file uploads

Protect forms from spam. If files can be uploaded to the site, restrict the allowed file types and prevent uploaded files from being executed on the server.

Finland's Cybersecurity Act and NIS2

The EU's NIS2 Directive was implemented in Finland through the Cybersecurity Act, which entered into force on 8 April 2025. The act generally applies to medium-sized and larger operators carrying out activities listed in its annexes. These sectors include energy, transport, healthcare, digital infrastructure, food, waste management and parts of manufacturing. Operators within its scope must manage cyber risks systematically and report significant incidents.

Even if the act does not apply to a business directly, its requirements spread through supply chains: a customer within its scope may require its suppliers to use two-factor authentication, a documented update process and incident notifications, for example. It is a good idea to prepare for this in the maintenance agreement.

Signs of a break-in

Suspect a break-in if you notice, for example, that:

  • visitors are redirected to unfamiliar sites on mobile or when arriving from a search engine
  • foreign-language or spam pages appear in search results under your site's name
  • Search Console reports security issues or harmful content
  • there are unknown administrator accounts in the CMS
  • there are files on the server that nobody has added
  • the hosting provider reports unusual traffic or spam being sent.

What to do after a break-in

  1. Limit the damage: put the site into maintenance mode if necessary.
  2. Change credentials: the CMS, hosting, database, FTP/SFTP and the domain service.
  3. Find out how the attacker got in: server logs, update history, malware scan.
  4. Restore a clean version from a backup taken before the break-in, and fix the vulnerability before restoring.
  5. Request a review in Search Console if Google has flagged the site as dangerous.
  6. Assess your reporting obligation: if personal data may have leaked, the breach must be reported to the data protection authority (in Finland, the Office of the Data Protection Ombudsman) within 72 hours, unless it is unlikely to result in a risk. The incident can also be reported to the National Cyber Security Centre Finland.

Security is continuous work, not a one-off project. When the basic measures are written into the maintenance plan, they get done even in busy periods.

Frequently asked questions

Why would anyone break into a small company's website?

The attacker is usually not after the company itself but the website's resources. A compromised site is used to send spam, host phishing pages, spread malicious links and ads into search engines or redirect visitors to scam sites. That is why every website is a target.

How do I know whether my site has been compromised?

Typical signs include strange redirects on mobile or when arriving from a search engine, a security warning in Search Console, unknown administrator accounts, odd files on the server, foreign-language or spam pages in search results and a notice from the hosting provider about unusual traffic.

Does Finland's Cybersecurity Act apply to my business?

The act mainly applies to medium-sized and larger operators in the sectors listed in its annexes, such as energy, transport, healthcare, digital infrastructure and certain areas of manufacturing. A small company may have to follow similar practices if it supplies a customer that falls within the scope of the act. Check your own situation in the guidance of the National Cyber Security Centre Finland.

Do I need a security plugin for WordPress?

A plugin can provide a web application firewall, login attempt limits and malware scanning. Many managed hosting providers already offer the same protections at server level, in which case an overlapping plugin only slows the site down. Find out first what your hosting provider offers.

Sources

  1. National Cyber Security Centre Finland: Cybersecurity Act enters into force 8 April 2025
  2. Finnish Government: proposal to confirm the new Cybersecurity Act (in Finnish)
  3. WordPress Developer Resources: Hardening WordPress
  4. OWASP Top 10
  5. Office of the Data Protection Ombudsman (Finland)