Colour theme
Book a consultation

Finding friction in everyday security habits

Ask staff where sign-in, updates and reporting get difficult, then use those answers to improve everyday security routines and support.

An illustration of a monitor displaying a yellow padlock and blue shield.

Staff can understand a security rule and still struggle to follow it. A password manager may be hard to access on a shared device. An update prompt may arrive during a client appointment. Someone who spots a suspicious message may not know where to send it.

Research such as the National Cybersecurity Alliance’s Oh Behave reports can suggest questions to ask. Its findings don’t measure your own team’s behaviour. Start with the tasks staff perform and the obstacles they encounter.

Ask about a recent task

Choose a few common situations: signing in from a new device, installing an update, sharing a client file and reporting an unexpected request.

Ask staff to describe the last time they completed each task. What took extra effort? Where did they need help? Which instructions were unclear?

Don’t collect passwords or ask people to demonstrate workarounds with live customer information. Use test accounts and examples cleared for the discussion.

Compare the rule with the available tools

Check whether staff can follow the rule using the accounts and devices assigned to them. If a password manager is required, confirm they have access and understand recovery. If updates are managed, explain what staff should do when a prompt appears.

Review shared-device and shift-work arrangements. A rule written for an office laptop may be impractical at a reception counter.

The Cyber Centre’s baseline controls cover awareness alongside technical controls. Training should accompany usable account protection, supported software and incident procedures.

Make reporting easy to practise

Give staff one clear contact route and examples of what to report. Include accidental clicks, lost devices and unexpected sign-in approvals.

Practise with a harmless scenario. Check that the report reaches someone who can respond and that the person reporting knows what to do next.

Don’t assume a late report means someone was careless. Find out whether staff feared blame, couldn’t find the contact or thought someone else had already reported it.

Measure a small improvement

Choose one obstacle and assign an owner to fix it. You might simplify the reporting instructions, provide recovery help or change an update window.

Afterward, ask the affected staff to try the task again. Record whether they can finish it and what still causes difficulty. Finishing a training course won’t tell you whether the process works.

Use the security-awareness guide to plan ongoing activities once these practical barriers are understood.


Featured Image Credit