There’s a big difference between having cybersecurity in place and knowing it’s working.
Your business might have multi-factor authentication, endpoint protection, email security, and backups. On paper, that can look reassuring. But when was the last time anyone checked that those controls are configured properly, being monitored and will respond when they’re needed?
A useful cybersecurity assessment looks beyond what tools and policies are in place. It asks what you can see, test and demonstrate.
These four questions give you a practical starting point for looking at your current security posture and identifying where further validation may be useful.
1. Do you have clear visibility of your IT environment?
Good cybersecurity starts with visibility. That means understanding what’s happening across your users, devices, systems and applications, and being able to recognise activity that falls outside the norm.
For example, would you know if an employee account was being accessed from an unusual location, or if an administrator changed an important security setting? Would repeated failed login attempts be noticed and investigated?
Most modern security platforms generate significant amounts of information, but having access to that information isn’t the same as having visibility. What matters is whether the right activity is being monitored, whether the alerts are meaningful, and whether someone is responsible for reviewing and acting on them.
If an alert is generated but nobody sees it, understands it or responds to it, the technology is only doing part of the job.
Try a simple test: if you wanted to understand what happened in your environment yesterday, could someone show you?
2. If a cyber incident happened today, would your response plan work?
No organisation can assume every cyber incident will be prevented. What happens next matters just as much.
If a suspicious login, compromised account, ransomware event or data breach occurred today, would the right people know what to do? That includes knowing who receives the first alert, who has the authority to isolate an account or device, and who needs to be involved if the incident starts affecting the wider business.
A documented incident response plan can provide structure, but having one on file isn’t enough. It needs to reflect your current environment, responsibilities and systems, and it needs to be understood by the people who may have to use it. The middle of an incident isn’t the ideal time to discover that responsibilities are unclear or an important contact list is out of date.
Even a simple discussion or scenario exercise can help identify gaps before they become a problem. The goal isn’t to predict every possible incident.
It’s to make sure the right people understand their role and can respond when something unexpected happens.
3. When did you last test your cybersecurity controls?
Security controls are often implemented once and then assumed to keep working. But environments change. People join and leave, devices are replaced, applications are introduced, and permissions shift over time. Security settings can change too, sometimes without anyone noticing.
That means there can be a gap between what you think is configured and what’s actually configured. Testing helps close that gap.
Think about some of the controls your business relies on most. When was the last time you successfully restored data from a backup? Is multi-factor authentication applied everywhere it should be? Are inactive accounts being removed, privileged access being reviewed, and devices receiving the updates you expect?
When did you last test your cybersecurity controls? If you can’t say when a restore was last tested, start by reviewing your backup and disaster recovery setup.
The same principle applies across your Microsoft 365 environment and other business systems. Settings that were appropriate when they were first configured may no longer reflect how your organisation operates today.
Frameworks such as the Essential Eight, and the new ASD Essentials framework that’s gradually replacing it, can also provide a useful structure for reviewing these controls and identifying where maturity could be improved. The new framework also brings guidance on AI, which is becoming part of the picture for most businesses.
Testing isn’t about ticking a box. Testing gives you evidence that the controls you’re relying on will perform when they’re needed. Security that’s never been validated is still partly an assumption.
4. Would your team recognise and report a security threat?
Technology is only one part of cybersecurity. People make decisions every day that affect security, often without thinking of those decisions as cybersecurity at all.
It could be an unexpected multi-factor authentication request, a supplier asking for payment details to be changed, or an email that looks almost identical to a legitimate Microsoft 365 notification. Would your team recognise that something wasn’t right? More importantly, would they know what to do next?
Security awareness works best when it’s practical, current, and connected to situations your team may genuinely encounter. That means going beyond annual training or asking people to remember a long set of technical rules. Your team should know where to report something suspicious, what to do if they think an account has been compromised, and who to contact when they’re unsure.
Completing training isn’t the real measure of awareness. What matters is whether your team can make better decisions when something doesn’t look right.
What can you prove about your cybersecurity?
These four questions come back to the same principle: if you can’t see it or test it, you can’t confidently rely on it.
That doesn’t mean every unanswered question represents a serious security failure. It means there may be a gap between the security measures you believe are in place and the evidence you have that they’re working as intended. That’s useful information.
Start by understanding what’s already in place, what can be demonstrated, and where uncertainty remains.
From there, it becomes much easier to decide what needs attention first.
A structured cybersecurity assessment can help validate that picture and identify practical areas for improvement. RES. Business IT works with organisations to review their current security position, including assessments aligned with the Essential Eight and the new ASD Essentials framework.
Having the right security tools matters. Knowing they work matters just as much.
Contact us if you’d like a clearer picture of your current security position.
Frequently asked questions
How can a business tell if its cybersecurity controls are working?
A business can tell whether its cybersecurity controls are working by looking for evidence that they are configured, monitored and tested as intended. That means being able to see relevant activity, confirm that alerts are reviewed, test important controls and understand how people would respond to an incident. The aim isn’t to prove that risk has been eliminated, but to build confidence that the controls being relied on are functioning as expected.
What should a cybersecurity assessment check?
A cybersecurity assessment should check how security controls are configured, monitored and tested across the organisation. It should also look at visibility, incident response responsibilities, access controls, backups, security settings and employee awareness. The purpose is to identify gaps between what the business believes is in place and what can actually be demonstrated, then use that evidence to prioritise practical improvements.
What does cybersecurity visibility mean for a business?
Cybersecurity visibility means being able to understand relevant activity across users, devices, systems and applications. It includes knowing whether unusual access, repeated failed logins or important configuration changes would be noticed and reviewed. Having security data available isn’t enough on its own. Someone also needs to understand the information, recognise what may require attention and know how to respond.
Why should an incident response plan be tested?
An incident response plan should be tested so the people involved understand their responsibilities before they need to use it under pressure. A simple scenario exercise can help reveal unclear ownership, outdated contact information or gaps in escalation processes. Testing doesn’t guarantee that every incident will be handled perfectly, but it can help the organisation identify practical issues and improve its ability to respond in a coordinated way.
Why is backup restoration testing important?
Backup restoration testing is important because having backups doesn’t automatically mean data can be recovered when it’s needed. A restore test helps confirm that the backup can be accessed and that the recovery process works as expected. It can also reveal issues with permissions, procedures or missing data before a real disruption occurs, giving the business clearer evidence about whether its recovery arrangements are dependable.
How can a business tell whether security awareness training is effective?
A business can assess security awareness by looking at whether team members recognise suspicious activity and know what to do next. Training completion alone doesn’t show how people will respond to a convincing phishing message, an unexpected authentication request or a suspicious payment change. Practical exercises, clear reporting processes and regular reinforcement can help show whether security guidance is translating into better decisions and behaviour.
Can a security self-assessment replace a formal assessment?
A security self-assessment can provide a useful first view of where the organisation has confidence and where questions remain, but it isn’t the same as an independent or formal assessment. Internal checks can help surface obvious gaps and prepare better questions. A more structured assessment can provide additional validation, particularly where the business needs a clearer view of how controls are implemented or where improvements should be prioritised.
What does security posture mean for a business?
Security posture describes the overall state of an organisation’s security arrangements, including its controls, processes, visibility and ability to respond to risk. It’s broader than the number of security tools a business owns. Understanding it involves looking at how controls are configured, whether they’re monitored and tested, how access is managed and whether people know what to do when something appears unusual.
