Two ideas that make DPU security possible: DOCA (how you program the DPU) and isolation (why a guard that lives outside the house can't be bribed by a burglar inside).
In Lesson 1 you saw BlueField-3 is a real computer on the network card. Two things turn that hardware into a security platform: the DOCA software framework, and the isolation that comes from running outside the host. Get these and Check Point's product (Lesson 3) is obvious.
You don't get BlueField's value by plugging it in; you get it by programming it. DOCA is NVIDIA's software framework/SDK for BlueField — the way vendors like Check Point build services that run on the DPU and drive its accelerators.doca
Here's the security insight that makes DPUs special. A traditional host agent runs inside the machine it protects — so if an attacker takes over the host, they can often disable or blind the agent. The DPU runs the guard on separate silicon with its own OS, outside the host's reach.
(1) Tamper resistance — the guard survives a host compromise because it lives on separate silicon. (2) Zero performance tax — inspection runs on the DPU's own cores/accelerators, so no GPU or host-CPU cycles are stolen from the AI workload.brief
Isolation raises a question: if the guard is outside the host, how does it see what's running inside? Answer: DOCA Argus — a DOCA service that uses the DPU's direct memory access to read the host's memory and enumerate every running process, with no agent installed on the host.cp
DOCA = the framework you program the DPU with. DOCA Argus = the specific DOCA service for agentless host process visibility via direct memory access. Check Point = the vendor whose firewall + threat prevention is built on DOCA and uses Argus. Don't collapse these into one word.
The NVIDIA DOCA documentation (framework + services, including Argus), and Check Point's AI Factory Firewall solution brief for how these ideas are used in the product.