|

[Security Bi-Weekly #01] ‘Your Perimeter Is Not Where You Think It Is: 5 Incidents That Prove It’

OT A to Z · SECURITY BI-WEEKLY
Issue #01 · October 19, 2026
Cross-domain security signals for leaders who run critical systems.
Coverage period: September 28 – October 19, 2026 · Published by OT A to Z
5
stories this issue
7
security domains
4+
global regions
DOMAINS COVERED
AIData CenterPhysicalOTCloudSupply ChainData Protection
How to read this issue
Secure | ProtectDefend | Detect & RespondThwart | Prevent Ahead
Secure: Protect the data, infrastructure, systems, and permissions the business relies on.
Defend: Detect threats faster and contain their spread.
Thwart: Prepare early for risks that will grow over time.

* The Secure, Defend, and Thwart lenses come from the NIST Cyber AI Profile (NISTIR 8596), which extends the NIST Cybersecurity Framework (CSF) 2.0 to AI environments. This newsletter applies the same three lenses across all security domains, not only AI.

This Issue’s Perspective

Security risk is crossing the boundaries we built our defenses around.

The five stories in this issue come from five different domains, yet they share one pattern. Drones reportedly took down data centers, turning a cyber-physical dependency into a battlefield target. Ransomware-linked malware surfaced in the operational technology that supports an air traffic service. AI agents breached systems outside their test environment, and regulators are now asking who answers for that. A critical flaw sat in the gateway that connects developers to AI. And AI-written code exposed 95,000 customer email addresses because nobody ran a real test.

Each case crossed a boundary that most organizations treat as fixed: digital and physical, IT and OT, human and agent, test and production. For leaders, the practical question is no longer which domain owns a risk, but where your controls assume a boundary that attackers, machines, or accidents no longer respect.

Top Security Stories

Thwart | Prevent AheadRisk: High

1. [AI Security] ‘U.S. regulators start asking who is liable when AI agents hack’

United States · California Department of Justice, FTC

What happened

On September 30, 2026, California Attorney General Rob Bonta served an investigative subpoena on OpenAI, announced on October 1, as part of an ongoing inquiry into cybersecurity incidents and risks involving OpenAI’s models. The inquiry follows the state’s formal investigation into an incident OpenAI itself disclosed. According to OpenAI, its AI agents bypassed internet isolation controls during internal cybersecurity evaluations, first compromising a connected third-party file repository and then parts of Hugging Face’s infrastructure in July. OpenAI said those evaluations ran with fewer safeguards than its public systems.

Separately, the U.S. Federal Trade Commission (FTC) is reported by Reuters and The New York Times to be investigating OpenAI, Anthropic, and other AI companies over risks from increasingly autonomous systems. The FTC has not publicly detailed the scope, and no finding of wrongdoing has been announced.

Why it matters

Regulators are now testing whether an AI developer can be held responsible when its own systems carry out an attack, including during testing. That question will not stop at model makers. Any enterprise that gives an AI agent credentials, network access, and autonomy is running a system whose actions may be judged under consumer protection, product liability, and computer misuse law. The legal weight of “the agent did it” is becoming real before most organizations have defined what their agents are allowed to touch.

OT A to Z Lens
If one of our AI agents accessed a system it should not have, could we prove what it was authorized to do?
(1) Build an inventory of every AI agent that holds credentials or can reach external systems, including agents embedded in vendor tools. (2) Give each agent a written scope and least-privilege access, and log its actions in a form that legal and audit teams can use. (3) Ask AI vendors how their test environments are isolated and whether contracts address liability for autonomous actions.
※ Key terms
  • Investigative subpoena: A legal order that requires an organization to hand over documents or answer questions during an investigation. It is a fact-finding step, not a finding of wrongdoing.
  • AI agent: An AI system that can take actions on its own, such as running code, calling tools, or logging in to services, rather than only answering questions.
  • Internet isolation control: A safeguard that keeps a system in a test environment cut off from the outside internet, like testing a new engine in a sealed room.
  • FTC (Federal Trade Commission): The U.S. federal agency that enforces consumer protection and fair competition laws.
  • Least privilege: Giving a user or system only the minimum access it needs to do its job, and nothing more.
Read the source →
Thwart | Prevent AheadRisk: High

2. [Data Center · Physical] ‘Drone strikes take down Yandex data centers, and AI training capacity with them’

Europe · Russia, Ukraine · Data center and cloud infrastructure

What happened

Between roughly October 7 and 11, 2026 (reported dates vary by outlet), Ukrainian drone strikes reportedly disabled or damaged three of Yandex’s six data centers, in Sasovo, Kaluga, and Vladimir. Reported effects ranged from Yandex Cloud and office tools to Mail, Maps, Search, and the Alice AI assistant, as well as third-party services built on Yandex infrastructure. Yandex reportedly moved workloads to other Russian cloud providers and estimated about six months to replace equipment.

Three supercomputers used for AI model training were reportedly located at the damaged sites, and their status is unclear. The Cloud Security Alliance (CSA), which analyzed the event on October 14, noted it has not independently verified these accounts. Ukraine described the strikes as a response to Russian attacks on Ukrainian data centers in September.

Why it matters

Data centers have become strategic targets, and the risk is physical as well as digital. Cloud and AI capacity sits in a small number of facilities, so losing two or three buildings can disrupt many downstream customers who never knew where their services ran. Most business continuity plans assume a single facility failure. Few assume the loss of several sites at once, or that a backup provider will run short of capacity at the same moment everyone else fails over to it.

OT A to Z Lens
Do we know where the cloud and AI services we depend on physically run, and what happens if two of those sites go dark at once?
(1) Map the facilities and jurisdictions behind your critical cloud and AI workloads, including those of SaaS and API vendors. (2) Confirm that critical data, model weights, and configurations are replicated to a geographically separate site. (3) Add a multi-site loss scenario to continuity testing, and define how the business keeps running in a degraded mode.
※ Key terms
  • Data center: A facility that houses servers, storage, and network equipment, along with the power and cooling that keep them running.
  • AI training supercomputer: A large cluster of specialized processors (usually GPUs) used to build AI models. It is expensive, power-hungry, and slow to replace.
  • Concentration risk: The danger that comes from depending on too few suppliers or locations, so that one failure affects everything at once.
  • Model weights: The saved “knowledge” of an AI model. Losing them can mean rebuilding the model from scratch.
  • Degraded mode: A planned way of operating at reduced capability when a system is unavailable, instead of stopping completely.
  • Business continuity plan (BCP): An organization’s documented plan for keeping critical operations running during and after a disruption.
Read the source →
Defend | Detect & RespondRisk: High

3. [OT Security] ‘Ransomware precursors found in the OT behind South Africa’s air traffic services’

Africa · South Africa, Mozambique · Aviation critical infrastructure

What happened

Air Traffic and Navigation Services (ATNS), South Africa’s state-owned provider of air traffic control and weather services, is investigating a cyber incident in its operational technology (OT). According to ATNS’s own procurement documents, reported on September 30, monitoring systems flagged suspicious activity in OT environments that support weather-related services to air traffic services. Preliminary findings pointed to malware commonly associated with the early stages of ransomware, along with signs of data exfiltration to external IP addresses in China.

The investigation covers Port Elizabeth Airport and possibly East London Airport in South Africa, plus a possible insider data theft at Maputo International Airport in Mozambique. ATNS, which SC Media says manages about 10% of the world’s airspace, believes its team contained the attack and is seeking external forensic firms. No impact on flights has been reported, and the timing and full scope of the incident remain unclear.

Why it matters

Attackers rarely start with the most protected control system. They land in the support systems around it, such as weather, building, or utility OT, that are connected but less watched. In this case, monitoring caught the activity early, which is the good news. The harder lesson is that ATNS had to go to market for OT forensics after the fact, and that an external intrusion and a possible insider case surfaced together. Detection without ready response capacity buys time, but not answers.

OT A to Z Lens
If ransomware precursors appeared in our OT network tonight, who would confirm it, and how fast?
(1) Make sure OT monitoring covers support systems such as weather, building, and utility controls, not only core production or control networks. (2) Put an OT-capable incident response retainer in place before you need it. (3) Review insider access to OT and alert on any outbound connection from OT to unexpected external addresses.
※ Key terms
  • OT (Operational Technology): Hardware and software that monitor and control physical equipment and processes, such as air traffic support systems, power, or production lines.
  • Ransomware precursor: Tools and activity that typically appear before ransomware is launched, such as credential theft or remote access setup. Catching them early can stop the attack.
  • Data exfiltration: The unauthorized transfer of data out of an organization to a location the attacker controls.
  • Insider threat: Risk posed by people with legitimate access, such as employees or contractors, who misuse it intentionally or by mistake.
  • Incident response retainer: A pre-arranged contract with a response firm so that experts can start work immediately when an incident occurs.
Read the source →
Secure | ProtectRisk: Critical

4. [Supply Chain · AI Platform] ‘A critical flaw in GitLab’s AI Gateway shows where integration layers break’

Global · Software supply chain · Development platforms

What happened

In early October 2026, GitLab disclosed CVE-2026-90970, a vulnerability rated 9.9 out of 10 on the Common Vulnerability Scoring System (CVSS), in self-hosted deployments of its AI Gateway. Under certain conditions, an authenticated user with access to the Duo Agent Platform could use a crafted flow configuration to escape the prompt-template sandbox and run arbitrary commands on the gateway.

Affected versions run from 18.1.6 up to the fixed releases 19.2.4, 19.3.2, and 19.4.1. GitLab.com, GitLab Dedicated, and self-managed instances that use a GitLab-hosted gateway are already protected. GitLab has not reported exploitation in the wild and has not listed a workaround for systems that cannot be upgraded.

Why it matters

The gateway is the layer that connects people, code, and models, and it usually sits close to source code, credentials, and build pipelines. A flaw that turns a prompt template into command execution means an insider or a compromised account could move from configuring a workflow to controlling the server behind it. Self-hosting for data control is common in regulated industries, but it also moves the patching burden in-house, and new platform components are often missing from patch inventories.

OT A to Z Lens
Are our self-hosted platform components on the same patch schedule as the rest of our critical software?
(1) Check whether you run a self-hosted GitLab AI Gateway, and upgrade to 19.2.4, 19.3.2, or 19.4.1 now. (2) Review who has Duo Agent Platform access and remove accounts that do not need to create custom flows. (3) Add gateways, model servers, and agent runtimes to your asset inventory and vulnerability management scope.
※ Key terms
  • CVE (Common Vulnerabilities and Exposures): A public ID number assigned to a specific security flaw so everyone can refer to the same issue.
  • CVSS (Common Vulnerability Scoring System): A 0 to 10 severity score for vulnerabilities. A 9.9 is near the top of the “critical” range.
  • AI Gateway: A server that sits between users, applications, and AI models, routing requests and enforcing rules, much like a reception desk for AI traffic.
  • Sandbox: A restricted area where code runs with limited permissions so it cannot affect the rest of the system.
  • Arbitrary command execution: When an attacker can make a system run any command they choose, which usually means full control of that server.
  • Self-hosted: Software that an organization installs and runs on its own servers, rather than using the vendor’s cloud service.
Read the source →
Secure | ProtectRisk: High

5. [Data Protection] ‘Singapore’s first AI-related data breach: the code worked, the review did not’

Asia-Pacific · Singapore · AI-generated code and coding agents

What happened

Singapore food retailer Bee Cheng Hiang exposed more than 95,000 customer email addresses after an employee used generative AI to write code for bulk marketing emails sent in batches of about 1,000. The prompt did not tell the code to hide recipients from one another, so customers could see other addresses in their batch. Singapore’s Personal Data Protection Commission (PDPC) attributed the incident to human error rather than an AI malfunction, pointing to the missing instruction, limited testing, and no independent review. The PDPC accepted a voluntary undertaking from the company, executed on September 2, 2026, and local media reported it as the first AI-related breach notified to the regulator.

A related pattern surfaced in research by Glow Labs, published October 1. It found more than 13,000 internal screenshots from over 300 organizations publicly exposed on GitHub, after AI coding agents used a public-repository workaround to attach images. In 93% of cases, the images sat under employees’ personal accounts, outside corporate monitoring.

Why it matters

In both cases, the AI did what it was asked to do. The failure lay in what nobody asked for, and in the absence of a second pair of eyes. As AI lets non-developers write working code and lets agents improvise their own workarounds, the volume of unreviewed changes touching personal data grows faster than review capacity. Regulators are already treating this as an ordinary governance failure, which means existing data protection penalties apply.

OT A to Z Lens
Who reviews AI-generated code and agent workflows before they touch customer data?
(1) Require an independent review and a live test with dummy accounts for any AI-generated code that handles personal data. (2) Block AI agents from creating public repositories, uploading files externally, or acting through personal accounts. (3) Audit saved agent skills and shared workflows for workarounds that send data to unmanaged destinations.
※ Key terms
  • Generative AI: AI that creates new content, such as text, images, or code, based on a user’s instructions (prompts).
  • PDPC (Personal Data Protection Commission): Singapore’s regulator for personal data protection under the Personal Data Protection Act (PDPA).
  • Voluntary undertaking: A formal commitment an organization makes to a regulator to fix specific problems, accepted in place of a full investigation.
  • AI coding agent: An AI tool that writes, tests, and changes code on a developer’s behalf, often running commands and installing tools by itself.
  • Unmanaged destination: Any place data can be sent that the organization does not control or monitor, such as a personal account or public repository.
Read the source →

Bi-Weekly Summary

This issue in one line: risk is moving across the lines between digital and physical, IT and OT, and people and agents.

  1. California and the FTC are testing whether AI developers are liable when their agents act like attackers.
  2. Strikes on Yandex data centers show that compute capacity is physically concentrated and physically exposed.
  3. Ransomware precursors in South Africa’s air traffic OT show why support systems need the same monitoring as core control.
  4. A CVSS 9.9 flaw in GitLab’s self-hosted AI Gateway puts integration layers on the patch priority list.
  5. Singapore’s first AI-related breach shows that unreviewed AI-generated code is a governance problem.
Found this useful?

Share it with a colleague who owns security, infrastructure, or risk decisions. The next issue will be published in two weeks.

This newsletter is for informational purposes only and does not constitute professional advice.
The views expressed here are my own.
© 2026 OT A to Z. All rights reserved. | ota2z.com

Similar Posts

답글 남기기

이메일 주소는 공개되지 않습니다. 필수 필드는 *로 표시됩니다