Verify and monitor

This page is for administrators who run a standalone deployment day to day. Everything on it is read-only except rotating per-user credentials. To upgrade, change the config, repair, or remove a deployment, see Upgrade, repair and remove. For a failed check, look up the code in Troubleshooting. Terms such as guardian, enumerator, and machine policy are defined in Concepts.

Status and verify

Two lifecycle actions report on a deployment. Neither one changes the host.

sudo /opt/defenseclaw/bin/defenseclaw-gateway enterprise linux status --json
sudo /opt/defenseclaw/bin/defenseclaw-gateway enterprise linux verify --json

sudo /opt/cisco/defenseclaw/bin/defenseclaw-gateway enterprise macos status --json
sudo /opt/cisco/defenseclaw/bin/defenseclaw-gateway enterprise macos verify --json

$DefenseClaw = 'C:\Program Files\Cisco\DefenseClaw\bin\defenseclaw.exe'
& $DefenseClaw enterprise windows status --profile standalone --json
& $DefenseClaw enterprise windows verify --profile standalone --json

Run these as root on Linux and macOS, and from an elevated prompt on Windows, so every check can read the protected files. On Windows, the lifecycle runs on PowerShell 7, which must be installed; you can start defenseclaw.exe from any shell.

On Linux and macOS, verify first waits up to 5 seconds for another lifecycle run to finish, and holds no lock while it checks. If that run is still going, verify skips its checks and exits 75 with lifecycle_busy. The Linux verify unit accepts that exit, so a daily run that met an administrator's change is not left failed. On Windows, verify does not wait: while another run's transaction is pending, it fails (1603); run it again after that run finishes. A transaction that an interrupted run left pending fails verify (1 with verify_failed, or 1603) until the next mutating run recovers it.

verify also runs on a schedule, and its result goes to the logs listed in Logs and events.

Review activity from the CLI (Linux and macOS)

The lifecycle's status and verify report the deployment. To see the gateway, who is enrolled and what the gateway decided, run these as root. No extra environment variables are needed: on a standalone host, run as root (or as the gateway's service account), status, audit and enterprise hooks read the managed config, data directory, target manifest and guardian state instead of ~/.defenseclaw, and audit opens the gateway's audit database read-only.

sudo /opt/defenseclaw/bin/defenseclaw-gateway status
sudo /opt/defenseclaw/bin/defenseclaw-gateway enterprise hooks status
sudo /opt/defenseclaw/bin/defenseclaw-gateway audit export --since 2h --connector claudecode --output /root/claudecode-audit.jsonl

sudo /opt/cisco/defenseclaw/bin/defenseclaw-gateway status
sudo /opt/cisco/defenseclaw/bin/defenseclaw-gateway enterprise hooks status
sudo /opt/cisco/defenseclaw/bin/defenseclaw-gateway audit export --since 2h --connector claudecode --output /var/root/claudecode-audit.jsonl

On a standalone host, hook decisions, rejected connector hooks, direct inspect-tool calls and refused hook-socket requests carry the verified account (user.id, defenseclaw.user.name); a refused request also names its route and reason. Each tool call the foreign-hook guard denies adds a connector-hook row with event: foreign_hook_session that names the file. Scan-finding and scan-verdict rows do not carry the account yet (#921); join them to the hook decision on evaluation_id.

For the machine-policy view per user, see Machine policy status. A standard user who runs enterprise hooks gets the managed-host message, which names the administrator command.

Health fields

With --json, every lifecycle action prints one result document. Its schema is packaging/mdm/contract/lifecycle-result.schema.json. The MDM wrapper scripts print the same document.

The two summary fields are computed differently on each OS:

• Enrollment counts. Linux and macOS read the counts from the guardian's authorization ledger, and exempt is always 0 there: accounts that exclude_users or exempt_users keep out of enrollment have no target, and enterprise policy show --user <name> names the rule for one account. Windows counts the rows of the target manifest: pending is deferred rows, exempt is disabled rows, and failed is always 0.
• Inspection. On Windows, inspection.ai_defense is ok when AI Defense is enabled in the config and the gateway is ready. It does not test the key or the network. On Linux and macOS the lifecycle reads both fields from the gateway's /health: local is active, disabled or unknown, and ai_defense is disabled, ok, unavailable:<code> or unknown (the gateway did not answer). The gateway's own /health guardrail detail carries ai_defense_available when AI Defense is enabled, and ai_defense_error when it is not available. To check AI Defense, see AI Defense is not used.
• Users. On Linux and macOS, neither summary field depends on whether any user is enrolled. Check enrollment for that.

What to alert on

Claude Code attestation (Windows). With Claude Code enabled, Windows reports security_complete: false until an administrator confirms, with a real Claude Code session on that host, that Claude Code runs DefenseClaw's managed hooks. After that check, run repair with --attest-claude-effective-policy. A later change to the Claude Code policy or the hook binary makes the attestation stale, and security_complete returns to false.

Machine policy status

Machine policy is the vendor policy file (Codex requirements, Claude Code managed settings, Cursor enterprise hooks, Copilot policy.d) where the lifecycle places DefenseClaw's hooks for the connectors that support it. See Machine policy. The machine_policy block of the result summarizes it. The enterprise policy commands show each connector's route, lock, and coverage in detail. They never write.

On this release, set DEFENSECLAW_CONFIG to the managed config path when you run these commands. Without it they read the calling user's ~/.defenseclaw/config.yaml and refuse.

sudo DEFENSECLAW_CONFIG=/etc/defenseclaw/config.yaml /opt/defenseclaw/bin/defenseclaw-gateway enterprise policy show --json
sudo DEFENSECLAW_CONFIG=/etc/defenseclaw/config.yaml /opt/defenseclaw/bin/defenseclaw-gateway enterprise policy verify --json

sudo DEFENSECLAW_CONFIG=/opt/cisco/defenseclaw/etc/config.yaml /opt/cisco/defenseclaw/bin/defenseclaw-gateway enterprise policy show --json

$env:DEFENSECLAW_CONFIG = 'C:\ProgramData\Cisco\DefenseClaw\etc\config.yaml'
& 'C:\Program Files\Cisco\DefenseClaw\bin\defenseclaw.exe' enterprise policy show --json

• policy verify exits 1 when coverage is incomplete.
• Add --connector <name> to check one connector, and --user <name> to also check that user's own agent config for hooks DefenseClaw has not approved.
• policy verify --live runs the real client as a user and proves that it loads DefenseClaw's hooks. It needs --user, exactly one --connector (codex or claudecode), and --agent-binary with the client's absolute path. The default timeout is 90 seconds (--timeout). On Windows, run it from the target user's own session.

sudo DEFENSECLAW_CONFIG=/etc/defenseclaw/config.yaml /opt/defenseclaw/bin/defenseclaw-gateway enterprise policy verify \
  --live --user alice --connector codex --agent-binary /usr/local/bin/codex --json

Per-user connector state

Connectors without a machine policy file, such as Devin, Antigravity, Hermes, OpenCode, and Amp, are wired into each user's own agent config by the guardian. The enumerator decides which users to protect.

1. The enumerator runs every 5 minutes on every OS. It writes the target manifest (targets.yaml), one row per user and connector. A new user or a newly enabled connector first appears on its next cycle, so allow up to 5 minutes.
2. The guardian then installs or repairs the hooks for each row. It reacts to file changes and also reconciles every minute.
3. On Linux and macOS, the guardian records each protected user in its authorization ledger. The gateway accepts per-user hook calls only from users in that ledger.

To reconcile now instead of waiting for the next minute, run the reconcile action (sudo … enterprise linux reconcile --json, or the macOS or Windows equivalent). It does not wait for the enumerator.

If a user you expect is missing, see A user is not enrolled and Enrollment.

When a user breaks their own setup (Linux and macOS)

A user can break the files DefenseClaw needs in their own account, for example by making ~/.defenseclaw unreadable, replacing an agent's config folder with a file or a symbolic link, or leaving an agent config the agent cannot parse. That account is then not protected for the affected agents. Every other account stays protected and the services stay ready. Once the account is fixed, the next reconcile (within a minute) clears the warning.

When the guardian is refused by a path in the user's own home (a link, a file where a folder belongs or a folder where a file belongs, or a folder the user made unreadable), status, verify and reconcile report it for that account as the warning guardian_target_user_path, which names the path. It does not fail reconcile, verify, detect.sh --require-healthy or security_complete, because only that account is affected and the user could have made the change themselves. Any other reason the account cannot be protected is reported as guardian_target_failed: it sets security_complete: false, verify fails, and detect.sh --require-healthy reports the device as not compliant.

The guardian repairs, as that user and within a minute, what DefenseClaw owns in the account:

• DefenseClaw's registration or plugin, removed or edited in the agent's default config;
• the modes of ~/.defenseclaw and its hooks folder, restored to owner-only (0700);
• a deleted or edited hook script, and a hook runtime whose fail mode no longer matches the config;
• a missing ~/.kiro or ~/.kiro/hooks folder, which Kiro does not create;
• group or other write on the home folder of an enrolled user.

It does not change anything else in the account, so these stay unprotected for that account until the user or an administrator fixes them: a link or a non-directory where an agent's config folder should be, an agent config the agent cannot parse, a special file such as a named pipe at a config path, and files another account owns.

To find the account, read warnings[] in status --json or verify --json: each guardian_target_user_path and guardian_target_failed entry names the user, the connector and the reason. As root, defenseclaw-gateway enterprise hooks status --json lists every user and connector with its state.

Rotate per-user credentials

The guardian gives each enrolled user credentials that it derives from one per-machine key and binds to that user's uid or SID. The agents' telemetry uses them on every OS, and so do hooks and in-agent plugins on Windows. On Linux and macOS, hooks and DefenseClaw's in-agent plugins reach the gateway over the hook socket and hold no credential. Rotate the key when a user's credentials may have been copied, or on your own schedule.

sudo /opt/defenseclaw/bin/defenseclaw-gateway enterprise linux rotate-credentials --json

sudo /opt/cisco/defenseclaw/bin/defenseclaw-gateway enterprise macos rotate-credentials --json

The rotation moves every user to the new key before the key takes effect:

1. Check. Nothing changes until the gateway reports that it serves the current key alone and a fresh guardian reconcile leaves every user who holds a credential current. A target the guardian cannot protect holds a credential when it was protected before, because the gateway keeps accepting the credentials the guardian wrote for it then. Such a target, including one whose own home blocks it (guardian_target_user_path), stops the rotation with rotation_failed. Fix that user or remove them from enrollment, then rotate again. A target that holds no credential does not stop the rotation. That covers an agent the guardian never protected, such as a version without a verified hook contract (hook_contract_unverified), an account that no longer exists, and a home that is not available yet. The rotation lists these targets in changes as skipped. The guardian gives them credentials from the new key once it can protect them.
2. Stage. The new key is written next to the current one. From then on the gateway accepts the credentials of both keys, and it must prove that it accepts each user's new credentials before any user is moved.
3. Move. The guardian re-renders every user from the new key. A second reconcile then re-reads each user's installed files and must find them unchanged.
4. Commit. The new key replaces the current one. The gateway refuses the old key's credentials from then on.

If any step before the commit fails, the rotation removes the new key and the guardian moves every user back. The old key is never changed, so each user gets back exactly the credentials they had. The command exits 1 with rotation_failed, which names the step and the users. rollback_failed beside it means the rollback is not complete yet; its message says whether the next lifecycle run finishes it or the guardian re-renders the remaining users at its next reconcile, within a minute. If the command is interrupted, the next lifecycle action (for example reconcile) completes a rotation that had already committed or rolls back one that had not, and reports rotation_recovered. The result names keys only by a prefix of their SHA-256. A rotation that committed lists in changes the new and the previous key, how many targets and users it moved, and the targets it skipped. If you interrupt the command, it prints the reconcile command to run.

What users see:

• Hooks and plugins on Linux and macOS keep working through the rotation, because they use the hook socket.
• Agents that are already running keep sending telemetry with the credential they loaded when they started. It works until the commit; after that the gateway refuses it, and that agent's telemetry is lost until the user restarts the agent. Agents started after the rotation use the new credentials. Ask users to restart their agents after a rotation.

On Windows, enterprise windows rotate-credentials exits 1639 and changes nothing. The Windows guardian writes a user's credentials only while that user is signed in, so it cannot move every user before a new key takes effect, and replacing the key would fail the hooks of every signed-out user closed until they sign in again. To cut off one Windows user, remove them from enrollment as described in Contain an incident.

Logs and events

Windows

Standard users can read the files in %WINDIR%\Logs\DefenseClaw. Only SYSTEM and Administrators can write them. The lifecycle writes these logs and events only when it runs elevated.

A healthy status or verify writes no event, so frequent polling does not fill the event log.

Linux

journalctl -u defenseclaw-enterprise-verify.service -n 50 --no-pager
systemctl list-timers defenseclaw-enterprise-verify.timer

macOS

All logs are in /Library/Logs/Cisco/DefenseClaw.

Audit records and SIEM forwarding

The gateway records every hook decision in its local audit store. This is the SQLite database set by observability.local.path. By default it is audit.db in the data directory: /var/lib/defenseclaw on Linux, /opt/cisco/defenseclaw/runtime on macOS, and C:\ProgramData\Cisco\DefenseClaw\runtime on Windows.

To forward records to a SIEM, add observability.destinations to the managed config that you deploy. Destination kinds include OTLP, Splunk HEC, HTTP JSONL, and JSONL files. See Observability.

Two limits apply on a managed host:

• The lifecycle writes each service's environment itself. The only variables you control are the proxy variables that Linux and macOS derive from enterprise.network, and the lifecycle offers no supported way to set the variable that a destination's token_env, bearer_env or {env: NAME} header names. A reference that cannot be resolved fails config validation, so ensure refuses the config. Splunk HEC always needs token_env. Use destinations that need no credential from the environment, such as a JSONL file that your log agent forwards.
• The gateway runs in a sandbox. On Linux it can write only inside /var/lib/defenseclaw and /var/log/defenseclaw, so a jsonl file destination must use a path there. Your log agent can collect the file from there.