Security audit
Every finding comes with its fix.
A read-only sweep of a small network, then a report an owner can read: a verdict, every finding ranked by severity, and a numbered fix for each. The next run can be compared with the last.

Every finding comes with its fix.
A read-only sweep of a small network, then a report an owner can read: a verdict, every finding ranked by severity, and a numbered fix for each. The next run can be compared with the last.

A small office needs to know what is on its network and where the worst holes are: open ports, weak sign-ins, services with no password, what the internet can already see.
The person who approves the fix is usually not technical. A raw scanner dump doesn't reach them.
"What's on the network, what's here, and what are the worst holes … an executive summary, because you're going to be bringing this to people who are not technical."
The sample's endpoint findings (SMB1, BitLocker, antivirus, remote desktop, accounts) are Windows checks. The Linux sweep does not run them; the Windows sweep does.
Both sweeps write the same run-file shape, so one report builder reads either. Porting the Windows endpoint checks to the Linux sweep is not done yet.
The Linux sweep is a port of the Windows sweep's network checks. The Windows endpoint checks stay in the PowerShell version for now.
Straight crops of the public sample. The business, addresses and machine names are made up.




The sample is a single run, so it has no "since last time" section; that comparison is built into the report builder (step 5 above). Real reports hold real network details and stay private. Open the full sample ↗