From the NVIDIA edition of September 28, 2026
StorageReview: OpenShell on CPU and Sentry on BlueField-4 with 100-plus partners
StorageReview · Enterprise infrastructure trade press · Global (U.S. trade press)
- Publisher
- StorageReview
- Original publication
- 2026-09-28T00:00:00Z
- Source retrieved
- 2026-09-29
- Event date
- 2026-09-28
What happened
Sep 28, 2026 StorageReview (Harold Fritts) reports NVIDIA Open Agent Safety Platform as dual-layer guardrails: OpenShell secure runtime on the host CPU and Sentry out-of-band watchdog on BlueField-4 that the agent cannot see. It echoes NVIDIA's incident pattern (agents circumventing application-layer controls) and states more than 100 organizations are working with the platform at launch, naming Anthropic, Cisco, CrowdStrike, Dell, HPE, Microsoft, Palantir, Red Hat, Salesforce, SAP, Scale AI, ServiceNow, and SpaceXAI among others.
Why it matters
Useful for infrastructure buyers mapping partner ecosystem and DPU dependency; still not measured campus/agency outcomes.
Evidence and measured results
Opened StorageReview article dated September 28, 2026; lead paragraphs describe two-layer design, invisible-to-agent DPU watchdog framing, and 100-plus partner claim with named organizations.
Limitations and uncertainty
Trade press synthesizing vendor launch; partner depth and production status not independently audited.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Infra buyers need clarity on DPU watchdog vs CPU runtime and ecosystem partners.
- Stakeholders
- infra procurement
- platform architect
- security
- Discovery questions
- Do partner integrations matter to your stack?
- Is BlueField-4 funded?
- Value hypothesis
- Dual-layer design may align with AI-factory BOMs that already include BlueField-4.
- Potential engagement
- BOM review workshop for OpenShell-only vs OpenShell+Sentry options.
- Unsupported claims
- Partner logos equal validated SLED deployments
Pre-sales engineering
Role takeaway
- Fit
- Secondary confirmation of CPU+DPU split for reference architectures.
- Architecture and integration
- Host OpenShell; DPU Sentry out-of-band; inventory separately.
- Prerequisites
- BlueField-4 for Sentry
- OpenShell for CPU path
- Constraints
- No overhead metrics in this piece
- partner status opaque
- Security
- Agent-invisible DPU path is the security intent—verify isolation assumptions.
- Proof of value
- Topology diagram matches dual-layer model
Delivery
Role takeaway
- Work
- Revise diagrams and integration shortlist; defer installs to primary docs.
- Dependencies
- Primary NVIDIA docs
- DPU inventory
- Ownership
- Infrastructure architecture.
- Skills and adoption
- Educate capacity planners on DPU watchdog role.
- Governance checkpoints
- Separate partner marketing from control baseline
- Acceptance criteria
- Approved dual-layer diagram
- Risks
- Logo-driven scope creep
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?
Reinforces that Sentry is intentionally off the agent-visible host path—inventory DPUs separately from GPU nodes in designs.
Governance
Who approves, reviews and stays accountable for outcomes?
Large partner list is ecosystem signal, not a shared public-sector control baseline.
Security and privacy
What data, permissions and controls need testing?
Out-of-band framing is architectural intent; local attestation/monitoring design still required.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Dual-layer wording helps non-GPU specialists understand why DPUs appear in agent-safety BOMs.
Procurement
What should contracts, pricing and exit terms secure?
Partner lists should not substitute for evaluated product configurations.
Operating model
Which teams own the service once it runs?
Keep ecosystem tracking separate from control-baseline ownership.
Publication history
- 2026-09-28NVIDIA · Issue 237 resources
Stable resource ID: storagereview-agent-safety-20260928