How does in-silicon security change the traditional security model?
Purpose-built for AI infrastructure, NVIDIA BlueField DPUs combine high-performance networking, programmable compute, hardware acceleration, and advanced security capabilities into a single platform embedded into every AI factory compute node. Unlike traditional security approaches that rely on host system software, BlueField establishes a hardware-enforced, in-silicon, and workload-independent security layer. Operating within its own trusted execution domain, BlueField isolates infrastructure and security services from the host system. Monitoring, policy enforcement, and telemetry operate eve
How does DOCA Flow accelerate advanced security services?
DOCA Flow is a foundational library within the DOCA software platform that enables developers and cybersecurity providers to create high-performance, hardware-accelerated packet processing pipelines on BlueField processors. Through a programmable API, developers can define packet processing “pipes” that execute directly in networking hardware, offloading networking and security operations from the host CPU while maintaining ultra-low latency and high throughput. By executing packet inspection, encryption, filtering, and policy enforcement directly in silicon, DOCA Flow enables network security
How does scanning help mitigate risk before skill publication?
Before a verified skill reaches the NVIDIA Skills catalog, NVIDIA runs it through SkillSpector as part of the publication validation pipeline. This approach treats the skill as a deployable agent capability rather than as a static prompt. SkillSpector checks conventional software risks such as vulnerable dependencies, suspicious scripts, dangerous code patterns, credential access, and data exfiltration paths. SkillSpector also checks agent-specific risks, such as hidden instructions, prompt injection, trigger abuse, excessive agency, tool poisoning, and mismatches between a skill’s declared p
An NVIDIA-verified skill starts in a source repository owned by a product team. From there, it moves through a publishing flow that can include both human review and automated policy checks, followed by scanning, evaluation, generation of the skill card, signing, cataloging, and synchronization into the public catalog. Each verified skill is paired with a skill card, a machine-readable trust record that explains the following: What the skill does
Who built the skill
How is the skill licensed
What are the skill dependencies
What are the known technical limitations, risks, and mitigatio