Warden docs

Documentation

How Warden works: the agents, cases and response plans, the security model, Bedrock access, install and licensing.

Overview

What Warden is, what its agents do in your AWS account, and how one passkey signature ends an attack.
Concepts

Estates, findings, cases and actors, the agents, the event lane, response plans, the console, the footprint and release keys.
Security model

What Warden can touch, why no model can act, what one passkey signature does, and what leaves your account.
Licensing

Watch is free and Defend is a paid plan, issued by request. The WDL1 file format, offline verification, and renewal.
Install

The one-line installer, what setup creates in your account, what it costs to run, and how to uninstall.
Install checks

The steps AWS makes you do yourself, each with a read-only Check button, and the reference for every install step behind them.
Onboarding

What the first keeper sees after setup. Five screens with their defaults chosen, then one passkey signature that sets all of it.
Settings

The console's Settings page, section by section, and how a signed change takes effect. Includes how to verify a webhook.
Recovery

Getting the console back, a new temporary password for the door, and signing a record when no console can be reached.
Bedrock access

Which Amazon Bedrock model access to enable for each agent role, how to enable it, what it costs, and what happens without it.
How Warden finds vulnerabilities

The sources it reads, what it knows about each running thing, which source can answer for which software, how it matches, how it ranks, and what to turn on in AWS with prices.
The advisory feed

What an install downloads, how often, who signs it, and what each host can see when it does.
FAQ

Short answers to the questions people ask first.