Docs

FAQ

Short answers to the questions people ask first.

On this page

What do I need to run it?

One AWS account, an EKS cluster at Kubernetes 1.30 or later with access entries, a domain you control for the console and the signing page, and any passkey. Setup needs an administrator of the account once. For the agents, enable Bedrock model access; without it Warden runs rules-only. See Install.

How do I install it?

Warden is in an early access preview: leave your email and access arrives by e-mail. Then run curl -fsSL https://wardensec.ai/install | sh, then warden setup. Setup prints what it creates and what it costs, then creates it. You become the first keeper in your browser with your passkey, and add the Watch license from this site.

What does it cost?

The license and the AWS bill are separate. The Watch license is free and lasts 365 days. Defend is a paid plan, issued by request, and nothing is charged for it yet.

Running Warden is billed by AWS, in your account, for what it creates there, including the Bedrock tokens the agents use under hard daily ceilings. Setup prints a dollar line for each item before it creates anything. See What it costs to run.

Does it change anything in my accounts?

Not in Watch, which is the default. Watch reads through read-only roles. Defend acts only on a response plan a keeper has signed with a passkey, and every step it takes is dry-run first, time-boxed and undoable.

What do the agents do?

Triage weighs every new finding. Investigate works every case that matters through CloudTrail, and through EKS audit and VPC flow logs where you have them. Hunt looks for what no rule names, including swarms of identities that copy themselves. Harden proposes ranked fixes. They propose; code checks; a person signs. See Concepts.

Can an attacker talk the agent into something?

No model can act, suppress a finding or excuse an actor. Models never see the raw names and tags an attacker writes, and a response plan is built by code from the case, never from chat text. Signing needs a keeper’s passkey. See Why the agent cannot be talked into anything.

How fast does it react?

The event lane reads write calls as AWS delivers them and runs a five-minute cycle. A case, its status and the request for a response plan exist within that cycle, before any model has answered. A scan every 15 minutes and a full read every hour run alongside it.

Can I stop an attack from the chat?

Yes. Type “block them” on a case and the response plan appears in the chat with its steps. Press Sign and confirm with your passkey. The plan is the same one the case page shows.

Which clouds does it cover?

AWS accounts and Kubernetes on EKS.

Where does it run?

Inside your own EKS cluster and AWS account. The agents call Bedrock in your account. There is no hosted service on our side that reads your estate.

Does any data leave my account?

Nothing goes to us. Notification mail goes through your account’s own notice topic to the addresses you set, and Slack notices go to the webhook you give; both carry code words and counts, never names from your estate. See What leaves your account.

Does it phone home?

There is no telemetry, no license server, and no request that carries anything about the install beyond what any download shows: the address it comes from, which reveals the AWS region, and its time. A license is a signed file that Warden verifies offline when it starts.

An install may download public, signed data that every install downloads identically (the advisory feed) on a schedule a keeper chose. A “Check now” also shows that someone asked at that minute. Releases and rule packs are downloaded only when a person asks. See The advisory feed for what each host can see.

How do I see what it installed?

The console’s Footprint page, or warden footprint, lists every resource by place, why it exists and what it costs a month. Everything in Kubernetes is in the wardensec namespace; everything in AWS is in stacks named wardensec-<part>.

How do I uninstall it?

From the console’s Uninstall page. It lists what goes and what stays, undoes any Defend holds first, and asks a keeper to sign. warden uninstall then removes everything except the ledger and proves what is left. See Uninstall.

How many installs do I need?

One per estate. An estate is the AWS accounts and EKS clusters one hub watches: a single account, or an organization’s accounts. One hub watches the whole estate, and each estate needs its own license.

Which passkeys can I use?

Any passkey: one saved in a password manager such as 1Password, on a phone or laptop, or on a security key. No hardware key is required anywhere. Each passkey’s class is recorded and shown wherever a keeper appears, and requiring security keys is a signed option if you choose it.

What happens if I retire a license?

It is marked as retired in the dashboard. Because a license is checked offline, the file itself keeps working until it expires.

How do I check a license file?

Paste it into the verify page. The check runs in your browser against our published public keys. Nothing is uploaded.

How do I sign in to this site?

With a passkey. There are no passwords. When you sign up you also get eight one-time recovery codes. Keep them somewhere safe.

How do I report a security problem?

Email support@wardensec.ai. See Security.