Dashboard
Witen dashboard guide
Add sites and servers, see what they report and block, set policies and trusted networks, download software, and manage your plan.
Add your first site or server
- Register, verify your email address, and sign in.
- Choose a plan, or start with the free capacity.
- Open Add Protection and create your fleet when asked. One fleet credential stands for your account's ownership and limits.
- Choose Server or VPS, WordPress, or Matomo.
- Follow that product's guide to create and use a one-time enrollment token. The Matomo plugin supplies its installation ID itself.
- Setup is done when the asset's first report shows under Protected Assets.
Read the Operations dashboard
Operations is your landing page. Its 24-hour summary shows accepted evidence, events reported with a local block reason, and unique source addresses. Follow the Activity link for the full graph and rankings.
- Fleet contact counts enrolled installations that reported in the last 24 hours.
- Receipt API available means the collector can serve receipts. It does not mean every actuator has synced its decisions.
- Synchronized enforcement counts real decision receipts, separately from ordinary block reports.
- Fleet health alerts are compromise and attack-surge observations, not a list of every routine block.
- CVE exposure comes from your installed plugin inventory. Confirm it against the affected software before you fix anything.
Investigate Activity
Pick a range from 1 hour to 30 days: 1h, 6h, 24h, 7d, or 30d. Activity shows your account's observations and top sources. New data appears once its five-minute reporting bucket closes.
Evidence events
Accepted security observations. One source address or request sequence can produce several.
Reported blocked
Events with a local block reason. A report, not receipt proof.
Unique attacker addresses
Distinct source addresses seen in hostile context. Not a permanent verdict that each one is malicious.
- Start at 24h and compare each number with the 24 hours before it.
- Switch to 1h or 6h to pin down a fresh spike; use 7d or 30d to tell it apart from recurring background traffic.
- Use Top categories for the behavior, Most active assets for where it hit, and Top sources to separate SSH, web, and plugin views.
- For examples, go back to Operations and recent events; for deeper host analysis, use Warden's local evidence.
Manage Protected Assets
Protected Assets lists each enrolled installation with its source type, display name, tags, software version, configuration version, last report, and reporting status. Sort by hostname, source, software version, or configuration version to spot drift.
- Reporting: reported within the expected window.
- Delayed: reports are later than expected; check the local service and network.
- Offline: the last report is old enough to need your attention.
- Awaiting first report: enrolled, but no event report has arrived yet.
Asset detail controls
Depending on plan and source, an asset can offer display-name and tag editing, reporting availability, a blocklist profile choice, and .htaccess backup and restore history where supported. A restore changes the live site, so review the chosen backup and the current web-server setup before you request one.
Verify decisions with receipts
A decision receipt records what the enforcing component, the actuator, did with a decision. Each shows its subject, action, scope, explanation, confidence, evidence count, actuator, lifecycle state, start, and expiry.
- Pending: issued, not yet confirmed as applied.
- Applied: the named actuator reported success.
- Failed: the actuator tried and reported failure; investigate on the host.
- Rolled back: an applied decision was reversed.
- Expired: its blocking period ended.
Manage configurations and policy groups
Configurations
Configs shows each enrolled reporter's configuration and version history. It should never expose installation credentials. Review changes before applying them to a production host.
Policy groups
- Create a group with a clear purpose, such as Production SSH or Public WordPress.
- Assign only assets you own. Each asset belongs to one policy group.
- Enter SSH and HTTP thresholds, windows, and ban duration within the allowed limits.
- Save a new draft version; saved versions never change.
- Review near misses and the seven-day conservative recommendations.
- Apply the version you want. Saving a draft never activates it.
Share trusted networks safely
The account allowlist takes one exact IPv4 or IPv6 address or CIDR per entry and sends it to your Warden and WordPress protections. Listed addresses are left out of correlation and never blocked.
- Use the label to say why an entry is trusted.
- Prefer one exact address to a broad CIDR.
- Add recovery and administration addresses before you tighten blocking.
- Behind a proxy, check the client address so you don't allow the proxy by mistake.
- Remove stale entries regularly.
Downloads and billing
Downloads
Downloads, behind sign-in, lists your products with exact version, platform and libc, file size, and SHA-256 checksum. Pick Warden glibc, musl, legacy 386, or Alpine APK, or a WordPress or Matomo plugin ZIP, to match the target.
Billing
Billing shows your plan and protected-asset capacity. After a plan change, setup usually finishes within seconds and the page updates its status itself. Contact support if it is still incomplete after a few minutes.
- Before a downgrade, remove or plan for any assets beyond the new capacity.
- Manage payment methods and your subscription in the billing portal.
- Confirm a newly bought slot shows as available before relying on it.
- Contact support for more capacity than the published plans offer.
Troubleshooting and recovery
The dashboard asks you to create a fleet
Your account has no usable fleet yet. Complete Add Protection. If you already created one, check that you're signed in to the same verified account and that your plan finished syncing.
An asset stops reporting
WordPress reports depend on site traffic and background jobs. A quiet site shows “No recent report”; the gap doesn't mean the site or its local protection is offline. Always-running agents such as Warden get a tighter check.
- Check the local service or plugin maintenance run and the system clock.
- Check its installation credential is present and readable.
- Check DNS, TLS, and outbound connections to the collector.
- A collector outage doesn't stop Warden blocking locally.
Activity is empty
- Try 7d or 30d; a quiet window is normal.
- Check Protected Assets for recent reports.
- Allow up to five minutes for the newest five-minute bucket to close.
- If Recent Events has data but Activity doesn't, send support the selected window and time.
Understand Outcomes
Outcomes ranks attacking addresses from hostile observations in your account. “Active verified blocks” is narrower: it counts only applied, unexpired decision receipts synced by an actuator. Ordinary event reports never pass as proof of blocking.
Contact support safely
- Open Support in the dashboard navigation.
- Include the protected asset name, UTC time, Warden version, and any relevant receipt IDs.
- Never send API keys, enrollment tokens, passwords, or private raw logs by email.
Customer activity is unavailable
The analytics service couldn't answer. Local protection is still on. Operations, asset state, and local Warden tools may still work while analytics recovers.