Website cyber security for SMEs: risks, obligations and a checklist
A company website is an SME's shop window and at the same time the part of its IT that anyone on the internet can reach. It usually runs on the side: built once by an agency, put on a hosting plan, rarely updated. That is exactly what makes it attractive to attackers. This article covers the typical risks, what the Swiss Data Protection Act requires, how to split responsibility with your hosting provider and agency, and what belongs on a checklist.
- According to Verizon's 2026 report, 31 percent of the breaches it examined started with an exploited vulnerability. For the first time, this route is ahead of stolen credentials.
- In 2025, 11,334 new vulnerabilities were reported in the WordPress ecosystem, 91 percent of them in plugins. 46 percent had no patch yet when they were disclosed.
- The Swiss Federal Office for Cybersecurity (BACS) advises immediate updates, two-factor login and admin access limited to known IP addresses.
- The Swiss Data Protection Act requires risk-appropriate data security in line with current technology. Intentionally ignoring the minimum requirements can lead to a fine of up to CHF 250,000.
Why the company website is a way in
A website is reachable around the clock and is constantly scanned by automated tools for known vulnerabilities. Verizon's 2026 Data Breach Investigations Report, which covers cases from November 2024 to October 2025, names vulnerability exploitation as the most common way in for the first time: 31 percent of the breaches examined started this way.
The Swiss Federal Office for Cybersecurity (BACS) names two common ways websites get hacked: stolen credentials for FTP or the admin interface, and outdated content management systems such as WordPress, Joomla or Typo3 and their plugins. Attackers then place malware or phishing pages on the site. In January 2026, the BACS described hacked sites that showed false content only to Google's crawler. Anyone opening the site directly saw the original, so the manipulation often went unnoticed for a long time.
The OWASP Top 10, the best-known list of risks for web applications, points the same way. In the 2025 edition, broken access control remains in first place, and security misconfiguration has risen to second.
Outdated CMS and plugins
Most SME websites run on a CMS, often WordPress. The core is rarely the problem. According to Patchstack's annual report, 11,334 new vulnerabilities were reported in the WordPress ecosystem in 2025, 42 percent more than the year before. 91 percent affected plugins, 9 percent themes, and only six were in the core, all low priority. 46 percent of the vulnerabilities had no patch yet when they were disclosed. For heavily exploited vulnerabilities, the median time to mass exploitation was five hours.
The consequence: updates should be automatic wherever the CMS allows it. The BACS recommends installing new versions immediately and switching on automatic updates. Every plugin is extra code that someone has to maintain. Remove what nobody needs and replace plugins whose vendor no longer ships updates. If a known vulnerability has no patch yet, switching the plugin off is often the only safe choice. How quickly a vulnerability is attacked after disclosure is shown by the case of SSHole in OpenSSH.
Certificates, forgotten subdomains and test instances
An expired TLS certificate triggers a browser warning and drives customers away. The risk is growing: since 15 March 2026, a public certificate is valid for at most 200 days, from March 2027 for 100 days and from March 2029 for only 47 days, as decided by the CA/Browser Forum. If you renew certificates by hand, switch to automatic renewal.
Every public certificate is also recorded in public Certificate Transparency logs that anyone can query. That makes the subdomain of an old test installation or a 2021 campaign site visible to attackers too. Such instances often keep running on outdated software. A DNS record that points to a deleted cloud service is dangerous as well. Microsoft describes how attackers register the freed name with the provider, serve their own content under your subdomain and even obtain a valid certificate for it. The consequences range from phishing in your name to cookie theft.
CyberTell's attack surface analysis gathers from public sources which subdomains, IP addresses, open ports and services belong to your domains. It reports certificates that expire in less than 21 days, domains close to expiry, new subdomains since the last run and DNS records that point nowhere.
Admin access and security headers
The login to the admin interface is the most valuable target on a website. The BACS recommends two-factor login, access limited to known IP addresses, encrypted transfer via SFTP instead of FTP and a clean computer for the webmaster. A web application firewall can also stop attacks before they reach the application.
Security headers are instructions from the server to the browser. The OWASP cheat sheet on HTTP headers recommends, among others, Strict-Transport-Security (encrypted connections only), a Content Security Policy, protection against being embedded in other sites and X-Content-Type-Options. Headers such as Server or X-Powered-By that reveal software and version should go. Mozilla's free HTTP Observatory shows whether your site sets these headers and gives a grade from A+ to F. Most headers can be configured with the hosting provider or in the CMS without rebuilding the site.
Email domain and forms
Your domain serves not only the website but also email. Without SPF, DKIM and DMARC, fraudsters can send mail that appears to come from your address. In April 2025, the BACS warned of a wave of CEO fraud against Swiss municipalities and recommended setting up these three sender verification mechanisms. A strict DMARC policy (p=reject) limits misuse of your identity, but according to the BACS it cannot rule it out entirely.
Forms are abused too. In subscription bombing, attackers enter a victim's address en masse into the newsletter and contact forms of reputable companies. The flood of confirmation emails is meant to bury the one warning that matters, for example about a payment from a hijacked account. The BACS advises website operators to protect forms with a CAPTCHA, limit submissions per IP address and time period, and send confirmations only after that. Email addresses do not belong on the page in plain text.
Website operators are also phishing targets themselves. In April 2026, the Federal Data Protection and Information Commissioner (FDPIC) warned of fake emails in its name that accuse operators of breaching the Data Protection Act and ask for data or money.
Leaked credentials
According to the BACS, attackers often steal FTP and CMS credentials with malware on the administrator's computer. Passwords stolen from another service and also used for the website are just as dangerous. After a hack, the BACS advises checking every computer used to manage the site first and only then changing the passwords. Otherwise the attackers quickly get back in.
CyberTell's dark web monitoring checks via HIBP, DeHashed and LeakCheck whether accounts on your domain appear in known data breaches. Hits get a status and a comment, and passwords are not displayed. For a first look, the free risk analysis checks a single email address against known data breaches, without an account.
What the Data Protection Act requires
As soon as a website processes personal data, for example through a contact form, a shop or a customer account, the Swiss Federal Act on Data Protection (FADP) applies, in its revised version since 1 September 2023. Article 8 requires risk-appropriate data security through technical and organisational measures. The Data Protection Ordinance adds detail: the measures depend on the current technology and the cost, they must ensure confidentiality, availability, integrity and traceability, and they are reviewed for as long as the processing lasts. A CMS that has not seen an update in years is hard to justify as current technology.
Article 19 requires you to inform the people concerned: who is responsible and how to reach you, what the data is used for, who receives it and in which countries. On a website, this is usually done in the privacy policy. According to the FDPIC, the law does not prescribe a fixed form. If a hack is likely to result in a high risk for the people concerned, it must be reported to the FDPIC as soon as possible. Anyone who intentionally fails to meet the minimum data security requirements can be fined up to CHF 250,000, upon complaint.
Who patches what: hosting provider, agency, company
Many SMEs assume the hosting provider takes care of security. Usually, though, it only runs the servers and the platform, while the CMS and the plugins remain the job of the customer or its agency. Clarify the split in writing before something happens. How to assess providers in a structured way is covered in the article on supplier risk in SMEs.
-
Updates
Who installs updates for server, CMS, themes and plugins, how soon after a security notice, and who checks afterwards that the site still works?
-
Access
Who has admin, FTP and DNS access? Have former employees and previous agencies been removed, and is two-factor login active everywhere?
-
Backups
How often are backups made, where are they stored, and has a restore ever been tested?
-
Incident
Whom does the hosting provider call when the site is hacked, who cleans it up, and who decides on reporting to the FDPIC?
Checklist and where CyberTell helps
The following points cover the most common gaps. Most of them are one-off work, some need regular checks. The attack surface analysis takes over these checks for everything visible from outside: it can run on a schedule, shows the changes since the last run and tracks findings with severity and status. Besides certificates and subdomains, it reports known vulnerabilities in exposed services, outdated TLS versions, admin interfaces reachable from the internet and missing SPF or DMARC. It does not check security headers or individual plugins. For those, use the HTTP Observatory and your CMS's update report.
-
Build an inventory
List all domains, subdomains and test instances and switch off what is unused.
-
Automate updates
Keep CMS, themes and plugins current, remove what is unused.
-
Harden admin access
Two-factor login, one account per person, access limited by IP, SFTP instead of FTP.
-
Check certificates and DNS
Set up automatic renewal, delete orphaned DNS records.
-
Headers and forms
Set security headers, protect forms with a CAPTCHA and a limit per IP address.
-
Protect the email domain
Set up SPF, DKIM and DMARC, move DMARC step by step to quarantine or reject.
-
Update data protection
Review the privacy policy and record who reports an incident to the FDPIC.
Frequently asked questions
Is a small company website really a target?
Is my hosting provider responsible for my website's security?
How often should I update WordPress plugins?
Do I need a privacy policy on my website under Swiss law?
Do I have to report a hack of my website?
Sources
- Verizon: 2026 Data Breach Investigations Report
- OWASP Top 10:2025
- The Register: OWASP Top 10, broken access control still tops the list (2025-11-11)
- Patchstack: State of WordPress Security in 2026
- BACS: Massnahmen zum Schutz von CMS
- BACS: Webseite gehackt
- BACS: Woche 3, Wenn Hacker Suchmaschinenoptimierung betreiben (2026-01-20)
- BACS: Woche 6, Subscription Bombing (2026-02-10)
- BACS: Woche 17, Anhaltende CEO-Betrugsversuche gegen Schweizer Gemeinden (2025-04-29)
- CA/Browser Forum: Ballot SC-081v3, schedule of reducing validity and data reuse periods
- CA/Browser Forum: TLS Baseline Requirements
- Certificate Transparency: How CT works
- Microsoft Learn: Prevent dangling DNS entries and avoid subdomain takeover
- OWASP Cheat Sheet Series: HTTP Security Response Headers
- Mozilla: HTTP Observatory
- Bundesgesetz über den Datenschutz (DSG), SR 235.1
- Verordnung über den Datenschutz (DSV), SR 235.11
- EDÖB: Informationspflicht
- FDPIC: Warning about fraudulent emails sent in the name of the FDPIC (2026-04-07)
Attack surface. What is visible from outside – found passively
Everything this article describes can be put into practice in CyberTell — in the demo with sample data or in your own account.