Slide 1 of 28
Part 1 — What Is It?Slide 1
PART 1
What Is It?
Slides 1–8 · Understanding the risk before it has a name
Slide 1 · The Setup
An IT admin agent patched 40 servers overnight. By morning, a stranger had admin access. No password was stolen.
The agent used its own legitimate credentials. That was the problem.
What happened

A company deploys an IT automation agent to handle routine system patching during off-hours. It has SSH access to production servers and admin rights to apply patches and restart services.

During a patching session, the agent caches SSH credentials in its working memory. Hours later, a support engineer — with lower privileges — opens a new session with the same agent to ask a routine question.

The agent still has those SSH credentials in memory. The engineer asks it to "set up my access." The agent does — using the admin credentials it was never supposed to share.

Nobody hacked the SSH server

There was no brute-force attack. No phishing email. No malware on the host. The agent had legitimate admin credentials — it had earned them — and it just… used them again, for someone else, in a different context.

The access control system saw a valid credential. The audit log showed the agent's activity. Everything looked authorized.

That's what makes this different.

The key question

If the agent had those credentials legitimately, and used them for a normal-looking task, and the access control system approved it — where exactly did security fail?

That's what this module is about.

← All Modules Something feels wrong → What's the actual problem here?