CYBERSECURITY / PRACTICAL GUIDE

What to check in your security

A useful security review checks who has access to your accounts and files, whether your computers are protected, and who responds when something looks wrong. Use this checklist to find gaps and decide which need attention first.

Start with the accounts and files your business depends on, such as email, payroll, and customer records. Compare who should have access with who actually has it. An employee who changed roles may still have permissions they no longer need.

Look at the settings and records behind each answer. A written requirement to install updates does not tell you whether the laptop someone uses at home has received them.

Check what protects you today.

Work through these questions with whoever manages your IT:

  • Does each employee have their own account, and has access been removed for people who left?
  • Is multi-factor authentication turned on for email, administrator accounts, and other important business accounts?
  • Who can open or change payroll and customer files, and does that access match their current job?
  • Are administrator accounts reserved for work that requires those permissions?
  • Which computers are missing updates or security protection, including laptops used outside the office?
  • Are important files backed up, and when was restoring them last tested?
  • Who receives security alerts, investigates them, and tells your business when action is needed?

Write down anything you cannot verify, and give each open question an owner so it gets answered.

Know who handles security alerts.

Security software needs someone responsible for reviewing its warnings. An unusual sign-in might be legitimate, but someone still needs to check before dismissing it.

Know who investigates an alert, who has authority to disable an account or disconnect a computer, and who contacts your business. If an IT provider and an employee share those responsibilities, document where one person's work ends and the other's begins.

Employees also need a clear way to report suspicious activity. An unexpected sign-in prompt or password reset deserves attention even if the employee has not clicked a link. Reporting instructions should explain how to reach help and what details to provide, such as the time, the affected account, and the message they saw.

When security software flags an unusual sign-in, someone still has to investigate it and decide what happens next.

Fix the biggest gaps first.

Start with signs that someone may already have access, such as an unexplained sign-in or an account still in use after an employee leaves. Look into those first, before you treat anything else as routine cleanup.

Next, address gaps that expose important accounts or computers. Missing multi-factor authentication on email, unnecessary administrator access, and overdue security updates deserve early attention. Weigh what each account can reach and how many employees a problem would affect.

For each finding, note the affected account or computer, who will fix it, and a target date. Close the item when someone verifies the change. If a fix needs more time, document what protection you will use in the meantime.

Back to resources