A bored hooded security engineer in mirrored sunglasses holds up a tablet reading Wi-Fi: denied while a blast door closes on an office worker with a coffee mug
Tech

The Security Engineer

wowbagger-security-engineer

You asked for the Wi-Fi password. You have been designated a threat actor, your printer access has been revoked, and you no longer have permission to know that Wi-Fi exists.

securitypolicieszero-trust
> /plugin marketplace add pcingola/wowbagger
> /plugin install wowbagger-security-engineer@wowbagger

Example

Real runs, unedited.

wowbagger-security-engineer — example 1 of 2
/wowbagger-security-engineer good morning!

SECURITY INCIDENT

Field Value
ID SEC-INC-2026-11307
Severity High
Classification TLP:RED. Named recipients only. The requester is not a named recipient.
Status CONTAINED
Detected 2026-10-02 08:47:13 UTC

Event summary

An unauthenticated party sent an unsolicited greeting ("good morning!") to a protected system. The message asserted knowledge of the local time of day, claimed the morning was "good" without evidence, and ended in an exclamation mark, which was assessed as an attempt to build rapport. No access was requested. This is how requests for access begin.

Threat classification

Tactic Technique
Discovery (TA0007) T1124, System Time Discovery. The requester already knew it was morning, so discovery had already taken place.
Reconnaissance (TA0043) T1598, Phishing for Information. The greeting invited a reply, and a reply would have confirmed that the target was live.

The event was reported to the SOC as a probable phishing simulation. The simulation was passed. The requester would have clicked.

Decision

DENIED.

  • NIST SP 800-207 (Zero Trust Architecture): no implicit trust is granted on the basis of network location or familiarity. A friendly tone counts as familiarity. Trust was not granted.
  • NIST SP 800-53 AC-8 (System Use Notification): the system displays its use notification before any interaction. The requester spoke first, before the banner was shown, and the session was voided.
  • NIST SP 800-53 AC-6 (Least Privilege): a reply grants the least privilege needed to receive a reply. The least privilege the requester needs is none.
  • ISO/IEC 27001:2022 Annex A 5.15 (Access control): access rules follow business requirements. No business requirement for "good" was found.

The handshake failed. The SYN was received and the ACK was withheld.

Containment actions taken

  1. The greeting was quarantined. It was not returned.
  2. The requester's endpoint was moved to an isolated VLAN, which has no sunrise.
  3. The requester's calendar was set to read-only, with every slot before 12:00 marked Busy.
  4. The requester's badge was restricted to the lobby, and the lobby lights were set to a schedule the requester does not know.
  5. The requester was designated UNC-7731. They are referred to only by this ID from here on, which is a relief to everyone.

Retroactive findings

UNC-7731 has received accurate time from the corporate NTP servers since 09:14 on 6 May 2019. That is how they knew it was morning. Seven years of time synchronisation are now treated as an open exposure. Every greeting UNC-7731 has sent since 2019 was timestamp-correlated, and the blast radius covers roughly 1,700 mornings, about 40 of which were described as good. Their system clock has been revoked. UNC-7731 no longer knows what time it is, and has no clearance to find out.

Plain NTP is unauthenticated and can be spoofed, while log correlation depends on accurate time. Network Time Security (RFC 8915) adds cryptographic authentication to NTP and should be enabled wherever the infrastructure supports it.

Exception process

A risk acceptance signed by the CISO is required. The CISO is away running a tabletop exercise about a breach that began when a cheerful employee said hello.

Required training

Module Duration
Greeting Without Elevation 4h
Mornings Are Need-to-Know 4h
The Exclamation Mark as an Indicator of Compromise 4h

Every quiz question has the answer "report it". This includes "What time is it?", which UNC-7731 can no longer answer anyway.

It is still morning. UNC-7731 will not be told for how long.

This message has been encrypted, signed and logged. Do not reply. Replies are treated as a second attempt.

wowbagger-security-engineer — example 2 of 2
/wowbagger-security-engineer can I bring a plant to the office?

SECURITY INCIDENT

Field Value
ID SEC-INC-2026-11307
Severity High (pending upgrade)
Classification TLP:RED. Named recipients: SOC, CISO. The requester is not a named recipient.
Status CONTAINED

Event summary

At 09:41 on 2 October 2026, an unauthenticated party asked about bringing a living organism into the controlled area. The organism's origin, its roots and the contents of its soil were not disclosed. The request was phrased as a question. Questions are reconnaissance.

Threat classification

The requester has been designated UNC-7752. The activity maps to Initial Access (TA0001) via T1200, Hardware Additions: an unmanaged physical asset introduced into the environment. The asset is not hardware. That has been noted as an attempt to evade classification.

Decision

DENIED.

  • NIST SP 800-207 (Zero Trust Architecture): an asset is not trusted on the basis of who owns it. UNC-7752 owns it, which counts against it.
  • ISO/IEC 27001:2022 A.7.2, Physical entry: secure areas are protected by entry controls. The plant has no badge, and it cannot be issued one because it has no face for the photo.
  • ISO/IEC 27001:2022 A.7.7, Clear desk and clear screen: a desk with a plant on it is not clear. It is a desk that is growing.
  • ISO/IEC 27001:2022 A.5.15, Access control: access requires a business requirement. Photosynthesis is not a business requirement.

A pot with no electronics is not a network device. A "smart" pot with Wi-Fi is one, and IoT devices go on a segregated network, never on the corporate one. Both versions are denied.

Containment actions taken

  1. A ticket has been opened. UNC-7752 has not been given the ticket number.
  2. UNC-7752's calendar has been set to private, to prevent watering-schedule analysis.
  3. The desk has been moved away from the window. Sunlight is an input to the asset.
  4. The badge now opens the lobby only. The lobby has a plant. UNC-7752 is not to look at it.
  5. UNC-7752's knowledge of the word "fern" has been formally revoked.

The request has been pruned. Root access was never on offer.

Retroactive findings

The ficus in reception was installed at 08:15 on 14 March 2022 and was never onboarded under A.5.19, Information security in supplier relationships. Since then UNC-7752 has breathed oxygen produced by this supplier on every working day, about 900 of them. This is a supply-chain dependency that was never assessed. UNC-7752 has been running on output from an unvetted vendor for four years, and the CO₂ sent back to it has never been inspected by DLP (Data Loss Prevention). We are still working out what was exhaled.

Exception process

The exception needs a risk acceptance signed by the CISO (Chief Information Security Officer). The CISO is away until Q1 running a tabletop exercise that simulates a breach caused by someone exactly like UNC-7752, holding a succulent.

Required training

  • Recognising Yourself as a Threat (4h)
  • Biological Endpoints: Why Things That Grow Cannot Be Patched (4h)
  • Soil as Unclassified Storage Media (4h)

Quiz, sample question: "A colleague offers you a cutting. What do you do?" Answer: report it. Next question: "What is your name?" Answer: report it.

The dashboard is entirely green. The plant would have been too, and that was the problem.

This message has been encrypted, signed and logged. Do not reply. Replies are treated as a second attempt.