The Defend-O-Tron fits a wide range of sites. The scenarios below are the ones we see most often. Pick the one that matches your setup best. If more than one applies, the device covers them all at once.
Each scenario has three parts: a checklist (does this describe you?), the usual setup, and what the Defend-O-Tron adds. In every scenario the device sits in the same place: between your ISP equipment and your firewall or router.
A single business location with servers on site (file, mail, web, a business application) and one or more services reachable from the internet. Most small and medium businesses fit here.

If two or more apply, this is your scenario.
- One Defend-O-Tron between the ISP modem and your firewall or router.
- Your servers work as before. The device passes legitimate traffic in both directions without changes.
- Optional: forward your web server, mail server or VPN logs to the device, so CrowdSec can find attacks in them and ban the attackers. See Log Ingress.
- It catches port scans, brute-force attempts and other probes before they reach your firewall.
- It makes the tamper-evident audit evidence your auditor and insurer want to see. See Compliance Reporting.
- One device covers your whole site, with no agents on your servers.
A headquarters and one or more branch offices, usually connected by VPN. Common in retail chains, multi-site healthcare, regional legal and accounting practices, and franchises.

- One Defend-O-Tron at each branch, and one at headquarters, each between that site’s ISP equipment and its firewall or router.
- Each branch’s SD-WAN equipment stays in place. The Defend-O-Tron does not change how it works.
- To see all sites in one place, enroll each device in the same free CrowdSec Console account. You can also connect your own tools to each device’s CrowdSec API.
- Each site reports the attackers it bans to the CrowdSec community, and every site downloads the community blocklist every 2 hours. An address that enough reports agree on is blocked at all your sites. A ban at one site does not reach your other sites on its own. In the CrowdSec Console you can manage bans for all your enrolled devices in one place.
- Each site’s audit evidence is signed separately and can be exported on its own, which keeps multi-site compliance reporting simple.
- Each site stands alone: if one Defend-O-Tron goes down, the others keep working.
¶ Industrial Control Systems (PLC and SCADA)
Manufacturing plants, water and wastewater treatment, energy distribution, building automation: any site where programmable logic controllers (PLCs), HMIs or SCADA systems sit behind an internet connection. Unlike the other scenarios on this page, this one comes with a government advisory.

In April 2026, the FBI, CISA, NSA, EPA, DOE, U.S. Cyber Command and the Treasury jointly warned that Iranian-affiliated attackers were exploiting internet-facing PLCs, Rockwell Automation / Allen-Bradley at first and later other makers, at government facilities, water utilities and energy operators. It followed the 2023 campaign in which at least 75 Unitronics PLCs were compromised, 34 of them at U.S. water utilities, by attackers who simply connected to controllers left on the internet with the factory default password.
The exposure is not small. Internet scanning firm Censys counted 5,219 Rockwell Automation / Allen-Bradley devices answering on EtherNet/IP from the internet, nearly three-quarters of them in the United States. Dragos counts 3,300 industrial organizations hit by ransomware in its latest year in review.
If two or more apply, this is your scenario.
- One Defend-O-Tron between the ISP equipment and the plant firewall, the same place as in the Single Office scenario.
- Turn on the Industrial site rule set on Detection → Rules. See Detection Rules.
- It covers what crosses your internet link: remote-access paths, vendor VPN endpoints, and any control equipment that is more exposed than the network drawing suggests.
- With the Industrial site rule set on, it watches your internet link for industrial protocols: EtherNet/IP (44818), Modbus (502), S7comm (102), DNP3 (20000), BACnet (47808), IEC 60870-5-104 (2404), OPC UA (4840) and Niagara Fox (1911).
- A probe of these ports from the internet raises an alert, so you know your equipment is being looked for.
- A device on your site that connects out to one of these ports is blocked from that address, and you get an alert. It can be a compromised device, or a vendor’s remote-access tool nobody knew about.
- The honeypot and CrowdSec ban the scanners that sweep the other ports attackers try first.
- Nothing is installed on any controller. There is no security agent for a PLC, and this device doesn’t need one.
- It makes the signed evidence that NIS2 (manufacturing, water and energy are all in scope) and IEC 62443 audits ask for. See Compliance Reporting.
- It comes out in seconds. If it ever gets in the way, reconnect your firewall to the ISP equipment and the link is exactly as it was.
To be clear about the limits:
- It does not replace taking controllers off the public internet. CISA’s first advice in each of these advisories is to disconnect PLCs from the internet and change default passwords. Do that first. This device defends what remains.
- It is not a deep industrial protocol analyser. It detects industrial protocols crossing your internet link, known exploit signatures, and IT-borne threats. Purpose-built OT monitoring platforms model your physical process and alert on abnormal control values. That is a different product at a very different price.
- It sees only your internet link. It does not see traffic inside your plant. Keep your control network separate from your office network too.
- It is an inline device. Put it on a UPS.
Edge IoT sites: environmental sensors, industrial equipment, telemetry uplinks, distributed monitoring. Often in places with limited power, unreliable connections, and no IT staff on site.

- One Defend-O-Tron at the site’s internet uplink. See Requirements for each model’s power.
- For management when the network is down: a monitor and keyboard, or on the V100 its serial console. See Installation.
- Optional: send your IoT gateway’s syslog to the device, so CrowdSec can find attacks in it.
- It catches probes against IoT protocols (TFTP, NetBIOS, SNMP: see the Honeypot page) before they turn into a compromise.
- Its protection runs on the device. It needs no cloud service to block attacks. The CrowdSec community blocklist adds to it when the connection is up.
A freelancer, sole proprietor, or one-person business (lawyer, accountant, healthcare provider, consultant, contractor) working from home or a small home office. Often handles confidential client data with no IT staff.
- One Defend-O-Tron between your ISP modem and your home router. This is the simplest setup.
- No software on your computers or phones. Every device on your network is protected.
- Optional: use the AdGuard DNS filter to block phishing sites. See DNS Filter.
- Protection without complexity: install it, finish the Setup wizard, and it runs by itself.
- Tamper-evident audit evidence, useful for compliance questions from clients in regulated sectors (healthcare, legal, financial advice) and for cyber-insurance applications.
- An easy way back: if anything ever feels wrong, reconnect your router to the modem and you’re back to your original setup in seconds.
An MSP, MSSP or IT consultancy that supports many small business clients. Each client site is usually a Single Office scenario. The MSP’s job is to install, monitor and report across all of them.
- One Defend-O-Tron at each client site, in the same place as in the Single Office scenario.
- See all sites in one place: enroll each device in your CrowdSec Console account, or connect your own tools to each device’s CrowdSec API.
- The same setup at every client: the same Setup wizard steps, the same way of installing the Root CA, the same administrator accounts and roles.
- Reach each Defend-O-Tron’s web interface through your own remote access (VPN, jump host, RMM). The device’s Remote Support is a session the customer opens for Awesome-O’s support team, not a remote-management path for the MSP.
- Strong protection for each client at a price that fits small business budgets, without a SIEM seat for each client.
- Signed audit evidence for each client (NIS2, SOC 2, ISO 27001), ready for that client’s auditor with one command. An easy compliance deliverable.
- Every client device reports to the CrowdSec community and uses its blocklist, so an attacker that enough reports agree on is blocked at every client.
- One thing to learn: the same web interface at every site.
The Defend-O-Tron works across scenarios. Many sites combine two or three of the above, for example a small business whose owner also works from home. When in doubt, start with the Single Office scenario.
For the full list of features, see System Features. For what you need before you order or install, see Requirements.