🕯 Issue #3
What Is an Insider Threat?
“Most insider threats don’t start with theft.
They start with trust — and the slow erosion of it.”
Act I — The Trusted One
The operations floor is calm.
Monitors glow white.
Keyboards click.
People work without urgency.

Secure operations floor during the day
This is what a secure workplace looks like when nothing is wrong.
Character Lock-in
Name: Elias Ward
Role: Security Analyst / Observer
Reliable.
Consistent.
Unremarkable.

Elias Ward observing dashboards behind glass
Elias Ward stands behind the glass partition.
His job isn’t to watch people closely.
It’s to notice when behavior slowly stops matching expectations.
Timing.
Access.
Patterns.
In his head:
“If something becomes a problem,
it usually looks normal at first.”
Character Lock-In
Name: Daniel Cole
Role: Trusted Employee / Insider Threat
Daniel Cole sits a few rows away.
He’s been here for years.
People rely on him.

Daniel Cole working among peers
Coworkers chat quietly and move with ease.
Daniel appears comfortable and integrated within the group.
This is normal.
Sharing work between trusted teammates is expected.

Coworkers moving freely through the office
Badges beep.
Doors unlock.
People move freely.
Everyone here has access because they’re supposed to.

Access granted message on screen
Access granted.
Daniel is authorized to be there.
The timing is normal.
The activity matches his role.
Elias doesn’t flag it.
There’s nothing unusual yet.
Act II — The Review
Later that week, Daniel is called into a meeting.

Closed office door with light underneath
Nothing urgent.
Nothing alarming.
Just routine.
Character Lock-In
Name: Marianne Holt
Role: Manager / Authority Figure
Policy-driven.
Professional to the core.
She documents performance.
She doesn’t track fallout.
Marianne Holt sits across from him.

Performance review meeting
She slides a document forward.
Marianne:
“This is your quarterly review.”
She points to a section.
Marianne:
“A few deliverables missed their targets.
We need improvement next cycle.”
Daniel listens carefully.
In his head:
“I stayed late.
I fixed problems no one else touched.”

Daniel listening
He keeps his voice even.
Daniel:
“Okay. I understand.”
The meeting ends politely.

Daniel exiting the office
The message lingers.
Daniel walks past Elias.
His pace is faster than usual.
His shoulders are tense.
Elias notices the shift.
In his head:
“That’s new.”

Elias notices Daniel passing
Not a violation.
Just a change.
Act III — Friction
At the next team meeting, a slide appears on the screen.
Elias:
“Starting Monday, cross-team access will require approval.”

Team meeting
Daniel speaks before anyone else.
Daniel:
“So now we need permission just to do our jobs?”

Daniel speaking up
The room goes quiet.
Elias:
“It’s a security requirement.”
Daniel:
“It feels excessive.”
A few people glance at each other.

No one agrees.
No one pushes back.
The moment passes — but it’s remembered.
Later, in the hallway:
Daniel:
“They keep adding rules because they don’t trust us.”
Coworker:
“I think it’s just policy.”
Daniel exhales sharply and walks off.

Daniel walks off
That night, most of the office is dark.
One desk is still lit.

Authentication logs
Elias reviews system activity.
03:12 AM.
04:47 AM.
Daniel’s account appears again — after midnight.
Once could be overtime.
Twice could be coincidence.
Repeated late access becomes a pattern.
In his head:
“Still authorized.
But no longer expected.”

Late-night office
Act IV — Curiosity
Break room.
Daniel pours coffee next to Jordan Reyes {Support Engineer}.

Break room conversation
Daniel:
“Hey — quick question.”
Daniel:
“How does your team handle credential resets?”

Daniel asking question
Jordan hesitates.
Jordan:
“Why do you need to know?”
Daniel:
“I don’t. Just curious.”
Jordan feeling uneasy gives a short, careful answer.
Enough to be polite.
Not enough to be useful.
The pause says more than the words.

Jordan uneasy
Elias watches from across the room.
In his head:
“That system isn’t part of Daniel’s responsibilities, niether was that a needed question.”

Elias observing interaction
Act V — Pressure
At lunch, Daniel jokes about money.
Daniel:
“Feels like everything costs more lately.”
A few people nod.
The topic changes.

Lunch conversation
A few days later, Elias notices something else.
A new car in the parking lot.
Expensive.

New car in parking lot
Daniel doesn’t mention it.
Act VI — The Choice
Back at the office, Elias reviews everything together with his lead.

Elias at his desk
|
|

Elias at his desk
None of it proves malicious intent.
All of it signals risk.
Elias:
“I don’t think he’s trying to hurt the company.”

Elias speaking to supervisor
Pause.
Elias:
“But he’s becoming vulnerable.”

Supervisor listening
They sit with the decision.
Intervene now — or wait for proof.
Elias has seen enough to be concerned — but not enough to accuse. Acting too late risks damage. Acting too early risks trust.
What should the defender do?
Security reaches out early. Support resources are offered. Access is reviewed quietly.
The situation stabilizes. No breach occurs.
Pressure continues unchecked. External influence deepens.
The next alert isn’t a warning. It’s an incident.
