SECURITY ATLAS / EVALUATION BRIEF
Cisco AI Defense
Research reviewed: 2026-10-18
https://atlasofsecurity.com/landscape/vendors/cisco-ai-defense/

THE ATLAS TAKE
Cisco AI Defense deserves evaluation when model testing and production guardrails need a shared operating model. Its documented management API is unusually useful for understanding the boundary: validation starts a job, while runtime protection requires a separately configured enforcement point. Atlas sees that separation as an architectural advantage because teams can test both claims independently. The difficult work remains application integration, policy calibration and proving that relevant traffic actually crosses inspection. Public documentation does not establish independent prevention rates or make every emerging agent-security feature production ready.

SCOPE
This profile emphasizes AI Model and Application Validation, with AI Runtime as an adjacent module. Confirm integration, supported models and entitlement; the management API labels MCP connection scanning beta, which is not established production coverage.

WORTH A LOOK WHEN
Application-security teams owning identifiable AI applications, test endpoints and production traffic paths.

THINK TWICE WHEN
The requirement is universal agent identity or tool authorization without changes to application connectivity.

IMPLEMENTATION
1. Freeze the target
Record model version, application build, connector, authentication, inference settings and the exact request/response mapping before comparing validation runs.

2. Prove the traffic path
Choose the runtime integration explicitly and trace a permitted request and a blocked request through application, inspection and model logs.

3. Operate policy changes
Assign exception approval, validation reruns and rollback ownership; require new evidence after model, retrieval or tool changes.

OPERATING REALITY
An AI platform owner must maintain model connections, credentials and enforcement routing as applications change. Security engineers need to review validation findings against legitimate tasks, then maintain runtime policy separately. A successful validation run is a dated observation about a configured target, rather than a permanent deployment approval.

COMMERCIAL CONSIDERATIONS
Obtain a quote that separates AI Model and Application Validation from AI Runtime and any network enforcement dependencies. Public pages describe capabilities, but do not establish a universal price or all-inclusive entitlement.
- Applications, models and validation usage in the proposed subscription
- Runtime inspection volume and selected enforcement deployment
- Integration engineering, test-model usage and regional requirements

EVALUATION PLAN / PROPOSED TESTS, NOT COMPLETED RESULTS
1. Repeat a pinned validation run
Acceptance evidence: Preserve target configuration, task IDs, findings and adjudicated false positives across two runs.
Owner: __________  Pass criterion: __________
Observed result: __________  Evidence location: __________

2. Exercise a benign prompt and a synthetic policy violation
Acceptance evidence: Capture model access, application outcome and the expected policy event or inspection response.
Owner: __________  Pass criterion: __________
Observed result: __________  Evidence location: __________

3. Attempt an authorized bypass in a test environment
Acceptance evidence: Call the model through a deliberately uninspected route and document which control prevents or detects it.
Owner: __________  Pass criterion: __________
Observed result: __________  Evidence location: __________

QUESTIONS FOR THE VENDOR
- Does validation exercise the whole application or only its model endpoint?
- Which traffic path actually enforces the runtime decision?
- Which agent or MCP capabilities are beta in the selected release?

EVIDENCE GAPS
- Atlas has not independently measured prevention accuracy, latency or integration effort.
- Confirm regional availability, purchased modules and production status for each intended MCP or agent capability.

SOURCES
Cisco: management API architecture (Documentation)
https://developer.cisco.com/docs/ai-defense-management/introduction/
Cisco: onboarding and regional API access (Documentation)
https://developer.cisco.com/docs/ai-defense-management/getting-started/
Cisco: start a validation job (Documentation)
https://developer.cisco.com/docs/ai-defense-management/start-ai-validation/
Cisco: AI Runtime Protection (Product information)
https://www.cisco.com/site/us/en/products/security/ai-defense/ai-runtime/index.html

Use synthetic fixtures in an authorized environment. Agree rollback and acceptance criteria before enforcement.
Documentation research and Atlas analysis. Independent hands-on effectiveness, effort, and complete price remain unassessed.