weave
module · Endpoints & MDM

Tenable

Tenable.io — assets, vulnerabilities, scans (Nessus cloud)

Namespace: weave tenable Env: TENABLE_ACCESS_KEY
6
Commands
1
State kinds
Endpoints & MDM
Category
1
API docs

Setup

Configure credentials via environment variables. We recommend sourcing them through 1Password or your secrets manager rather than committing them to the shell rc.

Official API reference

weave commands for this module are checked against the vendor's published API.

Variable Description Status
TENABLE_ACCESS_KEYRequired for authentication.required
TENABLE_SECRET_KEYRequired for authentication.required

Sanity-check the wiring:

weave secrets check
weave tenable --help
weave doctor   # reports TENABLE_ACCESS_KEY status

Capabilities

What this module can do, by entity and verb. means a working CLI surface; · means not (yet) wired.

Entity findlistshowdosnapshotdiffapply
asset·····
endpoints····
scan·····
vulnerability······

Commands

Every registered CLI command, grouped by verb. Each example uses placeholder arguments — substitute real values for your environment.

find (1)

find asset

read

Find an asset by IP or hostname.

weave tenable find asset <identifier>

list (3)

list assets

read

List discovered assets.

weave tenable list assets <arg>

list scans

read

List configured scans.

weave tenable list scans <arg>

list vulns

read

List open vulnerabilities.

weave tenable list vulns <arg>

do (2)

do launch

write

Launch a scan.

weave tenable do launch <scan-id>

do stop

write

Stop a running scan.

weave tenable do stop <scan-id>
snapshot / diff / apply are generated automatically from the State Kinds declared on this module — see the State kinds section below for per-kind details. Workflow: snapshot → edit YAML → diffapply --yes (or confirm interactively; apply --dry-run previews the same diff).

State kinds

Resources this module can snapshot and diff; apply where the kind supports live writes (see Round-trip per kind). Always run diff before apply; use --yes in automation after review. Files live under .weave-state/tenable/.

This module is on the thinner integration path — use snapshot / diff for audit; confirm apply per kind below before relying on writes.

endpoints

snapshot diff apply

tenable endpoints — field-level apply via REST.

Scope
Round-trip
Full round-trip — snapshot, diff, apply.

State file skeleton

module: tenable
kind: endpoints
items:
  - # <fields specific to this kind — see snapshot output>

Workflows

End-to-end recipes from operators who already run this module in production. Copy, adapt, and put under change-control.

Endpoints audit

Snapshot and diff endpoints.

weave tenable snapshot endpoints
$EDITOR .weave-state/tenable/endpoints.yaml
weave tenable diff endpoints
weave tenable apply endpoints

Terraform parity

For each Terraform resource in the canonical provider, here's the equivalent live-API verb in weave. Use this as a migration cheat-sheet, not a 1:1 contract — weave deliberately stays in the live-state lane, not the desired-state lane.

Terraform resource weave equivalent
tenable_endpointsweave tenable snapshot/diff/apply endpoints
Snapshot/diff for audit; confirm apply on the module page.

Troubleshooting & source

Missing credentials

Run weave doctor — it reports which env vars (including TENABLE_ACCESS_KEY) are set and which are blank.

Unexpected behaviour from a state apply

Re-run weave tenable diff <kind> to confirm the controller's current state, then re-snapshot before the next apply. The driver always re-snapshots before diffing.