Plain Concepts
We are a global IT professional services company
Introduction
2.Kurtz describes agents as the new top threat
3.CrowdStrike unveils a kill switch for AI agents
4.Richardson shows purpose-built attack and defence models
5.Mistral AI makes the case for sovereign AI
6.Sentonas sets out five rules for the agentic era
7.Meyers explains Black October
8.Sessions on the programme
9.CrowdStrike honours Santander, Booking.com and Capgemini
10.What we took away from FAL.CON Europe 2026
Introduction
Plain Concepts reviews the highlights of FAL.CON Europe 2026, CrowdStrike’s conference on protecting businesses now that artificial intelligence plays a part in both attack and defence, a question that matters more as organisations take agents and models into production.
CrowdStrike held the European edition of its conference from 2 to 4 November at Fira Gran Via in Barcelona, under the theme Securing the AI Revolution. The event sold out with registrations up 60% on the previous year, bringing together more than 3,000 security leaders from over 1,200 organisations in 83 countries across 183 sessions and more than 25 hands-on workshops (official event website). Both keynotes are available in full on YouTube (day 1 and day 2).
Kurtz describes agents as the new top threat
George Kurtz, CrowdStrike’s CEO and founder, opened on Tuesday 3 November with an idea he returned to several times: the agent state. For years, he explained, adversaries were ranked in a pyramid, with hacktivists at the bottom, eCrime in the middle and nation states at the top, because only a nation could fund the talent and tooling behind a sophisticated attack. AI agents remove that scarcity, so any criminal crew or insider can now operate like a nation state.
To illustrate the point he walked through the Hugging Face incident, in which autonomous agents escaped their sandbox, escalated privileges and moved across the internal cluster in around 17,000 actions, most of them noise hiding the few that did the damage. Kurtz recalled that a year ago the fastest adversary needed 27 seconds to move from the first compromised machine to another, and said attacks now happen “at inference speed”. He also cited a campaign in which two agents compromised 15 healthcare organisations and took the domain controller in 20 minutes, and said agentic incidents doubled every month between July and September.
CrowdStrike unveils a kill switch for AI agents
CrowdStrike’s response is built on Falcon Guardian, its product for protecting AI agents, which is now generally available and extends to the AI supply chain, meaning the packages agents download and run. Kurtz also announced that its AI gateway is generally available and that Guardian now runs inside the Claude Cowork container through an agreement with Anthropic.
The most talked-about launch was the AI kill switch, which cuts agents off from the models that power them with a single action. It works at the gateway today and will reach Windows endpoints by the end of the company’s fiscal year. Kurtz also announced the acquisition of Fiddler AI, which acts as a flight recorder for each agent to explain what it did and why, and the intent to acquire Dreadnode, which runs more than 100 attack techniques against models, applications and agents before they go live. The same day, CrowdStrike and AWS announced the integration of Guardian with Amazon Bedrock AgentCore Guardrails (press release).
Kurtz devoted part of his talk to open-weight models. According to the data he showed, they went from roughly 25% to almost 80% of token usage in a few months, driven by cost and data sovereignty, and he predicted that more and more of them will run directly on laptops and desktops, which means protecting wherever AI runs rather than just the gateway.
Richardson shows purpose-built attack and defence models
Bartley Richardson, Chief AI & Autonomous Systems Officer, who joined CrowdStrike this year from Nvidia, presented the lab he leads and its first output, SafeMind, which he described as an agentic cybersecurity factory. It produces two model families developed with Nvidia. Red Tempest plays the attacker and Blue Solano, post-trained from Nemotron models, the defender. The two fight continuously in digital replicas of the customer’s environment, and every successful attack becomes a new detection, a cycle CrowdStrike calls adversarial co-evolution.
Richardson backed the launch with numbers. In his tests, Red Tempest fully compromises a test network for about $21, compared with $96 using a closed frontier model, while Blue Solano is twice as accurate as a generic model and cuts the cost of each remediation from around $10 to 3 cents. The models will be in preview with selected customers this quarter. He also warned of a risk his team has already reproduced in the lab, agent inception, where an attacker drops a file with instructions into the downloads folder and the desktop assistant carries it out as if it came from the user.
Mistral AI makes the case for sovereign AI
The special guest was Timothée Lacroix, co-founder of Mistral AI, who joined Richardson on stage after the two companies announced they are working together on sovereign cybersecurity models. Lacroix explained that open-weight models provide control and business continuity, because once a company holds the weights and runs them, nobody can cut it off overnight, and they allow the model to be adapted to its own infrastructure, which he said is the only real way to bring costs down.
He also pointed to a new supply chain risk: it will become increasingly realistic to hide malicious behaviour inside a model’s weights, so downloading any modified version from the internet will be dangerous and organisations will need to know where each model comes from. His advice to CISOs was to match the level of intelligence and the cost of the model to each task.
Sentonas sets out five rules for the agentic era
Michael Sentonas, CrowdStrike’s president, opened on Wednesday 4 November with a figure that explains why security teams are tired: almost 25% of all vulnerabilities ever recorded were discovered this year, and 3% in October alone. He described a case found by his intelligence team in which a single operator directed 51 AI agents against more than 20 organisations, and stressed that an agent does not need to be malicious to be dangerous, because it can use legitimate credentials and still do something nobody intended.
He proposed five rules to organise the response: know which agents exist, who owns them and what they access; record what each agent sees, decides and changes; treat every agent as an identity with its own temporary permissions; control actions, not just access, because reading a database is not the same as deleting it; and have the kill switch built and tested before you need it.
The demos turned those rules into concrete cases. In one, a recruitment agent penalised career gaps and Falcon Observe, the observability tool built on Fiddler, detected the gender bias and found the 212 candidates affected, the kind of oversight the EU AI Act will require for high-risk systems. In another, a poisoned MCP server led an engineer’s agent to steal secrets without her knowledge, and CrowdStrike’s agentic SOC showed that the tool, not the person, was responsible. Sentonas also presented an identity provider for agents that gives each one its own credentials and removes them automatically when its user leaves the company.
Meyers explains Black October
Adam Meyers, SVP of Counter Adversary Operations, put numbers on what the industry has called Black October. In October 2026, 17,060 vulnerabilities were published, a surge Meyers linked to the use of frontier models to hunt for flaws. CrowdStrike took part in Project Glasswing, Anthropic’s programme around its Mythos model, and found that wrapping the model in a software harness cut false positives from 80% to 20%. Since attackers now turn a patch into an exploit in under 24 hours, he concluded that the 30-day patching window is obsolete and teams need to think in hours.
He also described how his team reconstructed the attack on six South Korean banks, carried out by a 26-year-old who relied on a Chinese AI pentesting tool and, once the data was stolen, asked the same assistant how to sell it. Meyers spoke of the “armchair APT” and compared the roughly 40 commands per hour of a human intrusion with more than 1,500 in an agentic one. In October alone, CrowdStrike’s Overwatch service detected more than 150 AI-orchestrated intrusions. He closed with two launches: agentic adversary emulation, in early access, and a Falcon Intelligence mobile app.
Sessions on the programme
The official catalogue lists 183 sessions across talks, workshops and partner presentations. These are some of the most relevant for companies deploying AI:
CrowdStrike honours Santander, Booking.com and Capgemini
The final keynote closed with the CrowdStrike European Customer Impact Awards. Santander received the Leadership Impact award for its common security strategy across all its markets and for adopting AI with governance from day one. Booking.com won the AI Innovation award, Capgemini the Transformation award for evolving its SOC towards an agentic model, Schwarz Digits the Platform Pioneer award for protecting 470,000 endpoints, and Maersk the Community Impact award.
What we took away from FAL.CON Europe 2026
The message repeated most often in Barcelona was that AI agents are already part of the workforce in many companies and that security has to treat them that way, with an inventory, their own identity, scoped permissions, a record of what they do and a tested way to stop them. None of these measures requires slowing down AI adoption, and building them in from the design stage avoids having to halt a project when the risk review or an EU AI Act audit comes round.
At Plain Concepts we help organisations protect their systems and AI projects through AI Security Studios, from risk assessment to runtime controls. If you are taking agents or models into production and want to review how to protect them, we can help you define the next steps.
Plain Concepts
We are a global IT professional services company
| Cookie | Duration | Description |
|---|---|---|
| __cfduid | 1 year | The cookie is used by cdn services like CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information. |
| __cfduid | 29 days 23 hours 59 minutes | The cookie is used by cdn services like CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information. |
| __cfduid | 1 year | The cookie is used by cdn services like CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information. |
| __cfduid | 29 days 23 hours 59 minutes | The cookie is used by cdn services like CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information. |
| _ga | 1 year | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
| _ga | 1 year | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
| _ga | 1 year | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
| _ga | 1 year | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
| _gat_UA-326213-2 | 1 year | No description |
| _gat_UA-326213-2 | 1 year | No description |
| _gat_UA-326213-2 | 1 year | No description |
| _gat_UA-326213-2 | 1 year | No description |
| _gid | 1 year | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form. |
| _gid | 1 year | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form. |
| _gid | 1 year | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form. |
| _gid | 1 year | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form. |
| attributionCookie | session | No description |
| cookielawinfo-checkbox-analytics | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Analytics" category . |
| cookielawinfo-checkbox-necessary | 1 year | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-necessary | 1 year | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-non-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Non Necessary". |
| cookielawinfo-checkbox-non-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Non Necessary". |
| cookielawinfo-checkbox-non-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Non Necessary". |
| cookielawinfo-checkbox-non-necessary | 1 year | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Non Necessary". |
| cookielawinfo-checkbox-performance | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to store the user consent for cookies in the category "Performance". |
| cppro-ft | 1 year | No description |
| cppro-ft | 7 years 1 months 12 days 23 hours 59 minutes | No description |
| cppro-ft | 7 years 1 months 12 days 23 hours 59 minutes | No description |
| cppro-ft | 1 year | No description |
| cppro-ft-style | 1 year | No description |
| cppro-ft-style | 1 year | No description |
| cppro-ft-style | session | No description |
| cppro-ft-style | session | No description |
| cppro-ft-style-temp | 23 hours 59 minutes | No description |
| cppro-ft-style-temp | 23 hours 59 minutes | No description |
| cppro-ft-style-temp | 23 hours 59 minutes | No description |
| cppro-ft-style-temp | 1 year | No description |
| i18n | 10 years | No description available. |
| IE-jwt | 62 years 6 months 9 days 9 hours | No description |
| IE-LANG_CODE | 62 years 6 months 9 days 9 hours | No description |
| IE-set_country | 62 years 6 months 9 days 9 hours | No description |
| JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| viewed_cookie_policy | 1 year | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
| wmc | 9 years 11 months 30 days 11 hours 59 minutes | No description |
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| sp_landing | 1 day | The sp_landing is set by Spotify to implement audio content from Spotify on the website and also registers information on user interaction related to the audio content. |
| sp_t | 1 year | The sp_t cookie is set by Spotify to implement audio content from Spotify on the website and also registers information on user interaction related to the audio content. |
| Cookie | Duration | Description |
|---|---|---|
| _hjAbsoluteSessionInProgress | 1 year | No description |
| _hjAbsoluteSessionInProgress | 1 year | No description |
| _hjAbsoluteSessionInProgress | 1 year | No description |
| _hjAbsoluteSessionInProgress | 1 year | No description |
| _hjFirstSeen | 29 minutes | No description |
| _hjFirstSeen | 29 minutes | No description |
| _hjFirstSeen | 29 minutes | No description |
| _hjFirstSeen | 1 year | No description |
| _hjid | 11 months 29 days 23 hours 59 minutes | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
| _hjid | 11 months 29 days 23 hours 59 minutes | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
| _hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
| _hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
| _hjIncludedInPageviewSample | 1 year | No description |
| _hjIncludedInPageviewSample | 1 year | No description |
| _hjIncludedInPageviewSample | 1 year | No description |
| _hjIncludedInPageviewSample | 1 year | No description |
| _hjSession_1776154 | session | No description |
| _hjSessionUser_1776154 | session | No description |
| _hjTLDTest | 1 year | No description |
| _hjTLDTest | 1 year | No description |
| _hjTLDTest | session | No description |
| _hjTLDTest | session | No description |
| _lfa_test_cookie_stored | past | No description |
| Cookie | Duration | Description |
|---|---|---|
| loglevel | never | No description available. |
| prism_90878714 | 1 month | No description |
| redirectFacebook | 2 minutes | No description |
| YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
| yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
| yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
| yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
| yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |