NVIDIA: AI security is an engineering problem — defend every layer of the agent stack
NVIDIA Blog · rss · 2026-09-21
NVIDIA argues AI security must be treated as engineering: defined requirements, enforceable controls, named owners, and evidence of protection.
- Security spans the full agent stack: models, harnesses, and runtime environments each carry responsibilities; controls must follow data, instructions, and actions.
- Boundaries must hold even when an agent errs: runtime should limit files, network destinations, and processes independently of the agent's reasoning; permission to update a record shouldn't imply permission to export it.
- Every agent needs traceable identity, least-privilege credentials, human approval for consequential actions, and protected logs for forensics.
- Tools: open-source NVIDIA OpenShell (sandboxed runtime enforcing policies beyond the agent's reach), with Cisco DefenseClaw, JFrog skill scanning, CrowdStrike SafeMind, Palo Alto Prisma AIRS, Capital One VulnHunter, ReversingLabs Spectra Assure.
- Teams need pre-deployment evidence (credential theft and exfiltration blocked), reproducible failure investigation, and open sharing of what works to shift advantage to defenders.
More from coding & agent
- Open-source coding-agent skills for Google ADK on Google Cloud, distilled from real engineering lessons — Difficult_Design6676 · 2026-09-22
- After trimming his Claude Code harness, a Max 20x user now has 9 spare hours of quota a week — carlito_17 · 2026-09-22
- OpenAI shows how a surgeon uses Codex to build tools and review PubMed literature — OpenAIDevs · 2026-09-22
- Similarity Isn't Relevance: Four Layers Every Personal Agent Memory System Must Separate — sujingshen · 2026-09-22
- JevHarness lets an LLM author and freeze task-specific agent harnesses — but who owns the frozen SOP? — sujingshen · 2026-09-22
- A file-first Claude-driven project harness, honestly compared against 5 alternatives — bishopZ · 2026-09-22