In many businesses, cybersecurity still follows a relatively familiar rhythm: detect an unusual signal, collect logs, pass them to a specialist team, assess severity, and only then decide whether to contain or remediate. AI is changing that rhythm on both sides. It can help defensive teams read large volumes of signals faster, but it can also make finding weaknesses, writing deceptive content, or trying many attack variants faster. The management implication is not simply that “risk increases”; the time available for an organization to understand and respond may become shorter.
In an update on 18 August 2026, OpenAI said that it is strengthening monitoring, alignment, and containment measures in response to advancing cyber capabilities in models. The post also noted that monitoring compute can be material in some configurations, with an estimate of about 20% of inference capacity. Although this is an estimate from one model developer, it raises an important management question: if control is not built into operating design from the start, businesses will tend to treat it as an add-on after systems have already been deeply connected.
Do not only protect the model; protect its ability to act
The practical risk is often not that a model gives an incorrect answer to a general question. Risk rises when a model or AI agent is connected to email, data repositories, CRM, development tools, or operational software. An inaccurate output can then become an action: sending information to the wrong recipient, changing data, accessing unnecessary files, or proposing a step that employees assume has been checked.
For this reason, an enterprise AI inventory should record not only the name of a tool and the department using it, but three further points: what data the tool reads, what actions it can take, and who approves those actions. This is the difference between managing applications and managing authority to act. A chatbot using only public material has a very different risk profile from an agent that can query a CRM, create emails, and update order status.
Three control layers should operate together
Access discipline. Grant the minimum access required for the task, separate read permission from edit permission, and set an expiry date for experimental connections. A shared administrator account should not be used merely because it makes deployment faster. Human escalation thresholds. Work that can create customer commitments, affect money, change official data, or touch critical systems must stop at a clear approval point. The threshold should be based on the consequence of the action, not on a feeling that “AI is usually right.” Traceability and exercises. Retain data sources, important instructions, actions performed, and approvers; also rehearse situations such as information exposure, an incorrect tool call, or persuasive synthetic content.
Which indicators show that control is working?
A business should not measure AI control by the number of policies it has issued. Track operational indicators instead: the share of AI connections with a named owner; the share of sensitive actions passing through approval gates; the time needed to detect and isolate an unusual connection; the number of completed exercises; and the share of AI recommendations that need correction or rejection because data, permissions, or reasoning are inadequate. These indicators do not eliminate risk, but they show whether the business is able to see and control it.
Over the next 90 days, a sensible step is to map the AI connections already in place, prioritize those that can affect the outside world, and then run a cross-functional exercise for one specific scenario. Technology teams cannot do this alone: operations, legal, risk management, HR, and process owners all need to know what the system may do and where it must stop. When the pace of change increases, a good control mechanism is not one that makes everything slower; it is one that helps the organization recognize risk and decide early enough.
References
OpenAI. (2026, August 18). Pacing model development in an era of cyber-critical capabilities. https://openai.com/index/pacing-model-development-cyber-capabilities/
