AI-Powered Network Security Audits Without Data Exposure.
NSAuditor AI is an open-core, AI-powered network security audit platform that runs agentless, read-only, and entirely on your infrastructure. Nothing is installed across your estate, credentials are read-only by design, and nothing goes to Nsasoft. Beyond the scan’s own traffic (your targets and local segment, DNS, your own cloud’s APIs) and NIST’s public NVD API for CVE matching (off with NSAUDITOR_OFFLINE_ONLY=1 and a local NVD store), every outbound path is opt-in and off by default.
With 56 plugins for networks and AWS, Azure, and GCP, one scan delivers risk-scored security findings, exploit-first prioritization using CISA KEV and FIRST EPSS, MITRE ATT&CK mapping, and auditor-ready evidence mapped to 8 compliance frameworks: SOC 2, HIPAA, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8, GDPR Article 32, and NIST SP 800-171 Rev 2.
Evidence packs include SHA-256 chain-of-custody manifests and opt-in RFC 3161 trusted timestamps. Operator-held Ed25519 signatures can be verified offline. NSAuditor AI supports air-gapped environments and reports evidence gaps explicitly—never claiming an unassessed surface is secure.
One scan. Technical security assessment. Eight compliance frameworks. Verifiable evidence. Zero data exfiltration.
An open-core scanner with risk-scored findings, threat intelligence, and octa-framework compliance evidence — SOC 2, HIPAA, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Critical Security Controls v8, GDPR Article 32, and NIST SP 800-171 Rev 2 — built so your audit trail holds up to a CPA-firm review, a QSA RoC walkthrough, an ISO Stage 2 assessment, a CIS-CAT self-attestation, and a GDPR Article 32 review.
Risk-Scored Prioritization
Every finding carries a risk score: CVSS/10 × a 0.6 weight — every finding the scanner emits is unverified — with a 15% uplift for findings carrying an initial-access ATT&CK technique, capped at 1.0. The queue sorts worst-first, and an operator suppression workflow tracks accepted-risk and false-positive dispositions with expiry.
Findings are mapped to MITRE ATT&CK techniques with kill-chain context, so you can show your CISO what an attacker would actually do — not just CVE noise.
One scan produces eight auditor-ready evidence packs: SOC 2 (AICPA TSC 2017), HIPAA §164.312 Technical Safeguards, NIST CSF 2.0, PCI DSS v4.0.1 (sub-requirement-level for QSA RoC; every citation derived from the standard itself), ISO/IEC 27001:2022 (per-Annex-A-code with Statement of Applicability discipline), and CIS Critical Security Controls v8 (per-Safeguard with the Implementation Group cumulative discipline — IG1 cyber-insurance baseline / IG2 / IG3; no-certification-body attestation via CSAT / CIS-CAT Pro), and GDPR Article 32 (Security of Processing — infrastructure substrate for Art. 32 only, not GDPR compliance; 4/5/2 across 11 sub-measure units), and NIST SP 800-171 Rev 2 (evidence substrate for CMMC Level 2 preparation — all 110 Rev 2 requirements enumerated; 2/49/59). SHA-256 chain-of-custody sidecars you can verify offline, and opt-in outbound push to Vanta, Drata or Secureframe. No BAA with Nsasoft required.
A network security audit is a systematic review of your network — hosts, ports, services, configurations, and cloud accounts — to find vulnerabilities, misconfigurations, and compliance gaps before an attacker does.
NSAuditor AI runs that audit locally: it discovers live hosts and services, fingerprints them with safe, non-destructive probes, matches those versions against CVE data offline, maps each finding to MITRE ATT&CK, and generates auditor-ready evidence for eight frameworks — SOC 2, HIPAA, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8, GDPR Article 32, and NIST SP 800-171 Rev 2 — from a single scan. Unlike SaaS scanners, every step runs on your own infrastructure, so a complete network security audit happens with zero data exfiltration.
Need cloud coverage? NSAuditor AI Enterprise extends the audit across AWS, GCP, and Azure with the full octa-framework compliance engine, air-gapped operation, and continuous monitoring (CTEM).
Watch: how do you actually run a network security audit on a cloud account in 2026?
A seven-minute how-to in six steps: scope it before you scan, use read-only credentials, check the scan actually audited, read the findings the way your auditor will, hand over what you did not examine too, and let the auditor verify it with standard shasum and openssl. English captions. Also on YouTube.
Three editions
Free, Pro, and Enterprise
Start with the MIT-licensed Community Edition. Upgrade only when you need CVE matching and risk-scored prioritization, compliance evidence, or cloud scanners.
EE 2.1.1 — GCP 1024 and 1025 down with a cause, openai 7 and one zod, a partial AI read stated, tier denials that name what you can use; paired with Community 1.1.1
The GCP Cloud Storage (1024) and IAM (1025) auditors report themselves down, with the cause, when no GCP project is set or no usable credential loads, as the GCP security audit (1021) does. Community 1.1.1 moves its OpenAI client to openai 7, so a project that depends on it holds one zod at 4.6.6 or later, with no overrides; its AI stage says at the head of the assessment when the provider reports reading less than half of the input, by the stage’s own estimate; a tier denial names the tools the caller can use now; and nsauditor-ai license with an unknown subcommand, or none, exits 2. Enterprise 2.1.1 is a patch release: no plugin added or removed, and no coverage-matrix, peer-floor or Node.js runtime change. With no GCP project set, or no usable credential, 1024 and 1025 return up: false with the cause 1021 gives, and call no API. In 2.1.0 they reported themselves up, and with credentials but no project named, 1024 could audit whatever project Google’s client library found on its own. The controls they map fail closed as not measured. A project that depends on Community holds one zod at 4.6.6 or later, with no overrides, and no node-domexception from Community; the AI stage was run end to end on openai 7 against OpenAI and a local Ollama model before the release. When the provider reports reading less than half of the input, by the CLI’s own estimate, the assessment files open with one line saying the assessment covers part of the scan, and the JSON response and the run record carry both numbers; a local Ollama model with default settings read about a tenth of a host scan. compliance_matrix without the Enterprise package names the licence it needs instead of an install command that fails. The 2.1.1 air-gap carrier ships Enterprise 2.1.1 with Community 1.1.1; replace a 2.1.0 carrier with it. The agent skill 1.1.2 teaches the release.
Where it stops, stated: without impersonation, resolving a GCP credential fetches no token: a key file that loads but is revoked, or a principal without the IAM permission, still fails at the first call and stays a LOW evidence gap with up: true. The partial-read check estimates input as characters ÷ 4 for every provider, and the threshold was not measured on the Claude provider. With Community 1.1.0, which Enterprise 2.1.1 still accepts, a project root still holds zod 3.25.76: install Community 1.1.1 with it. The two measured limits stated since Enterprise 1.3.0 still hold: a scan made before 1.3.0 could not record a plugin left out of it, and a scan that found its ports with the Nmap plugin (024) alone has no port oracle, so include the port scanner (003) in the scans you compare. Enterprise Edition 2.1.1 is the current release, published 2026-11-01 alongside Community Edition 1.1.1 and the agent-skill package 1.1.2. Coverage: all eight coverage matrices unchanged since EE 2.1.0.
29 Enterprise auditors, 56 plugins overall, all eight frameworks. The Community Edition floor is 1.0.0 or newer — install Community Edition first. Enterprise 2.1.1 runs on Node.js 24.22.1 or newer; upgrade both packages together, with Community 1.1.1: npm i -g nsauditor-ai@1.1.1 @nsasoft/nsauditor-ai-ee@2.1.1. Install Node.js 24.22.1 or newer first: on an older runtime npm prints an EBADENGINE warning and installs anyway, and the air-gap install.sh refuses. Enterprise 2.1.1, like 2.1.0 and 2.0.0, imports a name that first ships in Community 1.0.0; below it Enterprise’s core does not load while its plugins still do — on Community 0.2.57 as on 0.2.56 — so the scan skips its intelligence, analysis-agent and compliance stages. Do not name a Community older than 1.0.0 in the same npm install -g command as Enterprise: npm then nests a second Community under Enterprise, and Enterprise’s stages are skipped with no message and no compliance report (measured on 2.1.0). Install the paired versions together, or Community first. An estate scanned with 2.1.0 and then with 2.1.1 with no GCP project or no usable credential: the earlier scan’s 1024 and 1025 violations are withheld from MTTR closure, and the drift file lists them as could not measure, never as cleared. See the Enterprise plugin catalog →
Full release history: the Enterprise page and the package changelogs on npm.