Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Cisco edition of November 9, 2026

Independent reportingEmergingNew this fortnight

CRN: Cisco says partners can use Mythos through AI Defense to red team client agent rollouts; AI Defense has roughly 400 to 500 customers

CRN (interview with Cisco SVP DJ Sampath) · Partner-delivered AI security services; cross-SLED applicability via Cisco partners · Global (Cisco Live APJC, Melbourne)

Publisher
CRN
Original publication
November 9, 2026
Source retrieved
2026-11-10
Event date
2026-11-09
Read original source

What happened

CRN reports Cisco runs Mythos in a sandbox with control over what it can access, how it executes and how its sub-agents are spun up, and that partners can use Mythos through AI Defense to red team every client environment rolling out agents. Cisco says AI Defense has approximately 400 to 500 customers since launch, now supports Amazon Bedrock and CloudWatch for token-spend/ROI dashboards, and sits within Cisco Cloud Control. Availability remains 'coming soon for select enterprises'.

Why it matters

SLED buyers will likely meet Mythos-backed testing as a partner-delivered service. The 400 to 500 customer figure gives a more concrete scale than the press release's 'hundreds', but it shows AI Defense is still a young product with no stated public-sector reference base.

Evidence and measured results

Vendor executive interview reported by trade press; figures and claims ('no other red teaming service' with a model that powerful) are Cisco's, not CRN's findings. No customer, sector or outcome data.

Limitations and uncertainty

Interview-based; customer count is vendor-stated and unaudited; 'every client environment' is aspirational partner positioning. Dates, scope and regions subject to change.

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 lack in-house AI red-team skills and need trusted third parties to test agents before release.
Stakeholders
  • CISO
  • AI program lead
  • Procurement
  • Partner/MSSP account team
Discovery questions
  • Would you allow a partner to run adversarial tests against your agents?
  • What vetting do you require for third-party security testers?
  • How many agents need testing in the next year?
Value hypothesis
Partner-run adaptive red teaming could give smaller SLED IT teams access to testing they cannot staff, if authorization and evidence handling are contracted.
Potential engagement
A fixed-scope partner red-team assessment of one agent with remediation retest.
Unsupported claims
  • That Cisco's service is uniquely powerful (vendor assertion)
  • Any public-sector customer count
  • Measured improvement in agent security

Pre-sales engineering

Role takeaway
Fit
Fits agencies with AI agents nearing production and willingness to use partner-operated testing.
Architecture and integration
Partner operators use AI Defense within Cisco Cloud Control against agency-registered targets.
Prerequisites
  • Contracted partner with AI Defense access
  • Registered targets
  • Agency authorization letter
Constraints
  • Select-enterprise availability
  • Vendor-stated sandbox controls
  • Partner staffing variability
Security
Require named partner operators, MFA, scoped target lists, log export to agency SIEM, and stop-test procedures.
Proof of value
  • Verify audit logs show partner operator identity for each test
  • Retest closed findings to confirm remediation

Delivery

Role takeaway
Work
SOW design and execution of a partner-run AI red-team cycle with remediation tracking.
Dependencies
  • Partner availability of Mythos-backed features
  • Agency remediation staff
  • Test environment
Ownership
Agency security office, with partner as service provider.
Skills and adoption
Agency staff shadow partner tests to build internal capability.
Governance checkpoints
  • Operator vetting
  • Pre-test authorization
  • Post-test findings review
Acceptance criteria
  • Proposed: all tests within authorized scope per audit log
  • Proposed: retest completed for all critical findings
Risks
  • Scope creep
  • Operator access misuse
  • Availability delays

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?

Partner-run red teaming implies partner operators acting against agency systems through Cisco's platform; AI Defense placement within Cloud Control ties it to Cisco's broader SaaS management plane.

Governance

Who approves, reviews and stays accountable for outcomes?

Partner-delivered testing requires agency contracts to define partner operator identity, authorization scope and evidence handling, in addition to Cisco's named-operator attribution.

Security and privacy

What data, permissions and controls need testing?

Third-party operators running frontier-model attacks against agency agents increases the need for background checks, least-privilege access and evidence chain-of-custody.

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

  1. 2026-11-09Cisco · Issue 106 resources
Read preserved resource versions (JSON)

Stable resource ID: crn-cisco-mythos-ai-defense-partners-400-500-customers-20261109