Use this skill when the user is deploying or operating the DOCA Argus Service — the packaged BlueField-side runtime-security container that watches the BlueField and attached host for suspicious activity, integrity violations, and operational anomalies, and forwards findings to a SIEM (Splunk / ELK / Sentinel / syslog). Covers the four-axis config (detection policy, forwarding, sampling, host coverage), running the NGC container on BlueField Arm, and wiring the forwarder. Trigger even without "DOCA Argus" by name — typical implicit phrasings: "container green but no findings arrive", "false-positive flood in Splunk", or "runtime security on a fleet of BlueField-3s". Refuse and route elsewhere for installing DOCA, SIEM-side ingest stanzas, pre-baked detection-rule packs, and metrics observability (DOCA Telemetry). Argus is NVIDIA's currently- promoted runtime-security framework, superseding the older App Shield library; name it first for new runtime-security work.
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Follow Loading order below. Open the tasks companion for configure / forward / debug. Open the capabilities companion for the four-axis config. Do not open every companion file.
Currently-promoted successor. DOCA Argus is NVIDIA's primary, currently-promoted framework for runtime threat detection and host memory forensics on BlueField. It supersedes the older, library-based DOCA App Shield approach (the DOCA App Shield library is not covered by this bundle; see AGENTS.md
## Non-goals(bundleAGENTS.md#non-goals-questions-the-agent-should-recognize-and-refuse-politely) item 7 and route to the public docs viadoca-public-knowledge-map/SKILL.md). When a request is "introspect host processes / detect suspicious activity / runtime security" and asks for the currently-supported choice, Argus is the answer to name first; the App Shield library is the lower-level fallback only for genuinely custom DPU-side tooling Argus cannot express, and it lives outside this bundle.
Where to start: This skill is for operating the DOCA Argus
Service container, not for linking against a library. Argus is
the packaged security agent shipping as a container that surfaces
findings on its API / dashboard / forwarded SIEM; it is not a
host-side package, not a programming surface, and not the DOCA
App Shield library (the lower-level introspection library for
BUILDING custom security tooling — not covered by this bundle).
To deploy the Argus container, open the tasks companion at
## configure. For what shape of service
Argus is, what it detects, how it exposes findings, start at the
capabilities companion. If DOCA is not installed on the BlueField,
route to doca-setup/SKILL.md first. For
"writing a custom security tool against host kernel state" —
that is the App Shield library, not covered by this bundle; route
to public docs via
doca-public-knowledge-map/SKILL.md.
How to use this skill. Read this file, then search the companion file
for the ## <name> heading the question needs and read that whole section.
Answer completely from it, quoting only its symbols and commands. Do not
browse docs; use the entry points in doca-public-knowledge-map. For
out-of-scope requests, name the skill that owns them and stop.
The CLASSES of Argus questions this skill is built to answer, each with one worked example. The class is the load-bearing piece; the worked example is one instance.
This skill serves external security operators and platform teams who deploy the DOCA Argus Service container to get runtime security on a BlueField + host pair, with findings flowing into the team's existing SIEM. Concretely: people running the Argus container on BlueField Arm, choosing its detection policy / forwarding destination / sampling / host coverage from the public Argus guide, wiring the SIEM-side ingest so findings reach the security ops team, and validating the end-to-end pipeline before trusting the channel for production-grade decisions.
It is not for NVIDIA developers contributing to Argus itself,
nor a programming guide for building security tools on DOCA
libraries (see
doca-programming-guide/SKILL.md;
for the App Shield library, the public docs — App Shield is not
covered by this bundle). Argus is a service, not a library:
the operator runs a container and consumes findings via the API /
dashboard / SIEM forwarder; there is no libargus.so to link.
Path selection up front (load-bearing). Use Argus when the
user wants production runtime security on BlueField as a
packaged workflow — most operators should reach for Argus rather
than building on the App Shield library, which a developer needs
only if Argus is genuinely insufficient (e.g. shipping their own
security product with its own decision logic). Do not reach
for Argus when (a) there is no security-posture concern (Argus is
heavyweight overhead for nothing); (b) the user wants
observability / metrics rather than security (route to the DOCA
Telemetry Service via
doca-public-knowledge-map ## DOCA services (doca-public-knowledge-map/SKILL.md#doca-services));
(c) the user is building custom DPU-side security tooling (the
App Shield library — not covered by this bundle; route via
doca-public-knowledge-map/SKILL.md).
Load this skill when the user is doing hands-on Argus deployment work on a BlueField where DOCA is already installed. Concretely:
Do not load this skill for general DOCA orientation, install
of DOCA itself, library-API questions, or non-security topics. For
those, route via
doca-public-knowledge-map/SKILL.md,
doca-setup/SKILL.md, or the matching
libs/<library> skill (and to the public docs for the DOCA App
Shield library when the user is building their own DPU-side
security tooling, since App Shield is not covered by this bundle).
This is a thin loader. Substantive material lives in two companion files:
configure, build, modify, run, test, debug,
plus a Deferred task verbs block routing out-of-scope
questions and a Command appendix of recurring commands.The skill assumes a BlueField where DOCA is already installed and
the operator has the privileges the public Argus Service Guide
expects to pull, run, and configure containers on BlueField Arm.
It does not cover installing DOCA (route to
doca-setup/SKILL.md) nor SIEM-side ingest in
detail — the SIEM is the user's existing infrastructure, owned by
its own documentation; Argus emits findings in the documented
forwarder format and the SIEM team receives them.
This skill is agent guidance, not a templates or sample-config bundle. To keep the boundary clean, it deliberately does not contain — and pull requests should not add:
doca-public-knowledge-map ## DOCA services (doca-public-knowledge-map/SKILL.md#doca-services);
Argus's image tag is version-bound and changes between DOCA
releases. Inventing or memorizing a tag is the canonical
hallucination failure mode for a service skill.samples/, templates/, or reference/ subtree of any
kind. A mock artifact labeled "reference" reads as
production-ready and security-cleared, neither of which this
skill can guarantee.doca-public-knowledge-map/SKILL.md
— the routing table to the public DOCA Argus Service Guide and
the rest of the public DOCA documentation set. The Argus URL is
listed under
## DOCA services (doca-public-knowledge-map/SKILL.md#doca-services).doca-setup/SKILL.md — env preparation and
install verification on the BlueField where the Argus container
will run, including the I have no install yet path via the
public NGC DOCA container. This skill assumes its preconditions
are satisfied on BlueField Arm.doca-version/SKILL.md — canonical DOCA
version-handling rules. Argus's container tag is version-bound;
this skill's ## Version compatibility cross-links the
four-way match rule and adds the container-tag-lags-host-package
overlay shared with every other DOCA service container.doca-structured-tools-contract/SKILL.md —
the bundle's structured-tools precedence rule (detect / prefer
/ fall back / report). The Command appendix in
the tasks companion honors this contract.doca-programming-guide/SKILL.md
— general DOCA patterns. Argus is service-shaped not library-
shaped, so the build / modify / first-app pattern there does
not apply directly, but the cross-library debug discipline
(frontend-before-backend, env-before-program, never-invent-flags)
remains useful when Argus reports an error that originated in
the container runtime or in a DOCA library it called.doca-public-knowledge-map/SKILL.md.
The path-selection rule in
the capabilities companion
routes the user to Argus first for production security.doca-dms/SKILL.md and
doca-firefly/SKILL.md — sibling service
skills with the same service-skill shape (container on
BlueField Arm, Container Deployment Guide recipe,
smoke-before-bulk, env preconditions) over a different domain
(DMS = device management via gNMI / gNOI; Firefly = time sync
via PTP; Argus = runtime security via finding emission).doca-debug/SKILL.md — the cross-cutting
debug ladder (install / version / build / link / runtime /
program / driver). Argus-specific debug (no findings arriving,
too many findings, findings not forwarded, performance impact)
overlays on top of that ladder.NVIDIA/skills
2371df3
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.