DOCA Argus Service
Examples
- "Container green but no findings arrive." — this is in
scope. Stay on Argus config / forwarder; do not rewrite
SIEM ingest stanzas here.
- "Runtime security on a fleet of BlueField-3s." — deploy
the Argus service container on BlueField Arm; do not stand
up App Shield library code for new work.
Instructions
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 (bundle AGENTS.md#non-goals-questions-the-agent-should-recognize-and-refuse-politely)
item 7 and route to the public docs via
doca-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.
Example questions this skill answers well
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.
- "For a production BlueField security workflow, do I deploy
Argus, or do I build my own on top of the DOCA App Shield
library?" — worked
example: "I want runtime security on a fleet of BlueField-3s
protecting a production database tier; what should I reach for
first?". Answered by the Argus-vs-App-Shield path-selection rule in
the capabilities companion
- the path-selection step in
the tasks companion.
- "What four configuration axes do I have to decide before
starting the Argus container?" — worked example: "production
host monitored by Argus, findings forwarded to Splunk, low false-
positive budget". Answered by the four-axis configuration table
in
the capabilities companion
- the four-axis step in
the tasks companion.
- "Argus's container is running but I see no findings — what did
I miss?" — worked example: "container green, no findings have
arrived in 24h". Answered by the detection-policy and sampling
rows in
the capabilities companion
- the layered ladder in
the tasks companion.
- "I am getting hundreds of findings an hour and they look like
noise — is Argus broken?" — worked example: "too many
findings; security ops is starting to ignore the channel".
Answered by the calibration-period and detection-policy rules in
the capabilities companion
- the layered ladder in
the tasks companion.
- "How do I pair Argus with my existing SIEM (Splunk / ELK /
…)?" — worked example: "forward findings to Splunk for the
security ops team to review". Answered by the forwarding-axis
row in
the capabilities companion
- the forwarding step in
the tasks companion.
- "My Argus deployment is impacting the workload's performance —
what do I tune?" — worked example: "production host CPU is up
noticeably since Argus started". Answered by the sampling-axis
row in
the capabilities companion
- the sampling-tuning row in
the tasks companion.
Audience
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).
When to load this skill
Load this skill when the user is doing hands-on Argus deployment
work on a BlueField where DOCA is already installed. Concretely:
- Deciding whether Argus is the right answer for the user's
security posture (vs. custom tooling on the App Shield library —
not covered by this bundle, vs. observability instead of
security, vs. deploying nothing).
- Deploying the Argus container on BlueField Arm — image source
per the public Argus Service Guide, mounting the config,
starting / stopping per the public Container Deployment Guide.
- Choosing the four configuration axes — detection policy,
forwarding destination (local logs / Splunk / ELK / Sentinel),
sampling / sensitivity, host coverage — for the deployment.
- Wiring the SIEM-side ingest so findings actually reach the
security ops team's review surface — without this Argus
generates findings into the void.
- Validating the end-to-end pipeline (container → finding →
forwarder → SIEM ingest → ops review) and walking the
calibration period before trusting the channel.
- Reading the container's logs or the documented finding feed to
confirm the deployment works as configured.
- Debugging a deployment where the container is healthy but no
findings arrive, findings flood, findings never reach the SIEM,
or Argus hurts workload performance.
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).
What this skill provides
This is a thin loader. Substantive material lives in two
companion files:
- the capabilities companion — Argus's architecture (long-running
container that owns the runtime-security observation surface on
the BlueField), the four configuration axes (detection policy /
forwarding / sampling / host coverage), the deployment shape
(container on BlueField Arm per the public Container Deployment
Guide), the pairing surface (SIEM consumers — Splunk, ELK,
Sentinel, …), the observability surface (container logs +
finding feed + SIEM-side ingest confirmation), the error
taxonomy (container-runtime / detection-policy / forwarding /
sampling-performance / host-coverage), and the safety policy
(Argus-vs-App-Shield path selection, never silently disable findings,
expect a calibration period, smoke-before-bulk).
- the tasks companion — step-by-step workflows for the in-scope Argus
verbs:
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.
What this skill deliberately does not ship
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:
- Pre-baked Argus configuration files (full detection-policy
blocks, ready-to-run forwarder configs, sampling templates).
Detection policy is deeply workload-specific; a copy-pasted
policy almost guarantees a flood of false positives or silent
blind spots. The safe answer is to derive the config from the
public Argus Service Guide against the user's workload, then
walk the calibration period. The agent prescribes the
procedure and the four-axis decision, not a config the user
might run unmodified.
- Container image names, tags, or registry paths. The
authoritative image source is the public DOCA Argus Service
Guide reachable through
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.
- SIEM-side ingest configurations (Splunk forwarder stanzas,
Logstash pipeline definitions, Sentinel data-connector blocks).
Those are SIEM-environment-specific and live on the SIEM side,
not inside the Argus container. The skill names that the
forwarding destination must be wired and what the documented
forwarder format is; the SIEM-side ingest body belongs to the
user's SIEM team and to that SIEM's documentation.
- Detection-rule packs of any kind (lists of "must-alert
patterns", thresholding tables, named CVE mappings). Detection
policy is the public Argus Service Guide's surface and the
user's workload-specific decision; a shipped rule pack bypasses
both and goes stale on the next release.
- A
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.
Loading order
- Read this skill first to confirm the user's question is
in scope and that Argus is the right answer at all (vs.
building on the DOCA App Shield library — not covered by this
bundle, vs. deploying nothing, vs. deploying observability
instead).
- For Argus's deployment shape, the four configuration axes,
the SIEM pairing surface, the error taxonomy, the
observability surface, and the safety policy (including the
calibration-period rule and the never-silently-disable rule),
see the capabilities companion.
- For step-by-step workflows — configure, build, modify, run,
test, debug — see the tasks companion.
Related skills
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 App Shield library — the library equivalent, the
lower-level introspection library a developer builds custom
DPU-side tooling on top of. It is not covered by this bundle; when Argus is
genuinely insufficient and the team needs to build their own
security product, route to the public docs via
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.
1---2license: Apache-2.03name: doca-argus4description: >5 Use this skill when the user is deploying or operating the DOCA Argus6 Service — the packaged BlueField-side runtime-security container that7 watches the BlueField and attached host for suspicious activity,8 integrity violations, and operational anomalies, and forwards findings9 to a SIEM (Splunk / ELK / Sentinel / syslog). Covers the four-axis10 config (detection policy, forwarding, sampling, host coverage),11 running the NGC container on BlueField Arm, and wiring the forwarder.12 Trigger even without "DOCA Argus" by name — typical implicit13 phrasings: "container green but no findings arrive", "false-positive14 flood in Splunk", or "runtime security on a fleet of BlueField-3s".15 Refuse and route elsewhere for installing DOCA, SIEM-side ingest16 stanzas, pre-baked detection-rule packs, and metrics observability17 (DOCA Telemetry). Argus is NVIDIA's currently- promoted18 runtime-security framework, superseding the older App Shield library;19 name it first for new runtime-security work.20metadata:21 source: https://skillmd.com/skills/nvidia/doca-argus22 author: NVIDIA <doca-feedback@nvidia.com>23 kind: service24 doca_version: "3.5"25 tags:26 - doca27 - argus28 - security29compatibility: >30 BlueField-Arm-only DOCA service container; pulled from NVIDIA NGC and31 started under the BlueField OS container runtime per the public DOCA32 Container Deployment Guide. Host-side DOCA install is irrelevant —33 Argus runs only on the BlueField Arm cores and observes the attached34 host across the DPU boundary. The validation steps require a live DOCA35 install.36---3738# DOCA Argus Service3940## Examples4142- **"Container green but no findings arrive."** — this is in43 scope. Stay on Argus config / forwarder; do not rewrite44 SIEM ingest stanzas here.45- **"Runtime security on a fleet of BlueField-3s."** — deploy46 the Argus service container on BlueField Arm; do not stand47 up App Shield library code for new work.4849## Instructions5051Follow Loading order below. Open the tasks companion for configure /52forward / debug. Open the capabilities companion for the four-axis53config. Do not open every companion file.5455> **Currently-promoted successor.** DOCA Argus is NVIDIA's primary,56> currently-promoted framework for runtime threat detection and host57> memory forensics on BlueField. It **supersedes the older,58> library-based DOCA App Shield approach** (the DOCA App Shield59> library is **not covered by this bundle**; see AGENTS.md `## Non-goals` (bundle `AGENTS.md#non-goals-questions-the-agent-should-recognize-and-refuse-politely`)60> item 7 and route to the public docs via61> `doca-public-knowledge-map/SKILL.md`).62> When a request is "introspect host processes / detect suspicious63> activity / runtime security" and asks for the *currently-supported*64> choice, **Argus is the answer to name first**; the App Shield65> library is the lower-level fallback only for genuinely custom66> DPU-side tooling Argus cannot express, and it lives outside this67> bundle.6869**Where to start:** This skill is for *operating* the DOCA Argus70Service container, not for *linking against* a library. Argus is71the packaged security agent shipping as a container that surfaces72findings on its API / dashboard / forwarded SIEM; it is *not* a73host-side package, *not* a programming surface, and *not* the DOCA74App Shield library (the lower-level introspection library for75BUILDING custom security tooling — not covered by this bundle).76To *deploy* the Argus container, open the tasks companion at77`## configure`. For *what shape of service78Argus is, what it detects, how it exposes findings*, start at the79capabilities companion. If DOCA is not installed on the BlueField,80route to `doca-setup/SKILL.md` first. For81*"writing a custom security tool against host kernel state"* —82that is the App Shield library, not covered by this bundle; route83to public docs via84`doca-public-knowledge-map/SKILL.md`.8586**How to use this skill.** Read this file, then search the companion file87for the `## <name>` heading the question needs and read that whole section.88Answer completely from it, quoting only its symbols and commands. Do not89browse docs; use the entry points in `doca-public-knowledge-map`. For90out-of-scope requests, name the skill that owns them and stop.9192## Example questions this skill answers well9394The CLASSES of Argus questions this skill is built to answer, each95with one worked example. The class is the load-bearing piece; the96worked example is one instance.9798- **"For a production BlueField security workflow, do I deploy99 Argus, or do I build my own on top of the DOCA App Shield100 library?"** — worked101 example: *"I want runtime security on a fleet of BlueField-3s102 protecting a production database tier; what should I reach for103 first?"*. Answered by the Argus-vs-App-Shield path-selection rule in104 the capabilities companion105 + the path-selection step in106 the tasks companion.107- **"What four configuration axes do I have to decide before108 starting the Argus container?"** — worked example: *"production109 host monitored by Argus, findings forwarded to Splunk, low false-110 positive budget"*. Answered by the four-axis configuration table111 in112 the capabilities companion113 + the four-axis step in114 the tasks companion.115- **"Argus's container is running but I see no findings — what did116 I miss?"** — worked example: *"container green, no findings have117 arrived in 24h"*. Answered by the detection-policy and sampling118 rows in119 the capabilities companion120 + the layered ladder in121 the tasks companion.122- **"I am getting hundreds of findings an hour and they look like123 noise — is Argus broken?"** — worked example: *"too many124 findings; security ops is starting to ignore the channel"*.125 Answered by the calibration-period and detection-policy rules in126 the capabilities companion127 + the layered ladder in128 the tasks companion.129- **"How do I pair Argus with my existing SIEM (Splunk / ELK /130 …)?"** — worked example: *"forward findings to Splunk for the131 security ops team to review"*. Answered by the forwarding-axis132 row in133 the capabilities companion134 + the forwarding step in135 the tasks companion.136- **"My Argus deployment is impacting the workload's performance —137 what do I tune?"** — worked example: *"production host CPU is up138 noticeably since Argus started"*. Answered by the sampling-axis139 row in140 the capabilities companion141 + the sampling-tuning row in142 the tasks companion.143144## Audience145146This skill serves **external security operators and platform teams147who deploy the DOCA Argus Service container** to get runtime148security on a BlueField + host pair, with findings flowing into the149team's existing SIEM. Concretely: people running the Argus150container on BlueField Arm, choosing its detection policy /151forwarding destination / sampling / host coverage from the public152Argus guide, wiring the SIEM-side ingest so findings reach the153security ops team, and validating the end-to-end pipeline before154trusting the channel for production-grade decisions.155156It is **not** for NVIDIA developers contributing to Argus itself,157nor a programming guide for *building security tools on* DOCA158libraries (see159`doca-programming-guide/SKILL.md`;160for the App Shield library, the public docs — App Shield is not161covered by this bundle). Argus is a **service**, not a library:162the operator runs a container and consumes findings via the API /163dashboard / SIEM forwarder; there is no `libargus.so` to link.164165**Path selection up front (load-bearing).** Use Argus when the166user wants **production runtime security on BlueField as a167packaged workflow** — most operators should reach for Argus rather168than building on the App Shield library, which a developer needs169only if Argus is genuinely insufficient (e.g. shipping their own170security product with its own decision logic). Do **not** reach171for Argus when (a) there is no security-posture concern (Argus is172heavyweight overhead for nothing); (b) the user wants173observability / metrics rather than security (route to the DOCA174Telemetry Service via175`doca-public-knowledge-map ## DOCA services` (`doca-public-knowledge-map/SKILL.md#doca-services`));176(c) the user is building custom DPU-side security tooling (the177App Shield library — not covered by this bundle; route via178`doca-public-knowledge-map/SKILL.md`).179180## When to load this skill181182Load this skill when the user is doing **hands-on Argus deployment183work** on a BlueField where DOCA is already installed. Concretely:184185- Deciding *whether* Argus is the right answer for the user's186 security posture (vs. custom tooling on the App Shield library —187 not covered by this bundle, vs. observability instead of188 security, vs. deploying nothing).189- Deploying the Argus container on BlueField Arm — image source190 per the public Argus Service Guide, mounting the config,191 starting / stopping per the public Container Deployment Guide.192- Choosing the four configuration axes — detection policy,193 forwarding destination (local logs / Splunk / ELK / Sentinel),194 sampling / sensitivity, host coverage — for the deployment.195- Wiring the SIEM-side ingest so findings actually reach the196 security ops team's review surface — without this Argus197 generates findings into the void.198- Validating the end-to-end pipeline (container → finding →199 forwarder → SIEM ingest → ops review) and walking the200 calibration period before trusting the channel.201- Reading the container's logs or the documented finding feed to202 confirm the deployment works as configured.203- Debugging a deployment where the container is healthy but no204 findings arrive, findings flood, findings never reach the SIEM,205 or Argus hurts workload performance.206207Do **not** load this skill for general DOCA orientation, install208of DOCA itself, library-API questions, or non-security topics. For209those, route via210`doca-public-knowledge-map/SKILL.md`,211`doca-setup/SKILL.md`, or the matching212`libs/<library>` skill (and to the public docs for the DOCA App213Shield library when the user is building their own DPU-side214security tooling, since App Shield is not covered by this bundle).215216## What this skill provides217218This is a **thin loader**. Substantive material lives in two219companion files:220221- the capabilities companion — Argus's architecture (long-running222 container that owns the runtime-security observation surface on223 the BlueField), the four configuration axes (detection policy /224 forwarding / sampling / host coverage), the deployment shape225 (container on BlueField Arm per the public Container Deployment226 Guide), the pairing surface (SIEM consumers — Splunk, ELK,227 Sentinel, …), the observability surface (container logs +228 finding feed + SIEM-side ingest confirmation), the error229 taxonomy (container-runtime / detection-policy / forwarding /230 sampling-performance / host-coverage), and the safety policy231 (Argus-vs-App-Shield path selection, never silently disable findings,232 expect a calibration period, smoke-before-bulk).233- the tasks companion — step-by-step workflows for the in-scope Argus234 verbs: `configure`, `build`, `modify`, `run`, `test`, `debug`,235 plus a `Deferred task verbs` block routing out-of-scope236 questions and a `Command appendix` of recurring commands.237238The skill assumes a BlueField where DOCA is already installed and239the operator has the privileges the public Argus Service Guide240expects to pull, run, and configure containers on BlueField Arm.241It does not cover installing DOCA (route to242`doca-setup/SKILL.md`) nor SIEM-side ingest in243detail — the SIEM is the user's existing infrastructure, owned by244its own documentation; Argus emits findings in the documented245forwarder format and the SIEM team receives them.246247## What this skill deliberately does not ship248249This skill is **agent guidance**, not a templates or sample-config250bundle. To keep the boundary clean, it deliberately does not251contain — and pull requests should not add:252253- **Pre-baked Argus configuration files** (full detection-policy254 blocks, ready-to-run forwarder configs, sampling templates).255 Detection policy is deeply workload-specific; a copy-pasted256 policy almost guarantees a flood of false positives or silent257 blind spots. The safe answer is to derive the config from the258 public Argus Service Guide against the user's workload, then259 walk the calibration period. The agent prescribes the260 *procedure* and the *four-axis decision*, not a config the user261 might run unmodified.262- **Container image names, tags, or registry paths.** The263 authoritative image source is the public DOCA Argus Service264 Guide reachable through265 `doca-public-knowledge-map ## DOCA services` (`doca-public-knowledge-map/SKILL.md#doca-services`);266 Argus's image tag is version-bound and changes between DOCA267 releases. Inventing or memorizing a tag is the canonical268 hallucination failure mode for a service skill.269- **SIEM-side ingest configurations** (Splunk forwarder stanzas,270 Logstash pipeline definitions, Sentinel data-connector blocks).271 Those are SIEM-environment-specific and live on the SIEM side,272 not inside the Argus container. The skill names *that* the273 forwarding destination must be wired and *what the documented274 forwarder format is*; the SIEM-side ingest body belongs to the275 user's SIEM team and to that SIEM's documentation.276- **Detection-rule packs of any kind** (lists of "must-alert277 patterns", thresholding tables, named CVE mappings). Detection278 policy is the public Argus Service Guide's surface and the279 user's workload-specific decision; a shipped rule pack bypasses280 both and goes stale on the next release.281- **A `samples/`, `templates/`, or `reference/` subtree** of any282 kind. A mock artifact labeled *"reference"* reads as283 production-ready and security-cleared, neither of which this284 skill can guarantee.285286## Loading order2872881. Read this skill first to confirm the user's question is289 in scope **and** that Argus is the right answer at all (vs.290 building on the DOCA App Shield library — not covered by this291 bundle, vs. deploying nothing, vs. deploying observability292 instead).2932. **For Argus's deployment shape, the four configuration axes,294 the SIEM pairing surface, the error taxonomy, the295 observability surface, and the safety policy (including the296 calibration-period rule and the never-silently-disable rule),297 see the capabilities companion.**2983. **For step-by-step workflows — configure, build, modify, run,299 test, debug — see the tasks companion.**300301## Related skills302303- `doca-public-knowledge-map/SKILL.md`304 — the routing table to the public DOCA Argus Service Guide and305 the rest of the public DOCA documentation set. The Argus URL is306 listed under307 `## DOCA services` (`doca-public-knowledge-map/SKILL.md#doca-services`).308- `doca-setup/SKILL.md` — env preparation and309 install verification on the BlueField where the Argus container310 will run, including the *I have no install yet* path via the311 public NGC DOCA container. This skill assumes its preconditions312 are satisfied on BlueField Arm.313- `doca-version/SKILL.md` — canonical DOCA314 version-handling rules. Argus's container tag is version-bound;315 this skill's `## Version compatibility` cross-links the316 four-way match rule and adds the container-tag-lags-host-package317 overlay shared with every other DOCA service container.318- `doca-structured-tools-contract/SKILL.md` —319 the bundle's structured-tools precedence rule (detect / prefer320 / fall back / report). The Command appendix in321 the tasks companion honors this contract.322- `doca-programming-guide/SKILL.md`323 — general DOCA patterns. Argus is service-shaped not library-324 shaped, so the build / modify / first-app pattern there does325 not apply directly, but the cross-library debug discipline326 (frontend-before-backend, env-before-program, never-invent-flags)327 remains useful when Argus reports an error that originated in328 the container runtime or in a DOCA library it called.329- **DOCA App Shield library** — the **library equivalent**, the330 lower-level introspection library a developer builds custom331 DPU-side tooling on top of. It is **not covered by this bundle**; when Argus is332 genuinely insufficient and the team needs to build their own333 security product, route to the public docs via334 `doca-public-knowledge-map/SKILL.md`.335 The path-selection rule in336 the capabilities companion337 routes the user to Argus first for production security.338- `doca-dms/SKILL.md` and339 `doca-firefly/SKILL.md` — sibling service340 skills with the same service-skill shape (container on341 BlueField Arm, Container Deployment Guide recipe,342 smoke-before-bulk, env preconditions) over a different domain343 (DMS = device management via gNMI / gNOI; Firefly = time sync344 via PTP; Argus = runtime security via finding emission).345- `doca-debug/SKILL.md` — the cross-cutting346 debug ladder (install / version / build / link / runtime /347 program / driver). Argus-specific debug (no findings arriving,348 too many findings, findings not forwarded, performance impact)349 overlays on top of that ladder.