How Cisco Uses OpenAI to Achieve Machine-Speed Defense

Cisco partners with OpenAI to advance security response to machine speed through network intelligence plus model reasoning.
Cisco collaborates with OpenAI to build an adaptive security defense system. The core idea is to use contextual information accumulated by network devices—such as traffic patterns, device identities, and access relationships—as model input, combined with OpenAI's reasoning capabilities, to advance threat detection and response from manual analyst review to machine speed. The article notes that relying solely on model capabilities is insufficient; the key lies in what data the model can see, and network intelligence provides a differentiated advantage. Machine speed means defense strategies can adapt to evolving attacks, letting security teams focus on strategy and high-risk decisions. For enterprises, evaluating security solutions should consider both model capabilities and data integration depth.
The speed of enterprise security defense response is becoming a critical variable determining success or failure. Cisco recently disclosed its approach to building an adaptive defense system in collaboration with OpenAI: combining network intelligence with OpenAI models to advance the pace of threat detection and response from manual processes to machine speed.

From Manual Response to Machine Speed
In traditional enterprise security operations, after an alert is generated, analysts often need to review it one by one, correlate context, and then decide on response actions. This chain is barely feasible when staffing is sufficient, but in the face of large-scale, automated attack methods, the manual pace easily becomes a bottleneck.
Cisco's direction is to use the intelligence accumulated by the network itself as input to the model. Network devices inherently possess contextual information such as traffic patterns, device identities, and access relationships. When this data is combined with the reasoning capabilities of OpenAI models, the defense system can determine anomalies and respond in a shorter time. The officially stated goal is clear: build a more adaptive defense system.
Machine-speed response in the context of security operations refers to the entire closed loop from signal collection, anomaly determination, to response actions being completed automatically by the system, with end-to-end latency typically measured in seconds or milliseconds, rather than relying on analysts working in shifts. In contrast, the traditional SOC (Security Operations Center) tiered alert process involves first-line analysts triaging, second-line deep investigation, and escalation to the incident response team, with the average handling time for a single alert often measured in hours or even days. The prerequisites for achieving machine speed include high-quality, low-latency telemetry data pipelines, automatically executable response interfaces (such as isolating endpoints or issuing access control policies), and determination models sufficient to suppress false positives—otherwise automation will only amplify false positives into business interruptions.
Why Network Intelligence Is the Differentiator
Relying solely on model capabilities is not enough to solve enterprise security problems; the key lies in what the model can see. Cisco's advantage is that its network product line covers key nodes of enterprise traffic, enabling it to provide the model with signals close to the actual environment.
The significance of this combination is that the model does not have to rely only on isolated logs or endpoint data, but can make judgments based on behavior patterns at the network level. According to Cisco, the combination of network intelligence and OpenAI models is the core path to strengthening enterprise security, and the adaptability of defense comes from the superposition of data breadth and reasoning depth.
Network-side context is regarded as a differentiated input for security models because of the position of network devices: switches, routers, and firewalls inherently sit on the必经 path of east-west and north-south traffic, and can observe communication peers, protocol fingerprints, traffic baseline deviations, and device identities (such as terminal types identified via MAC, certificates, or network access control). Compared with endpoint logs or application logs, network telemetry is harder for attackers to tamper with at the host level, and its coverage does not depend on installing an agent on every device. However, network data also has limitations such as reduced visibility of encrypted traffic and high volume and noise, so it usually needs to be cross-correlated with endpoint, identity, and cloud logs to form a complete basis for judgment.
The Implementation Logic of Adaptive Defense
"Machine speed" does not just mean faster response; it means defense strategies can be adjusted as attack patterns change. When models can continuously learn from network signals, security teams have the opportunity to delegate repetitive analysis to the system and focus manpower on strategy formulation and high-risk decisions.
Cisco has not disclosed specific performance metrics or deployment scale in public information, but its technical route sends a signal: enterprise security is shifting from "detection to alert" to a closed loop of "detection as response." For security teams, this means the evaluation criteria for toolchains will also change—beyond model capabilities, the depth of data integration will become increasingly important.
Adaptive defense differs from static rule-based protection in its feedback loop: the system continuously adjusts detection thresholds, policy priorities, and response actions based on the actual evolution of attacks and response outcomes, rather than waiting for manual updates to the rule base. In engineering practice, this usually involves automated policy orchestration (such as SOAR-type platforms), dynamic access control based on risk scoring, and continuous evaluation of model outputs to prevent drift. It should be noted that adaptive does not mean completely unsupervised—high-risk actions (such as cutting off core business links) generally still retain manual approval steps, and models are more responsible for initial judgment and noise reduction.
Practical Implications for Enterprises
For enterprises planning security architectures, this collaboration provides an evaluation perspective: when choosing security solutions, not only should the strength of the model itself be considered, but also whether the vendor can provide sufficiently rich network-side context. Models lacking data support are unlikely to demonstrate adaptability in the face of real attacks.
Cisco's collaboration with OpenAI is still evolving, and the specific productized form remains to be seen. However, the combination of "network intelligence + model reasoning" has already provided a reference sample for machine-speed defense.
One-line Summary
Cisco partners with OpenAI to advance security response to machine speed through network intelligence plus model reasoning.
Paragraph Summary
Cisco collaborates with OpenAI to build an adaptive security defense system. The core idea is to use contextual information accumulated by network devices—such as traffic patterns, device identities, and access relationships—as model input, combined with OpenAI's reasoning capabilities, to advance threat detection and response from the manual pace of analysts reviewing alerts one by one to machine speed. The article points out that relying solely on model capabilities is insufficient to solve enterprise security problems; the key lies in what data the model can see. The signals close to the actual environment provided by network intelligence constitute a differentiated advantage. Machine speed is not just faster response, but rather defense strategies that can adaptively adjust to attack patterns, allowing security teams to delegate repetitive analysis to the system and focus manpower on strategy and high-risk decisions. For enterprises, evaluating security solutions should consider both model capabilities and the depth of data integration.
Related articles

Running a Local LLM on a Laptop CPU: Ollama + Qwen3 Gives a Desktop Pet a Brain
An ordinary laptop without a GPU can run a local LLM: a Bilibili creator uses Ollama plus open-source Qwen3 8B on pure CPU to give an original desktop pet a local brain, with DeepSeekHarness handling plugin development and three rounds of debugging — 0 yuan, works offline, privacy stays on-device.

AgentScope 2.0 in Practice: A Guide to Enterprise-Level AI Agent Development in Java
AgentScope 2.0 is Alibaba's Java enterprise-grade distributed agent framework. This article explains why it suits server-side AI applications, contrasts client-side AI apps in permissions, state management, and concurrency, and outlines a practical learning path from environment setup to project integration.

GPT-6 Astra Directly Edits Weights to Fix Models? Full Analysis of the MIT Paper and Leaks
MIT paper shows GPT-6 Astra repairs small models by directly editing weights, raising math scores from 7.9% to 48.1%; OpenAI internal charts hint an unreleased model leads on BenchCAD 2.0; Fable 5.5 pure-code movies and the Claude WiFi radar incident analyzed.