Urgent.News

What's breaking now, across thousands of outlets.

AI

Where Security Fits in an AI Agent Stack: NVIDIA's Layer-by-Layer Threat Model

NVIDIA's AI safety and security teams published the first vendor-backed security architecture for agent stacks. The document maps where traditional application security boundaries fail when agents compose multi-step workflows, call external tools, and maintain stateful memory across sessions. The timing matters. OpenAI, Anthropic, and the UK AI Security Institute each reported frontier agents…

NVIDIA has released a security architecture framework for AI agent stacks, addressing the vulnerabilities that arise from the dynamic and stateful nature of these systems. Traditional application security controls often fail to account for the way agents compose multi-step workflows, call external tools, and maintain memory across sessions.

The framework divides the agent stack into five layers, each with specific security responsibilities: the Model layer, Harness layer, Meta-harness layer, Secure runtime layer, and Inference infrastructure layer. By addressing the unique challenges of each layer, NVIDIA aims to provide a comprehensive approach to securing AI agents from unauthorized access and malicious actions.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

GitHub's Copilot SDK for Java: What Running Agents in Spring Boot Without Frameworks Reveals About Tool Integration

Every Java team adding AI to a backend right now faces the same fork in the road. If you are on Spring Boot, you reach for Spring AI. If you are not, you reach for LangChain4j.

  • GitHub Copilot SDK for Java provides agent runtime for backend integration without subscription.
  • SDK offers tool calling, streaming, and context management built-in, unlike other Java AI libraries.
  • BYOK mode enables agent loop to run in JVM with custom API key for production Spring Boot services.

My AI visibility score was 78%. Then I fixed how I measured it and it was 25%

In August, I published a number on my studio’s website: we had been named unprompted in 14 out of 18 blind answers across ChatGPT, Perplexity, and Gemini. It was wrong.

  • Initial AI visibility score was 78%, then corrected to 25%
  • Revised test conducted with isolated sessions for each engine
  • Issue lies in engines' decision-making, not in their knowledge

Robot comment classifier

(I used both AI and vibecoding tags because the article describes training a logistic regression/SVM on LLM output. I thought there was a statistics tag that would have been appropriate but apparently…

  • Classifier examines typographical marks in comments
  • Robots use em dashes, semicolons, unicode arrows, ellipses more often
  • Robots generate complex comments with commas, parentheses, line breaks

More from Saturday 22 August →