From the Cisco edition of October 29, 2026
Cisco launches Model Foundry in Cloud Control for partners; Cisco reports a fine-tuned Deep Network model found the right fix in 11 of 12 WWT lab problems
Cisco · AI for network and security operations (partner channel) · Global (announced at Cisco Partner Summit, Vancouver)
- Publisher
- Cisco Blogs
- Original publication
- Cisco Blogs, Oct. 26, 2026
- Source retrieved
- 2026-10-30
- Event date
- 2026-10-26
What happened
Cisco introduced Model Foundry, a Cisco Cloud Control service in controlled availability for partners first, giving access to Cisco domain models (Deep Network 1.4, Antares-3B, Decision Model 1.0, Time Series Model 1.0) through an OpenAI-compatible API with tenant-scoped keys, per-model access controls and usage visibility, plus fine-tuning on customer data with side-by-side base-versus-tuned evaluation. In a lab test with World Wide Technology on real Cisco devices, Cisco fine-tuned the 31-billion-parameter Deep Network model and reports it recommended the exact right fix in 11 of 12 unseen problems (BGP, OSPF, link failures, router policy, simultaneous faults, benign changes), graded against an answer key and by an AI judge. Cisco says the work took five weeks and that recognizing a healthy network and untangling simultaneous faults are still hard problems. Cisco states training data and created models belong to "you".
Why it matters
State IT agencies, large districts and universities usually reach Cisco through integrators, so a partner-first model service means the first tuned Cisco models in SLED networks will come from those integrators. Relevant to network operations teams facing staff shortages, but evidence is a single vendor-run lab test.
Evidence and measured results
Opened the Cisco blog and read it in full, including footnotes on the grading method. The results table image was not machine-readable; figures used are from the text and the WWT quote.
Limitations and uncertainty
Vendor-run, 12-problem lab evaluation with an AI judge; not production, not public sector; controlled availability; features "when-and-if-available".
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Network teams have too few engineers for troubleshooting load across large public networks.
- Stakeholders
- Network operations manager
- State or campus CIO
- Integrator account team
- Legal / procurement
- Discovery questions
- Which incident types take the most engineer time?
- Is historical ticket and config data usable for evaluation?
- Can network data be used for training outside the agency?
- Value hypothesis
- A domain model evaluated on the agency’s own past incidents may speed triage, with humans approving fixes.
- Potential engagement
- Replay evaluation of an untuned Cisco model on past incidents before any fine-tuning.
- Unsupported claims
- Production accuracy of 11 of 12
- Autonomous remediation
- Ownership of tuned weights without contract terms
Pre-sales engineering
Role takeaway
- Fit
- Fits Cisco-heavy networks with integrator support and incident history.
- Architecture and integration
- OpenAI-compatible API into existing agents; fine-tuning on configs, logs, tickets and agent traces; base-versus-tuned evaluation.
- Prerequisites
- Incident and config history
- Integrator access to Cloud Control
- Data-sharing approval
- Constraints
- Controlled availability, partners first
- Single vendor lab test
- Healthy-network and dual-fault cases still weak
- Security
- Training data is sensitive infrastructure data; restrict processing location and access to tuned weights.
- Proof of value
- Replay past incidents and score against shipped fixes
- Include healthy-network cases
- Export evaluation results
Delivery
Role takeaway
- Work
- Run a replay evaluation, then decide on tuning.
- Dependencies
- Integrator engagement
- Legal review of data use
- Incident data extraction
- Ownership
- Network operations manager with legal/procurement
- Skills and adoption
- Engineers learn to review and approve agent recommendations; integrator supplies tuning skills.
- Governance checkpoints
- Data-use approval before training
- Ownership clause signed
- Human approval for every change
- Acceptance criteria
- Ownership of weights and evaluations in contract
- Replay pass rate agreed in advance
- Zero unapproved changes during pilot
- Risks
- False faults on healthy networks
- Lock-in to partner-managed models
- Leakage of config data
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
OpenAI-compatible endpoints let existing agents call Cisco models with a configuration change; fine-tuning uses configs, logs, alerts, tickets and agent traces.
Governance
Who approves, reviews and stays accountable for outcomes?
Fine-tuning on agency network data raises ownership and retention questions; the blog’s "your data belongs to you" addresses partners.
Security and privacy
What data, permissions and controls need testing?
Network configurations and tickets used for training are sensitive infrastructure data; where training runs and who can access tuned weights must be contracted.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Decision Model is designed to escalate to a human; positioned as augmenting scarce network engineers.
Procurement
What should contracts, pricing and exit terms secure?
Partner-delivered tuning may appear as recurring services on statements of work; agencies should specify ownership of tuned weights and evaluations.
Operating model
Which teams own the service once it runs?
Agent recommends a fix for a human to approve in the WWT test; autonomous remediation is not claimed.
Publication history
- 2026-10-29Cisco · Issue 0111 resources
Stable resource ID: cisco-model-foundry-cloud-control-partners-wwt-lab-11-of-12-20261026