Executive Summary: Cisco Secure AI Factory with NVIDIA

Cisco is the only vendor in this assessment series whose AI infrastructure authority is anchored by networking and security rather than compute, storage, or cloud services. Where Dell builds up from servers, HPE from sovereign compute, VAST from storage, and hyperscalers from managed services, Cisco builds outward from the network fabric and security posture that connects everything else. The Secure AI Factory with NVIDIA is a reference architecture, not a vertically integrated platform, and that distinction defines Cisco's entire 4+1 profile.

Layer 0 is Cisco's strongest position, strong at all three sub-layers: networking at 0B, compute at 0A, and VAST's storage on Cisco's paper at 0C. Cisco owns the network fabric (Silicon One G300, Nexus 9000/8000, Nexus Hyperfabric) and has built a three-tier GPU compute portfolio (C880A HGX B300 and C885A MI350X dense servers for training, C845A modular MGX for inference, X-Series X580p for composable blade AI) that competes directly with Dell PowerEdge and HPE ProLiant. The X-Series disaggregated GPU architecture, independently managing CPU and GPU lifecycles via X-Fabric, is an architectural differentiator no other blade vendor matches. Cisco does not own storage; the AI POD storage story is partner-delivered (VAST Data primary, now on Cisco's Global Price List with full Cisco support, plus NetApp, Pure Storage, Hitachi Vantara, Nutanix as validated options), which reads as strong capability whose authority cedes to the chosen partner. This makes Cisco's Layer 0 the inverse of Dell's: Dell owns compute and storage but brands NVIDIA networking silicon. Cisco owns networking silicon and has purpose-built AI compute but depends on partners for the data foundation.

The security and observability layers are where Cisco makes its most differentiated claim. AI Defense, Duo Agentic Identity, DefenseClaw, Splunk Observability Cloud with AI Agent Monitoring, and the Galileo acquisition together represent the most comprehensive agent security and observability portfolio of any infrastructure vendor assessed. These capabilities span Layers 2A through 2C, and they constitute genuine Cisco-owned IP, not rebranded NVIDIA or partner technology. The structural question is whether security and observability are sufficient to constitute a control plane, or whether they remain constraint enforcement without placement reasoning.

The AGNTCY initiative (open-sourced by Cisco's Outshift incubator, donated to the Linux Foundation with Dell, Google Cloud, Oracle, and Red Hat as formative members) contributes infrastructure primitives (discovery, identity, messaging, observability) to the broader agentic standards ecosystem. AGNTCY sits within the Agentic AI Foundation (AAIF), the fastest-growing project in Linux Foundation history, where MCP (Anthropic), A2A (Google), AGENTS.md (OpenAI) define the foundational protocols. Cisco is a Gold member of AAIF, not a Platinum founder: the ecosystem-defining standards were originated by Anthropic, Google, and OpenAI, not Cisco. AGNTCY contributes essential plumbing beneath those protocols, and Cisco's commercial products (AI Defense, Duo, Splunk) could become the enterprise implementation layer if these open standards achieve adoption. But Cisco's position is contributor, not definer.

Cisco's ~$9B in projected FY2026 AI infrastructure orders, record $15.8B quarterly revenue, and hyperscaler design wins (Silicon One P200, G200) validate market traction. The Galileo acquisition and DefenseClaw open-source release signal an intent to own the AI agent trust layer. But the 4+1 assessment reveals a vendor whose authority is wide but thin: strong at the network layer and security perimeter, Delegated or a gap at the data plane and runtime layers. Cisco secures the AI Factory. It does not yet govern it.

Layer-by-layer status: Layer 0A (UCS C885A and C845A GPU Servers, X-Series Composable Blades and AI PODs), Layer 0B (Nexus Hyperfabric and the AI POD Fabric on Silicon One; G300 Watch-Listed), Layer 0C (VAST on C225 M8 EBOX, on Cisco's Price List, Plus Nutanix Storage on Cisco PIDs), Layer 1A (VAST's Catalog on Cisco's Price List, With Hypershield and Isovalent), Layer 1B (Partner-Delivered Retrieval), Layer 1C (Partner-Delivered Pipeline Engines), Layer 2A (Networking-Centric Orchestration), Layer 2B (Security Layer, Not Runtime), Layer 2C (Security and Observability, Not Yet Governance; Agent Identity in Beta), Layer 3 (+1) (Splunk and the Security Portfolio, First-Party Security Applications).

Assessment framework: 4+1 Layer AI Infrastructure Model. Scoring model: Decision Authority Placement Model (DAPM) — Retained, Delegated, or Ceded. Published by The CTO Advisor LLC (DBA The Advisor Bench). Author: Keith Townsend. Date assessed: October 27, 2026. Version: v1.39 - 4+1 v3: Layer 0 Sub-Layers.

Cisco Secure AI Factory with NVIDIA

Mapped to the 4+1 Layer AI Infrastructure Model

v1.39 - 4+1 v3: Layer 0 Sub-LayersAssessed October 27, 2026Sources & revision history
ACTIVE ASSESSMENT

Summary Finding

Cisco is the only vendor in this assessment series whose AI infrastructure authority is anchored by networking and security rather than compute, storage, or cloud services. Where Dell builds up from servers, HPE from sovereign compute, VAST from storage, and hyperscalers from managed services, Cisco builds outward from the network fabric and security posture that connects everything else. The Secure AI Factory with NVIDIA is a reference architecture, not a vertically integrated platform, and that distinction defines Cisco's entire 4+1 profile.

Layer 0 is Cisco's strongest position, strong at all three sub-layers: networking at 0B, compute at 0A, and VAST's storage on Cisco's paper at 0C. Cisco owns the network fabric (Silicon One G300, Nexus 9000/8000, Nexus Hyperfabric) and has built a three-tier GPU compute portfolio (C880A HGX B300 and C885A MI350X dense servers for training, C845A modular MGX for inference, X-Series X580p for composable blade AI) that competes directly with Dell PowerEdge and HPE ProLiant. The X-Series disaggregated GPU architecture, independently managing CPU and GPU lifecycles via X-Fabric, is an architectural differentiator no other blade vendor matches. Cisco does not own storage; the AI POD storage story is partner-delivered (VAST Data primary, now on Cisco's Global Price List with full Cisco support, plus NetApp, Pure Storage, Hitachi Vantara, Nutanix as validated options), which reads as strong capability whose authority cedes to the chosen partner. This makes Cisco's Layer 0 the inverse of Dell's: Dell owns compute and storage but brands NVIDIA networking silicon. Cisco owns networking silicon and has purpose-built AI compute but depends on partners for the data foundation.

The security and observability layers are where Cisco makes its most differentiated claim. AI Defense, Duo Agentic Identity, DefenseClaw, Splunk Observability Cloud with AI Agent Monitoring, and the Galileo acquisition together represent the most comprehensive agent security and observability portfolio of any infrastructure vendor assessed. These capabilities span Layers 2A through 2C, and they constitute genuine Cisco-owned IP, not rebranded NVIDIA or partner technology. The structural question is whether security and observability are sufficient to constitute a control plane, or whether they remain constraint enforcement without placement reasoning.

The AGNTCY initiative (open-sourced by Cisco's Outshift incubator, donated to the Linux Foundation with Dell, Google Cloud, Oracle, and Red Hat as formative members) contributes infrastructure primitives (discovery, identity, messaging, observability) to the broader agentic standards ecosystem. AGNTCY sits within the Agentic AI Foundation (AAIF), the fastest-growing project in Linux Foundation history, where MCP (Anthropic), A2A (Google), AGENTS.md (OpenAI) define the foundational protocols. Cisco is a Gold member of AAIF, not a Platinum founder: the ecosystem-defining standards were originated by Anthropic, Google, and OpenAI, not Cisco. AGNTCY contributes essential plumbing beneath those protocols, and Cisco's commercial products (AI Defense, Duo, Splunk) could become the enterprise implementation layer if these open standards achieve adoption. But Cisco's position is contributor, not definer.

Cisco's ~$9B in projected FY2026 AI infrastructure orders, record $15.8B quarterly revenue, and hyperscaler design wins (Silicon One P200, G200) validate market traction. The Galileo acquisition and DefenseClaw open-source release signal an intent to own the AI agent trust layer. But the 4+1 assessment reveals a vendor whose authority is wide but thin: strong at the network layer and security perimeter, Delegated or a gap at the data plane and runtime layers. Cisco secures the AI Factory. It does not yet govern it.

Strength
Moderate
Gap
Partner
Layer 0A · ComputeComputeUCS C885A and C845A GPU Servers, X-Series Composable Blades and AI PODsdecides: enterprise · Retained▼

CPUs, accelerators, servers, integrated systems, OS and hypervisor, physical plant

Vendor-Provided

Cisco UCS C885A M8 (8x AMD Instinct MI350X)Retained

Eight-way dense GPU server, now offered with "8x AMD MI350X OAM" GPUs (data sheet updated July 14, 2026), one NVIDIA ConnectX-7 or AMD Pensando Pollara NIC per GPU, and NVIDIA BlueField-3 DPUs or AMD Pollara NICs for data access. The NVIDIA HGX H200 and AMD MI300X configurations reached end of sale on June 25, 2026. ROCm is an open runtime: a ROCm or PyTorch workload moves to another OEM's MI350X server without a rebuild, Retained.

Cisco UCS C845A M8 With NVIDIA PCIe GPUs (Modular GPU, MGX Platform)Retained

Flexible, scalable AI server based on NVIDIA MGX modular reference design, with "Two, four, six, or eight of the following PCIe GPUs": NVIDIA RTX PRO 4500, 6000D and 6000 Blackwell, H200 NVL, H100 NVL and L40S, in a 4RU chassis. GPU hot-swap, E1.S SSDs, Day-1 Intersight management. A VAST Certified CNode-X platform (UCS C845A M8 with RTX PRO 6000). A standalone server: the workload moves to another OEM's server without a rebuild, Retained.

Cisco UCS X-Series + X580p GPU Node (Modular Blade AI)Retained

Disaggregated, composable AI compute within the UCS X9508 blade chassis. X580p PCIe Node adds up to 4 NVIDIA GPUs (RTX PRO 6000/4500 Blackwell, H200 NVL, L40S) to X210c/X215c compute nodes via X-Fabric Technology. X9516 X-Fabric Module provides PCIe Gen 5 switching with ultra-low-latency, NVLink Bridge support, and dynamic GPU-to-host provisioning. Independent CPU and GPU lifecycle management: upgrade GPUs without replacing compute nodes. MLPerf Inference benchmarks published April 2026. Up to 8 GPUs per chassis, per the X580p data sheet. Standard NVIDIA PCIe GPUs: a CUDA or PyTorch workload moves to another OEM's GPU server without a rebuild, Retained, as Cisco's other GPU servers read. X-Fabric's composition and dynamic provisioning are Cisco's, named here, not scored apart.

Cisco UCS C240 M8 / C225 M8 (Mainstream + Storage)Retained

C240 M8: 2U rack server with Intel Xeon 6 processors, up to 2 double-width NVIDIA GPUs (RTX PRO 6000 Blackwell, H200 NVL). Balanced compute for distributed AI, analytics, edge AI, and vision workloads. Up to 28 NVMe/SAS/SATA drives for high-speed data access. C225 M8: designated as VAST Data Platform EBOX (storage servers) in AI POD architecture, the persistent storage foundation for Cisco AI PODs. Both managed through Cisco Intersight.

Cisco Unified Edge (Edge AI Compute)Retained

Edge compute platform supporting NVIDIA RTX PRO 4500 and 6000 Blackwell Server Edition GPUs for mission-critical AI at the edge. Also supports NVIDIA L4 GPUs. Zero-touch deployment with pre-validated blueprints. Centralized management via Intersight with Splunk and ThousandEyes integrations for end-to-end edge observability. Multi-layered zero-trust security with tamper-proof features, deep telemetry, drift-free configurations. Cisco AI Grid reference design extends edge AI to service providers via Cisco Mobility Services Platform, a unique go-to-market that no other assessed vendor offers.

Cisco AI PODs (Pre-Validated Full-Stack Infrastructure)Ceded

Modular, full-stack AI infrastructure platform combining UCS C885A/C845A compute, Nexus 9000 networking (up to 800G), NVIDIA GPUs, and partner storage (VAST Data, NetApp, Pure Storage, Hitachi Vantara, Nutanix). Scalable from 32 to 128+ GPUs. Cisco Validated Designs (CVDs) and NVIDIA Enterprise Reference Architectures (ERAs) for training, fine-tuning, inference, and RAG workloads. Pre-validated designs reduce setup time by up to 50%. Integrated management through Cisco Intersight and Nexus Dashboard. Modular scale-unit design enables growth without full infrastructure overhaul. Proprietary Cisco platform: opinions captive, no open exit.

Cisco Compute Hyperconverged with Nutanix (M8; AHV)Ceded

Pre-configured UCS M8 nodes (HCINX225C, 240C and others, plus compute-only and XE130c edge) carrying UCS firmware, Nutanix AHV and AOS, with Nutanix software and services ordered as Cisco PIDs.

Cisco UCS C880A M8 (8-Way NVIDIA HGX B300)Retained

10RU air-cooled server on NVIDIA's HGX reference architecture with eight HGX B300 NVL8 GPUs and two Intel Xeon 6 processors (data sheet updated August 13, 2026). Standard NVIDIA HGX: a CUDA or PyTorch workload moves to another OEM's HGX B300 server without a rebuild, Retained; the CUDA dependency is read on NVIDIA's row.

Cisco UCS C845A M8 With AMD Instinct PCIe GPUs (MI210)Retained

The C845A M8 with AMD Instinct PCIe GPUs: the data sheet lists the "AMD ™ Instinct MI210 GPU, 300W, 64GB, FHFL, 2-slot" A standalone server on ROCm, Retained. The data sheet also lists the MI350P, marked with an asterisk it doesn't explain, so it's noted, not scored.

NVIDIA-Provided

NVIDIA GPU Silicon (HGX, MGX, RTX PRO Blackwell)

Every NVIDIA path in UCS depends on it, from the C880A's HGX B300 to the MGX and RTX PRO servers. The C885A ships AMD MI350X and the C845A takes AMD MI350P, so the dependency isn't exclusive.

NVIDIA BlueField DPUs

BlueField-3 DPUs in the C885A, or AMD Pollara NICs in their place, for GPU-to-data access, with Hybrid Mesh Firewall policy enforced on BlueField.

◆ Gap Analysis

Cisco sells compute the enterprise racks and runs, in three tiers. The UCS C880A M8 is an eight-way HGX B300 server, and the C885A M8 now ships with eight AMD MI350X. The C845A M8 takes two to eight PCIe GPUs on NVIDIA MGX. The X-Series with the X580p node composes up to 8 GPUs per chassis over X-Fabric, so GPUs upgrade without replacing compute nodes. AI PODs package it all from 32 to 128+ GPUs, and Compute Hyperconverged adds Nutanix AHV on Cisco part numbers. The buyer gets GPU vendor optionality and composable blades on hardware it owns. The architect's concern is the integrated systems. The C-Series lifts to another OEM; the X-Series chassis and the AI PODs can't be lifted as deployed. Calibration: Dell, HPE and Lenovo read strong on the same OEM shape; AWS and GCP strong on compute the enterprise rents.

◆ Borrowed Judgment

Retained where the grade rests. A UCS server the enterprise owns makes no runtime call on Cisco's behalf; the enterprise's own hypervisor, scheduler and policies decide, and the CIMC reads with each server. Portability splits: the C-Series and Unified Edge read Retained, while the X-Series, the AI PODs and Compute Hyperconverged with Nutanix read Ceded.

◆ Working Notes

Named, not scored: the Cisco AI Grid reference design for service providers, Mobility Services Platform plus RTX PRO Blackwell GPUs. Named, not scored (October 23, 2026): the C885A M8 with NVIDIA HGX H200 and with AMD MI300X, past their June 25, 2026 last order date.

Layer 0B · FabricNetwork FabricNexus Hyperfabric and the AI POD Fabric on Silicon One; G300 Watch-Listeddecides: vendor · Ceded▼

Interconnects, switching and routing, network virtualization

Vendor-Provided

Nexus Hyperfabric (Cloud-Managed AI Fabric)Ceded

Cloud-managed network fabric integrating networking, GPU and storage, with automated deployment and operations. Cisco's datasheet offers pre-configured designs for the front end, back end, rails and storage, with a lossless back-end network, on Cisco 6000 Series switches with Silicon One (HF6100 spines and leaves) and N9300, or on NVIDIA Spectrum-4 based N9100 switches. The full-stack option complies with NVIDIA's Enterprise Reference Architecture (ERA), and the N9100 option with NVIDIA's Cloud Partner (NCP) reference architecture. Proprietary Cisco platform: opinions captive, no open exit.

Cisco AI PODs (Pre-Validated Full-Stack Infrastructure) (networking facet)Ceded

The Nexus 9000 networking integrated into the AI POD. Cisco's AI POD for NVIDIA design runs a dedicated, isolated back-end fabric on the Silicon One based N9364E-SG2 and a front end on the N9332D-GX2B and N9364D-GX2A that carries storage access. Integrated-system rule at this facet.

Cisco N9100 Series (NVIDIA Spectrum-4 Silicon; NX-OS or Nexus Hyperfabric)Ceded

Cisco N9000 switches powered by the NVIDIA Spectrum-4 ASIC (the N9164E-NS4-O), on Cisco paper, under Cisco NX-OS or Nexus Hyperfabric, with 800 GbE capacity. Hyperfabric's datasheet uses them for its NCP reference architecture option. Ceded: the silicon is NVIDIA's and the network OS opinions are Cisco's, and neither lifts without rebuilding.

Catalyst 9000 Campus Switching (9200 to 9600; IOS XE)Ceded

Cisco's campus access, distribution and core family, including the Silicon One based 9350 and 9610 smart switches, managed from Catalyst Center or Meraki Dashboard.

Cisco 8000 Series Routers (8100, 8200, 8700, 8800; Silicon One; IOS XR or SONiC), through IOS XRCeded

Silicon One routing from 1RU fixed (8201-32FH, 12.8 Tbps) to the 8812 modular chassis (172.8 Tbps), with G300-powered systems announced. Cisco documents third-party NOS and SONiC on the platform. The 8200 family includes the 8223, offered with IOS XR or an open network OS, for data center interconnect that needs deep buffers. Cisco builds it on Silicon One P200, whose datasheet describes distributing AI workloads across geographically dispersed data centers.

Cisco 8000 Series Routers (8100, 8200, 8700, 8800; Silicon One; IOS XR or SONiC), through SONiCDelegated

Silicon One routing from 1RU fixed (8201-32FH, 12.8 Tbps) to the 8812 modular chassis (172.8 Tbps), with G300-powered systems announced. Cisco documents third-party NOS and SONiC on the platform. The 8200 family includes the 8223, offered with IOS XR or an open network OS, for data center interconnect that needs deep buffers. Cisco builds it on Silicon One P200, whose datasheet describes distributing AI workloads across geographically dispersed data centers.

Cisco UCS X-Series + X580p GPU Node (Modular Blade AI) (Fabric Interconnect facet)Ceded

The UCS 6536 (36 x 100G, 7.42 Tbps per FI) and 6600 Series Fabric Interconnects the X9508 chassis connects through in Intersight Managed Mode, carrying Ethernet and Fibre Channel for every node behind them.

NVIDIA-Provided

NVIDIA Spectrum-X Switch Silicon

Cisco also sells Spectrum-X-based switches beside its own Silicon One, both managed through Nexus One, a dual-silicon choice no other row offers.

◆ Gap Analysis

Cisco designs its own switching silicon, Silicon One, and no other OEM on the instrument does. Nexus Hyperfabric is a cloud-managed fabric that integrates networking, GPU and storage, on Silicon One or on NVIDIA Spectrum-4 based N9100 switches, aligned with NVIDIA's reference architectures, and the AI POD runs a dedicated back end on the Silicon One based N9364E-SG2. The 8223 router on Silicon One P200 carries AI workloads between data centers. Catalyst 9000 covers campus, and Cisco 8000 routing runs Silicon One with IOS XR or SONiC. UCS Fabric Interconnects carry every X-Series node. The buyer gets an AI fabric from a networking vendor, not a reseller. The architect's concern is that it's Cisco's design throughout. Silicon One and Nexus opinions don't leave without rebuilding; SONiC on the 8000 is the exit. Calibration: HPE reads strong on Slingshot it owns, NVIDIA on Spectrum-X and InfiniBand; Dell and Lenovo strong on Spectrum-X on their own paper.

◆ Borrowed Judgment

Ceded where the grade rests. Silicon One and the Nexus switches make the routing and load-balancing calls, and Hyperfabric's cloud controller manages the fabric, inside a configuration the enterprise writes with no per-decision override: vendor decides, visible, not overridable, Ceded. Portability: Hyperfabric, the AI POD fabric, the N9100, Catalyst and the Fabric Interconnects read Ceded; the Cisco 8000 splits by network OS, IOS XR Ceded and SONiC Delegated.

◆ Working Notes

Watch-list (October 16, 2026, not scored): Silicon One G300 and the G300-powered Nexus 9000 and 8000 systems. Cisco's OCP 2026 release says the G300 is sampling and the first systems are shipping, with no product documentation confirming GA. Named, not scored here: Nexus One, which reads at 2A. The 8223's scale-across reading joins two Cisco datasheets, the 8200 datasheet (8223 part numbers for deep-buffer data center interconnect) and the Silicon One P200 datasheet (AI workloads across dispersed data centers), through Cisco's October 2025 blog posts; that join is flagged. The AI POD's back-end silicon, G200, is GA; only G300 is watch-listed. Named, not scored: Sharon AI's Hyperfabric selection, a customer announcement.

Layer 0C · StorageStorage SubstrateVAST on C225 M8 EBOX, on Cisco's Price List, Plus Nutanix Storage on Cisco PIDsdecides: vendor · Ceded▼

Arrays, storage servers and software, front-end protocols: where the data sits

Vendor-Provided

VAST Data Platform on Cisco AI PODs (EBOX) (storage half)Ceded

VAST's DASE storage engine, NVMe over TCP front end and global namespace on the C225 M8 EBOX servers. VAST's Catalog and database stay at 1A.

Front-End Interfaces on VAST on Cisco AI PODs (NFS, SMB, S3, NVMe/TCP)Delegated

The standard front ends VAST serves on the C225 M8 EBOX servers: NFS v3/v4 and SMB v2/v3 per Cisco's EBox reference architecture, the S3 API, a documented subset per VAST's S3 implementation overview, and NVMe over Fabrics. Delegated, as on VAST's own row: a channel's paper never changes the reading, and a genuine multi-vendor interface keeps its Delegated reading through any paper. VAST's DASE engine stays in the VAST chip, Ceded to VAST.

Cisco UCS C240 M8 / C225 M8 (Mainstream + Storage) (C225 M8 EBOX facet)Retained

The C225 M8 as the storage server under VAST in the AI POD. Its chip's Retained reading is kept; see the open question on VAST's DASE nodes.

Cisco Compute Hyperconverged with Nutanix (AOS and Nutanix Unified Storage facet)Ceded

Nutanix AOS on each node, with Nutanix Unified Storage (block, file, object) orderable as Cisco PIDs.

NVIDIA-Provided

NVIDIA AI Data Platform Reference Design

Cisco, NVIDIA and VAST were validated as one of the first NVIDIA AI Data Platform reference designs.

◆ Gap Analysis

Cisco doesn't build storage; it sells VAST's. The VAST Data Platform runs on UCS C225 M8 servers designated as EBOX, with the VAST AI OS on Cisco's Global Price List and full Cisco support. DASE gives a shared-everything model over NVMe over Fabrics with one global namespace. Compute Hyperconverged adds Nutanix AOS and Nutanix Unified Storage as Cisco part numbers. The buyer gets AI-throughput storage on the same invoice as the servers and the fabric. The architect's concern is that the storage opinions are VAST's, captive through any paper. The C225 M8 under them is a Cisco server, but the software runs only on certified nodes. Calibration: Supermicro reads strong on VAST on its own paper; VAST strong on the same platform under its own name; Dell and HPE strong on storage they own.

◆ Borrowed Judgment

Ceded where the grade rests. VAST's DASE engine decides placement and protection at runtime, and a channel's paper never changes who decides: vendor decides, visible, not overridable, Ceded. Portability: VAST and the Nutanix storage read Ceded, as on their owners' rows; VAST's S3 and NVMe-oF front ends read Delegated, as on VAST's row; the C225 M8 EBOX server keeps its Retained reading.

◆ Working Notes

Named, not scored: the NetApp and Everpure designs validated in AI PODs, which are bought from their vendors (October 16, 2026). Hitachi Vantara is no longer listed.

Layer 1A · DataData Foundation & GovernanceVAST's Catalog on Cisco's Price List, With Hypershield and Isovalentdecides: code · Retained▼

The data itself, organized and governed: the Governance Catalog that Layer 2C queries

Vendor-Provided

VAST Data Platform on Cisco AI PODs (EBOX) (data half: VAST Catalog and database)Ceded

VAST Data Platform running on Cisco UCS C225 M8 servers (designated EBOX). VAST DASE architecture provides shared-everything model with NVMe-over-Fabrics, global namespace, and ACID guarantees. Managed through Cisco Intersight alongside compute and networking. VAST was recognized at VAST Forward 2026 for its Cisco partnership. The customer buying a Cisco Secure AI Factory gets VAST storage as a validated, integrated component, and the VAST AI OS rides Cisco's Global Price List with full Cisco support. Cisco delivers the capability; VAST's opinions do the capturing: the platform's data-architecture opinions are VAST-captive through any paper, as on VAST's own row.

Cisco Hypershield + Isovalent (Data Security)Ceded

Zero-trust, ransomware-resilient storage security and inline network security. Cisco Secure AI Factory security principles applied to the data layer. Isovalent provides eBPF-based runtime security for containerized AI workloads. Hybrid Mesh Firewall extends policy enforcement to BlueField DPUs at the storage server level. Security is Cisco-owned and layered on top of whichever storage partner the enterprise selects: consistent security posture regardless of storage choice. Proprietary Cisco platform: opinions captive, no open exit. Not scored within this chip under the GA evidence table: Hybrid Mesh Firewall policy enforcement on NVIDIA BlueField DPUs ("General Availability: Q4 CY26").

NVIDIA-Provided

NVIDIA AI Data Platform Reference Design

Cisco + NVIDIA + VAST validated as one of the first NVIDIA AI Data Platform reference designs. NVIDIA provides the reference architecture standard; Cisco provides networking and compute; VAST provides the data platform.

◆ Gap Analysis

Cisco owns no catalog. 1A reads strong because VAST's Catalog and database arrive with the VAST platform on Cisco's Global Price List, with Cisco support. The 1A catalog-classification criterion names that Catalog as its strong exemplar, and the whose-paper rule credits it in full. Cisco adds consistent security above the storage it sells: Hypershield for zero-trust, ransomware-resilient storage security, and Isovalent's eBPF runtime security for containerized AI workloads. The VAST storage engine holds the bytes, a 0C function. The grade rested on the catalog, so it doesn't move. The architect's concern is the seam. Cisco's Layer 2C ambitions depend on a partner's metadata model, and building from VAST's metadata to a Cisco control plane is a cross-vendor integration neither party has announced. Calibration: Supermicro reads strong on the same VAST delivery; Dell and HPE moderate on indexes they own.

◆ Borrowed Judgment

VAST's Catalog indexes the tags the enterprise applies and executes what it configured, and a channel's paper never changes who decides: code decides, visible, overridable, Retained, the reading on VAST's own row. Portability: the catalog stays with VAST through any paper, and Hypershield and Isovalent are Cisco-captive, both Ceded.

◆ Working Notes

Confidence flag: Isovalent's Cilium networking and Hybrid Mesh Firewall enforcement on BlueField DPUs are network decisions, closer to 0B than to 1A. Out of the Cisco Hypershield + Isovalent chip under the GA evidence table (October 24, 2026): Hybrid Mesh Firewall policy enforcement on NVIDIA BlueField DPUs ("General Availability: Q4 CY26").

Layer 1B · RetrievalContext Management & RetrievalPartner-Delivered Retrievaldecides: vendor · Ceded▼

Low-latency retrieval for RAG — vector/hybrid search, context windows

Vendor-Provided

VAST InsightEngine on Cisco AI PODsCeded

VAST InsightEngine on Cisco UCS C845A M8 servers (first VAST Certified CNode-X platform). Real-time vector embedding and retrieval for RAG and agentic workflows. Integrates with NVIDIA NIM microservices for AI-native retrieval. Automates embedding, indexing, and retrieval pipelines. Marketed as reducing RAG pipeline latency from minutes to seconds. This is a validated component of the Cisco Secure AI Factory: the customer asking Cisco for RAG capability receives InsightEngine as part of the delivered solution, on Cisco paper via the GPL. Lift-to-leave: the retrieval and indexing opinions are VAST-captive through any paper, as on VAST's own row. Generally available on VAST's row (VAST's March 18, 2025 availability release, fulfilling its dated GA commitment) and orderable through Cisco Commerce Workspace with Cisco TAC Level 1 support (Cisco UCS with VAST Data data sheet).

NVIDIA-Provided

NVIDIA AI Data Platform + NeMo Retriever

NVIDIA AI Data Platform reference design validates the Cisco + VAST retrieval architecture. NeMo Retriever provides embedding models and reranking. Same NVIDIA retrieval stack available to Dell and HPE. The differentiation is in the validated integration, not the NVIDIA components.

◆ Gap Analysis

Applying the customer litmus test: the enterprise asking Cisco for RAG and retrieval capability receives VAST InsightEngine as a validated component of the Secure AI Factory, on Cisco paper. The retrieval function is delivered at the strength it carries on VAST's own row. That is the capability grade. The authority chip says the rest: the retrieval opinions are Ceded to VAST through any paper. Cisco's owned contribution at Layer 1B is the networking fabric that makes high-performance retrieval possible: lossless connectivity between GPU compute nodes and VAST storage with predictable latency. This is not the retrieval capability itself, but it is the enabling condition. The Cisco + NVIDIA + VAST data platform is marketed as 'the first enterprise architecture unifying compute, fabric, and storage into a single, validated platform to accelerate RAG', and the validated integration is genuine, even though each component has a different owner. Where Cisco is thinner than Dell at Layer 1B: Dell has Data Analytics Engine with its own MCP Server (Feb 2026), blurring the 1A/1B boundary with search, analytics, and orchestration surfaced as a single queryable service, Dell-owned IP. HPE has Data Fabric with integrated vector search capabilities. Cisco's Layer 1B retrieval is entirely partner-provided. If the enterprise selects a storage partner other than VAST (NetApp, Pure Storage, etc.), the Layer 1B retrieval story changes entirely: each partner brings different retrieval capabilities, and Cisco provides no Cisco-owned retrieval abstraction above them. The network-to-retrieval performance correlation is an underappreciated Cisco contribution. When Nexus One's AI Job Observability shows that retrieval latency degraded because of network congestion on a specific path between compute and storage tiers, that's retrieval-relevant intelligence that no storage vendor can provide independently. Cisco sees the network between the GPU and the data: VAST sees the data, NVIDIA sees the GPU, Cisco sees the fabric connecting them.

◆ Borrowed Judgment

High for retrieval logic, low for retrieval-enabling networking. All retrieval and context management intelligence is provided by VAST (InsightEngine) and NVIDIA (NeMo Retriever, AI Enterprise). Cisco provides the networking substrate that determines retrieval performance characteristics, and that substrate is Cisco-owned IP with genuine impact on retrieval latency and throughput. The structural comparison: Dell borrows retrieval acceleration from NVIDIA (cuVS, NeMo Retriever) but retains the storage platform on which retrieval operates (PowerScale). Cisco borrows both retrieval logic (VAST InsightEngine) and retrieval acceleration (NVIDIA) but retains the networking fabric that connects them.

◆ Working Notes

The network-as-retrieval-enabler framing is worth developing further. In a disaggregated architecture where GPU compute and vector storage are on separate server tiers connected by fabric, the network IS part of the retrieval path. Cisco's ability to correlate network telemetry with retrieval latency via Nexus One and Splunk is a genuine observability advantage, one that could feed Layer 2C placement decisions about which compute-to-storage path to use for a given retrieval workload. The VAST InsightEngine as first VAST Certified CNode-X platform on Cisco UCS C845A M8 (with RTX PRO 6000 acceleration) represents the deepest Cisco-VAST integration point. This is where the partnership moves from 'VAST storage on Cisco servers' to 'VAST compute-storage fusion on Cisco infrastructure', closer to a joint product than a validated configuration. The Cisco fabric that carries this traffic is scored at 0B; transport isn't credited at this layer (October 19, 2026 /reconcile). Re-ruled October 24, 2026 (Keith): strong restored the same day it moved to moderate, with VAST's row. InsightEngine's GA rests on VAST's own availability release fulfilling a dated GA commitment, and the product is on Cisco's price list with Cisco support.

Layer 1C · PipelinesData Movement & PipelinesPartner-Delivered Pipeline Enginesdecides: code · Retained▼

Move/transform data — ETL/ELT, lineage, cost-aware movement, KV cache tiering

Vendor-Provided

VAST DataEngine / SyncEngine (on Cisco AI PODs)Ceded

VAST DataEngine executes serverless functions directly where data lives, 'bringing compute to the data.' SyncEngine indexes and synchronizes data from external sources, triggering enrichment pipelines automatically. Both are delivered as part of the Cisco Secure AI Factory with VAST Data, on Cisco paper via the GPL. The customer asking Cisco for data pipeline capability receives these as validated components, a pipeline capability set rated strong on VAST's own row. Lift-to-leave: DataEngine functions and SyncEngine flows are VAST-captive through any paper.

NVIDIA-Provided

Assessment pending

◆ Gap Analysis

Applying the customer litmus test: the enterprise asking Cisco for data pipeline capability receives VAST DataEngine and SyncEngine as validated components of the Secure AI Factory, on Cisco paper via the GPL. The pipeline function is delivered at the strength it carries on VAST's own row. The capability grade credits it fully, the GPU-parallel rule. The authority chip says the rest: pipeline opinions are Ceded to VAST through any paper. Cisco has no proprietary data pipeline, ETL, or feature engineering tools, and this is consistent with Cisco's architectural identity. Cisco has never been a data management software company. Dell's Dataloop-powered Data Orchestration Engine is notable precisely because it's Dell's first proprietary software asset in the data lifecycle. HPE's Data Fabric provides policy-based data placement. IBM has watsonx.data with Confluent streaming. Cisco's equivalent is the validated partner integration. Cisco's owned contribution at Layer 1C is the networking fabric that data pipelines traverse. In a disaggregated AI architecture, data movement between storage tiers, GPU compute, and model serving endpoints is constrained by network bandwidth and latency. Silicon One G300's Intelligent Collective Networking (the 33% utilization improvement and 28% job completion time improvement) directly accelerates data pipeline throughput. This is an infrastructure contribution, not a software contribution, but it's a real one. The Splunk data ingestion and processing capabilities could theoretically extend into data pipeline territory: Splunk already handles high-volume data streams for observability. But Splunk is positioned as an observability and security platform, not an AI data pipeline tool. No Cisco signals suggest this expansion. Decision authority reads as it does on VAST's row: DataEngine executes the functions and triggers the enterprise writes and exercises no judgment of its own, so code decides, visible, overridable, Retained. Cisco's paper changes the invoice, not who decides at runtime (channel scope, October 4, 2026).

◆ Borrowed Judgment

High for pipeline logic, low for data movement infrastructure. All data pipeline orchestration, serverless execution, and data synchronization judgment is provided by VAST (DataEngine, SyncEngine) or by the enterprise's own tooling. Cisco provides the networking fabric that determines data movement performance, Cisco-owned IP that directly impacts pipeline throughput. If the enterprise selects a storage partner other than VAST, the Layer 1C story changes significantly. NetApp, Pure Storage, and Hitachi Vantara each have their own data movement capabilities, none validated at the same depth as VAST within the Cisco AI POD architecture.

◆ Working Notes

The networking-as-data-movement framing is structurally consistent across Layers 1A, 1B, and 1C. At each data layer, Cisco's Retained contribution is the networking fabric that connects and enables partner-provided data capabilities. This is not a gap in the customer experience: the customer gets a complete data plane. It is a structural characteristic of Cisco's reference architecture model: Cisco owns the connectivity, partners own the data logic. This pattern has a Layer 2C implication. If Cisco ever builds a control plane that makes placement decisions about data (where should this data live, how should it move, which pipeline should process it), that control plane would need to integrate with multiple storage partners' data APIs. Dell's hypothetical control plane only needs to integrate with Dell's own storage. Cisco's hypothetical control plane needs to be multi-vendor by design, which is harder to build but potentially more valuable in heterogeneous enterprise environments. The Cisco fabric that carries this traffic is scored at 0B; transport isn't credited at this layer (October 19, 2026 /reconcile).

Layer 2A · OrchestrationInfrastructure OrchestrationNetworking-Centric Orchestrationdecides: vendor · Ceded▼

GPU scheduling, quotas, RBAC, fair-share scheduling, utilization optimization

Vendor-Provided

Cisco Intersight (Unified Fleet Management)Ceded

Cloud-based infrastructure management for UCS compute, Nexus networking, and VAST storage lifecycle. Policy-driven server profiles, firmware management, and workload optimization. Manages the chassis and networking, comparable to Dell's OpenManage Enterprise but with stronger networking integration. Does not manage GPU workload scheduling directly. A fleet management plane sold and run on its own across many systems, so it's a 2A component (Keith, October 16, 2026); the CIMC in each UCS server is that server's management half and reads with it at Layer 0. Third-party support reaches Dell PowerEdge and HPE ProLiant servers through Redfish, so the hardware under it can be another OEM's, but server profiles and policies stay Intersight objects. Proprietary Cisco platform: opinions captive, no open exit.

Nexus One (AI Network Operations)Ceded

Unified management plane for data center networking. AI Job Observability correlates network telemetry with AI workload behavior. AgenticOps-powered autonomous network operations. The AI-aware network management capability is Cisco-unique: no other vendor correlates network health with GPU job completion at this level of integration. Proprietary Cisco platform: opinions captive, no open exit.

AgenticOps (Agent-First IT Operating Model)Ceded

Agent-driven IT operations across networking, security, and observability. Cross-domain telemetry from Cisco Networking, Security Cloud Control, Nexus One, Splunk, and ThousandEyes. Agentic Workflows and AI Canvas for troubleshooting and automation. Deep Network Model provides system-wide awareness. Extends from cloud to on-premises to air-gapped industrial environments. Proprietary Cisco platform: opinions captive, no open exit.

Cisco Hybrid Mesh FirewallCeded

Policy enforcement across network switches, workloads, and NVIDIA BlueField DPUs. Extends security policy to the GPU server level. This is a Layer 0/2A security function: infrastructure-level policy enforcement that operates below the application runtime. Proprietary Cisco platform: opinions captive, no open exit. Not scored within this chip under the GA evidence table: Enforcement on NVIDIA BlueField DPUs ("General Availability: Q4 CY26").

NVIDIA-Provided

NVIDIA GPU Operator + Run:ai

GPU scheduling, resource allocation, and workload orchestration. Same NVIDIA dependency as Dell and HPE at this layer. Cisco does not own GPU-aware scheduling primitives.

NVIDIA AI Enterprise

Enterprise AI software platform providing GPU drivers, container runtime, and validated AI frameworks. Licensed separately from Cisco infrastructure.

◆ Gap Analysis

Cisco's Layer 2A is networking-centric: Intersight manages the infrastructure fleet, Nexus One manages the AI network, AgenticOps provides agentic IT operations. These are genuine Cisco-owned capabilities with no equivalent in Dell's or HPE's stack in terms of network-to-GPU observability correlation. But GPU-aware scheduling and workload orchestration (the core Layer 2A functions) are NVIDIA-controlled (GPU Operator, Run:ai, AI Enterprise). This is the same gap Dell and HPE face. The enterprise using Cisco AI PODs schedules GPU workloads through NVIDIA's stack, not through Cisco's. The AgenticOps framework is architecturally interesting because it applies agentic AI to IT operations itself: using AI agents to manage the infrastructure that runs AI agents. No other on-prem vendor has an equivalent agent-driven IT operations model. But AgenticOps manages infrastructure operations (networking, security, observability), not AI workload placement. It's a Layer 2A operational capability, not a Layer 2C governance capability. Nexus One's AI Job Observability deserves specific note: correlating network telemetry with AI job behavior is a genuine signal that could feed Layer 2C placement decisions. If the network can tell you that a training job's completion time degraded because of network congestion on a specific spine switch, that's placement-relevant intelligence. Whether this signal is consumed by any placement logic today is not evident.

◆ Borrowed Judgment

Moderate. Cisco retains infrastructure management and network orchestration judgment (Intersight, Nexus One, AgenticOps). GPU workload scheduling judgment is borrowed from NVIDIA (Run:ai, GPU Operator), same as Dell and HPE. The AI Job Observability capability reduces borrowed judgment marginally: Cisco can see network-to-GPU correlations that NVIDIA's orchestration layer may not surface. But seeing the problem and acting on it are different functions. Cisco sees; NVIDIA schedules.

◆ Working Notes

AgenticOps' cross-domain telemetry (ingesting signals from networking, security, and observability into a single agentic decision surface) is the closest thing to a unified operations control plane in the on-prem assessment series. HPE's GreenLake Intelligence is comparable but serves a different function (infrastructure operations vs. networking operations). The question is whether AgenticOps evolves from operational automation into policy-driven governance. Hardware-management scope (Keith, October 16, 2026): Intersight is the fleet plane (2A, Ceded on Intersight-proprietary profiles). AgenticOps is a vendor-sold day-two tool, read at 2A like any component. The UCS servers' CIMC reads with them at Layer 0. Open question for Keith: Nexus One is a network-device management plane with facets at Layer 0 and 2A; whether the split of hardware management by scope sends it to 2A or the fabric decision keeps it at 0B is unruled. Out of the Cisco Hybrid Mesh Firewall chip under the GA evidence table (October 24, 2026): Enforcement on NVIDIA BlueField DPUs ("General Availability: Q4 CY26").

Layer 2B · RuntimeApplication Runtime & ExecutionSecurity Layer, Not Runtimedecides: model · Delegated▼

Model serving, agent execution, inference APIs, distributed inference

Vendor-Provided

Cisco AI DefenseCeded

Industry-first AI security solution for securing AI models, agents, applications, and infrastructure. Integrates NVIDIA NeMo Guardrails for AI application security. Secures NVIDIA OpenShell agent development platform with controls and guardrails to govern agent and claw actions. Model validation, prompt injection defense, data leakage prevention, bias detection. Spans Layer 2B (runtime security) and Layer 2C (agent governance). This is Cisco's most differentiated Layer 2B contribution: no other infrastructure vendor has an equivalent AI-specific security product. Proprietary Cisco platform: opinions captive, no open exit.

DefenseClaw (Open Source Secure Agent Framework)Retained

Open-source framework that automates security governance for agentic AI. Admission control: scans skills, MCP servers, plugins, and code before they run. Observe mode (log without blocking) and action mode (block HIGH/CRITICAL findings). Integrates with NVIDIA OpenShell as the sandbox runtime. Splunk Observability Cloud dashboards for monitoring. Apache 2.0 licensed. Plans to integrate with NVIDIA OpenShell as the sandbox to eliminate manual steps and accelerate secure agent deployment.

Cisco Isovalent Runtime SecurityCeded

eBPF-based runtime security for containerized AI workloads. Deep kernel-level visibility into container behavior, network flows, and system calls. Part of the Secure AI Factory security stack. Runtime enforcement, not runtime execution: secures the container environment, does not provide the model-serving or agent execution runtime. Proprietary Cisco platform: opinions captive, no open exit.

Splunk AI Agent MonitoringCeded

Tracks performance, cost, quality, and behavior of LLM and agentic applications in Splunk Observability Cloud. Visualizes agent workflows. Integrating with Cisco AI Defense for risk mitigation (bias, hallucinations, data leakage, prompt injection). GA February 2026. Galileo acquisition (expected Q4 FY2026) will add real-time guardrails, 20+ evaluation metrics including hallucination detection and context adherence, full ADLC coverage. Proprietary Cisco platform: opinions captive, no open exit.

NVIDIA-Provided

NVIDIA NemoClaw / OpenShell

Agent runtime and sandboxed execution environment. Cisco AI Defense integrates with OpenShell to add security governance. The runtime is NVIDIA's; the security layer is Cisco's.

NVIDIA NIM + AI Enterprise

Containerized model serving and commercial AI platform. Same dependency as Dell and HPE.

NVIDIA Dynamo

Distributed inference framework with KV-aware routing. Performance optimization, not policy-driven placement.

NVIDIA NeMo Guardrails

Runtime safety boundaries integrated into Cisco AI Defense. Cisco extends NeMo Guardrails with its own AI Defense policy enforcement.

◆ Gap Analysis

Cisco does not own the core agent runtime, model-serving runtime, or distributed inference framework. Same structural position as Dell and HPE at Layer 2B. The NVIDIA NemoClaw/OpenShell stack provides execution; Cisco provides security governance around it. But Cisco's security contribution at Layer 2B is the most comprehensive of any infrastructure vendor assessed. AI Defense is not a rebranded NVIDIA capability. It's Cisco-developed AI-specific security that integrates with NVIDIA's runtime. DefenseClaw is open-source admission control for agent capabilities. Isovalent provides kernel-level container security. Splunk AI Agent Monitoring provides behavioral observability. Together, these constitute a 'trust layer' for AI execution that no other infrastructure vendor matches. The Galileo acquisition is strategically significant: it extends Splunk from infrastructure observability into AI agent evaluation, covering the full Agent Development Lifecycle (ADLC): prompt optimization, model selection, production monitoring, and guardrail enforcement. Post-Galileo, Cisco will have the most comprehensive AI observability stack of any infrastructure vendor. The distinction the 4+1 model draws: security constrains what agents CAN'T do. Runtime governs what agents DO. Governance determines what agents SHOULD do. Cisco has the first. NVIDIA has the second. Nobody fully has the third.

◆ Borrowed Judgment

Moderate but inverted from Dell's pattern. Dell borrows runtime judgment from NVIDIA and security judgment from partners (CrowdStrike, Fortanix, F5). Cisco borrows runtime judgment from NVIDIA but retains security judgment entirely: AI Defense, DefenseClaw, Isovalent, and Splunk AI Agent Monitoring are all Cisco IP. The enterprise inherits NVIDIA's runtime decisions but Cisco's security decisions. Post-Galileo, the observability judgment becomes even more Retained: Cisco will own infrastructure observability (Splunk), network observability (ThousandEyes, Nexus One), and AI agent observability (Galileo + AI Agent Monitoring) in a single platform. Decision authority: the runtime is NVIDIA's, and it reads as it does on NVIDIA's row. The model makes the runtime call inside it, and the enterprise's own tool code, executing client-side and able to refuse, gates the effect: model decides, visible, overridable, Delegated. Portability is a separate reading, carried by the components.

◆ Working Notes

Peter Bailey (SVP/GM Cisco Security): 'We have this opportunity to be a trust layer, not just for network activity, but actually what's happening at the application layer, at the workload layer, between agents, between workloads, between data.' This is a Layer 2B/2C strategic claim: Cisco as the trust layer that wraps around other vendors' execution layers. DefenseClaw's open-source model is strategically similar to AGNTCY: Cisco open-sources the agent security framework, building community adoption and standards influence, while retaining the commercial AI Defense product. Open-source for influence, commercial for revenue.

Layer 2C · ReasoningAgentic Infrastructure — The Reasoning PlaneSecurity and Observability, Not Yet Governance; Agent Identity in Betadecides: vendor · Delegated▼

Policy-driven placement and resource coordination — the Autonomy Layer

Vendor-Provided

AGNTCY (Linux Foundation, Infrastructure Layer)Retained

Open-source infrastructure for multi-agent systems: agent discovery (Open Agent Schema Framework / DNS-like agent directory), agent identity (cryptographic verification across organizational boundaries), agent messaging (SLIM: Secure Low-Latency Interactive Messaging, quantum-safe), agent observability (end-to-end across multi-agent, multi-vendor workflows). Originally open-sourced by Cisco Outshift (March 2025), donated to Linux Foundation (July 2025) with Dell, Google Cloud, Oracle, Red Hat as formative members. 75+ supporting companies. Critical context: AGNTCY is one component within a larger standards convergence, not the defining standard itself. The Agentic AI Foundation (AAIF), formed December 2025, is the umbrella, analogous to CNCF for cloud-native. AAIF's founding projects are MCP (Anthropic), AGENTS.md (OpenAI), and goose (Block). Platinum members are AWS, Anthropic, Block, Bloomberg, Cloudflare, Google, Microsoft, OpenAI. Cisco is a Gold member of AAIF, not Platinum. A2A (Google) reached v1.0 and joined the broader LF agentic ecosystem. AGNTCY sits as complementary infrastructure beneath these protocols: the plumbing (discovery, identity, messaging, observability) that MCP and A2A need but don't provide themselves. AAIF is already called 'the fastest-growing project in Linux Foundation history' with 190 members by May 2026, more than double CNCF's membership at the same stage. Microsoft explicitly draws the Kubernetes parallel: 'Just as Kubernetes needed RBAC and admission controllers to be enterprise-ready, agentic systems need governance primitives.' AGNTCY contributes some of those primitives. It does not define the ecosystem.

Cisco AI Defense (Agent Governance Functions)Ceded

Secures multi-agent systems with controls for agent discovery, behavioral guardrails, and policy enforcement. Integrates with NVIDIA OpenShell for sandbox governance. Combined with Duo Agentic Identity, provides: which agents exist (discovery), who they are (identity), what they can access (authorization), what they do (monitoring), and what they can't do (guardrails). This is the closest thing to an agent governance stack in Cisco's portfolio. Proprietary Cisco platform: opinions captive, no open exit.

Splunk Observability + Galileo (Agent Evaluation)Ceded

AI Agent Monitoring in Splunk Observability Cloud for production agent behavior tracking. Galileo acquisition adds real-time guardrails, hallucination detection, context adherence, chunk attribution, 20+ evaluation metrics across the full ADLC. The Futurum Group positioned Splunk post-Galileo as 'an AI-era control plane candidate, concentrating network, security, and AI agent behavior telemetry in a single vendor.' Whether telemetry concentration constitutes a control plane is the open question. Proprietary Cisco platform: opinions captive, no open exit. Not scored within this chip under the GA evidence table: Galileo (no Cisco page shows it on Cisco's paper).

NVIDIA-Provided

No NVIDIA Layer 2C Dependency

All Layer 2C components are Cisco IP or Cisco-originated open standards. NVIDIA does not control agent identity, governance policy, or observability in Cisco's stack. This is the same pattern as Google's Layer 2C: the intelligence governance layer is vendor-owned, not NVIDIA-dependent.

◆ Gap Analysis

Applying the 'Routing Is Not Reasoning' test from the 4+1 model: • Duo Agentic Identity = identity management (which agents exist and what they can access), in Beta and unscored • AI Defense = constraint enforcement (what agents cannot do) • DefenseClaw = admission control (what agent capabilities are approved to run) • AGNTCY = infrastructure primitives (how agents discover, authenticate, and message each other) • Splunk + Galileo = observability and evaluation (what agents are doing and how well) None of these provides policy-driven decisions about where compute runs relative to data, which model serves which request, or how cost/compliance/latency are arbitrated in real time. Cisco's Layer 2C is the most comprehensive SECURITY and OBSERVABILITY story of any vendor assessed, but security and observability are not the same as governance and placement. The AGNTCY positioning requires careful calibration. The K8s analogy applies to the broader Agentic AI Foundation (AAIF), the Linux Foundation umbrella with MCP (Anthropic), AGENTS.md (OpenAI), goose (Block) as founding projects, and AWS/Google/Microsoft/Anthropic/OpenAI as Platinum members. AAIF is 'the fastest-growing project in Linux Foundation history' with 190 members and more than double CNCF's early-stage membership. AGNTCY is one project within this ecosystem: important infrastructure (discovery, identity, messaging, observability) that MCP and A2A need but don't provide. But Cisco is a Gold member of AAIF, not Platinum. The ecosystem-defining standards (MCP, A2A) were originated by Anthropic and Google respectively, not Cisco. AGNTCY contributes the plumbing beneath the protocols, valuable, but not the protocols themselves. The structural comparison: • Google has a productized Layer 2C control plane (Agent Identity + Gateway + Registry + Orchestration + Observability + Memory Bank) AND originated A2A • IBM has cross-framework agent governance (watsonx Orchestrate) + cross-platform model governance (watsonx.governance) • VAST has PolicyEngine + Polaris for data-plane governance • Cisco has agent security + agent observability + open infrastructure primitives (AGNTCY), with agent identity in Beta, but no agent orchestration, no model routing, no placement reasoning Cisco is building the trust layer and contributing to the infrastructure standards layer. The question the 4+1 model poses is whether trust (can this agent be trusted to act?) plus interoperability standards (can agents discover and talk to each other?) is sufficient without governance (should this agent act here, now, with this data, on this model?). Trust and interoperability are necessary for governance. They are not governance. However, Cisco's Layer 2C position is stronger than Dell's (gap) and arguably stronger than HPE's (Delegated to Kamiwaza). Cisco owns genuine Layer 2C primitives. They just don't compose into a placement engine yet.

◆ Borrowed Judgment

Low for the functions Cisco provides. All Layer 2C components are Cisco IP or Cisco-originated open standards. No NVIDIA dependency, no partner dependency for identity, security, or observability at this layer. But 'low borrowed judgment for partial Layer 2C' is structurally different from 'low borrowed judgment for complete Layer 2C.' VAST has low borrowed judgment for a comprehensive (if captive) Layer 2C. Cisco has low borrowed judgment for agent trust functions, but the placement, routing, and governance functions are gaps, not borrowed judgment. The enterprise architect using Cisco for Layer 2C gets strong agent security with zero borrowed judgment; agent identity (Duo) is in Beta. They do not get agent orchestration, model routing, or policy-driven placement from anyone, Cisco or otherwise.

◆ Working Notes

The Futurum Group's framing of post-Galileo Splunk as 'an AI-era control plane candidate' is the most explicit analyst validation of Cisco's Layer 2C potential. The path from candidate to actual control plane requires composing identity (Duo) + security (AI Defense) + observability (Splunk/Galileo) + networking intelligence (Nexus One AI Job Observability) into a single decision surface that makes placement and governance decisions. The pieces exist. The composition does not. This is the inverse of Dell's position: Dell has no pieces. Cisco has pieces without composition. VAST has composition without openness. Google has composition with captivity. The AAIF ecosystem is the right frame for understanding where agentic governance standards are heading. Microsoft's explicit Kubernetes parallel ('Just as Kubernetes needed RBAC and admission controllers to be enterprise-ready, agentic systems need governance primitives and those primitives belong in the open') validates the 4+1 model's Layer 2C thesis. The governance primitives Microsoft references are exactly what Layer 2C defines. AAIF is building the open-standards foundation for Layer 2C; the question is whether any vendor productizes it as a coherent control plane. Cisco's strategic position within AAIF: contributor of infrastructure plumbing (AGNTCY), commercial implementer of trust functions (AI Defense, Duo, Splunk), Gold-tier member. This is a meaningful position, but it's one contributor among 190 members, not the ecosystem definer. Anthropic (MCP) and Google (A2A) contributed the foundational protocols. Cisco contributed the infrastructure layer beneath them. The analogy: Google contributed Kubernetes; Cisco contributed something more like the CNI (Container Network Interface) or service mesh layer: essential infrastructure, but not the orchestration standard itself. The commercial bet: if AAIF standards mature into the enterprise agentic governance stack, Cisco's commercial products (AI Defense for security, Duo for identity, Splunk for observability, DefenseClaw for admission control) become the enterprise implementation layer on top of open standards: the Red Hat model applied to agentic infrastructure. That's a credible business model if the standards achieve adoption. Cisco survey data: 55% of organizations have agentic AI running as pilots or in production (Jan 2026). Only 4% are fully confident in full-scale deployment. 59% cite security concerns as the biggest barrier. Cisco is positioned to address the security barrier. The governance barrier, which the 4+1 model argues is structurally different, is what AAIF and AGNTCY are attempting to address at the standards level. Instrument note: live Infrastructure-2C (a policy engine deciding at request time where inference runs relative to the data, which model serves the request, and how cost, latency, and compliance are arbitrated) does not ship from any vendor on this instrument. It is recorded here as a universal finding about the market, not as a charge against this vendor. The sibling finding applies here as well: you cannot prompt your way to deterministic output. The controls credited in this cell answer whether an action is legal (permissions, schema and policy checks, rate and token limits, approval gates), and none of them validates whether the outcome was right under a graduated escalation policy. Controls that work by instructing the model shift the output distribution without pinning it. That deterministic outcome-validator is missing instrument-wide, and like live placement it is noted as universal rather than charged to one vendor. To notes under the GA evidence table (October 24, 2026): Duo Agentic Identity (Every public Duo Agentic Identity integration doc (AgentCore Gateway, agentgateway, Cisco AI Defense) marks it Beta, and Duo's gateway blog offers only early access; no GA statement found. ("Duo Agentic Identity for Amazon Bedrock AgentCore Gateway is a Beta feature.")). Out of the Splunk Observability + Galileo chip under the GA evidence table (October 24, 2026): Galileo (no Cisco page shows it on Cisco's paper).

Layer 3 (+1) · ApplicationsAI Application Layer — The Value PlaneSplunk and the Security Portfolio, First-Party Security Applicationsdecides: vendor · Ceded▼

AI-powered business capabilities — business logic, workflow automation

Vendor-Provided

Splunk Platform (Analytics + Security Applications)Ceded

Splunk Enterprise Security TDIR platform. Splunk Observability Cloud. These are Layer 3 security applications that run on Cisco's own infrastructure. Splunk's installed base provides a distribution channel for AI capabilities: existing Splunk customers can adopt AI Agent Monitoring without new vendor relationships.

Cisco Security Portfolio (Security Applications)Ceded

AI Defense, Duo, Umbrella, Talos threat intelligence: the security product portfolio that Cisco positions as the 'trust layer' for enterprise AI. Each product addresses a specific security function; together they constitute a security application suite that sits alongside (not above) AI applications from other vendors. Proprietary Cisco platform: opinions captive, no open exit. Not scored within this chip under the GA evidence table: SecureX (Item 6: the SecureX product URL no longer presents SecureX (no SecureX content served); I couldn't retrieve Cisco's end-of-life notice, so no verbatim marker. Keith should confirm.).

NVIDIA-Provided

NVIDIA NIM + NemoClaw / OpenShell Runtime

Execution surface for AI applications on Cisco infrastructure. NVIDIA provides the application runtime; Cisco provides the infrastructure substrate and security layer.

◆ Gap Analysis

Cisco sells first-party security and observability applications: Splunk Enterprise Security and Splunk Observability Cloud (Splunk is a Cisco subsidiary), and the security portfolio of AI Defense (with a Cisco offer description and support pages), Duo, Umbrella and Talos threat intelligence. They watch the enterprise's traffic, identities and telemetry, so they're business applications, and enterprises already running Splunk can add AI agent monitoring and AI Defense integration inside an existing investment. The scope is security and observability, a fixed-function slice, so the grade is moderate. Cisco's AI ecosystem doesn't add to it: the Secure AI Factory is a reference architecture partners build on, not applications sold on Cisco's paper, and it's named, not scored. Calibration: Arista reads moderate on NDR and AGNI and Nokia on Deepfield Defender, the same first-party security reading. HPE reads partner because customers buy ISV applications from HPE on the GreenLake Marketplace; Dell, Nutanix, Red Hat, VMware, VAST and Supermicro read gap, because their AI ISV programs are certification, not procurement (as ruled October 19, 2026: business applications bought or supported on the vendor's paper).

◆ Borrowed Judgment

The enterprise borrows Cisco's detection, policy and threat-intelligence judgment in Splunk and the security portfolio. Detection content, correlation searches and policies are Splunk and Cisco objects, and leaving means rebuilding them in another security stack.

◆ Working Notes

Named, not scored: the Cisco Secure AI Factory partner ecosystem (reference architecture). The service-provider motion (Cisco AI Grid, managed AI services for telcos) is noted as go-to-market, not a business application. Out of the Cisco Security Portfolio chip under the GA evidence table (October 24, 2026): SecureX (Item 6: the SecureX product URL no longer presents SecureX (no SecureX content served); I couldn't retrieve Cisco's end-of-life notice, so no verbatim marker. Keith should confirm.).

Sources & revision history · v1.39 - 4+1 v3: Layer 0 Sub-Layers

Cisco Live EMEA 2026, GTC 2026, RSA Conference 2026, Cisco Q3 FY2026 earnings, Galileo acquisition announcement (Apr 2026), AGNTCY/Linux Foundation donation (Jul 2025), DefenseClaw open source, Cisco/VAST partnership, analyst coverage, published 4+1 model. v1.5: two instrument rulings applied. (1) Whose-paper capability rule (the GPU parallel): the VAST AI Operating System is on Cisco's Global Price List with full Cisco support. The full platform deploys on Cisco paper, exposed and customer-administered, passing the exposure test; 1A/1B/1C promote moderate→strong at parity with the Supermicro row's identical delivery of the same engine. (2) Retraction of the OEM-channel DAPM rule: VAST components at 1A/1B/1C move Delegated→Ceded: a proprietary single-implementation platform's opinions are captive to its owner through any paper, matching VAST's own row. statusLabels moved to capability vocabulary. Capability grades and authority chips now read on their own axes. /reconcile (September 1, 2026): retired status vocabulary replaced with gap. /reconcile (September 1, 2026): shared 2C findings stated explicitly (live-placement universality, outcome-validation finding). /reconcile (October 5, 2026): 2B authority re-read from {decides:vendor,visible:true,overridable:false,boundary:vendor,direction:Ceded} to model / visible / overridable / Delegated, matching NVIDIA's row for the same NVIDIA AI Enterprise runtime (the open-source seam and tool-call ruling, September 2, 2026). Components and grade unchanged. /reconcile (October 5, 2026): 1C authority column (rulings of September 15 and October 4, 2026). 1C authority vendor / Ceded to code / Retained, matching VAST's row for the same DataEngine; a channel's paper doesn't change who decides. Grade and components unchanged. /reconcile (October 5, 2026): authority visible set from the cell's own text where it settles it: layer0 true. Direction, grades, and components unchanged. /reconcile (October 5, 2026): authority read against product docs: layer1a visible true. Grades and components unchanged. v1.13 (October 16, 2026, hardware-management scope ruling): a controller embedded in one system is that system's management half and reads with it; a fleet management plane sold and run on its own across many systems is a 2A component, its portability read by the standard-interface test (Keith, October 16, 2026, after the AWS, Dell, and HPE pressure tests). Intersight stays at layer2a as the fleet plane. Its third-party server support reaches Dell PowerEdge and HPE ProLiant through Redfish (cisco.com Intersight licensing page), but server profiles and policies are Intersight objects that don't lift to another plane, so Ceded holds; the boundary is on the October 16 judgment sheet. The Cisco Integrated Management Controller (CIMC) in each UCS server reads with that server at Layer 0. AgenticOps stays at layer2a as a vendor-sold day-two tool. Nexus One keeps its Layer 0 and 2A facets pending Keith's ruling on network-device fleet planes. Grades, authority, and chips unchanged. v1.14 (Layer 0 sub-layers, October 16, 2026): Layer 0 split into 0A Compute, 0B Network Fabric and 0C Storage Substrate by runtime decision (Keith, October 16, 2026); storage left 1A for 0C, and 1A, now Data Foundation & Governance, is graded on the catalog that classifies the data. 0A strong, 0B strong, 0C strong; summary edits (summary worksheet, Keith, October 16, 2026). v1.15 (October 19, 2026, /reconcile partner ruling): Layer 3 partner to moderate on Splunk and the security portfolio; the Secure AI Factory reference architecture moved to notes. (Same pass) 1B and 1C: the networking chips removed; the fabric is scored at 0B and transport isn't credited above it. Grades rest on VAST InsightEngine and DataEngine and hold. (Same pass) Plain-language pass: methodology rule numbers in the prose and audit notes replaced with the reasoning they stood for; no grade, chip or authority reading changed. v1.16 (October 19, 2026, /reconcile voice pass): em-dashes in the prose replaced with periods, colons, commas or parentheses; wording, grades, chips and authority readings unchanged. v1.17 (October 21, 2026, /reconcile): 0C door chip added for VAST's S3 and NVMe-oF front ends on Cisco's paper, Delegated, matching VAST's own row (its S3 interface chip, v1.18, and its NVMe-oF chip), from reconcile's peer calibration; the channel-substitution rule keeps a multi-vendor standard interface Delegated through any paper. Grade and cell authority unchanged; the cell rests on VAST's DASE engine. v1.18 (October 22, 2026, /reconcile): 0B rebuilt on Cisco's own documents. Hyperfabric's detail drops a mis-expanded "NCP" and records the datasheet's front-end, back-end and storage designs on Silicon One or NVIDIA Spectrum-4 N9100 switches (ERA and NCP compliant). The AI POD facet records the dedicated G200-based N9364E-SG2 back end and the front end carrying storage. The 8000 chips record the 8223 on Silicon One P200 for scale-across, flagged. The N9100 (NVIDIA Spectrum-4 on Cisco paper, under NX-OS or Hyperfabric) is added, Ceded. Found by the 0B fabric research. Grade and authority unchanged. v1.19 (October 23, 2026, /reconcile): 0A's C885A chip follows Cisco's current data sheet (8x AMD MI350X); its H200 and MI300X configurations, past their June 25, 2026 last order date, move to a named, unscored note. The C880A M8 with HGX B300 comes in as Cisco's NVIDIA eight-way server. The X580p count comes down from 24 to 8 GPUs per chassis, per its data sheet. Uniqueness and first-in-market claims with no independent evidence come out of the C885A, C845A and X-Series text. Found by the 0A compute research. Grade and authority unchanged. v1.20 (October 23, 2026, /reconcile): 0A: One chassis, NVIDIA or AMD PCIe cards. Found by the Layer 0 data pass after the sniff read. Grade and cell authority unchanged. v1.21 (October 23, 2026, storage door pass): The VAST door on the AI PODs takes NFS and SMB, and the X580p GPU node reads Retained like its peers. Grade unchanged. v1.22 (October 24, 2026, /reconcile): 1B moves from strong to moderate with VAST: the InsightEngine chip becomes VAST's documented vector search on Cisco's price list, and InsightEngine is unscored. Found in the 1B dependency audit follow-ups. Grade changed: 1B strong to moderate. v1.23 (October 24, 2026, /reconcile): 1B strong restored with VAST's row: InsightEngine is GA on VAST's own announcement and orderable on Cisco's price list (Keith, October 24, 2026). Grade changed: 1B moderate to strong. v1.24 (October 24, 2026, /reconcile): GA evidence recorded on 1 of 1 Layer 1B chips under the GA evidence table. Grade unchanged. v1.25 (October 24, 2026, /reconcile): Layer 1B GA evidence migrated to the GA evidence table version 2. Grade unchanged. v1.26 (October 24, 2026, /reconcile): GA evidence recorded on 1 of 2 Layer 1A chips under the GA evidence table version 2. Grade unchanged. v1.27 (October 24, 2026, /reconcile): GA evidence recorded on 1 of 1 Layer 1C chips under the GA evidence table version 2. Grade unchanged. v1.28 (October 24, 2026, /reconcile): GA evidence recorded on 7 of 7 Layer 0B chips under the GA evidence table version 2. Grade unchanged. v1.29 (October 24, 2026, /reconcile): GA evidence recorded on 9 of 9 Layer 0A chips under the GA evidence table version 2. Grade unchanged. v1.30 (October 24, 2026, /reconcile): GA evidence recorded on 4 of 4 Layer 0C chips under the GA evidence table version 2. Grade unchanged. v1.31 (October 24, 2026, /reconcile): GA evidence recorded on 3 of 4 Layer 2A chips under the GA evidence table version 2. Grade unchanged. v1.32 (October 24, 2026, /reconcile): GA evidence recorded on 4 of 4 Layer 2B chips under the GA evidence table version 2. Grade unchanged. v1.33 (October 24, 2026, /reconcile): GA evidence recorded on 1 of 2 Layer 3 chips under the GA evidence table version 2. Grade unchanged. v1.34 (October 24, 2026, /reconcile): GA evidence recorded on 1 of 4 Layer 2C chips under the GA evidence table version 2. Grade unchanged. v1.35 (October 24, 2026, /reconcile): GA evidence table version 2.1 applied: 5 chips recorded or narrowed, 1 to notes. Grade unchanged. v1.36 (October 24, 2026, /reconcile): Stale text corrected from the GA backfill: VAST's block front end on Cisco named NVMe/TCP, as Cisco and VAST document it. Grade unchanged. v1.37 (October 24, 2026, /reconcile): 2C prose: Duo Agentic Identity is in Beta. Grade unchanged. v1.38 (October 24, 2026, /reconcile): SecureX out of the Layer 3 security-portfolio list; the chip’s GA note already excluded it. Grade unchanged. v1.39 (October 27, 2026): each component now carries a durable offering id; nothing else changed.

4+1 Layer AI Infrastructure Model · Vendor Assessment Series · The CTO Advisor LLC (DBA The Advisor Bench) · thectoadvisor.com