Most organisations do not need a complex security programme before they can reduce risk. They need the basics done consistently: know what you have, patch it, control access, protect the backups and make sure people know how to report a problem.
Key takeaways
- An asset and account inventory is the foundation for every other control.
- Multi-factor authentication and least privilege reduce common attack paths.
- Patching and backup testing need a routine, not a one-off effort.
- Joiners, leavers and incident reporting are operational controls, not paperwork.
Know what you have
You cannot patch, protect or recover assets you do not know about. Maintain a list of servers, endpoints, network devices, cloud services, accounts and data stores. Record owners, versions, support dates and locations.
The inventory does not need to be perfect before work starts. It needs to be maintained and used. A spreadsheet can be sufficient for a small organisation if someone owns it.
Patch consistently
Operating systems, applications, browsers, firmware and network devices all need updates. Define a routine, assign responsibility and record exceptions. Prioritise internet-facing systems and known exploitable vulnerabilities.
Patching is not risk-free. Test critical systems, schedule maintenance windows and have a rollback position. The goal is a repeatable process, not a heroic monthly effort.
Control access
Use named accounts, remove shared logins where possible, and apply multi-factor authentication to email, remote access and administrative accounts. Review privileged access regularly.
Joiners and leavers processes should be explicit. Access granted for a project should have an end date. Accounts belonging to former staff should be disabled promptly, not left for convenience.
Protect the backups
Keep at least one backup copy separate from the production environment and inaccessible from a compromised account. Test restores and record the results. Treat backup credentials as privileged.
Ransomware often targets backups first. If the backup system uses the same domain credentials as production, an attacker who compromises the domain may be able to delete the backups too.
Secure endpoints and email
Use supported operating systems, full-disk encryption, endpoint protection and a standard build. Keep browsers and plugins updated. Configure email filtering and warn users about payment-change and credential-phishing attempts.
Endpoint protection is not a substitute for patching or access control. It is one layer among several.
Make reporting easy
Staff need a clear route to report a suspicious email, a lost device or a strange login prompt without fear of blame. A short reporting guide and a named contact are more useful than a long policy.
Record incidents and near misses. Look for patterns and fix the underlying cause. A reported mistake is an opportunity; an unreported one is a hidden risk.
Review and improve
Set a quarterly or annual review of accounts, privileged access, patching status, backup results and incidents. Use the review to agree a small number of actions with owners and dates.
Security is a moving target. The basics need to remain in place while the organisation changes systems, staff and suppliers.
Need a second opinion?
Tell us what you are trying to fix, build or buy. We will give you a clear view of the options and the next step.