NSAuditor AI Enterprise turns one read-only cloud scan into seven auditor-ready evidence packs mapped to SOC 2, HIPAA, NIST CSF 2.0, PCI DSS, ISO 27001, CIS Controls v8, and GDPR Article 32. It audits AWS, Azure, and GCP entirely inside your infrastructure with Zero Data Exfiltration: no telemetry, no SaaS backend, and air-gapped operation, so cloud credentials, findings, and config never leave your network.
NSAuditor AI Enterprise Edition is a self-hosted, multi-cloud security and compliance auditor that converts a single read-only scan into auditor-ready compliance evidence. In one pass it maps findings to seven frameworks at once: SOC 2, HIPAA, NIST CSF 2.0, PCI DSS, ISO 27001, CIS Controls v8, and GDPR Article 32. Every evidence pack carries a cover-page scope attestation and SHA-256 chain-of-custody sidecars, so auditors can independently verify report integrity.
Built for Zero Data Exfiltration, NSAuditor runs entirely inside your own infrastructure using read-only APIs and offline licensing. There are no cloud uploads, no telemetry, and no SaaS backend, which means no BAA or DPA is required and your cloud credentials, findings, and configuration never leave your network. This makes it a fit for air-gapped and highly regulated environments across financial services, healthcare, and government.
Under the hood, NSAuditor performs deep auditing across AWS, Azure, and GCP with 55 plugins, including transitive security-group reachability, IAM shadow-admin chains, KMS key custody, and backup and snapshot exposure. Delivered as a container for deployment in your own VPC, ECS, EKS, or on-premises environment, it integrates with existing pipelines so compliance evidence generation becomes a repeatable, automated step rather than a manual scramble before each audit.
Highlights
One scan, seven frameworks: generate auditor-ready evidence packs with SHA-256 chain-of-custody for SOC 2, HIPAA, NIST CSF 2.0, PCI DSS, ISO 27001, CIS Controls v8, and GDPR Article 32.
Zero Data Exfiltration by architecture: runs entirely inside your infrastructure with read-only APIs and offline licensing. No cloud uploads, no telemetry, no BAA or DPA required.
Deep multi-cloud auditing across AWS, Azure, and GCP with 55 plugins, including transitive security-group reachability, IAM shadow-admin chains, KMS key custody, and backup and snapshot exposure.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
You pick one of three Enterprise tiers based on how many seats you need. A seat is one installation on one machine, node, or CI runner. Enterprise Base covers up to 5 seats. Enterprise Growth covers up to 25 seats. Enterprise Scale covers unlimited seats (listed as 1000). All three tiers include the same Enterprise feature set; the tiers differ only by seat capacity and the level of support you receive. Billing is contract-based and runs to your AWS account, with consolidated billing and Private Offers for custom terms.
Top-of-mind questions for buyers
What counts as one seat for billing across the three tiers?
One seat is one installation of the software on one machine. That includes a laptop, server, container image, or CI runner. It is counted per installation, not per named user. If one engineer installs it on a laptop and a build server, that counts as two seats.
What happens if my team grows past the seat count in my tier?
Nothing breaks at runtime. Seat enforcement is contractual, not technical, so there are no lockouts or remote check-ins. The license status command shows your seat number. If you outgrow your tier, you move to a tier with more capacity; usage is reconciled and prorated at renewal.
How do the three tiers differ beyond seat capacity?
All three tiers include the same Enterprise feature set. Enterprise Base adds email support and an onboarding call. Enterprise Growth adds a dedicated support channel and priority response. Enterprise Scale adds a dedicated support engineer, a 4-hour critical response window, and custom plugin development.
www.nsauditor.com+1
Helpful?
Vendor refund policy
Refunds are governed by the EULA and the applicable AWS Marketplace order terms. Except as required by AWS Marketplace policies, all fees are non-refundable. Contact support@nsauditor.com for cancellation or refund requests.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
NVD feed data can now cross an air gap, and a delivery gate proves it. feed bundle merges the NVD feed files you downloaded on a connected host into one portable archive; feed import reads one on the isolated host. Bundling the source feeds rather than the built store was deliberate: the store is a lossy derivation of an NVD feed - configurations flattened, references dropped, withdrawn records and CPE-less entries discarded at ingest - so it cannot be turned back into one. Keeping the source keeps a single ingest path across the trust boundary, and mints no archive format we would owe compatibility on forever.
Import says WHY it skipped, at the terminal. On a real NVD year file about a quarter of records are skipped (measured on the 2024 feed: 39,219 in, 29,866 imported, 9,353 skipped). A bare "skipped 9353" reads as data loss, so the reasons are named where the support ticket would start: withdrawn by NVD, no CPE match data, and - separately, because this one is not expected - malformed records, which are a prompt to re-download and check the feed's checksum.
Your own exploit intelligence can ride the archive. feed bundle --kev <catalog> --epss <scores> carries your downloads from CISA and FIRST inside it; feed import --extras-dir <dir> places your own files and prints the two environment lines to set. No exploit data ships with this product - these are your files. Both are validated at bundle time, on the connected host, where a bad file can still be re-downloaded, and the reason is measurable: the KEV and EPSS parsers return an EMPTY result for unparseable input rather than throwing, and an empty catalogue makes every finding read "not known exploited" - exactly what a host with nothing exploited reports. Refusing at import would be refusing where it cannot be fixed. Absence is stated rather than omitted, in both directions: a bundle carrying no exploit data says so, and so does the import.
The archive is INTEGRITY-CHECKED, NOT AUTHENTICATED. Each carried file records a SHA-256 that import verifies, which detects a file altered or truncated in transit. It cannot establish authorship: the hash travels inside the same archive as the data it covers, so whoever rewrites one rewrites the other. Import therefore treats every field it reads from an archive as untrusted input - a recorded filename must be a plain filename, and anything path-shaped is refused by name rather than quietly normalised. Signing the bundle on the connected host is the closure for the authorship half and is not in this release.
Requires Community Edition 0.2.42 or newer. That is a real floor bump, not a courtesy one: on CE 0.2.41 the new flags are unknown and parse to nothing, so a bundle would be built carrying no exploit data and say NOTHING about it, and the archive would reach the isolated host looking complete. Bundles Community Edition 0.2.42. Plugin catalog unchanged at 28; all seven coverage matrices unchanged (SOC 2, HIPAA, NIST CSF 2.0, PCI DSS v4.0.1, ISO 27001:2022, CIS Controls v8, GDPR Art. 32).
Additional details
Usage instructions
REGISTER FOR YOUR LICENSE KEY (one time, after subscribing).
Open https://www.nsauditor.com/ai/marketplace/register/ and enter: (a) your email, (b) the 12-digit AWS account ID holding this subscription, (c) your Agreement ID.
WHERE TO FIND IT: starts with 'agmt-'. AWS Console -> AWS Marketplace -> Manage subscriptions -> NSAuditor AI Enterprise. It is checked against the agreement AWS reports for that account.
Your ES256-signed license key (JWT) is emailed to that address.
Support: support@nsauditor.com.
RUN WITH YOUR LICENSE. Pass it via NSAUDITOR_LICENSE_KEY (or mount a config volume and run license install <key> once):
docker run --rm -e NSAUDITOR_LICENSE_KEY=<key> 709825985650.dkr.ecr.us-east-1.amazonaws.com/nsasoft-us/nsasoft/nsauditor-ai-enterprise:0.37.0 --help
Suppression approvals are CLI subcommands: compliance keygen (refuses to overwrite - regenerating a key voids every signature it produced), compliance suppress (signs its approval when NSAUDITOR_SIGNING_KEY names a local Ed25519 key, and a report verifies that signature ONLY for approvers whose registry entry carries key material), review / renew. A MISSING verdict means NOT CHECKED, never FAILED.
NEW IN 0.37.0 - AIR-GAPPED USE. No feed data and no exploit data ship with this image. On a connected host: feed bundle --from <nvd-dir> --kev <catalog> --epss <scores> --out bundle.json.gz carries the NVD feeds YOU downloaded plus your own CISA KEV and FIRST EPSS files (keep the .json.gz name - import reads gzip by filename). Move the image (docker save) and the bundle across. On the isolated host: feed import --file bundle.json.gz --cache-dir <store> --extras-dir <dir> imports your own CVE data and prints the two exploit-store env lines to set; add NSAUDITOR_OFFLINE_ONLY=1 to keep the scan path fully offline. The archive is INTEGRITY-CHECKED, NOT AUTHENTICATED: a carried SHA-256 detects alteration in transit but cannot establish authorship. Requires CE >= 0.2.42; amd64 only.
Cloud credentials are supplied read-only at runtime (-e AWS_* / mounted profiles). One image serves every tier; base / growth / scale differ only by the license key. Air-gapped operation: license validation is fully local (ES256, embedded key, no callback). Set NSAUDITOR_OFFLINE_ONLY=1 to serve CVE lookups locally and make the scan path fully offline; a configured egress path under it is refused at startup (exit 2), never skipped. Every other outbound path is opt-in and off by default (AI enrichment, GRC push, timestamping, KMS signing, NTP probe, monitoring webhook); the full register is in the image's docs (architecture 14.1.1).
Opt-in RFC 3161 timestamping, not yet exercised against a live Time-Stamp Authority from inside this exact image version: set NSAUDITOR_TSA_URL, outbound there only, no default TSA.
WHERE SENSITIVE INFORMATION IS STORED (Zero Data Exfiltration).
All scan data - credentials, findings, configuration, and generated reports - stays inside YOUR environment (the container and any volumes you mount). The product sends no telemetry and has no SaaS backend, and no customer data is collected, transmitted, or stored by Nsasoft US LLC. Outbound connections are limited to the register above: by default your cloud provider's control plane (the scan itself), NVD CVE lookups (servable locally with NSAUDITOR_OFFLINE_ONLY=1) and SES DNS lookups during AWS scans; all else is opt-in and off by default. The only data we receive is the billing/fulfillment metadata above (AWS account ID, Agreement ID, registration email), processed solely to verify the subscription is yours and issue your license.
Enterprise Base: Email support plus an onboarding call, across the full Enterprise feature set and cloud scanners.
Enterprise Growth: Dedicated Slack / email channel with priority response (SLA per contract) and custom compliance-mapping help.
Enterprise Scale: A dedicated support engineer and a custom SLA (4-hour critical, 24-hour standard) plus custom plugin development.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.