Free tool

Endpoint audit rollup.

You asked fifteen people to run an audit script. Now you have fifteen JSON files and an afternoon of reading ahead of you. Drop them all in here instead and get one compliance matrix, a list of exactly what failed where, and an export your auditor will accept.

Your files never leave this page. Every file is parsed in your browser. There is no upload, no server, no logging, and no account. Open your network tab and watch.

Drop your audit JSON files here

or click to choose · select as many as you like · nothing is uploaded

Nothing to hand? Load a sample fleet of 15 machines to see the output.

Policy thresholds — set these to match the client you are testing

Each machine is judged against these values. Change one and the matrix recalculates — the files are already in memory, nothing is re-read.

Compliance matrix

One row per machine. This is your population.

Exceptions

Every failed control, named with the machine and what to do about it. This is the list you work, and the list the auditor reads.

! This reports, it does not attest. The rollup is only as good as the files you feed it — a machine that never ran the script simply is not here, and a population with gaps is the first thing a competent auditor checks. Track who has reported against your actual asset inventory, not against this table.
Doing this across a whole company?

I set these programs up from nothing.

Collecting evidence, defining the policy thresholds, and getting non-technical staff to actually comply is most of the work in a SOC 2 or ISO 27001 cycle. It is what I do.

Get in touch

What it reads.

Standard fields from a Windows endpoint audit. Anything missing shows as n/a rather than a false pass.

Control fields

  • AntivirusEnabled, RealTimeProtection
  • FirewallCompliant
  • BitLockerCompliant
  • LastUpdateInstalled
  • RequireSignInOnWakeup
  • ScreenTimeout_AC_Minutes
  • NonStandardAdminCount
  • WindowsHelloEnrolled

How it decides

  • Thresholds come from the policy panel, not from the file
  • A missing or unreadable field is unknown, never a pass
  • A machine with any failure is an exception
  • Files that are not audit output are skipped and named
  • Duplicate machine names are kept, newest audit first
  • Everything recalculates when you change a threshold

Need the script that produces these?

The endpoint audit script reads the machine and writes the JSON this page consumes. It reports only — it changes nothing.

Download for offline use See the tools Get in touch