Defender module

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.

Microsoft Defender API

Variable	Description	Status
DEFENDER_TENANT_ID	Required for authentication.	required
DEFENDER_CLIENT_ID	Required for authentication.	required
DEFENDER_CLIENT_SECRET	Required for authentication.	required

Sanity-check the wiring:

weave secrets check
weave defender --help
weave doctor   # reports DEFENDER_TENANT_ID status

Capabilities

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

Entity	find	list	show	do	snapshot	diff	apply
alert	·	✓	·	·	·	·	·
machine	✓	✓	·	✓	·	·	·
resources	·	·	·	·	✓	✓	✓

Commands

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

find (1)

find machine

read

Find a machine by hostname or id.

weave defender find machine <identifier>

list (2)

list alerts

read

List recent alerts.

weave defender list alerts <arg>

list machines

read

List onboarded machines.

weave defender list machines <arg>

do (3)

do isolate

write

Isolate a machine from the network.

weave defender do isolate <machine-id>

do release

write

Release a machine from isolation.

weave defender do release <machine-id>

do run-av-scan

write

Trigger an AV scan.

weave defender do run-av-scan <machine-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 → diff → apply --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/defender/.

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

resources

snapshot diff apply

defender resources — field-level apply via REST.

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

State file skeleton

module: defender
kind: resources
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.

Resources audit

Snapshot and diff resources.

weave defender snapshot resources
$EDITOR .weave-state/defender/resources.yaml
weave defender diff resources
weave defender apply resources

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
defender_resources	weave defender snapshot/diff/apply resources Snapshot/diff for audit; confirm apply on the module page.

Troubleshooting & source

Missing credentials

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

Unexpected behaviour from a state apply

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

Open the source

The module lives at https://github.com/andy-broyles/weavewhatever/tree/main/src/weave/modules/defender. File a bug or feature request at https://github.com/andy-broyles/weavewhatever/issues.