How to Secure Your Website: Checklist for Singapore SMEs

On this page
Short answer: to secure your website, keep the software updated and remove what you don’t use. Protect every login with a long, unique password and multi-factor authentication, and keep tested off-site backups. Serve the site only over HTTPS with security headers, put a web application firewall in front of it, and decide in advance what you will do, and who you must tell, if something goes wrong. Many small business websites are not hacked by a person who chose them. They are hit by automated attacks on known weaknesses, often within hours of a flaw becoming public, which is why getting the basics right matters so much. Most steps below apply to any website; the WordPress-specific advice is marked.
Key takeaways
- Updates come first. Attackers start mass-exploiting heavily targeted WordPress flaws a median of 5 hours after they are made public (Patchstack, 2026).
- Plugins are the weak point. Of 11,334 new WordPress vulnerabilities found in 2025, 91% were in plugins, 9% in themes and only 6, all low priority, in WordPress core (Patchstack).
- Updates alone aren’t enough. 46% of those vulnerabilities had no fix from the developer when they were disclosed (Patchstack), which is why a firewall matters.
- Small businesses are targets too. In the Cyber Security Agency of Singapore’s (CSA) 2025 survey, almost nine in ten Singapore organisations had at least one cyber incident, yet nearly half (46%) of businesses that held back on cybersecurity said they were unlikely targets (CSA).
- You stay responsible. Under the Personal Data Protection Act (PDPA), a notifiable data breach must be reported to the Personal Data Protection Commission (PDPC) within 3 calendar days of deciding it is notifiable, and using an IT vendor doesn’t shift the responsibility (PDPC).
Why website security matters for a small business
It’s easy to think a small company website has nothing worth stealing. Attackers see it differently. A hacked site can host spam pages, redirect your visitors to scams, skim card details from a checkout, or collect the personal data your forms receive. If you sell online, use your payment provider’s hosted checkout or payment fields, so card numbers never pass through your own server.
The risk is rising. On 13 November 2026, CSA warned that monthly cyber incidents since September were three times the January to August average (CSA media statement). Globally, the average data breach now costs US$4.99 million (IBM Cost of a Data Breach Report 2026), and 31% of breaches start with the exploitation of a software vulnerability (Verizon DBIR 2026).
A hack also hurts your marketing. Google may show a warning label under your listing in search results, or a full-page warning in the browser, until you clean the site and ask for a review (Search Console Help). Google’s spam policies, which cover hacked content, say that sites that break them “may rank lower in results or not appear in results at all” (Google spam policies). A review after a clean-up can take from a few days to a few weeks (Search Console Help).
The website security checklist, in order of priority
Start at the top. The “Do now” measures close the gaps that automated attacks look for first. This order is our own recommendation, based on the sources below and on the sites we maintain.
| When | Measure | Why it matters |
|---|---|---|
| Do now | Update the CMS, plugins and themes within days | Known flaws are attacked within hours of disclosure |
| Do now | Delete plugins and themes you don’t use | Each one is code an attacker can target, even when switched off |
| Do now | Multi-factor authentication on every admin login | A stolen password alone is no longer enough |
| Do now | Long, unique passwords in a password manager | Stops password reuse and guessing attacks |
| Do now | Off-site backups, tested by restoring them | Your way back from ransomware, a bad update or a hack |
| This month | Give each person their own login with the least access they need | Limits the damage from one compromised account |
| This month | Web application firewall (WAF) | Blocks attacks on flaws that have no patch yet |
| This month | Limit login attempts and close unused entry points | Slows down automated password guessing |
| This month | HTTPS on every page, with HSTS | Protects form data and stops browser warnings |
| This quarter | Security headers | Reduces cross-site scripting and clickjacking |
| This quarter | Monitoring, uptime alerts and Google Search Console | Tells you about a problem before your customers do |
| This quarter | Lock your domain and secure the registrar account | Stops someone taking over your domain or email |
| This quarter | Remove old agency, freelancer and staff access | Third parties are a common way in |
| Plan ahead | A written incident response plan, including PDPA steps | Saves hours when every hour counts |
1. Keep everything updated, and remove what you don’t use
Singapore’s CSA tells organisations to “promptly apply security updates to Internet-facing servers” (CSA advisory AD-2026-017). For WordPress sites, the official hardening guide says to keep WordPress and every plugin up to date, and “if you are not using a specific plugin, delete it from the system” (WordPress hardening guide).
This is where many small business sites fall behind. A WordPress or WooCommerce site often collects plugins over the years, including some whose developers no longer maintain them. Patchstack found that 46% of the vulnerabilities disclosed in 2025 had no fix in time for disclosure. For those, the only protections are removing the plugin or blocking the attack before it reaches the site.
Singapore’s regulator has fined businesses for exactly this. In the FortyTwo decision, the PDPC found that failing to patch the website “increased the risks of a malicious code injection capable of capturing users’ personal data”, and imposed a S$8,000 penalty (PDPC decision).
2. Protect every login with MFA and strong passwords
Turn on multi-factor authentication (MFA) for the website admin, the hosting account, the domain registrar and the email accounts that can reset those passwords. WordPress doesn’t include MFA by default, so it needs a plugin or a login provider (WordPress brute force guide).
For passwords, the current US NIST guidance is simpler than most office rules: at least 15 characters for a password used on its own, no forced complexity rules, no forced changes every few months, and password managers should be allowed (NIST SP 800-63B-4). A password manager makes long, unique passwords easy.
Don’t use “admin” as a username, and give each person their own account. Shared logins make it impossible to remove one person’s access or see who changed what.
3. Keep backups you have actually restored
Follow the 3-2-1 rule: three copies of your data, on two different types of storage, with one copy kept off-site (CISA). Backups stored on the same server as the website can be deleted or encrypted in the same attack.
Test a restore at least every few months. A backup you have never restored is a hope, not a plan.
4. Put a web application firewall in front of the site
A web application firewall (WAF) filters malicious requests before they reach your website. Many are provided by a content delivery network (CDN), a network of servers that delivers your site from locations close to your visitors. CSA recommends web application firewalls and “virtual patching”, which blocks attacks on a known flaw while you wait for, or replace, the vulnerable plugin (CSA advisory AD-2026-017).
Ask your host or developer to limit login attempts at the firewall or CDN level. On WordPress, also block xmlrpc.php, an old remote-publishing feature, if you don’t use it. WordPress calls it “a frequent brute-force target” (WordPress brute force guide).
5. Use HTTPS everywhere, and add security headers
Every page should load over HTTPS, and the site should tell browsers to always use HTTPS with a Strict-Transport-Security (HSTS) header (MDN). Google has called HTTPS only a “very lightweight” ranking signal (Google Search Central). The bigger reason is trust: browsers warn visitors away from forms on insecure pages.
Security headers are short instructions your server sends with every page:
| Header | What it does |
|---|---|
| Content-Security-Policy | Limits which scripts can run, the main defence against cross-site scripting (MDN) |
| Strict-Transport-Security | Forces HTTPS on every future visit |
| X-Content-Type-Options | Stops browsers guessing file types (nosniff) |
| frame-ancestors (in CSP) or X-Frame-Options | Stops other sites embedding yours to trick clicks |
| Referrer-Policy | Controls what your URLs reveal to other sites |
| Permissions-Policy | Turns off browser features you don’t use, such as the camera |
You can check your own site for free with securityheaders.com or Mozilla’s HTTP Observatory. A low grade usually just means nobody has added the headers yet, and they can be added without changing how the site looks. Test a Content-Security-Policy in report-only mode first, so it doesn’t block your own analytics, chat or payment scripts.
6. Monitor for hacks, outages and Google warnings
Add your site to Google Search Console. It reports security issues Google finds and is where you request a review after a clean-up (Security Issues report). Add uptime monitoring and malware scanning, and make sure the alerts go to someone who will act on them.
7. Secure your domain and remove old access
Lock your domain at the registrar so it can’t be transferred without your approval (ICANN), and put MFA on the registrar account. Whoever controls your domain controls your website and your email.
Then review who still has access: former staff, previous agencies, freelancers and plugin vendors. Verizon found that 48% of breaches involved a third party (Verizon DBIR 2026). If a website maintenance provider looks after your site, agree in writing who updates what, and how fast.
In the Century Evergreen decision, job applicants’ NRIC (national identity card) images were left publicly accessible on the company’s website, and the PDPC held that the company “remained solely responsible” even though an IT vendor had built the site, with a S$9,000 penalty (PDPC decision).
8. Collect less data, and plan for a breach
The safest personal data is data you never collected. Ask only for what you need on forms, don’t store NRIC numbers or ID images on the website, and delete old enquiries you no longer need.
Under the PDPA, if a data breach is likely to cause significant harm, or affects 500 or more people, you must notify the PDPC no later than 3 calendar days after you determine that it is notifiable, and tell affected individuals where required (PDPC guide on managing and notifying data breaches). Fines can reach S$1 million or 10% of Singapore annual turnover for organisations with more than S$10 million in turnover, whichever is higher (PDPA section 48J).
Write down now who decides whether a breach is notifiable, who contacts the host and developer, and where the backups are. Three days passes quickly.
What to do if your website is hacked
- Don’t delete everything in a panic. Take the site offline or into maintenance mode, and keep copies of the logs.
- Change every password: website admin, hosting, database, FTP or SFTP, domain registrar and email. Turn on MFA as you go.
- Ask your developer or host to find how the attacker got in, restore a clean backup from before the attack, and patch or remove the weak point. Restoring without closing the hole only resets the clock.
- Check whether personal data was accessed, and decide whether the breach is notifiable to the PDPC.
- Request a review in Google Search Console once the site is clean.
- For help, Singapore organisations can call CSA’s Cyber Incident Helpline at 6890 9555 (CSA).
Free help for Singapore SMEs
- CSA’s free Cybersecurity Health Check takes about ten minutes and is based on the Cyber Essentials standard.
- The Cyber Essentials mark is CSA’s certification for organisations that have the basic measures in place. As of June 2026, more than 800 organisations held at least one Cyber Essentials certification (CSA).
- Eligible SMEs can get up to 70% co-funding for CSA’s CISO-as-a-Service, a consultant who helps you build a cybersecurity health plan.
How our websites score
We apply this checklist to the websites we build and maintain, including our own. On 17 November 2026, all six websites in our group scored A+ on securityheaders.com: vuetechsg.com, www.cctvsg.net, 123ledlighting.sg, 1cloudaicrm.com, vue.sg and vuedigitalsignage.com. That grade covers security headers only. It shows one layer is in place, not that a site is secure in every way, which is why the other measures in this checklist matter too. The full results are on our website security page.
Frequently asked questions
How do I know if my website has been hacked?
Common signs are unfamiliar pages or links in Google results for your site, redirects to other websites, new admin users you didn’t create, a “This site may be hacked” label in Google, warnings from your browser or antivirus, or a sudden slowdown. Google Search Console’s Security Issues report will also tell you if Google has detected a problem.
Is a free SSL certificate as secure as a paid one?
For encryption, yes. A free certificate such as Let’s Encrypt encrypts the connection just as well as a paid one. Paid certificates add things like company validation and support, not stronger encryption.
How often should I update WordPress plugins?
As soon as practical after a security update is released, and within days at most. Attacks on popular flaws start within hours, so many businesses enable automatic updates for minor and security releases, with backups and a quick check that the site still works.
Who is responsible for my website’s security, the host, the developer or me?
You are, as the business that owns the site and the data. Hosts, developers and agencies can do the work, but under the PDPA the organisation remains responsible. Put the security tasks and response times in writing with whoever maintains your site.
Does website security affect SEO?
Yes. A hacked site can be labelled in search results, show browser warnings, or drop out of results. HTTPS is a small ranking signal on its own, but a hack can undo years of SEO work in days.
Do I need to report a hacked website to the PDPC?
Only if personal data was affected and the breach is notifiable: likely to cause significant harm, or affecting 500 or more people. If it is, you have 3 calendar days from that determination to notify the PDPC.
Want us to check your website?
Security isn’t a one-off project: new vulnerabilities appear every week, so updates, monitoring and backups need to continue every month. Contact us or WhatsApp us your website address. We’ll run a free check of your security headers, software versions and exposed entry points, and tell you in plain English what to fix first. Learn more about our website security service, or see how we moved a WordPress site to a faster and more secure platform, with Google clicks up in the first days after launch, in our CCTVSG.Net case study. If you’re thinking of leaving an old, plugin-heavy setup behind, see our website migration service.
About this guide
Written by the VueTech SG team. VueTech SG is a Singapore web design, SEO and website maintenance agency that builds, secures and looks after websites for small and medium businesses. Every source was checked on 19 November 2026. This guide is general information, not legal advice; for your PDPA obligations, see the PDPC’s guides or ask a lawyer.
Sources
- Patchstack: State of WordPress Security in 2026
- Cyber Security Agency of Singapore: Singapore Cybersecurity Health Report 2025 release, media statement, 13 Nov 2026, advisory AD-2026-017
- IBM: Cost of a Data Breach Report 2026
- Verizon: 2026 Data Breach Investigations Report
- WordPress: Hardening WordPress and Brute force attacks
- NIST: SP 800-63B-4, Authenticators
- CISA: Back up business data
- MDN: Strict-Transport-Security, Content Security Policy, HTTP Observatory
- Google: Spam policies, Security Issues report, HTTPS as a ranking signal
- PDPC: Guide on managing and notifying data breaches, decisions on FortyTwo and Century Evergreen
- ICANN: EPP status codes