Five simple measures that prevent a good share of the security problems in a small business's systems
When people talk about security, they think of sophisticated attacks. In practice, many problems start with much simpler things: a password the whole team uses, the account of someone who left a year ago and is still active, or a user who can see and delete everything even though they only need to enter orders.
None of these is expensive to fix. They tend to stay pending because the system works and nobody takes care of it.
The minimum
- One user per person. No shared accounts like "admin" or "office". If everyone logs in with the same user, nobody knows who did what, and changing the password means telling everyone.
- Permissions by role. Each person sees and does what they need for their job. Whoever enters orders doesn't need to delete customers or see invoicing.
- Two-factor authentication on what matters. A code on the phone on top of the password, at least for email, system administration and the bank. It stops most logins with stolen passwords.
- Access granted and removed the same day. When someone joins or leaves, their access is created or closed that day. A list of who has access to what helps nothing slip through.
- An activity log. The system should record who made each change and when. It helps find mistakes, not just attacks.
Where to start
With a list: which systems the company uses, who has access to each one and with what permissions. With that in view, the accounts that shouldn't be there and the excess access show up on their own.
Do you know today who has access to each of your company's systems? If the answer takes a while, get in touch and we'll review it together.




