Colour theme
Book a consultation

Thirteen checks for a maintained security baseline

Thirteen checks that keep a small business's security basics in place, each with evidence, an owner and a date to follow up.

An open padlock surrounded by loose black keyboard keys under red and green lighting

A security baseline needs maintenance after the initial setup. Accounts change, devices reach the end of support and an alert can quietly lose its owner.

The Cyber Centre’s baseline controls offer a Canadian starting point. Work through these thirteen checks at a set time each year to confirm the basics still hold and each one still has an owner. Passing them won’t make a business immune to attack.

1. Keep the scope current

List the systems, devices and cloud services covered by the review. Record anything excluded, why it was excluded and who accepted that gap.

Look for services a department signed up for on its own since the last review, such as a file-sharing or survey tool.

2. Review cloud responsibilities

For each cloud service, name who manages access, sharing, retention and recovery. Then open the admin settings and compare one setting, such as external sharing in SharePoint, with what you agreed.

A security feature the supplier offers only helps if it’s switched on for your accounts.

3. Check sign-in and recovery

Review authentication methods and recovery routes for important accounts. Remove methods that belong to departed staff.

Use a unique password for each account, ideally from a password manager, and multi-factor authentication on email, banking and admin accounts. Change a password when there’s reason to think it’s exposed. A yearly change on its own won’t catch a password that leaked last week.

4. Verify payment-change procedures

Ask finance to walk through a supplier banking-change request. Check that they call the supplier back on a number already on file (never one given in the request), and that a second person approves the change.

Ask your bank or payment provider what fraud controls they offer. A shared codeword can help, but it shouldn’t be the only check.

5. Confirm device protection

Pick a typical laptop and check that its firewall, malware protection and anything else your baseline requires are switched on.

If something’s off, find out why before buying another security product to cover it.

6. Follow up on update failures

Review systems that missed updates, need a restart or no longer receive support. Assign the corrective work and its deadline.

Track temporary workarounds until the underlying issue is resolved.

7. Test supplier-access handoffs

Identify who decides whether a supplier gets access, which information is shared and how access ends. Take a supplier whose project finished recently and confirm their access has ended.

Keep suppliers’ emergency contact details somewhere other than the system they support, so you can reach them if it’s down.

8. Test a recovery dependency

Choose an important service and verify that its recovery plan includes the data, credentials and configuration it needs.

Restore something to a safe location and record the result. A backup brings your data back, but if an attacker copied it first, you’ll still have a breach to deal with.

9. Check remote-work arrangements

Confirm which devices and access methods staff should use for the work they do away from the office. Review any remote-access exception.

A VPN protects the connection between the device and the office. It can’t make an infected laptop safe to use.

10. Review impersonation handling

Check how staff verify an unexpected request using an established contact route. Include messages apparently sent from your own organization.

Lookalike domains are cheap to register, so buying a few similar names won’t stop impersonation. Set up SPF, DKIM and DMARC on your own domain so receiving mail servers can reject messages that only pretend to come from it.

11. Practise a reporting decision

Use a harmless, role-specific example and ask staff to show the reporting route. Check that someone receives and acts on the report.

If someone gets it wrong, improve the instructions. Don’t blame the person.

12. Revisit privileges

Review administrator and sensitive-data access against current duties. Remove permissions that no longer have a business reason.

Check service accounts and supplier accounts as well as employee accounts.

13. Close the review with assigned work

Turn each gap into an action with an owner, priority and review date. If you decide to put something off, write down why and until when.

Check again once each fix is done, and revisit the baseline when your systems or the business change.


Featured Image Credit