There is a quiet problem with letting an AI assistant run your security and compliance scans: the output is only as trustworthy as the chain that produced it. An agent can call a tool, summarise a finding and write you a beautiful paragraph — and none of that tells an auditor when the underlying artifact was created, or whether anyone touched it afterwards.

NSAuditor AI 0.33.0 — shipped 7 August 2026 across Enterprise Edition 0.33.0, Community Edition 0.2.37 and the agent-skill package 0.2.35 — closes that gap at the artifact layer, where it belongs.

Everything the engine can do is now something an operator (or an agent) can actually reach

This release is about reachability. Eleven compliance options existed inside the engine, were tested, and could not be populated by any shipped entry point — no flag, no environment variable, nothing an automation harness or an MCP client could set. They are now driven by a real NSAUDITOR_* environment surface.

Community Edition also gains three new command-line entry points that matter specifically for automated and scheduled use:

• compliance attest — recurring-scan attestation, the multi-period evidence that answers “show me you ran this every month for six months”
• --sla-policy — remediation SLA and MTTR tracking, with failures now rendered into the document an assessor reads rather than buried in a JSON field
• --compliance-history — multi-period evidence history

For anyone driving NSAuditor from Claude, an MCP client or a CI job, this is the difference between a tool that reports and a tool you can build a compliance programme on.

The headline: evidence your auditor verifies without you

Point NSAUDITOR_TSA_URL at a Time-Stamp Authority you choose, and every artifact in the evidence pack gets an RFC 3161 trusted-timestamp sidecar — the compliance report, the scope attestation, and the chain-of-custody record.

What makes that useful rather than decorative is who can check it. The verification is stock OpenSSL, run against the timestamp authority’s own certificate chain, on the assessor’s own machine:

openssl ts -verify -data scan_compliance_soc2.json \
  -in scan_compliance_soc2.json.tsr \
  -CAfile <tsa-ca>.pem -untrusted <tsa>.crt

Offline. Against a third party. With none of NSAuditor’s software in the path.

It was proved in both directions on 7 August 2026, against a real public TSA and through the binaries published to npm: Verification: OK across all three artifacts, and Verification: FAILED the moment a single byte was appended to one of them. A check that cannot fail proves nothing — the failure is what makes the pass a statement about those exact bytes.

One deliberate non-convenience: NSAUDITOR_TSA_URL has no default and never will. Unset means the feature is off, not “use ours” — because a timestamp is an outbound call to a third party, and that is the operator’s call. An air-gapped environment simply leaves it unset.

Zero Data Exfiltration, now written as a register you can read

NSAuditor has always run inside the customer’s own network, and the promise used to be phrased as a negative absolute. 0.33.0 replaces it with something stronger because it is checkable: a published register of 17 enumerated outbound paths across six counterparty classes, each with its trigger, whether it is on by default, the class of data involved, and how to switch it off. The published table is generated from the same register the code reads and held byte-identical to it, so documentation and behaviour cannot drift apart.

That is a better answer for an AI-driven workflow than any promise: if your agent is going to run a scan unattended, you want an enumerable list of every network call the run can make.

Still one command, still seven frameworks

A single scan across AWS, Azure and GCP with all seven frameworks enabled evaluates 1,608 controls and returns seven separate auditor-shaped reports: SOC 2, HIPAA §164.312, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8 and GDPR Article 32. All seven coverage matrices are unchanged in this release; the plugin count holds at 28 Enterprise plugins — 27 cloud auditors plus a Zero Trust posture assessment scored from a network-host scan.

Getting it

Community Edition is MIT-licensed on npm: npm i -g nsauditor-ai. Pro and Enterprise ship as @nsasoft/nsauditor-ai-ee and install alongside it. Enterprise 0.33.0 requires Community 0.2.37 or newer — the new entry points live in the Community package, so the pairing matters.

Agentless, read-only credentials, no SaaS backend, no telemetry, no phone-home.

More: nsauditor.com/ai/enterprise