The Defend-O-Tron is a small, silent appliance that sits between your internet connection and your network. It watches the traffic that passes through it, looks for attacks, and blocks the attackers before they reach your firewall. Below is what it gives you, and where to find each part in the web interface.
The Defend-O-Tron goes between your ISP equipment and your router. Traffic passes through it in both directions without changes, and it has no address on that path, so attackers see your existing firewall, not the appliance. There’s no software to install on anything else and no agents on your computers.
If something ever doesn’t feel right, unplug the Defend-O-Tron and connect your router to the ISP equipment the way it used to be. You’re back to your original setup in seconds.
Where to find it: cabling is covered in the Installation Guide.
The traffic between your ISP and your router is inspected as it passes. Suricata recognizes known attack patterns from its rule sets. CrowdSec decides whether to ban the source, and for how long. The Defend-O-Tron’s firewall then blocks the banned address.
Suricata’s rules are updated every week, and so are CrowdSec’s parsers and scenarios. You choose which rule sets fit your site, for example industrial control or IoT devices.
Where to find it: Threat activity → Dashboard shows what is being blocked (Dashboard). Detection → Rules chooses the rule sets (Detection Rules). The Honeypot page explains how scans are caught.
The Defend-O-Tron takes part in the CrowdSec community. It reports the attackers it bans, and in return it downloads the community blocklist every 2 hours. When enough reports about an address agree, CrowdSec adds it to that list, and every device that uses the list blocks it. So the address that probed you may already be blocked on the device before it reaches you.
The device sends a report to CrowdSec after each ban. Each report carries:
CrowdSec also receives usage figures from the device: the CrowdSec and bouncer versions, the operating system, the log sources, the installed parsers and scenarios, and how many packets the bouncers dropped.
CrowdSec’s privacy policy covers how it uses this information.
Where to find it: the dashboard’s totals show how many addresses the community blocklist holds (Dashboard).
Optional but recommended: point your network’s DNS at the Defend-O-Tron, and AdGuard Home filters every lookup. It blocks ads, trackers, phishing and malware sites and, if you want, whole categories of services. It sends the lookups it doesn’t answer itself to public resolvers over encrypted DNS. You also see, for the first time, what your network is asking for.
Where to find it: Detection → DNS filtering (DNS Filter). The guide Use the Defend-O-Tron for DNS shows how to point your network at it.
Most security appliances detect attacks. Far fewer can prove they did, in a way an auditor will accept months or years later. The Defend-O-Tron records its events and threat decisions as they happen. Every day it signs a manifest of the day’s logs with an Ed25519 key, and an external Time-Stamp Authority timestamps the signature. When an auditor asks for proof of, say, last quarter, you give them one signed ZIP, which they can check without the device.
This is the kind of capability you’d typically pay extra for as a SIEM add-on on Cisco, Fortinet or Sophos. On the Defend-O-Tron it’s built in and runs automatically. NIS2 Article 21, SOC 2, ISO 27001 and Cyber Essentials draw on the same kind of evidence.
Where to find it: Detection → Audit evidence in the web interface. Compliance Reporting explains what the evidence covers and how to make an evidence pack.
The device checks for new firmware every week, and shows a banner when a version is offered. Click Stage to download it, then Apply, and restart when it suits you.
The firmware you had before stays on the device, so you can roll back if anything feels off after an update. The firmware the device shipped with is always kept as a last-resort recovery point.
Where to find it: Device → Firmware (Firmware Update).
Forward syslog from your other firewalls, routers, servers and web servers to the Defend-O-Tron, and CrowdSec turns the attacks it finds in them into bans that the device enforces. You catch attacks that hit somewhere else in your network, and block them at the edge.
The device understands Linux system and SSH logs, iptables and nftables logs, NGINX and Traefik, UniFi gateways, MikroTik, and Windows Firewall, among others. You can add CrowdSec parsers for more, such as pfSense or Apache.
Where to find it: Log Ingress, and the guide Send Logs to the Defend-O-Tron.
Run your own firewalls, reverse proxies or web servers? Connect them to the Defend-O-Tron’s CrowdSec Local API, and they enforce the same bans as the device, each on its own traffic.
Where to find it: CrowdSec API, with setups for Linux nftables and iptables, NGINX, Traefik, MikroTik and pfSense, and the guide Connect Another System to the Block List.
Sign up for a free CrowdSec account and enroll the device to see its alerts in CrowdSec’s console, with more context about each attacker, and to manage bans from there.
The appliance works fully without it.
Where to find it: enroll the device in Device → Terminal with
sudo cscli console enroll <token>. The console is at app.crowdsec.net.
Manage everything from a browser, with no special software. The built-in web interface covers the device and its services, logs and monitoring, threat activity, detection rules, the firewall, DNS filtering, audit evidence, firmware and software updates, backups, the management port, certificates, remote support, accounts, and a terminal.
The interface has a dark and a light theme. It follows your browser’s preference until you choose one. The built-in terminal saves you an SSH client.
Where to find it: Admin Interface covers every page.
Both run the same firmware and the same web interface.
Where to find it: Hardware Specifications, and Open Source Hardware for the V100’s schematics.
When you need help, open a support session from Device → Remote support, or with the tech-support command. The device connects to Awesome-O support through a WireGuard tunnel with new keys for each session, and the support engineer gets full administrator access to the device until you end the session with one click. A session is never open unless you opened it.
Where to find it: Remote Support, which also explains what Awesome-O receives during a session.