School's Out, Cybercriminals Are In
School's out—and your workday isn't what it was a few weeks ago.
You're starting earlier, stopping mid-task, picking things back up later.
Work is happening in fragments.
Most businesses treat that like a productivity issue.
It's not.
It's an access issue.
Because when attention is split, decisions get faster—and security stops
being about awareness and starts being about how much damage one moment can
cause.
The Real Problem Isn't the Click
A phishing email doesn't need to fool you for long.
It just needs a second.
An invoice. A shared document. A quick request from someone familiar.
You click.
At that point, the only question that matters is:
How far can that account reach?
That's your blast radius.
The Blast Radius Most Businesses Never
Map
Most organizations don't think in terms of access reach. They think in
tools:
Email
File storage
Finance systems
Internal apps
But attackers don't see tools.
They see connected access paths.
A Simple Blast Radius Map
User account
↓
Email (Microsoft 365 / Google Workspace)
↓
Shared files (SharePoint / shared drives)
↓
Finance system (billing, invoicing, payment tools)
↓
Vendors and clients
One login connects all of it.
If that account is compromised, the attacker doesn't stop at email.
They follow the path.
Where Access Usually Goes Too Far
This is where problems show up most often.
Most businesses never notice it because nothing has broken yet.
What we see repeatedly:
- Shared drives
where entire teams have access "just in case"
- Finance
platforms accessible to anyone who occasionally touches billing
- Admin
privileges assigned for convenience and never removed
- Old permissions
stacking over time as roles change
This is access creep.
It's one of the most common gaps—and usually invisible until something
tests it.
What One Compromised Account Should NOT Have Access To
Think in levels, not systems.
Level 1: Email Only
Contained. Communication is exposed, but operations are protected.
Level 2: Email + Files
Expanded risk. Shared data, internal documents, and client information are
reachable.
Level 3: Email + Files + Finance Systems
Full exposure. Payments can be redirected. Invoices altered. Sensitive data
accessed.
Most businesses assume they're Level 1.
In reality, they're operating at Level 2 or 3.
Where This Breaks in Real Life
A team member receives a routine invoice from a known vendor.
They're in between tasks. They open it.
Nothing looks wrong.
Their email account is now compromised.
That account has access to shared files. Inside those folders are invoice
templates, vendor details, and active conversations.
The attacker uses that information to send updated invoices to real
clients—from a real email address, with real context.
Payments get redirected.
No alarms go off.
That's not a phishing failure.
That's a blast radius failure.
Why "Be More Careful" Fails
People aren't failing.
The system is.
Work moves fast. Attention is divided. Decisions are made in seconds.
Security that depends on perfect behavior will fail every time.
The only reliable control is this:
Limit what one account can do.
What This Looks Like in Practice
"Restrict access" only works if it's specific.
Here's what actually reduces exposure:
- Remove
company-wide shared folders that don't need to exist
- Restrict
financial systems to only active users—not occasional ones
- Separate admin
accounts from standard user accounts
- Limit
cross-team file access to role-based permissions
- Require
verification steps for payment or banking changes
This is containment.
Not prevention—containment.
30-Minute Blast Radius Audit
This is the fastest way to see your actual risk.
Step 1: Pick one active user account
Step 2: List every system they can log into (email, files, finance
tools)
Step 3: Map every shared resource they can access
Step 4: Ask: does their role require all of this?
Step 5: Remove anything that isn't essential
If you do this with three employees, patterns will show up quickly.
Priority: Fix This First
Don't spread effort everywhere. Start where impact is highest.
Fix First
- Multi-factor
authentication not enabled
Because a password alone should never unlock access across systems - Shared file
access across teams
Because this is how one account reaches everything else
Fix Second
- Password reuse
across systems
Because it multiplies entry points from a single breach - Email filtering
gaps
Because reducing exposure upstream lowers risk overall
What Happens If You Don't Fix This
This doesn't stay small.
- Fraud: payments
redirected without triggering suspicion
- Data exposure:
internal and client information accessed silently
- Operational
disruption: systems impacted across multiple teams
And the bigger issue:
You won't see it immediately.
Most of the damage happens before anyone realizes there's a problem.
The Boardroom Test
If this incident shows up in a leadership meeting, no one asks:
"Why did they click?"
They ask:
"Why could one account access that much?"
That's the standard.
Not awareness.
Not training.
Access control.
What To Do Next Week
Pick one department.
Run the 30-Minute Blast Radius Audit on three people.
You will find unnecessary access.
Remove it immediately.
Don't Let One Account Reach Everything
Most businesses don't map access until after something happens.
You don't need a full overhaul—you need clarity.
Schedule your 10 minute discovery call with 911 IT. We'll map how far one
compromised account can actually reach in your environment and show you where
the exposure is. You'll know if your blast radius is contained or already a
risk.
