AI-Driven Network Defense

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 your security data never leaves your environment.

With 55 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 7 compliance frameworks: SOC 2, HIPAA, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8, and GDPR Article 32.

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. Seven compliance frameworks. Verifiable evidence. Zero data exfiltration.

55 Scanner Plugins 7 Frameworks SOC 2 · HIPAA · NIST · PCI DSS · ISO 27001 · CIS v8 · GDPR Art. 32 Zero Data Exfiltration MIT Open Core
nsauditor-ai — scan
$ nsauditor-ai scan --host 10.0.0.0/24 --plugins all --compliance soc2,hipaa,nist-csf,pci-dss,iso-27001,cis-v8,gdpr
Initializing AI core... [OK]
Scanning 254 hosts · 55 plugins (parallel: 10)…
Critical Vulnerability Found CVE-2024-3321
Mapping to MITRE ATT&CK · SOC 2 CC6.1 · HIPAA §164.312(a) · NIST CSF PR.AC-1 · PCI DSS Req 8.4.1 · ISO 27001 A.8.5 · CIS Safeguard 6.5
Initial Access
Lateral Movement
Engineered for precision

What NSAuditor AI ships

An open-core scanner with risk-scored findings, threat intelligence, and hepta-framework compliance evidence — SOC 2, HIPAA, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Critical Security Controls v8, and GDPR Article 32 — 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 composite risk score — severity × exploitability × impact × exposure — so the queue sorts worst-first, and an operator suppression workflow tracks accepted-risk and false-positive dispositions with expiry.

Learn more →

Hepta-Framework Compliance

One scan produces seven 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; Defined-vs-Customized Approach per Appendix E), 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). SHA-256 chain-of-custody sidecars you can verify offline, and opt-in outbound push to Vanta, Drata or Secureframe. Zero BAA required.

View Enterprise compliance →
How it works

From your network to auditor-ready evidence

One local scan flows through risk scoring, threat mapping, and the compliance engine — ending in a hash-chained evidence pack your auditor can verify.

The fundamentals

What is a network security audit?

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 seven frameworks — SOC 2, HIPAA, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8, and GDPR Article 32 — 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 hepta-framework compliance engine, air-gapped operation, and continuous monitoring (CTEM).

New to auditing? Read our step-by-step guide: How to Conduct a Network Security Audit — Checklist & Best Practices.

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.

Community
Free · MIT
27 Community plugins · forever free · no signup
  • Full scanner plugin set
  • AI analysis (your API keys)
  • CTEM watch mode
  • JSON · HTML · SARIF · CSV
  • MCP server for AI agents
npm install -g nsauditor-ai
Enterprise
$2k+/yr · 3 tiers
28 EE plugins — 27 cloud auditors · hepta-framework compliance · air-gapped
  • 55 plugins (27 CE + 28 EE — 27 cloud auditors across AWS · GCP · Azure, plus a zero-trust posture check scored from a network-host scan)
  • Hepta-framework compliance — one scan, seven evidence packs
  • SOC 2 (AICPA TSC 2017) — 10/4/37
  • HIPAA §164.312 — 7/3/45 · Zero BAA
  • NIST CSF 2.0 — 13/10/83 subcategories
  • PCI DSS v4.0.1 — 19/9/39 sub-requirements (MVP-67)
  • ISO/IEC 27001:2022 — 17/14/62 Annex A controls
  • CIS Controls v8 — 17/23/113 Safeguards
  • GDPR Article 32 — 4/5/2 across 11 sub-measure units
  • Zero Data Exfiltration · Air-gapped operation
  • Vanta / Drata / Secureframe GRC connectors (opt-in)
Enterprise tiers →
Latest release

EE 0.39.0 — every cloud provider now declares what it does not evaluate

Enterprise Edition 0.39.0, published 19 August 2026 alongside Community Edition 0.2.44 and the agent-skill package 0.2.42 — the 97th consecutive trio. A scanner that reports only what it found leaves the reader to guess whether silence means “clean” or “never looked”. NSAuditor answers that with deferredScope, a declaration of the surfaces a plugin does not examine — and until this release, all nine of those declarations sat on AWS plugins while the seven GCP and Azure plugins declared nothing. AWS disclosing is precisely what made the others’ silence read as completeness. Seven new declarations close that asymmetry, across plugins 1021, 1022, 1024, 1025, 1220, 1221 and 1222 — between 8 and 12 boundaries each, ordered by materiality because Community Edition abridges the declaration to 420 characters in its scan badge, so the boundaries that invalidate a cross-cutting conclusion lead and per-resource depth trails.

The precision matters more than the count. Every boundary was verified against the implementing code rather than a keyword search, and that changed four of them — because the absence of a word is a hypothesis about vocabulary, not a capability boundary. serviceTag appears nowhere in the fleet, yet plugin 1221 handles the Internet and AzureCloud service tags with their own severity calibration; publishing that as “deferred” would have denied a capability that ships. Three more were corrected the same way before shipping. An overstated boundary is an underclaim, which is the expensive direction, because nothing ever complains about it. Two of the seven boundary texts were promoted out of places no report reader could reach — one from a code comment, one from a data field the summariser never reads.

What this release does not change: a deferredScope declaration routes to zero controls by design — re-measured across 49 declaration-by-framework combinations at zero control violations, beside a live negative control that correctly routed to three SOC 2 controls. It is a statement of what was never assessed, never a finding and never a gap. Plugin catalog unchanged at 28; all seven coverage matrices unchanged. The Community Edition floor is unchanged at 0.2.43 or newer. Community Edition 0.2.44 rides this trio for a separate reason worth naming: the model-facing description that tells an AI assistant how to read these results was being truncated by at least one MCP client, and a truncated description that keeps its routing mechanics while losing its honesty rules fails silently. It now leads with the reading rules, so anything a client clips is mechanics — and mechanics failing is loud.

Full release history: the Enterprise page and the package changelogs on npm.