From the Cisco edition of November 9, 2026
The Register: Cisco exposes Mythos functionality inside AI Defense under existing licenses without giving customers the model; IBM follows with Concert
The Register (reporting on Cisco, Anthropic and IBM) · AI security tooling and frontier-model access controls; cross-SLED applicability · Global (Cisco Live Melbourne announcement); no U.S. public-sector detail
- Publisher
- The Register
- Original publication
- November 10, 2026 00:00 UTC (November 9, 2026 evening U.S. Central)
- Source retrieved
- 2026-11-10
- Event date
- 2026-11-09
What happened
The Register reports that Cisco AI Defense red teaming will be able to call Anthropic's Mythos to test customer setups, and that Cisco will offer it under users' existing licenses at no additional cost. It frames Mythos as a model whose distribution has been controlled (Project Glasswing) because it could help attackers, notes the Cisco deal exposes functionality without model access, and reports IBM announced a similar Concert integration hours later. Anthropic says demand has created a long queue of buyers.
Why it matters
If Mythos-backed testing arrives under existing AI Defense licenses, SLED customers with AI Defense may gain access without a new procurement, which affects budget and contract review. It also signals that frontier cyber-capable models will reach public-sector environments through vendor products before agencies set their own policies.
Evidence and measured results
Reporting with on-record quotes from Cisco SVP Jeff Schultz and Anthropic APAC head of applied AI Natalie Mead; no hands-on testing, metrics or customer evidence. Anthropic declined to say whether similar third-party deals exist.
Limitations and uncertainty
Pricing statement ('without additional cost') is vendor-stated and may change; availability is still limited to select enterprises per Cisco. The article's Mythos 5.2 pricing details concern Anthropic's direct API, not Cisco's product.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies may receive frontier-model capabilities through existing licenses without a procurement or privacy review designed for them.
- Stakeholders
- CISO
- Procurement/contracts officer
- Privacy officer
- AI governance committee
- Discovery questions
- Does your AI Defense contract cover new AI subprocessors automatically?
- Who approves enabling new AI features in existing SaaS tenants?
- Would your policy allow a frontier cyber-capable model to test your systems via a vendor?
- Value hypothesis
- Existing AI Defense customers could evaluate advanced red teaming with lower procurement friction, if governance review keeps pace.
- Potential engagement
- A short contract and subprocessor review of AI Defense terms paired with a test-authorization policy draft.
- Unsupported claims
- That the feature is free in all contracts or regions
- That Mythos finds more vulnerabilities than other tools
- That public-sector tenants are eligible
Pre-sales engineering
Role takeaway
- Fit
- Relevant only where AI Defense is already deployed and AI apps or agents are exposed to testing.
- Architecture and integration
- Through AI Defense's structured red-team jobs; no direct Mythos API access.
- Prerequisites
- Existing AI Defense tenant
- Registered test targets
- Documented data flows for test traffic
- Constraints
- Limited availability
- Vendor-controlled safeguards not independently inspectable
- Jurisdictional data-processing terms unknown
- Security
- Require documentation of Anthropic's role as processor, logging and retention for test interactions, and the ability to disable the feature tenant-wide.
- Proof of value
- Confirm in writing which contract terms cover Mythos processing
- Verify a tenant-level control exists to enable or disable Mythos-backed tests
Delivery
Role takeaway
- Work
- Governance updates so licensed AI features introduced mid-contract are reviewed before enablement.
- Dependencies
- Cisco contract documentation
- Agency privacy and procurement policies
- Ownership
- Agency CISO with procurement and privacy office.
- Skills and adoption
- Contract and privacy staff need familiarity with AI subprocessor and dual-use model risks.
- Governance checkpoints
- Subprocessor review before enablement
- AI governance committee sign-off for dual-use testing tools
- Acceptance criteria
- Proposed: documented approval exists before any Mythos-backed test runs
- Proposed: subprocessor list updated within 30 days of feature availability
- Risks
- Feature enabled without review
- Terms change after enablement
- Assumed no-cost inclusion proves incorrect
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?
The model stays behind Cisco's AI Defense service; customers interact with structured test jobs, so integration is via AI Defense, not direct model APIs.
Governance
Who approves, reviews and stays accountable for outcomes?
No-additional-cost inclusion may bypass procurement review that would normally assess a new AI subprocessor; agencies should check whether Anthropic becomes a processor of test data under existing Cisco terms.
Security and privacy
What data, permissions and controls need testing?
Dual-use capability: controls rest on Cisco's wrapper and Anthropic program safeguards, which agencies cannot independently inspect.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Limited direct accessibility content in the source; workforce implication is the need for staff able to configure, interpret and act on AI security or cost tooling outputs (interpretation).
Procurement
What should contracts, pricing and exit terms secure?
Check whether new AI features arrive under existing Cisco/Splunk contracts, whether new subprocessors (e.g., Anthropic) are introduced, and whether public-sector authorizations cover them before enablement.
Operating model
Which teams own the service once it runs?
Security, observability and finance teams need a shared operating loop (test, observe cost/quality, remediate) with named owners; the source does not describe a public-sector operating model.
Publication history
- 2026-11-09Cisco · Issue 106 resources
Stable resource ID: register-anthropic-mythos-cisco-ibm-products-existing-licenses-20261109