SSL, Backups and Hosting Security

SSL protects data in transit

An SSL certificate enables HTTPS, encrypting traffic between the visitor and server. Redirect all HTTP requests to HTTPS and renew certificates automatically where possible. HTTPS does not remove malware or fix weak passwords, so it is one layer of a wider security plan.

Backups protect recoverability

Use automated backups with a retention period that matches how often content changes. Keep at least one copy outside the hosting account. Test restoration periodically; an untested backup can fail because of corruption, missing databases or incomplete archives.

Updates close known gaps

Outdated content-management systems, plugins and themes are common entry points. Apply security updates promptly, remove software you no longer use and test major updates on staging. Record changes so unexpected behavior can be traced and reversed.

Control account access

Use unique passwords and multi-factor authentication for hosting, domain, email and CMS accounts. Give each person only the access required for their role. Remove old accounts and avoid sharing a single administrator login across a team.

Monitor useful signals

Watch uptime, file changes, login attempts, malware alerts and unusual resource usage. Alerts should reach a monitored address and have a response plan. Logs are most valuable when retained long enough to investigate an incident.

Build a recovery routine

Document who controls the domain, where backups are stored and how to restore service. Include clean contact details for hosting support. A short tested recovery plan reduces downtime and rushed decisions when an issue occurs.