AI malware workshops are becoming a practical evaluation point for critical infrastructure, telecom, OT, and security teams that need to separate defensible preparation from broad claims about AI-enabled attacks. As of November 5, 2026, the available event set spans short virtual sessions, policy conferences, AI security workshops, and incident-response labs scheduled from November 6, 2026, through April 25, 2027.
The key change is not that every event is narrowly about AI-generated malware. The research set is wider: some sessions focus on AI agents, prompt injection, vendor diligence, OT and ICS security, AI governance, red-team and blue-team exercises, and early incident response. For infrastructure teams, that breadth matters because AI-enabled threats can enter through software supply chains, model behavior, vendor tools, agentic workflows, or conventional enterprise systems connected to operational environments.
What The Scheduled Events Actually Cover
Date Order And Scope
The schedule begins with the Netsync AI Defense Workshop on November 6, 2026, described as a virtual session on securing the AI lifecycle. Its stated focus includes discovery, red teaming, model protection, checks for embedded malicious payloads, agentic workflow defense, and runtime policy enforcement. That makes it relevant to teams reviewing how AI components are introduced into OT, IT, or telecom support systems.
On November 19, 2026, the Digital Government Institute’s AI to Support Cybersecurity workshop is listed as a virtual session from 1:00 pm to 3:30 pm Eastern. The research notes say it covers defensive and offensive roles of AI, threat actors using AI, IoT and federal systems, and enterprise hardening against AI-enabled adversaries. The critical infrastructure link is indirect but plausible where federal systems, IoT, and enterprise networks connect with public services.
On December 3, 2026, SANS is scheduled to present AI Threats to OT & ICS Security from 10:30 am to 11:00 am Eastern. The session is described as highlighting survey data on industrial organizations facing adaptive malware, AI-enabled lateral movement, and detection evasion in OT and ICS environments. Among the listed opportunities, this appears closest to industrial infrastructure operations.
On January 23, 2027, Packt Publishing’s When AI Agents Go Rogue is listed as an interactive online workshop from 9:00 am to 12:30 pm Eastern, with coverage of adversarial AI, rogue agents, prompt injection, and attack-and-defense scenarios in critical systems. The event listing identifies the session date and online format through Eventbrite’s workshop page.
AI Malware Workshops And The First 72 Hours
The February 22, 2027, Workshop B at the Healthcare & Life Sciences AI Summit is framed differently. It is not presented as an infrastructure malware session in the narrow sense. It focuses on vendor and model diligence, cyber risk, simulated AI incidents, and legal and operational response during the early hours of an AI failure. The session is listed by American Conference Institute as running from 1:00 pm to 4:30 pm Eastern on the workshop agenda.
That first-72-hours framing is useful for infrastructure operators because incident response is often where policy, procurement, legal review, communications, and engineering collide. A model failure, compromised agent, or AI-supported malware event will not be handled only by a SOC. It may require vendor contacts, system owners, data protection staff, physical operations teams, and executives who can approve containment steps that affect service availability.
How AI Malware Workshops Map To Infrastructure Risk
Why OT, ICS, And Telecom Teams Should Separate Claims
AI malware workshops should be assessed by the operational problem they help solve, not by the most dramatic scenario in the title. Critical infrastructure environments include long-lived assets, safety constraints, regulated change windows, vendor dependencies, remote access paths, monitoring tools, and legacy systems. A useful event should make clear whether it is teaching general AI security concepts, AI-assisted attacker behavior, AI-agent safety, OT-specific detection, or incident governance.
For telecom teams, the connection is also practical. Communications networks support public safety, enterprise connectivity, cloud access, industrial telemetry, and remote operations. A workshop that covers AI agents or adversarial prompt behavior may be relevant if the organization is testing AI copilots, automated ticket handling, network operations support, or security triage. It is less relevant if it never reaches the controls needed for production systems.
The AAAI-27 Workshop on Artificial Intelligence for Cyber Security, scheduled in conjunction with AAAI-27 in February 2027 in Montreal, is described as focused on AI applications in cybersecurity and the security of AI-enabled systems themselves. The research notes also describe offensive cybersecurity repurposed for defense as a special theme. That can be valuable for research teams, but infrastructure operators should ask whether the material translates into policy, monitoring, procurement, and change-control actions.
| Event Date | Event Type | Most Relevant Infrastructure Question |
|---|---|---|
| November 6, 2026 | AI lifecycle defense workshop | How are models, agents, and runtime policies controlled? |
| November 19, 2026 | Government cybersecurity workshop | How are AI-enabled adversaries considered in enterprise and IoT defenses? |
| December 3, 2026 | OT and ICS security presentation | What evidence exists for AI-enabled activity in industrial environments? |
| January 23, 2027 | Agentic AI red/blue workshop | How do prompt injection and rogue-agent scenarios affect critical systems? |
| February 22, 2027 | Contracting and incident-response lab | What should happen during the first 72 hours of an AI failure? |
Evaluation Criteria For Security And Telecom Teams
Practical Questions To Bring Into A Session
Teams reviewing AI malware workshops can use a short checklist before allocating staff time. The goal is not to reject broader AI security events, but to identify whether the session produces decisions that can survive contact with production constraints.
- Does the event distinguish AI-generated malware from AI-assisted phishing, AI-agent misuse, prompt injection, model tampering, and conventional malware with AI branding?
- Does the agenda address OT, ICS, telecom, healthcare, federal, or industrial environments with concrete operational limits?
- Are defensive practices framed around governance, monitoring, incident response, vendor oversight, and change control rather than offensive technique replication?
- Does the session explain what evidence is based on surveys, simulations, lab demonstrations, or observed incidents?
- Can participants leave with updates to playbooks, procurement questionnaires, tabletop exercises, or escalation procedures?
Prior analysis of AI governance workshops made a similar point: events are most useful when teams connect the agenda to stakeholders, evidence, and follow-up work. That same discipline applies here. A security team should be able to say which control, document, workflow, or escalation path changed after the session.
For organizations that turn workshop outputs into staff education, the wider publishing network includes learning-focused resources such as this related site. Infrastructure security training still needs sector-specific validation, but clear educational design matters when technical material must reach legal, operations, procurement, and executive audiences.
Gaps And Uncertainties In The Current Event Set
What Is Not Yet Proven
The event list does not prove that AI-generated malware is already causing widespread failures in critical infrastructure. It shows that training providers, research workshops, policy forums, and security educators are organizing around AI-enabled cyber risk. That distinction matters. Infrastructure teams should avoid treating workshop descriptions as incident evidence.
Several listed events are adjacent to the malware question rather than centered on it. The FAR.AI Technical Innovations for AI Policy conference in Washington, DC, scheduled for April 15–16, 2027, is described as including workshops and sessions on AI security law, governance, and policy. The San Francisco Alignment Workshop on April 24–25, 2027, is described as focused on trustworthy and secure AI. Both may intersect with infrastructure defense, but the research notes do not show that either is designed specifically around AI-generated malware in power, water, telecom, transport, or industrial control systems.
This does not reduce their value. It does mean infrastructure teams should classify opportunities by fit. A policy forum may help with regulatory language and governance. A red/blue workshop may help security engineers test assumptions. An OT and ICS presentation may help operations leaders assess detection and response concerns. A contracting lab may help legal and procurement teams tighten vendor obligations. Each format answers a different question.
AI Malware Workshops For Critical Infrastructure Teams
The near-term value of AI malware workshops is in disciplined preparation: better questions for vendors, clearer incident roles, sharper tabletop scenarios, and a more careful distinction between AI-agent risk, model failure, and malware behavior. The schedule from November 6, 2026, through April 25, 2027, gives infrastructure teams several ways to test their assumptions without treating any single session as definitive.
The strongest approach is to map each event to a current operational gap. If the problem is OT visibility, the December 3, 2026, SANS session appears closer to the operating environment described in the research notes. If the problem is agent behavior or prompt injection, the January 23, 2027, online workshop is more directly aligned. If the problem is vendor accountability and early response coordination, the February 22, 2027, contracting and incident-response lab offers a clearer match.
For telecom and critical infrastructure professionals, the evidence supports cautious participation rather than hype. Workshops can help teams rehearse decisions, expose weak assumptions, and translate AI security language into operational controls. They do not, by themselves, validate threat prevalence, replace sector-specific engineering judgment, or prove that a simulated scenario will match a real incident.