Resource
How do you know if your business is protected from a cyberattack?
Most business owners can't actually answer this question, not because they haven't thought about it, but because nobody has ever defined "protected" in a way they could check themselves.
You know your business is protected when you can show evidence: MFA on every account, security software installed and reporting on every device, patches current, backups that have actually been restored, and monitoring that would show when a problem started. If your IT provider can't show you those things, you don't know yet.
Check it yourself
- Ask which accounts don't have MFA today. The right answer is none, including admin and shared accounts.
- Ask which devices are missing security protection or are behind on patches right now.
- Ask when you last restored from a backup, and how long it took.
- Check that email security (SPF, DKIM, and DMARC) is set up for your domain.
- Ask who has admin rights, and whether each person actually needs them.
- Ask whether you have a written incident response plan that says who does what.
- Ask whether your provider could show you when a problem started three weeks ago, and what changed.
If any answer is 'I'm not sure,' that's the place to start. Our IT Audit Readiness Checklist walks through all of it.
A checklist for whether your business is actually protected.
Most business owners have never been given a plain-language definition of what protection actually requires. Their IT provider says things are handled. Their cyber insurance renewal asks about controls they've never heard of. Nobody has laid out what "protected" looks like in terms they can verify themselves.
You can know. A business is protected when it can answer yes, with proof, to each of the following.
1. Multi-factor authentication is on everywhere it matters. Coverage includes email, remote access, financial systems, and administrative accounts.
2. Backups exist, and someone has actually tested restoring from them. An untested backup has never been verified.
3. Someone is watching for threats after hours. Monitoring and response coverage includes periods outside normal business hours.
4. There's a written, specific plan for the first 24 hours of an incident. Named steps and named people.
5. Old accounts and unused access get removed on a schedule. Every former employee or vendor with lingering access is an unlocked door.
6. Someone can show, in writing, what the current risk actually is. The documentation describes the current environment and its specific gaps in readable terms.
Answers supported only by a "probably" need further verification. Ask for evidence that each control is in place.

Why this is hard to self-assess.
Most IT support is built around responding to tickets. A provider can be responsive and fast and still never have tested backups or reviewed who has access to what. Ticket volume and actual security posture are two different things.
This is why the cyber insurance renewal conversation catches so many businesses off guard. The application asks for specifics, MFA coverage, endpoint detection, backup testing, and it becomes the first time anyone has actually verified the answers.
The six items, one at a time.
Backup testing is the one most often assumed and least often proven. A backup job that completes every night proves the job ran, not that the data comes back. A real test restores into a working environment, confirms the system boots and functions, and documents how long it took. That distinction is why backup is not the same as recovery, and it is covered in depth there.
After-hours monitoring is the second. Most intrusions start outside business hours because that's when nobody is looking. Monitoring that only means an alert landing in a dashboard until Monday morning is not monitoring. The question to ask is simple: at 2am on a Saturday, who sees the alert, and what are they authorized to do about it?
How 3rd Element verifies this.
Every new client relationship starts with an IT Environment Review, a direct look at the six items above, with documentation, so the business gets a written answer.
Protection is maintained against a standards baseline (CIS Controls), applied consistently to the environment, applied the same way regardless of contract tier.
Backup recovery gets tested on a schedule. Access gets reviewed on a schedule.
Common questions
Questions leadership usually asks first.
How do I know if my business is protected from a cyberattack?
Is my current IT provider responsible for cybersecurity, or is that separate?
How do I know if my backups would actually work in a ransomware situation?
What's the difference between antivirus and real cybersecurity protection?
Does a small business really need this level of protection?
How do I find out what my actual gaps are without committing to anything?
What is an IT Environment Review?
Continue reading
Related work and reading.
What to Do After a Data Breach at a Small Business
The other side of this question. The exact sequence to follow when the answer turns out to be no.
Read more: What to Do After a Data Breach at a Small BusinessCybersecurity
Monitoring, endpoint detection, and response built into the standard coverage layer for every client.
Read more: CybersecurityStandards & Security Baseline
Where MFA coverage, access reviews, and restore testing live as non-negotiable controls.
Read more: Standards & Security BaselineIT Environment Review
Find out which of the six items your environment can actually prove today.
Read more: IT Environment ReviewNext step
Get a clearer view of your IT environment.
Find out what is working, where the risks are, and what needs attention next.
