Let's talk
IT teams and managed service providers

Fairwire

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.

A network rack with blinking ports, Wi-Fi waves and a clipboard with a check

Engagements

$1,500 · One company

Network traffic and DNS

Flow exports, DNS query logs, DNS zones and DHCP leases

$1,500 · One company

Call quality

Call-detail and call-quality exports from your phone system or SBC

$1,500 · One company

AI usage and retries

LLM usage logs and API request logs: repeated prompts, oversized models, retry spend

$2,500 · One company

Firewall, VPN and Wi-Fi

Firewall rules, remote-access logs, Wi-Fi controllers, switch ports and VLANs

$3,000 · One company

Identity and admins

Sign-in logs, MFA coverage, admin roles, directory hygiene and the email gateway

$3,000 · One company

Devices and software

CMDB against what is seen, patches, endpoint protection, mobile devices, software licences and printers

$2,500 · One company

Backups and operations

Backup results, restore tests, uptime and incidents, change calendar, ticket SLAs and log retention

$2,000 · One company

IT spend

Cloud bills, IT contracts and renewals, telecom bills

$9,500 · One company

Whole IT team

All 31 agents set up on your exports, with one training session for the team

$15,000 · Partner rollout

For MSPs and IT firms

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.

Thirty-one checks.

Network and edge
Network and edge

Firewall rules

Any-to-any allows, risky ports open from the internet, shadowed, duplicate, expired, unused and unlogged rules

Network and edge

Network flows

Risky ports reached from outside, cleartext protocols, large uploads at night, port scans and top talkers

Network and edge

VPN and remote access

Leavers still connecting, one account in two countries at once, failed bursts, shared accounts, old clients

Network and edge

DNS queries

Tunnelling signals, clients using outside resolvers, blocked lookups, NXDOMAIN-heavy clients

Network and edge

DNS zones

Names pointing at cloud services that may be gone (takeover risk), CNAME conflicts, private addresses in public zones

Network and edge

Wi-Fi

Rogue access points, WEP, TKIP and open networks, offline and outdated access points, bad channels

Network and edge

Switch ports and VLANs

Trunks carrying every VLAN, user ports in VLAN 1, half duplex, CRC errors, unused ports

Network and edge

DHCP leases

Rogue DHCP servers, address conflicts, nearly full scopes, devices missing from the asset list

Network and edge

Call quality

Low MOS, loss and jitter, one-way audio, sites, trunks and hours where poor calls cluster

Identity, mail and admins
Identity, mail and admins

Sign-in logs

Password spraying, a success right after many failures, impossible travel, legacy protocols

Identity, mail and admins

MFA coverage

Admins without phishing-resistant MFA, accounts with none, exclusions, SMS-only accounts

Identity, mail and admins

Admin roles

Too many top admins, guests with admin roles, break-glass use, standing roles, admins with mail

Identity, mail and admins

Directory hygiene

Password-not-required flags, group loops, stale and unsupported computers, ownerless groups

Identity, mail and admins

Email gateway

Phishing released from quarantine, allow-listed senders that sent malware, mailboxes sending spam

Devices and software
Devices and software

Assets against the CMDB

Retired devices still seen, devices with no record, duplicate serials, ghost records, warranties

Devices and software

Patch status

Critical updates past your days to patch, unsupported systems, failed installs, silent devices

Devices and software

Endpoint protection

Devices with no agent, protection or tamper protection off, passive mode, old high alerts

Devices and software

Mobile devices

Jailbroken phones, devices of leavers, no passcode or encryption, old operating systems

Devices and software

Software and licences

Prohibited software, more installs than licences, outdated versions, licences nobody uses

Devices and software

Printers

Printers nobody uses, cost per page, colour share, leases ending

Operations and resilience
Operations and resilience

Backups

Critical systems no job covers, missed recovery points, repeated failures, no offsite copy

Operations and resilience

Restore tests

Systems never tested, failed tests not repeated, restores slower than the RTO, a test calendar

Operations and resilience

Uptime and incidents

Services below target, major incidents with no review, repeat failures, slow responses

Operations and resilience

Change calendar

Changes inside a freeze, no approval or back-out plan, overlapping changes on one system

Operations and resilience

Ticket SLAs

Tickets past their targets by priority, unassigned and parked tickets, teams with many breaches

Operations and resilience

Log retention

Logs kept shorter than policy, silent sources, systems sending no logs, volume jumps

IT spend and AI usage
IT spend and AI usage

Cloud bills

Spend in regions you do not use, month-on-month jumps, untagged spend, commitments ending

IT spend and AI usage

IT contracts

Notice deadlines for auto-renewals, price rises above your cap, vendors paid without a contract

IT spend and AI usage

Telecom bills

Lines billed for leavers, unused lines, roaming and premium charges, oversized plans

IT spend and AI usage

AI usage

The same prompt sent again and again, large models for tiny jobs, answers cut off, untagged spend

IT spend and AI usage

Retries

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

Measured, not promised.

270 of 270planted problems found
0false alarms on 424 clean rows
66 of 66one-change tests caught
4public data sources run

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.

Run it yourself

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.

Common problems it finds

  • Firewall rules that open RDP or FTP to the internet, allow any to any, or never match because an earlier rule does
  • People who have left still connecting to the VPN, or still enrolled on company phones
  • Administrators without phishing-resistant MFA, and more top administrators than your cap
  • Critical systems with no recent good backup, no offsite copy, or no restore test on record
  • Devices on Windows releases past end of support, or missing critical updates past your deadline
  • Cloud spend in regions you do not use, untagged spend, and test machines running all month
  • Contracts that renew automatically within weeks, and vendors paid with no contract on file
  • DNS names pointing at cloud resources that may no longer exist (takeover risk)

Run on public data

SourceWhat ran and what it foundLicence
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.

What a person still decides

PackageWhat a person reviews and decides
Network traffic and DNSWhether a flagged port, upload, scan or DNS name is expected; any firewall, DNS or DHCP change is made by the network owner.
Call qualityWhether 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 retriesWhether 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-FiEach drafted change request (a rule, port, VLAN or network); a named person approves it and makes the change on the device.
Identity and adminsWhether a flagged sign-in or role is legitimate before any account is blocked or role removed; the identity owner makes every change.
Devices and softwareWhich devices to upgrade, wipe or retire and which installs to remove; licence counts are checked against the contracts.
Backups and operationsRestore priorities, change board decisions, ticket escalations and retention changes; the agents start, stop and delete nothing.
IT spendEvery cancellation, notice letter and commitment purchase; the agents draft lists and letters, a person sends or buys.
Whole IT teamAll of the above, plus the thresholds in the settings files, which are working defaults until your team sets them.
For MSPs and IT firmsEach client's settings and export mapping, and every client-facing note before it is sent.
Export formats (17): 3 tested on a real or public file, 14 not yet tested on a real export.
SystemReport or exportStatus
Palo Alto Networks PAN-OSSecurity policy rules exported to CSVNot yet tested on a real export
Fortinet FortiGateFirewall policy list exported to CSVNot yet tested on a real export
Microsoft Entra IDSign-in logs downloaded as CSVNot yet tested on a real export
OktaSystem Log exported as CSVNot yet tested on a real export
Microsoft Entra IDUser registration details (authentication methods)Not yet tested on a real export
Amazon Web ServicesCost and Usage Report, CSVNot yet tested on a real export
Microsoft AzureCost details export, CSVNot yet tested on a real export
Google CloudBilling report downloaded as CSVNot yet tested on a real export
Veeam Backup & ReplicationJob session history exported to CSVNot yet tested on a real export
Microsoft IntuneAll devices list exported to CSVNot yet tested on a real export
Microsoft Defender for EndpointDevice inventory exported to CSVNot yet tested on a real export
Windows Server DHCPAddress leases exported from the DHCP consoleNot yet tested on a real export
ServiceNowIncident list exported to CSVNot yet tested on a real export
ServiceNowIncident 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 ManagementIssue search exported to CSVNot yet tested on a real export
HP Service ManagerChange records (BPI Challenge 2014)Tested on a public sample
BIND, Windows DNS, zone transferDNS zone (master) fileTested 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.

Security

What reaches the AI model

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.

Support

Who keeps the rules current

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.

How a setup runs.

1

You export the files

We send the list of reports by name. You export them from the systems you already use; nothing is connected.

2

Setup on your computer

Over a shared screen: the checks are installed, your columns are matched, and your own rules and dates are set.

3

The first report

The checks run on your files. We go through the worklist with you, and every flagged row is a person's call.

4

After that

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.

A sample report.

Written by the check itself on made-up files. Every person, business and number is invented.

Firewall rule review All samples

The first page of the Firewall rule review sample report