Symstar Technology Insights
Small Business IT Security Checklist for London Teams
Small businesses depend on many of the same technologies as larger organisations, but often have fewer people available to manage them. Email, Microsoft 365, laptops, cloud storage and remote access can become business-critical without anyone formally owning their security and maintenance.
This checklist provides a practical starting point for London small businesses. It is designed for business owners and managers rather than technical specialists. For help with your users, devices and everyday support responsibilities, explore our small business IT support service. For local availability and onsite arrangements, see our IT support service in London.
1. Keep an accurate technology inventory
Record business computers, mobile devices, network equipment, software subscriptions, domains and cloud services. Include the assigned user, age, warranty and support status of each important device.
An inventory helps you identify unsupported equipment, unused licences and unknown devices. It also speeds up incident response because your support provider can see what should be present.
2. Protect every important account with MFA
Enable multi-factor authentication for Microsoft 365, domain management, backup platforms, accounting systems and other sensitive services. Prioritise administrator accounts and avoid sharing one administrator login between several people.
Microsoft states that MFA adds another verification method to protect access to data and applications. Its Microsoft Entra MFA deployment guidance explains how organisations can plan implementation.
3. Review administrator access
Everyday user accounts should not normally have administrator permissions. Keep privileged access limited to people who need it, review it regularly and create a documented recovery process in case an administrator becomes unavailable.
For Microsoft 365, check Global Administrator and other powerful roles. Remove outdated accounts and ensure that emergency access is controlled rather than improvised.
4. Create a reliable starter and leaver process
Prepare a checklist covering equipment, licences, email, Teams, SharePoint, business applications and security training. When someone leaves, disable access promptly, preserve required business information and recover company devices.
Clear ownership between management, HR and IT prevents accounts from remaining active unnecessarily.
5. Keep devices and applications updated
Operating systems, browsers, productivity software and security tools should receive supported updates. Replace devices that can no longer run a supported operating system or that regularly disrupt work.
A managed patching process should show which devices are compliant and identify machines that have been offline or unable to update.
6. Use suitable endpoint protection
Business computers need properly configured protection against malicious files, suspicious behaviour and other threats. Alerts must be reviewed by someone; installing software without monitoring it can create a false sense of security.
Consider whether personally owned devices can access business data and what controls apply to them. Microsoft provides Business Premium security resources covering devices, MFA and managed access.
7. Strengthen email security
Email remains a common route for fraudulent payment requests, credential theft and malware. Configure anti-phishing controls, protect your domain and train staff to verify unusual requests using a separate communication method.
The NCSC’s guidance on how to secure business email forms part of its current small-organisation security guidance.
8. Review Microsoft 365 sharing
Check who can create public or anonymous sharing links, which external guests have access and whether old Teams or SharePoint sites are still required. Sensitive data should be available only to authorised users.
Licence choice alone does not secure Microsoft 365. Settings, permissions and everyday administration all need attention. Symstar provides Microsoft 365 security support for UK businesses.
9. Separate backup from everyday cloud storage
Understand how deleted, encrypted or overwritten information would be recovered. Document which Microsoft 365, server, application and endpoint data is backed up, where copies are stored and how long they are retained.
Test representative restores instead of relying only on a successful-job notification. The NCSC’s small-organisation guide highlights backing up data as a core protective measure. See Symstar’s backup and disaster recovery services.
10. Secure remote and mobile working
Apply consistent controls whether staff work in a London office, from home or while travelling. Business devices should use encryption, screen locking, updates and secure access. Lost or stolen devices need a documented reporting and response process.
Avoid making sensitive services directly available to the internet without appropriate protection and monitoring.
11. Prepare an incident response plan
Write down who should be contacted if email is compromised, a device is infected, data becomes unavailable or a fraudulent payment is suspected. Include internal decision-makers, your IT provider, insurer and relevant suppliers.
The Information Commissioner’s Office provides guidance on responding to a personal data breach. Not every incident is reportable, but businesses should be ready to assess the circumstances quickly and obtain appropriate advice.
12. Test recovery and review the plan
Run a simple exercise: assume the office internet is unavailable, a key Microsoft 365 account is compromised or an important file set has been encrypted. Can staff contact the right people? Can essential work continue? Can data be restored?
Repeat the review after major recruitment, an office move, a new cloud system or a security incident. A checklist is valuable only when it reflects the current business.
How many items can you confirm today?
Mark each item as complete, partly complete, unknown or not applicable. “Unknown” deserves attention because it usually indicates that responsibility or documentation is missing.
- Complete: the control exists, is documented and has an owner.
- Partly complete: the control exists but is inconsistent or untested.
- Unknown: evidence or ownership cannot be confirmed.
- Not applicable: record why it does not apply.
Prioritise administrator accounts, MFA, unsupported devices, backup recovery and any known security alerts. Other improvements can then be organised into a realistic plan.
