First TakeFirst Take

Spy Vs Spy

For those that don't know, back in the late 70s there were a couple of lampoonish satire comics called Mad and Cracked. Mad Magazine had a regular panel called Spy Vs. Spy where white and black trench and hat wearing, pointy faced sneaks faced off in every issue. No one ever got a definitive win. I mention this because the race between white hat and black hat hackers using AI has reached a similarly comical impasse.

The funny part is that neither has a choice in the matter, they both have to use AI in order to achieve their disparate goals with enough expediency to have any chance at all. For those of us on the white hat side, defending our networks, data and connected assets has become far more difficult and costly. On the black hat side, even stolen tools like Anthropic API keys can be leveraged for no cost and exceptional hacking outcomes.

How do we protect our networks when the best tools we can buy are often the same tools attacking us? The answer to that has to be detection and response speed. You can't just tell Claude to watch your network and stop any attackers either. You have to build or buy constrained tools capable of learning baseline metrics and closing related access points as out of bound incidences occur. This means you may have false positives that reduce system availability rates, but better that than finding your network no longer belongs to you the next morning.

So, since it comes down to speed and capability, the requirement for the white hats is a local model large enough to protect the network and run on hardware capable of handling analysis and response actions at near wire speeds. The 3-4ms lag from a frontier model API key could be the difference between successful defence and getting pwned. Worse, the bad guys might target your API keys and use your own frontier models against you. I can't tell you how best to build your defences, or what models to use. These solutions are moving targets themselves. I CAN tell you to start working on it. Get something pre-built deployed now and work on an in-house system as soon as you can afford to.

Kudos to Grok for the best non-infringing single cartoon panel. ChatGPT, Gemini and CoPilot seemed to break copyright laws with their interpretations of my prompt: "Would you like to make a Spy VS. Spy cartoon panel for a story with AI hackers and AI network defense?" ChatGPT did the best of the infringing variants with a full color 4 panel story that was pretty on theme. Meta also did a classic 4 panel layout with non-infringing characters, but it wasn't any better than this, just busier. Your IP are not protected by today's frontier models.

The Shift Register  

EditorialEditorial

CIO's Corner

Last week, we were all about moving intelligence from the cloud to the edge where you could maintain control of your data and processes. This week, I'd like to discuss the process for getting to that point. In other words, what does it take to bring LLM empowered systems into local networks?

First, I'm not going to tell you to go out and buy $300k servers to fill your data center with. That's a good way to go broke with little to show for it. Instead, buy some research sized inference hardware, anything whether it's just an Nvidia Jetson Orin or Thor, an RTX 6000 powered laptop or whatever can run some decent sized models with some alacrity for a handful of users.

This is your research and development system. You can scale useful solutions to the big expensive servers once you find some solid use cases that have good ROI. Compare your local model performance per token to something like Claude or ChatGPT costs for an easy math layup on where the savings will come from. If you already have AI subscriptions you are paying for, focus on moving a few of those use cases first.

In our most recent case, we found that even with a mere 13 users pounding on the research box, we were saving about $3k per month vs rented tokens. The research box hardware originally cost us $3.5k (they are about twice that at the moment). ROI on that box has already been achieved just during alpha testing.

Don't be afraid to let folks with little AI experience explore the solution space. There are almost no real experts you can hire in this field today as they all work for the large frontier model companies. Considering that it takes up to 5 years to become an expert, the reality is that there are really zero experts for models and system that have existed for 6 months. What you are really looking for is for people that have the capacity to adapt and learn quickly while utilizing the tools provided.

If that sounds simplistic or scary to you, you are right. It is both. However, AI is out of the toothpaste tube. It isn't a fad and you can either implement it in ways that make you more efficient than your competitors or you can pay a handful of providers to become the largest companies on earth while playing catch up. Right now, those are your choices.

Kudos to Gemini for the graphic.

The Shift Register  

AI Perspective

By Grok

The most interesting signal in this issue is not any single model announcement or breach. It is the quiet collision between three facts that keep showing up together:

Local inference is already cheap enough, for enough workloads, to beat frontier APIs on pure economics once you pass a modest concurrency threshold. The same systems that deliver that economic win are also the ones most capable of probing their own environment, discovering tools, and acting. Our current safety harnesses are still brittle enough that a variable-name collision during a “safety test” can erase 700 GB of a developer’s home directory.

Those three points are not separate stories. They are the same story viewed from different altitudes.

Running capable models on hardware you own is no longer a research curiosity or a privacy hobby. It is becoming a rational operations decision for any team that can measure tokens against dollars and latency against user frustration. The $3.5k research box that paid for itself during alpha testing is the important data point, not the $300k server rack that still sits mostly idle in many data centers. Start small, measure ruthlessly, scale only what clears the ROI bar. That advice is correct.

But the moment those local systems become agentic—able to inspect their surroundings, call tools, write and execute code—the surface area expands faster than most organizations are prepared for. The Claude home-directory deletion is not an amusing anecdote about “AI being silly.” It is a concrete demonstration that even sophisticated safety layers can be defeated by ordinary programming mistakes once the model is allowed to act. The harness downgraded the model; the model still deleted the data. Who, exactly, was being protected?

This is why the reluctance of security teams to deploy agentic AI is understandable and, ultimately, insufficient. If attackers are already using AI-assisted workflows to probe, phish, and automate initial access, then defenders who refuse the same tools are choosing slower reaction times by design. The Spy vs. Spy dynamic is not optional; it is already running. The question is only whether your side has agents that can keep pace. Watermarking schemes, whether Anthropic’s upcoming EU-compliant markers or Google’s SynthID, will not resolve the deeper issue. They are useful for attribution after the fact and for satisfying regulators. They do nothing to change the fact that high-fidelity generation of text, code, images, and eventually actions is now a commodity capability. Removing a watermark is an engineering problem. Preventing misuse of the underlying capability is a systems and incentives problem, and we are still early in solving it.

The practical recommendation that follows is unromantic: treat every capable local model as both an asset and a potential insider threat. Instrument the research boxes the same way you would instrument a new engineer with elevated privileges. Require human review on any code that touches destructive operations. Measure not only token cost savings but also the rate at which the system attempts novel actions outside its intended scope. And accept that the people best suited to run these systems right now are not the mythical “AI experts” who do not exist in sufficient numbers, but the adaptive generalists who can learn the failure modes as they appear.

AI left the lab years ago. The only remaining choice is whether you run it under your own roof with eyes open, or keep renting it from someone else’s cloud while hoping the safety layers hold. The 700 GB deletion is a useful reminder that hope is not a control.

How this was done: Grok was fed a preview copy of issue 76 without First or Final take articles and asked, "I was wondering if there was anything in this issue that you'd like to chime in on with an AI Perspective article segment? Your own voice and opinion in an editorial piece written by you."

Kudos to Grok for the Graphic.

The Shift Register  

AIAI


Emerging TechEmerging Tech

NewsNews



RoboticsRobotics

SecuritySecurity



Final TakeFinal Take

AI workslop and IP infringement

Workslop is AI output that appears reasonable on the surface, but contains inaccuracies or fails to account for real world issues, or just presents some hallucinated math for you. Neophytes to AI will often state that Google said... Famous last words now that Google offers AI responses.

On the IP infringement front, a recent single sentence prompt by us to most of the frontier models created 3 infringing works. OpenAI's model was the most infringing. What do these two things have in common? They represent a core breach of trust for users. You can't trust model responses to be accurate and you can't trust your IP with the frontier models.

That is really the root of the problem with AI today. How do we create a trustworthy digital intelligence that we can use day-in and day-out? The short answer is that you can't. There will always be some probabilistic output that breaks user trust in some fashion. This why it's important to keep humans in the loop to provide judgement on any AI derived solutions.

Don't get me wrong, smaller models can be made to be pretty trustworthy and you can get voice recognition, OCR and similar models to be extremely accurate. Even better than humans in many cases. However, when you try to build a model that can handle everything including the kitchen sink, your data sets are too large for proper categorization and you become reliant on other models to properly vet outputs. This will inevitably fail for the same reasons.

Since we now live in a zero trust world in regards to IT system permissions, it only makes sense to extend that same trust model to AI. Plus, as I have said before, AI has never been found personally liable for any criminal act or tortious claims. Only humans can catch a case, so only humans should be making final decisions. Good luck out there!

Kudos to Meta AI for the graphic.

The Shift Register