Protected by disappearing
On November 19, the European Commission confirmed a cyber campaign that it had detected on October 22 and confirmed four days later. As a protective measure, it temporarily took down several applications; most had since been restored. Investigators had found no evidence of a data breach affecting Commission staff as a whole, although the investigation remained open. The apps disappeared before the uncertainty did. [1]
The Commission also confirmed that a publicly available AI tool had been used and called the activity an “AI generated cyber campaign.” It described a series of incidents but did not identify the attacker, establish the objective, name the affected applications or qualify the campaign’s scale. Nor did it explain exactly how much difference the AI made. That missing detail matters more than the label. [1]
In plain English, an AI-assisted security tool can help search for weaknesses in computer systems and automate parts of that search. The same basic capability may help a defender inspect its own systems or help an attacker probe somebody else’s. A useful tool does not acquire morals when its user changes tabs. The Commission said AI can help prevent attacks and can also be misused to detect vulnerabilities. [1]
What interests me is the small contradiction inside the response. Applications were taken away in order to protect their users. That may have been exactly the right decision. Yet to anyone who needed one of those applications, protection and interruption could arrive as the same event. Security had succeeded provisionally, while service had failed temporarily. [1]
Containment has customers
We often discuss cyber incidents as a contest over data: was information stolen, altered or exposed? Those are essential questions. But an organisation can avoid a confirmed large breach and still impose a real cost through containment. Work pauses. A process moves to email or paper. Someone waits for access while investigators decide whether restoring it would reopen the door. [1]
The Commission did not disclose which applications were unavailable or what consequences followed, so it would be wrong to invent a queue of stranded citizens. The narrower point survives without drama: when defenders withdraw a digital function, its users bear part of the defensive cost. They may never know whether the shutdown prevented disaster or merely accompanied suspicion. [1]
This changes the practical meaning of resilience. Keeping attackers out is one task. Keeping essential work going while nobody yet knows whether they got in is another. The first favours walls, locks and isolation. The second requires fallback routes, limited modes, recoverable records and people authorised to make difficult decisions without switching off everything around the suspected problem. [1]
A rehearsal before reality
There is an unexpected connection in Google’s new testing system for browser agents—AI software that can click, type and navigate websites for a user. Google built an isolated synthetic web containing thousands of simulated sites. There, agents can encounter hostile material, including prompt injections: instructions hidden in a page that try to manipulate the agent into doing something unauthorised. [2]
Google says this “mirror dimension” lets its security pipeline generate more than 1,000 test candidates per security engineer each day. The controlled environment can be reset, repeated and attacked without touching real accounts or websites. Its announcement describes impressive testing capacity, but it does not publish independent results demonstrating how much safer the browser agent became. [2]
A fake web and a real shutdown point towards the same useful habit: rehearse uncertainty before users have to live inside it. Security teams should not only test whether an AI-enabled threat can enter. They should test what the organisation removes in response, how long restoration takes, and whether the remaining service is enough for the person trying to finish an ordinary task. [1] [2]
There is a serious counterargument. The Commission has disclosed too little to show that AI materially changed this campaign. Taking applications offline can be prudent containment, not evidence of a new technological era. I think that caution is right. “AI-generated” should not become a theatrical prefix attached to every familiar security problem, especially while attribution, scale and method remain unresolved. [1]
Still, prudent containment needs a human measure. If you run a service, ask which functions must survive an investigation, what manual fallback exists and who can isolate one component without darkening the whole building. If you depend on a service, ask how you would retrieve essential records or continue urgent work during an outage. Backups preserve data; continuity preserves agency.
The Commission called the applications’ removal temporary. That word measures the event from the defender’s side: it ended. “Unavailable” measures it from the user’s side: it mattered while it lasted. Good AI security must hold both meanings at once. The safest system is not necessarily the one that never closes a door. It is the one that knows which doors must remain usable, even while everyone is still asking what came through. [1]
Sources and further reading
AI Transparency
This Founder Reflection and its editorial image were produced with AI under Andrew David Baron's editorial direction. Linked sources support reported facts; the perspective and interpretation are editorial.
