Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My team works from home and I do not know what security the business actually needs

Short answer

For a small remote team, the biggest wins are the dull ones: two-step verification on email and key accounts, unique passwords in a password manager, updated and encrypted devices, files shared only with named people, and a checklist for when someone joins or leaves. Do those before buying any security product.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • People log in to company tools from home Wi-Fi and personal phones and I have no rules for it.
  • Passwords are shared in chat.
  • I am not sure who still has access after someone left.
  • Files are shared by link and nobody knows who can open them.
  • A client or insurer asked what security the company has and I had no answer.

Why does this happen?

  1. The office used to be the security

    In an office, a shared network and a few machines were the whole perimeter. When people moved home, the company's data ended up on many devices and accounts nobody listed.

  2. Email and a few accounts hold almost everything

    NCSC says to secure your email first, then review your other important accounts, and that two-step verification can stop criminals who know the password.

  3. Access is added quickly and never removed

    NCSC advises removing or disabling accounts that are no longer needed and reviewing access to important accounts every few months. In small companies that review rarely happens.

  4. Devices and shared files carry their own risks

    Unencrypted laptops and public links to files are covered on their own pages, because each has its own fix.

What can I do about it today?

  1. Protect email accounts firstTurn on two-step verification for every mailbox, starting with owners and anyone who handles money or customer data.
  2. Move passwords into a password managerStop sharing passwords in chat. Each person gets a named login and shared accounts live in the manager.
  3. List the tools that hold company dataEmail, files, accounting, customer records, code, hosting, domain. Write down the owner of each and who else has access.
  4. Agree a joiner and leaver checklistOn day one a person gets named access. On their last day each item on the list is switched off the same day, and the shared passwords they knew are changed.
  5. Set a minimum for devicesUpdates on, disk encryption on, screen lock on, and no company data kept only on a personal device.
  6. Decide who to callWrite on one page who to tell if a phone is lost or someone clicked a bad link, so people report fast instead of hiding it.

When should I bring someone in?

  • A client, insurer or tender asks for written security answers.
  • You suspect an account was taken over.
  • You are hiring remote developers and do not know what access to give them.

How do I handle it?

  1. Ask what would hurt mostI start with the data and accounts whose loss would stop the business, not with a generic checklist.
  2. Fix in order of effectSign-in protection, access review, devices, sharing, then backups, one step at a time.
  3. Keep it small enough to followA few rules in plain language that your people will actually keep.
  4. Leave a written baselineA short document you can show a client or insurer and update.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Does my team need a VPN?

It depends on what your team connects to. For most small teams the first gains come from sign-in protection and device basics, and I would decide on a VPN after looking at your actual systems.

Is a security product enough?

No product replaces access control and habits. Tools help once the basics are in place.

How often should I review all this?

NCSC suggests reviewing access to important accounts every few months. Put it in the calendar.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.