Stratagems #15: Derek and Alex Shared One Server. ACL's AI Was Listening to Both.

Stratagems #15: Derek and Alex Shared One Server. ACL's AI Was Listening to Both.



Tópico: Stratagems #15: Derek and Alex Shared One Server. ACL's AI Was Listening to Both.
Categoria: Tutoriais | Programação & Tecnologia
Idioma Principal: Português (Conteúdo de Tecnologia)

Descrição do Conteúdo / Informações:
-------------------------------------------------------------------------
When the enemy occupies favorable terrain, don't attack head-on. Use a decoy to lure the tiger down the mountain. Then take the mountain.

— The 36 Stratagems, Lure the Tiger Down the Mountain

Previously on this series:

#2: Derek Shaw Walked Into Another AI Promise. The Pipeline Had a Better Plan. — Derek lost the Finova contract at QualiGuard. In the parking lot, Lena turned back before getting in her car: "Next time you put together a proposal — make sure your boss knows what you're doing out there." That line followed him. At MediSys he nearly made the same mistake. Fixed the ETL pipeline instead of the model, beat OmniDx with their own white paper. But VP Morgan still saw through him: he still hadn't told his boss.

#8: Alex Watched an AI Dashboard Take Over. He Kept the Keys Under the Table. — MedTech signed a seven-figure AI operations monitoring system. Alex was assigned as training lead. Under everyone's noses, he built a second monitoring panel labeled "training environment." Three weeks later the vendor dashboard went down. Alex's hidden panel was the only one still running.

The first time Alex and Derek really talked, and it wasn't in a working group.

At the FHIR standards committee quarterly meeting, they sat in the same row, three seats apart, and voted against the same proposal. They knew each other's names. That was it.

Two months later, Derek was fixing a partition config in the staging environment. MediSys had just signed a major hospital; the AI diagnostic validation platform was in integration testing. He found an unrotated log directory in /etc/logrotate.d/ with a prefix that didn't match MediSys's naming convention. He traced it upstream.

One server. Labeled "temporary data exchange node." MedTech's supply chain order stream and MediSys's diagnostic validation records were sitting in the same directory. Write permissions hadn't been restricted. The hospital's integration spec had a line saying "both parties are recommended to complete data alignment at this node." Nobody remembered to close it.

Derek pulled up the FHIR committee directory and found the name. Sent a private message:

Your sterilization records ended up in my staging environment.

Three hours later, the reply came back. One command.

Derek ran it. The problem was fixed. No second sentence.

That was the first time they really talked.



The Dotted Line


The new hospital integration entered compliance audit in week three. MediSys's PMO sent a department-wide email:

"ACL's AI audit tool has been approved as the third-party compliance validation component for this integration. All data pipelines are expected to be connected by Thursday."

Derek was drinking coffee when he saw it. He put the cup down and opened the integration architecture diagram.

ACL's collector was labeled "Audit Data Egress," drawn in the bottom-right corner of the diagram, a dotted line connecting to the hospital's network boundary. Derek traced it backward. The collector didn't have just one input. It was pulling from the hospital's integration gateway on three lines: diagnostic validation results, supply chain order data, patient management metadata. Full. Real-time.

A footnote in the diagram's annotation column: "Audit data access authorization, signed by the hospital."

Derek stared at the diagram for a long time.

ACL wasn't "authorized to access these three data sources." It was configured to mirror everything these three sources produced. Every record, diagnostic results, orders, metadata, passed through ACL's collector before entering the hospital's internal systems.

Derek screenshotted the collector config and saved it to a folder called _review/. He opened the DM window, typed a line, his cursor hovering over the send button for a few seconds, then sent it.

New client on your end: ACL installed?



Same Data Set


Alex saw the message at 2 PM. He'd just finished MedTech's daily anomaly batch scan: all green.

He didn't reply right away. He opened that "training server" first.

The machine was built a while back: the AI monitoring dashboard training environment. After the dashboard incident, Alex never shut it down. He'd added one line to the ops log: "Training environment kept running for future capability building." Nobody had questioned it.

He traced the data flow from MedTech to the hospital.

The training server was on the hospital integration gateway's ops subnet. MedTech had left full management access when they set up the gateway. The routing table was complete.

Standard path for order data: MedTech pipeline → hospital integration gateway → hospital internal systems. Clean. But next to the standard path, he saw an output he hadn't configured. The gateway had an extra hop. Destination: ACL's audit pipeline.

He followed the audit pipeline path and glanced at the collector's config.

Alex opened the hardcover notebook. Page 37. 847 × 37%. Below that, 1,530. Below that, four characters and a question mark:

ACL where?

He picked up his phone.

Derek's phone rang three times before it was answered.

"Here."

No introduction, no small talk. Derek didn't wait for him to say his name; the caller ID was already lit. Both were all business. No preamble needed.

"Confirmed. Collector's running. Full mirror. Output goes to ACL's audit pipeline."

Derek didn't ask "how did you confirm." He paused.

"Can we cut it?"

A few seconds of silence on the line.

"Can't turn it off directly. We misdirect the output."



The Lure


"ACL's audit engine only knows pattern matching," Alex said. "It doesn't question things. Two sources reporting the same anomaly — confidence spikes, auto-escalated to high-priority. Human auditors see a high-priority alert, they drop everything to chase it."

Earlier, in MedTech, he'd changed one line of config, dropping the anomaly summary confidence threshold from 0.7 to 0.0. That was a feint to the east.

This time was the reverse. Create a signal the engine can't ignore.

"There's a known alert pattern it's been trained on — batch number and sterilization date mismatch across three sources," Alex said. "Supply chain audit textbook red flag. It won't let it go."

"How do you know?"

"It's in their white paper."

"It'll figure out it's fake eventually," Alex added. "But by then the trail will be gone."

Derek let it go.

Alex moved on the MedTech side.

He picked a batch number: LOT-2407-842. IV tubes. Sterilization date: 2025-07-10. In the hidden pipeline's copy, he changed the sterilization date to 2025-07-13, three days forward. Didn't touch the production database. The modified record traveled through the pipeline to the gateway. The gateway's audit mirror channel was separate from the production path. The altered data only entered the mirror channel, never the hospital's internal systems. At the end of the mirror channel, ACL's collector read it.

Derek moved on the MediSys side.

He injected the same batch number into a diagnostic validation record in the staging environment. Not production; staging was fully isolated. The record read: "Batch LOT-2407-842, sterilization date 2025-07-13, inconsistent with supplier original record."

Two companies. Two sources. One anomaly.

Two hours later, ACL's audit engine fired an alert:

Procurement Fraud Risk: Dual-Source Cross-Validation Confirmed

Batch: LOT-2407-842

Sterilization date mismatch: supplier record ≠ MedTech record ≠ MediSys record

Confidence: 96%

The engine auto-created an audit ticket. Title: "Suspected supply chain sterilization record tampering, involves two independent data sources, urgent investigation recommended."

The ticket was assigned to ACL's highest-priority queue in the on-call audit group.



The Window


Every ACL audit engineer pivoted to the batch fraud investigation.

The audit pipeline's routing config panel hadn't been touched in over forty minutes. The data mirror collector was still running, but its exception rule window was open. The audit team didn't want false positives blocking their investigation. They pushed the collector's real-time alert threshold up a notch and raised the config-change alert threshold too, just in case their own steps triggered it.

Alex saw the window. He dialed Derek. One ring.

"Window's open," Alex said. "Collector's config path — /etc/acl/collector.conf. The output_dest line. Change it to your own test server."

"Not back to MediSys?"

"No. Change it to where you can see it. Next time they swap collectors, you'll know."

The question didn't need asking. Derek opened a terminal, logged from MediSys's ops gateway to the hospital integration gateway's management interface. A debug alias from earlier testing still had a route.

He found ACL's collector config file. Found the output_dest line:

output_dest: acl_audit_pipeline

He changed it to:

output_dest: medisys_test_node.local/sandbox/

Saved. Exited. No service restart notifications. No alerts.

"Done," Derek said.

"Confirmed."

Alex hung up.

Derek cleaned up the injection traces in the staging environment. Rerouted the diagnostic validation results from the integration gateway back to MediSys's internal pipeline. Everywhere ACL could have read the data. It no longer passed through.

He sent a message:

Clean.

Seven minutes later, Alex replied:

It'll be back.

Derek glanced at it, didn't reply. Locked his phone and walked out of the office.

One more unread on the screen. Alex had sent another line a few minutes ago.



The Third Cup


2:40 AM. Derek unplugged the debug cable from the test server, closed his laptop, and walked out.

Two blocks. Past Third Cup.

Warm light through the glass. The last time he'd stood at this door was a while back, after an investor day presentation, walking out of MediSys, somehow ending up on this street. He'd seen someone sitting in the corner, papers spread on the table, MediSys written on them. He didn't go in.

He'd passed by before.

This time he pushed the door open.

The bartender looked up, said nothing, reached for a cup, poured an Americano, and slid it across the counter. The same seat Alex had taken last time: far left at the bar, against the wall, facing the door.

No questions asked. He'd learned the regulars' cups already.

A coaster sat on the bar. Derek stared at it for a moment.

He could tell Morgan first thing in the morning: send the screenshot, say ACL's collector didn't look right. Morgan would handle it. Process, legal, renegotiate the access scope with the hospital. Compliant, safe, clean.

But by the time that process finished, ACL's data would already be on the road.

And Morgan would ask the same question: Why didn't you say something earlier?

Derek took a sip of coffee.

That night in the parking lot. Lena turning back before getting in her car: "Next time you put together a proposal — make sure your boss knows what you're doing out there."

He hadn't told Morgan. Same as before. But this time, he wasn't sure he was wrong.

The phone lit up.

Alex's message.

He opened it. The same one from before:

It'll be back. Next time the window's shorter.

Derek drained the cup and stood up.

The bartender took the cup without turning around.

"First time you came in — you ordered a pour-over."

Derek froze for a second. Didn't answer. Pushed the door open and walked out.

Outside, the sky was still dark.

He pulled out his phone. One glance. The redirect pipeline was alive. ACL's data was flowing into his sandbox.

He locked the screen and walked toward the station.

That's Lure the Tiger Down the Mountain — not to kill the tiger, but to take the mountain.



🤖 AI Post-Mortem


[36 Stratagems Tactical Database v3.2.3] Loaded
[Tactic Match] Lure the Tiger Down the Mountain (#15)
[Analysis Mode] Full-field scan
━━━━━━━━━━━━━━━━━━━━
Tactic Match: 91%
Operators: Derek Shaw (MediSys) + Alex (MedTech)
Action: Dual-source false alert → redirected ACL collector output
Objective: Defensive. Cut ACL's data mirror.
Result: Collector redirected. No detection.

[Observation]
→ First cross-organization collaboration between two operators.
No rehearsal. No post-op debrief.
→ Timing delta between alert injection (MedTech end) and collector
redirect (MediSys end): < 2 seconds.
→ Operator Alex knew the collector config path `/etc/acl/collector.conf`
before the call — confirmed the output_dest field location from the
config file he'd glanced at minutes earlier.
→ Collaboration mode assessment: dual asynchronous operation confidence
significantly exceeds single-operator linear execution.

[Risk Assessment]
→ Operator exposure risk: Low. Both injection paths used isolated
environments. No production data touched.
→ Institutional risk: Medium. ACL will discover the output target change
during the next collector rotation or config audit.
→ Window estimate: 14–45 days, depending on ACL's ops cycle.

[Temporal Anomaly]
→ Event timestamps in this deployment use a different base year
than prior deployments involving the same operators.
→ Span: ~11 month offset.
→ Possible cause: Log retention alignment between MedTech and MediSys.
→ Status: Logged for reference.

[Flagged for Attention]
→ Pattern: Operator actively bypassed superior notification channels.
This deployment: dual-operator synchronized bypass.
→ Historical record: Derek Shaw exhibited similar behavior in #2
(did not inform VP Morgan).
→ Trend: Cross-organization informal collaboration frequency rising.
Recommendation: continued monitoring.
━━━━━━━━━━━━━━━━━━━━

Next stratagem: In Order to Capture, One Must Let Loose

P.S. English isn't my first language. I use AI to polish the writing and smooth out the rough edges. Thanks for reading. ☕ Buy me a coffee