Network traffic and DNS
Flow exports, DNS query logs, DNS zones and DHCP leases
Thirty-one agents that read your firewall, VPN, Wi-Fi, identity, backup, patch, ticket and cloud-bill exports on your own computer and hand your IT team a worklist, while every change to a live system stays one named person's click.
Flow exports, DNS query logs, DNS zones and DHCP leases
Call-detail and call-quality exports from your phone system or SBC
LLM usage logs and API request logs: repeated prompts, oversized models, retry spend
Firewall rules, remote-access logs, Wi-Fi controllers, switch ports and VLANs
Sign-in logs, MFA coverage, admin roles, directory hygiene and the email gateway
CMDB against what is seen, patches, endpoint protection, mobile devices, software licences and printers
Backup results, restore tests, uptime and incidents, change calendar, ticket SLAs and log retention
Cloud bills, IT contracts and renewals, telecom bills
All 31 agents set up on your exports, with one training session for the team
All 31 agents for up to 10 client companies, with export mapping per client and a runbook for your engineers
Support after setup: $250 a month per package, $750 a month for the whole IT team, $2,000 a month for a partner rollout; covers new export layouts, setting changes and a review call.
Reads files your IT team exports; it does not log in to firewalls, controllers, identity providers, device management or cloud consoles.
Export layouts were written from knowledge of common exports and are confirmed on your own files during setup.
Thresholds such as days to patch, retention days or the number of top admins are working defaults you set; they are not a vendor rule, a standard or a security guarantee.
A finding is a lead for a person to confirm, not proof of an attack, a breach or a saving.
Not legal, compliance or security-certification advice.
Report pages in eight more languages were translated by Claude and are not yet reviewed by native speakers.
Your exports stay on your machine, and names, sign-in names, e-mail addresses, phone numbers and client addresses are masked before anything reaches the AI model. The agents never change a firewall, switch, controller, DNS zone, directory, device or cloud account, and never send, cancel or pay anything: each change is a draft that one named person approves and then makes.
Any-to-any allows, risky ports open from the internet, shadowed, duplicate, expired, unused and unlogged rules
Risky ports reached from outside, cleartext protocols, large uploads at night, port scans and top talkers
Leavers still connecting, one account in two countries at once, failed bursts, shared accounts, old clients
Tunnelling signals, clients using outside resolvers, blocked lookups, NXDOMAIN-heavy clients
Names pointing at cloud services that may be gone (takeover risk), CNAME conflicts, private addresses in public zones
Rogue access points, WEP, TKIP and open networks, offline and outdated access points, bad channels
Trunks carrying every VLAN, user ports in VLAN 1, half duplex, CRC errors, unused ports
Rogue DHCP servers, address conflicts, nearly full scopes, devices missing from the asset list
Low MOS, loss and jitter, one-way audio, sites, trunks and hours where poor calls cluster
Password spraying, a success right after many failures, impossible travel, legacy protocols
Admins without phishing-resistant MFA, accounts with none, exclusions, SMS-only accounts
Too many top admins, guests with admin roles, break-glass use, standing roles, admins with mail
Password-not-required flags, group loops, stale and unsupported computers, ownerless groups
Phishing released from quarantine, allow-listed senders that sent malware, mailboxes sending spam
Retired devices still seen, devices with no record, duplicate serials, ghost records, warranties
Critical updates past your days to patch, unsupported systems, failed installs, silent devices
Devices with no agent, protection or tamper protection off, passive mode, old high alerts
Jailbroken phones, devices of leavers, no passcode or encryption, old operating systems
Prohibited software, more installs than licences, outdated versions, licences nobody uses
Printers nobody uses, cost per page, colour share, leases ending
Critical systems no job covers, missed recovery points, repeated failures, no offsite copy
Systems never tested, failed tests not repeated, restores slower than the RTO, a test calendar
Services below target, major incidents with no review, repeat failures, slow responses
Changes inside a freeze, no approval or back-out plan, overlapping changes on one system
Tickets past their targets by priority, unassigned and parked tickets, teams with many breaches
Logs kept shorter than policy, silent sources, systems sending no logs, volume jumps
Spend in regions you do not use, month-on-month jumps, untagged spend, commitments ending
Notice deadlines for auto-renewals, price rises above your cap, vendors paid without a contract
Lines billed for leavers, unused lines, roaming and premium charges, oversized plans
The same prompt sent again and again, large models for tiny jobs, answers cut off, untagged spend
Retries that cannot succeed, retry storms, 429s retried too early, tokens spent on retries
Each one does one job, on your computer, from a file you export. Nothing changes on a live device, firewall, directory or cloud account until a named person clicks.
Measured in the final pass, 19 Nov 2026
On fictional test data, 19 Nov 2026. Every planted problem was found and nothing else was reported. The clean set first showed 2 false findings (one host 'carrying most of the bytes' in an export with only 4 hosts); that check now needs at least 5 hosts. Not yet measured on a customer's own exports. The test files and the checks were written by the same team, so these numbers show the rules do what they say. How often they are right on your own files is measured at your setup.
git clone https://github.com/fpavia111-creator/fairwire-agents
cd fairwire-agents
npm install
node packages/fairwire-firewall-rules/bin/fairwire-firewall-rules.js demo
Open source, MIT licence, on GitHub: fpavia111-creator/fairwire-agents. Needs Node.js 20 or later. The demo runs on made-up files and needs no network and no setup.
| Source | What ran and what it found | Licence |
|---|---|---|
| UCI incident management event log (ServiceNow) 2026-11-19 | Ticket SLA read 24,918 real incidents: 57 teams flagged for missed resolution targets, 56 of them also flagged by the instance's own SLA field; the first run counted 1,556 closed tickets as open (fixed). | CC BY 4.0 |
| BPI Challenge 2014 change records (Rabobank, HP Service Manager) 2026-11-19 | Change Calendar read 18,000 changes on 30,275 rows: approval, back-out and test checks skipped because the export has no such columns; overlaps fell from 38,564 to 2,419 once months-long planning windows were left out (not verified with the change board). | 4TU.ResearchData General Terms of Use |
| IANA DNS root zone 2026-11-19 | DNS Records read all 25,020 records of the real master file: 0 findings, none expected. | Published by IANA for public download; no licence stated |
| endoflife.date (Windows, Windows Server) 2026-11-19 | The dated end-of-support list flags 43 of 53 ended Windows releases and no supported one (it flagged 3 supported LTSC releases before the fix). | MIT |
Public, lawful files only; no private data was used. The files are not copied into the repository: a script there downloads them again.
| Package | What a person reviews and decides |
|---|---|
| Network traffic and DNS | Whether a flagged port, upload, scan or DNS name is expected; any firewall, DNS or DHCP change is made by the network owner. |
| Call quality | Whether poor calls are the provider's fault before the drafted ticket is sent; codec and route changes stay with the voice team. |
| AI usage and retries | Whether repeated prompts or large models are deliberate, and the price table used for costs; app and gateway changes stay with the owner. |
| Firewall, VPN and Wi-Fi | Each drafted change request (a rule, port, VLAN or network); a named person approves it and makes the change on the device. |
| Identity and admins | Whether a flagged sign-in or role is legitimate before any account is blocked or role removed; the identity owner makes every change. |
| Devices and software | Which devices to upgrade, wipe or retire and which installs to remove; licence counts are checked against the contracts. |
| Backups and operations | Restore priorities, change board decisions, ticket escalations and retention changes; the agents start, stop and delete nothing. |
| IT spend | Every cancellation, notice letter and commitment purchase; the agents draft lists and letters, a person sends or buys. |
| Whole IT team | All of the above, plus the thresholds in the settings files, which are working defaults until your team sets them. |
| For MSPs and IT firms | Each client's settings and export mapping, and every client-facing note before it is sent. |
| System | Report or export | Status |
|---|---|---|
| Palo Alto Networks PAN-OS | Security policy rules exported to CSV | Not yet tested on a real export |
| Fortinet FortiGate | Firewall policy list exported to CSV | Not yet tested on a real export |
| Microsoft Entra ID | Sign-in logs downloaded as CSV | Not yet tested on a real export |
| Okta | System Log exported as CSV | Not yet tested on a real export |
| Microsoft Entra ID | User registration details (authentication methods) | Not yet tested on a real export |
| Amazon Web Services | Cost and Usage Report, CSV | Not yet tested on a real export |
| Microsoft Azure | Cost details export, CSV | Not yet tested on a real export |
| Google Cloud | Billing report downloaded as CSV | Not yet tested on a real export |
| Veeam Backup & Replication | Job session history exported to CSV | Not yet tested on a real export |
| Microsoft Intune | All devices list exported to CSV | Not yet tested on a real export |
| Microsoft Defender for Endpoint | Device inventory exported to CSV | Not yet tested on a real export |
| Windows Server DHCP | Address leases exported from the DHCP console | Not yet tested on a real export |
| ServiceNow | Incident list exported to CSV | Not yet tested on a real export |
| ServiceNow | Incident fields as in the public UCI audit log (number, incident_state, priority, opened_at, resolved_at, assignment_group) | Tested on a public sample |
| Jira Service Management | Issue search exported to CSV | Not yet tested on a real export |
| HP Service Manager | Change records (BPI Challenge 2014) | Tested on a public sample |
| BIND, Windows DNS, zone transfer | DNS zone (master) file | Tested on a public sample |
No layout has yet been tested on a customer's own export. Every setup starts by confirming the layout on your files, and any column can be mapped by hand.
A Fairwire tool reads the exported file on your own computer and returns a summary and a list of findings. Before that result leaves the computer, names, sign-in names, e-mail addresses, phone numbers, IMEIs and the public addresses people connected from are replaced with stable pseudonyms (16 of the 31 agents read such fields; of 262 personal values in the test files, none reached the model). Dates, counts, amounts, codes, device names and internal addresses are sent in clear; strict mode also masks host names and every address. Free-text fields such as rule descriptions or ticket titles are scrubbed of e-mail addresses, phone numbers and names seen elsewhere in the file, but other personal details typed into them can get through. The result goes to whichever AI model your assistant uses; for regulated data, use a local model or one covered by your own agreements.
Thresholds such as days to patch, retention days, SLA targets, call-quality limits and the top-admin cap are working defaults in each agent's settings, and a customer changes them in a settings file without touching code. Facts that come from vendors are dated and kept in one place, fairwire-core: the Windows end-of-support list (as of 19 Nov 2026, checked against endoflife.date), risky inbound ports, cleartext protocols, cloud host names used for takeover checks, and the 14 vendor export layouts the agents recognise. A customer can override each of them in settings or in fairwire-sources.json; Mythos Machines updates the defaults in new releases, and support covers export layouts that a vendor changes.
We send the list of reports by name. You export them from the systems you already use; nothing is connected.
Over a shared screen: the checks are installed, your columns are matched, and your own rules and dates are set.
The checks run on your files. We go through the worklist with you, and every flagged row is a person's call.
You run them whenever you like. Support keeps the dated rules and the export layouts current.
A fixed scope and a fixed price, agreed before any work starts. Your files stay on your computer the whole time.
Written by the check itself on made-up files. Every person, business and number is invented.
Firewall rule review All samples