Colour theme
Book a consultation

Keeping your business website secure

Assign website maintenance, protect administration, test recovery and check forms and integrations without assuming the hosting provider covers everything.

Illustration of a desktop computer and a website layout.

A contact form still working doesn’t tell you whether its software is supported or who can administer the website. Website upkeep needs an owner, even when most of the hosting is handled by a supplier.

Start with the platform, the accounts that control it and the information visitors send through it. That gives you a useful maintenance list without assuming every site has the same risks.

Identify what you’re responsible for

For a hosted builder, ask which platform updates, backups and recovery tasks the provider handles. You’re still responsible for account access, content, connected apps and the information you collect.

For a self-hosted content management system, record the core software, themes, plugins and hosting services. For a static site, include its build and deployment accounts, dependencies and any forms or other dynamic services.

The Cyber Centre’s website guidance covers hosting, authentication and application security. Use the parts that fit your website when agreeing responsibilities with its maintainer.

Write down who applies updates, receives alerts, renews services and responds to a suspected compromise. A design agreement doesn’t automatically include ongoing maintenance.

Keep software supported and updates checked

Attackers scan the web automatically for sites running plugins and themes with known flaws, so an outdated site can be found without anyone singling out your business. Inventory extensions and remove the ones you no longer need. Confirm that remaining components still receive security fixes. A popular, well-reviewed plugin can still be abandoned.

For WordPress, the official hardening guide includes updates, trusted software sources and backups. Avoid unofficial copies of paid themes or plugins.

Use a controlled update process with a recovery option. After updating, test forms, booking links, checkout and other important functions. Arrange urgent security fixes separately from routine cosmetic changes.

Protect the accounts around the website

Use named accounts with only the access each person needs. Enable MFA where supported, including on hosting, deployment and DNS administration. Protect recovery methods and remove old agency or contractor access.

Keep the domain and hosting under business control. Record who holds administrative access and how the business retrieves it if a supplier changes.

Review API keys, form-delivery credentials and connected services too. Secrets must stay out of public page code and source repositories. Give integrations only the permissions they need and revoke unused credentials.

Collect only what the form needs

Trace a test submission from the public page to its destination. Check whether copies are stored in the website database, a mailbox, a CRM or another provider’s logs.

Don’t ask for passwords or sensitive support details in a general contact form. Establish retention and deletion practices for stored submissions, and make the privacy notice match what the form does.

Spam protection doesn’t replace server-side validation or access controls. Have the maintainer check those controls along with the form’s delivery.

Test a recoverable backup

Confirm what a backup contains: website files, database, uploads and relevant configuration. Protect backup access separately from routine site editing.

Test restoring into a safe environment and check that the site functions. A backup job that reports success can still fail to restore. Record who can initiate recovery and what information they need from the host.

A firewall or security plugin can add protection, but it doesn’t remove the need to patch software or maintain access and recovery processes.

Investigate suspicious changes before restoring

If visitors are being redirected, unknown pages appear or a host reports a compromise, contact the responsible provider. Restrict access if necessary to protect visitors while preserving logs and evidence.

Determine how the change occurred before bringing a restored site back online. Remove any accounts or access you don’t recognize, fix the underlying issue and rotate affected credentials. A backup can contain the same compromise.

If personal information may have been exposed, involve your privacy lead. The Privacy Commissioner’s breach guidance explains PIPEDA’s reporting, notification and record requirements. Check which federal, provincial and sector rules apply to the organization.


Featured Image Credit