NSAuditor AI Enterprise 1.0.0 — One Read-Only Scan, Eight Frameworks, and an Evidence Contract That Is Now Frozen

Most software reaches 1.0 by adding features. NSAuditor AI Enterprise reaches it by making a commitment your procurement team can hold us to: the eight surfaces that define how it produces evidence — the finding shape and its markers, the MCP scan and query schemas, the report, attestation and rationale formats, the framework-mapping conventions, the Community peer floor and the GRC push posture — are frozen from this release, and a change to any of them is now a semver-major event. Build an integration on NSAuditor today and 1.0 is the commitment that it will not shift under you. This release also sharpens the numbers an assessor reads: the 'Findings analyzed' line now counts findings, and every report summary carries findingsReceived and findingsRouted so the arithmetic is checkable from the pack alone — no vendor portal, no callback, no trust required. An Azure RBAC assignment at the root scope is named as the root scope; PCI DSS 11.5.2 is described as critical-file change detection, in the standard's own terms. 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 one agentless, read-only scan, with read-only credentials enforced in code. 29 Enterprise auditors, 56 plugins overall; plugin count is unchanged at 29 and all eight coverage matrices are unchanged. Paired with Community Edition 0.2.54 and agent-skill 0.2.52; the peer floor is unchanged at CE >= 0.2.49.

Posted on: 15 September 2026 | 4:00 pm

NSAuditor AI Enterprise 0.46.0 — Every PCI DSS Citation, Derived From the Standard Itself and Guarded Against Drift

Every compliance product cites standards. NSAuditor AI Enterprise 0.46.0 reads its PCI DSS v4.0.1 citations from the PCI SSC publication itself rather than from a summary of it: sub-requirement identifiers, Customized Approach eligibility and the objective column are derived into a self-validating artifact that the mapping file points at — one source, no second copy to drift. Eligibility is read from where the standard states it, each requirement's own Customized Approach Objective cell, and every one of the 28 mapped controls is Customized-eligible. Each objective says, per control, whether it is the requirement cell's own wording or NSAuditor's paraphrase, and the report labels it from that flag. The derivation ships guarded: a build guard fails on any cited identifier the standard does not contain, and every objective flagged verbatim is checked against the document in both directions — so a citation your QSA reads is one the standard backs, and a drifting citation is a red test rather than a line in your report. The PCI DSS coverage matrix is enumerated at 19 covered + 9 partial + 44 out-of-scope across 72 sub-requirements — covered and partial unchanged, no control changed status — and the other seven framework matrices are unchanged. Paired with Community Edition 0.2.53 and agent-skill 0.2.51; the peer floor is unchanged at CE >= 0.2.49.

Posted on: 9 September 2026 | 4:00 pm

NSAuditor AI Enterprise 0.45.0 — Evidence That Says Only What It Can Prove: Authority-Anchored Timestamps, and an Artifact That Names Its Own Limits

NSAuditor AI Enterprise 0.45.0 makes every evidence pack a document whose words never outrun its proof. Report time is anchored by RFC 3161 trusted timestamping, opt-in via the NSAUDITOR_TSA_URL environment variable: each artifact gets a .tsr sidecar whose time comes from the Time-Stamp Authority you name rather than from the scanning host, so a wrong host clock cannot corrupt a token, and an assessor reads host skew from the token itself — with a signature behind it. The artifact names its own limits: the scope attestation's ntp block is frozen at six keys with constant values and a note stating plainly that this scanner does not measure its own clock, on an unchanged nsauditor.scope-attestation/v1 schema, so nothing an auditor's tooling reads has moved and the roughly 990 timestamp sidecars already taken stay verifiable. Consistent with that standard, the NTP clock-attestation probe is WITHDRAWN as of EE 0.45.0 — it attested the scanner's own host clock, never your estate, which is the subject of every framework time-synchronisation control — and its wording is guarded against reappearing on any published surface. The agent skill 0.2.50 carries the same discipline into AI assistants: asked whether the scanner measures its own clock, it answers no and points at the timestamping path. The change ships as a minor version so it is findable in the version series auditors read. Eight compliance frameworks from one read-only scan — SOC 2, HIPAA, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8, GDPR Article 32 (Security of Processing infrastructure substrate only, not GDPR compliance) and NIST SP 800-171 Rev 2 — across a catalogue of 56 plugins in total (27 Community + 29 Enterprise). Every coverage matrix is unchanged this cycle. Enterprise Edition 0.45.0 pairs with Community Edition 0.2.52 and agent-skill 0.2.50, and requires Community Edition 0.2.49 or newer.

Posted on: 7 September 2026 | 4:00 pm

NSAuditor AI Enterprise 0.43.0 — Silence Is Not a Pass: an Unscanned Cloud Now Reports as Unscanned

NSAuditor AI Enterprise 0.43.0 makes every scan report exactly the estate it examined. A cloud provider whose scanner did not run is now reported as NOT audited, with the reason stated, so the provider summary and the audited-provider list describe precisely what was scanned — and compliance verdicts continue to fail closed over any unscanned surface. Evidence gaps now state the cause an assessor needs rather than a remediation command, keeping operator instructions on the operator channel where they can be acted on — which matters most in air-gapped installations. The restricted offline carrier is pinned to the dependency versions its own test suite runs against and builds reproducibly, byte-identical across consecutive builds, verified in an isolated container with the network interface down and zero outbound attempts recorded. Also in this release: cleaner “Why this violates” rationale across four framework files, GDPR Article 32 (Security of Processing infrastructure substrate only, not GDPR compliance) fails closed on an Azure refusal, and the frozen interface record documents the envelope liveness keys the fail-close reads. Eight compliance frameworks from one agentless, read-only scan: SOC 2, HIPAA §164.312, 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. 29 Enterprise auditors (28 cloud auditors plus one Zero Trust posture check), 56 plugins overall, all eight coverage matrices unchanged. Paired: CE 0.2.50, agent-skill 0.2.48. Requires Community Edition 0.2.49 or newer. Zero Data Exfiltration — the scan runs entirely inside your infrastructure.

Posted on: 4 September 2026 | 4:00 pm

NSAuditor AI Enterprise 0.44.0 — The Scan You Can Send: a Client-Ready Report That States What It Could Not Read

NSAuditor AI Enterprise 0.44.0 turns a finished scan into the deliverable a consultant actually sends. `nsauditor-ai report --from --format executive` renders a completed run as a self-contained, print-ready HTML report with optional cover-page branding; `--format jira` writes a Jira-importer CSV. The HTML opens with no external network reference at all — it is a file you can hand to a client on an air-gapped laptop. The report also states what it could NOT read: a container census walks the scan record, and any finding-shaped record sitting in a place the report does not open is named and counted on the page itself. Silence is disclosed, never rendered. On the AWS side, an audit-trail gap now means BOTH audit trails are missing: S3 server access logging being off is no longer reported as a gap when a CloudTrail data-event trail already covers that bucket, with coverage judged per selector and organization trails and prefix-scoped selectors refused rather than assumed. Fewer findings, and the ones that remain are real. Eight compliance frameworks from one read-only scan — 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 — across a catalogue of 56 plugins in total (27 Community + 29 Enterprise). Every coverage matrix is unchanged this cycle. Enterprise Edition 0.44.0 pairs with Community Edition 0.2.51 and agent-skill 0.2.49, and requires Community Edition 0.2.49 or newer.

Posted on: 4 September 2026 | 4:00 pm

NSAuditor AI Enterprise 0.42.0 — Sovereign-Estate Correctness: Partition-Correct AWS Auditing and Fail-Closed Azure Sovereign-Cloud Selection

NSAuditor AI Enterprise 0.42.0 audits your sovereign and government cloud estates as themselves. AWS auditing is now partition-correct across GovCloud, the China regions, the intelligence-community partitions and the European Sovereign Cloud, so resource names, severity ladders and region handling all follow the partition your estate actually runs in — a finding in GovCloud lands with the same weight it would in commercial. Azure sovereign clouds are selected explicitly through AZURE_ENVIRONMENT and resolve fail-closed, and every Azure scan stamps the estate it addressed, so the subject of the report is visible on the face of the report. Also new: an on-demand CycloneDX or SPDX software bill of materials generated over the package you actually install rather than a maintainer’s working tree, and a published FIPS posture statement that names the FIPS-approved algorithms the product employs and states plainly that the product is not itself a FIPS 140-validated cryptographic module. 29 Enterprise auditors, 56 plugins overall, all eight compliance frameworks; the coverage matrices are unchanged because this release deepens correctness on controls already covered. Requires Community Edition 0.2.49 or newer — install Community Edition first.

Posted on: 27 August 2026 | 6:30 pm

NSAuditor AI Enterprise 0.41.0 — The 29th Plugin: Amazon DocumentDB Gets Its Own Auditor

Amazon DocumentDB now has a dedicated auditor. EE 0.41.0 adds the platform’s 29th Enterprise plugin — 1230 AWS DocumentDB Auditor — which assesses your MongoDB-compatible clusters on their own terms across seven dimensions: storage encryption at rest with KMS key-custody classification, TLS enforcement via the tls cluster parameter, audit logging together with its CloudWatch export, automated backup retention, deletion protection, replica and Availability-Zone topology under the cluster lens DocumentDB actually uses, and whether manual cluster snapshots are restorable publicly or by accounts you did not intend. Every dimension the scan cannot read becomes a named evidence gap rather than silence; remediation instructions speak DocumentDB’s own API, so what the report hands your engineer is a command that runs; and DocumentDB Elastic clusters are declared deferred rather than silently absent. The RDS auditor now delegates DocumentDB to the new plugin and carries a standing disclosure that a Neptune estate is unaudited — stated where an auditor reads. The plugin was proven live against paired known-good and known-violating fixtures, detecting six of six planted violations with no false positive on the hardened pair. It routes to all eight supported frameworks — SOC 2, HIPAA Security Rule §164.312, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8, GDPR Article 32 as Security of Processing substrate, and NIST SP 800-171 Rev 2 as evidence substrate for CMMC Level 2 preparation — through 245 mapping entries keyed to its own findings, and all eight coverage matrices are unchanged: this release is evidence depth on controls already covered. 29 Enterprise auditors, 56 plugins overall. Community Edition 0.2.48 and the agent-skill 0.2.46 are paired refreshes and the peer floor is unchanged at Community Edition 0.2.45 or newer.

Posted on: 26 August 2026 | 7:00 am

NSAuditor AI Enterprise 0.40.3 — Eight Compliance Frameworks From One Read-Only Scan, and an Evidence Chain Your Auditor Verifies Without Us

Eight compliance frameworks from a single agentless, read-only scan of AWS, Azure, GCP and on-prem networks — SOC 2, HIPAA Security Rule §164.312, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8, GDPR Article 32 as Security of Processing infrastructure substrate only and never GDPR compliance, and NIST SP 800-171 Rev 2 as evidence substrate for CMMC Level 2 preparation and never a CMMC certification. The eighth framework landed in EE 0.40.0 and it is still the reason to look: SP 800-171A decomposes every requirement into determination statements and a C3PAO scores each one, so this engine publishes the full objective list beside the subset it evidences — 69 of 172 determination statements across the 51 mapped requirements — and every partial names which shortfall it is. All 110 Rev 2 requirements are enumerated with no declared subset, so there is nothing hidden behind a sample. It informs your System Security Plan and POA&M and never produces them, emits no MET or NOT MET determination and no score, and CUI scope stays your assertion. EE 0.40.3 is the version you install today, and it makes the evidence chain underneath all eight check itself: on the RFC 3161 trusted-timestamp path — opt-in via NSAUDITOR_TSA_URL, with no default authority and an outbound call only to the authority you name — every timestamp token is matched against the exact artifact digest it attests before anything is written to disk, so a .tsr sidecar in your evidence pack provably belongs to the artifact beside it, and one framework’s chain-of-custody envelope records that check per artifact as an explicit boolean your auditor can read. The verification instruction printed on the compliance report cover page is one that runs exactly as printed, so an assessor reproduces the result with stock openssl and none of our software in the path. Tokens encoded in BER — which CMS permits and which openssl ts -verify accepts — are accepted rather than discarded, so timestamps from commercial authorities such as DigiCert, GlobalSign or Sectigo land in the pack where you expect them. All eight coverage matrices and the 28-auditor Enterprise catalog are unchanged. Community Edition 0.2.47 and the agent-skill 0.2.45 are paired refreshes and the peer floor is unchanged at Community Edition 0.2.45 or newer.

Posted on: 25 August 2026 | 7:00 am

NSAuditor AI Enterprise 0.40.2 — Eight Compliance Frameworks From One Read-Only Scan, Mapped at the Level an Assessor Actually Scores

Eight compliance frameworks from a single agentless, read-only scan of AWS, Azure, GCP and on-prem networks — SOC 2, HIPAA Security Rule §164.312, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8, GDPR Article 32 as Security of Processing infrastructure substrate only and never GDPR compliance, and NIST SP 800-171 Rev 2 as evidence substrate for CMMC Level 2 preparation and never a CMMC certification. The eighth framework arrived at EE 0.40.0 and it is the reason to look: SP 800-171A decomposes every requirement into determination statements and a C3PAO scores each one, so this engine publishes the full objective list beside the subset it evidences — 69 of 172 determination statements across the 51 mapped requirements — and every partial names which shortfall it is. All 110 Rev 2 requirements are enumerated with no declared subset, so there is nothing hidden behind a sample. It informs your System Security Plan and POA&M and never produces them, emits no MET or NOT MET determination and no score, and CUI scope stays your assertion. EE 0.40.2 is the version you install today, and it strengthens the evidence chain underneath all eight: on the RFC 3161 trusted-timestamp path — opt-in via NSAUDITOR_TSA_URL and never a default — the authority’s status is now read from its own response bytes before anything reaches disk, so only a token the authority actually granted is ever recorded, five distinct authority responses are reported by name, and any timestamp already held from an earlier run is left byte-identical. Policy-OID timestamping on that same opt-in path now works on OpenSSL 3.0 and later including the shipped container, so operators pointing at a commercial authority such as DigiCert, GlobalSign or Sectigo get timestamps. Customer-facing Google Cloud remediation text is cleaner too. All eight coverage matrices and the 28-auditor Enterprise catalog are unchanged. Community Edition 0.2.46 and the agent-skill 0.2.44 are paired refreshes and the peer floor is unchanged at Community Edition 0.2.45 or newer.

Posted on: 24 August 2026 | 7:00 am

NSAuditor AI 0.2.45 / Enterprise 0.40.1 — The Eighth Framework: NIST SP 800-171 Rev 2, and Only Two of 110 Requirements Come Back Covered

Enterprise Edition adds NIST SP 800-171 Rev 2 as its eighth compliance framework, scoped as evidence substrate for CMMC Level 2 preparation. THE HEADLINE NUMBER IS AN UNFLATTERING ONE AND THAT IS THE POINT: of the 110 requirements in Rev 2, this engine reports 2 as covered, 49 as partial and 59 as out of scope with a written reason each. That is not a coverage gap - it is what happens when you claim coverage at the level an assessor actually scores. SP 800-171A decomposes each requirement into determination statements and a C3PAO scores every one; a requirement counts as covered here only when EVERY one of its objectives is a statement about technical system state the scan reads directly, and almost every requirement retains an objective about a defined procedure, an identified set or an authorization that configuration cannot evidence. All 110 are enumerated - no declared subset, so no under-enumeration surface - and every mapped requirement carries its full objective list beside the subset this engine supplies examine-method material for: 69 of 172. Rev 2 is pinned deliberately, because CMMC assesses Rev 2 by rule and Rev 3 is a different 97-requirement universe. WHAT THIS IS NOT, stated as a refusal rather than a disclaimer: it is not a CMMC certification, not a FedRAMP authorization, it emits no MET or NOT MET determination and no SPRS score - those are the assessor's words and the DoD methodology's arithmetic, and a score implied from partial evidence is a fabrication. Two data fields were removed during development rather than shipped, a per-requirement scoring weight and a requirement-type label, because both were transcriptions this repository cannot re-derive from an authority it holds. CUI scope remains the operator's assertion: the scanner cannot see CUI, cannot distinguish it from FCI, and cannot see an enclave boundary. Requirement ids collide exactly with PCI DSS sub-requirement ids - 3.5.1 is real in both standards - so every citation must carry its qualifier. Requires Community Edition 0.2.45 or newer - a REAL floor raise, because an older Community Edition rejects the eighth framework by name.

Posted on: 21 August 2026 | 5:00 pm

NSAuditor AI 0.2.44 / Enterprise 0.39.0 — Every Cloud Provider Now Declares What It Does Not Evaluate

Enterprise Edition 0.39.0 extends coverage-boundary declarations to every cloud provider. A deferredScope declaration is the only channel by which a report reader learns a surface was never examined - and all nine shipped declarations sat on AWS plugins, while the seven GCP and Azure plugins declared nothing. AWS disclosing is exactly what made the others' silence read as completeness, which is the false-completeness class this marker exists to close; it was field-confirmed on an operator scan where deferredScope was EMPTY on Azure beside a non-empty AWS list. Seven new declarations ship across plugins 1021, 1022, 1024, 1025, 1220, 1221 and 1222 - between 8 and 12 static boundaries each, emitted at run() scope on the audited path including over an empty estate, and never on a precondition-failure path where no audit ran. They are ordered by materiality, because Community Edition abridges the declaration to 420 characters in its scan badge. 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 - grep-absence is a hypothesis about vocabulary, not a capability boundary, and an overstated boundary is an underclaim, the direction nothing ever complains about. Two 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. A declaration is not a finding and not a gap - it routes to ZERO controls by design, re-measured at 49 declaration-by-framework combinations returning 0 control violations beside a live negative control that correctly routed to 3 SOC 2 controls. Plugin catalog UNCHANGED at 28; all seven coverage matrices UNCHANGED. Requires Community Edition 0.2.43 or newer - the floor is UNCHANGED this cycle. Community Edition 0.2.44 rides the trio because the model-facing scan_cloud description was being truncated by an 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.

Posted on: 19 August 2026 | 5:00 pm

NSAuditor AI 0.2.43 / Enterprise 0.38.0 — Evidence-Pack Authorship, Proven Against Published Bytes

Enterprise Edition 0.38.0 adds two commands for evidence-pack authorship: compliance sign-pack signs the chain-of-custody envelope at an approval station with an operator-held Ed25519 key, covering one framework envelope and the artifacts it enumerates, and compliance verify-pack establishes authorship from it. PROVEN against published bytes: the three-part gate ran on the registry build - sign and verify clean, a length-preserving one-byte edit to a covered report caught while the signature itself still verifies, and the openssl-only auditor procedure reproduced beside a live negative control. The verifier also recomputes every artifacts[].sha256 against disk, because checking the signature alone would authenticate a manifest whose artifact claims nothing had ever verified. Scope, stated plainly: a verified signature proves the holder of a key asserted authorship of ONE framework's envelope at a stated time, relative to your own key custody - never a vendor attestation, and never proof the findings are true. Exit 0 verified, 1 a violation, 2 the run could not measure - and the third is never a failure. Also corrected: gzipped KEV/EPSS stores loaded as zero entries in 0.37.0 (compression is now decided by content, not filename), and a GCP evidence gap that named the wrong cause. Requires Community Edition 0.2.43 or newer.

Posted on: 17 August 2026 | 5:00 pm

NSAuditor AI 0.2.42 / Enterprise 0.37.0 — Vulnerability Data You Can Carry Onto A Network That Cannot Fetch It

A scanner on an isolated network has a standing problem: the vulnerability data it matches against lives on the internet, and it does not. The offline CVE store and its hardened ingest path have shipped for several releases — and no shipped entry point could reach them, which is why offline CVE matching was never advertised as delivered. Enterprise 0.37.0 ships the two commands that close it. `feed bundle` merges the NVD feed files YOU downloaded on a connected host into one portable archive; `feed import` reads it into the offline store on the isolated one, and names why it skipped records — about a quarter of a real NVD year file is skipped by design, being withdrawn CVEs and entries with no CPE match data, and that is not data loss. Bundling the SOURCE feeds rather than the built store was re-ruled on a measurement taken before it was built: the store is a lossy derivation of an NVD feed, so it cannot be turned back into one. Optional --kev and --epss carry YOUR OWN CISA KEV catalogue and FIRST EPSS scores inside the same archive, validated on the connected host where a bad download can still be replaced, because both parsers return an EMPTY result for unreadable input rather than failing — and an empty catalogue at a store path reports every finding as not-exploited, which is exactly what a clean host reports. No exploit data ships with this product. A bundle is INTEGRITY-CHECKED, NOT AUTHENTICATED: the recorded SHA-256 detects a file altered in transit but travels inside the archive it covers, so it cannot establish authorship. Air-gapped delivery ships as a dependency-complete bundle with an install script and checksums, distributed RESTRICTED and amd64 only; no arm64 image is published. Requires Community Edition 0.2.42 or newer, raised this cycle because the new entry points live there. Plugin catalog unchanged at 28; all seven coverage matrices unchanged.

Posted on: 16 August 2026 | 7:00 am

NSAuditor AI 0.2.41 / Enterprise 0.36.0 — The Report Stops Repeating What You Said About A Signature And Starts Checking It

A compliance report contains exceptions — findings an approver accepted as risk or marked a false positive — and each carries an approval record. Until now the report verified the approver’s IDENTITY against a registry but never the SIGNATURE on the record, so an auditor was told who approved something on the record’s own authority. Enterprise 0.36.0 checks it. A registry entry may now carry the approver’s public key beside its fingerprint, and the two must agree — enforced when the registry loads, so a mis-declared member is refused rather than quietly trusted. Each suppression signature is then verified for approvers whose registry entry carries key material, and the verdict names the exact signature bytes it checked, so a verdict cannot be attached to a different record sharing an identifier. The check answers two questions rather than one: whether the suppression should stand, and whether the bytes came from the key they name. These diverge on exactly one case — a key revoked after it signed — and separating them turns “this approval was signed after the approver’s credential was revoked” from a statement about an editable text field into a cryptographic finding. What it deliberately does not say: a MISSING verdict means NOT CHECKED, never FAILED. Every identity registry in the field today carries fingerprints only, so the common case is that verification is unavailable until approvers supply key material; reporting those as failures would accuse an organisation’s own approvers of forgery for not having migrated. The report says “signed — not checked by this report”, and a new advisory names how many registered approvers are still awaiting key material and exactly what to paste. An engine fault in the identity phase now fails that framework’s report loudly rather than rendering a degraded section telling the auditor to restore a registry that was working. Requires Community Edition 0.2.40 or newer — unchanged this cycle, because nothing in it needs new Community Edition code. Plugin catalog unchanged at 28; all seven coverage matrices unchanged.

Posted on: 13 August 2026 | 5:00 pm

NSAuditor AI 0.2.40 / Enterprise 0.35.0 — Every Accepted Risk Now Has A Name, A Date And An Expiry

Suppressing a finding is the moment an auditor looks hardest, and until now the workflow had no command behind it. Enterprise 0.35.0 ships four: compliance suppress, review, renew and keygen — so every accepted risk carries an owner, a rationale, a date and an expiry, and review lists what is about to lapse before your assessor asks. keygen creates an approval keypair for this capability - reachable, and not yet proven AT THAT RELEASE; it was proven at EE 0.36.0 and both arms are driven every release since - writes the private half 0600 and prints an identity-registry member ready to paste, and it refuses to overwrite an existing signing key so previously produced signatures stay verifiable. suppress signs the approval it writes when NSAUDITOR_SIGNING_KEY names a local Ed25519 key — a capability not yet proven at that release, and proven from EE 0.36.0; a malformed key fails at the command and writes nothing, because an operator who configured a key asked for a signed approval and being handed an unsigned one plus an error is evidence weaker than their stated intent. renew now warns that renewing a signed approval invalidates its signature: the expiry and the renewal record live inside the signed payload, so the record afterwards reads “signature does not match payload” — a verdict an auditor cannot distinguish from real tampering. What this release did not claim: Ed25519 suppression signing was reachable and NOT YET PROVEN AT THIS RELEASE. It became checkable against recorded key material at EE 0.36.0, and a tamper drive covering both a valid and a tampered signature has run on the built artifact every release since. The verification gate had not yet run against the published bytes at that release, so no surface there presented a produced signature as verified evidence. It ran at EE 0.36.0, and a tamper drive covering both a valid signature and a one-byte tampered one has been driven on the built artifact every release since. No new environment variables ship — NSAUDITOR_SIGNING_KEY already existed and was inert; what changed is that it is now consumed. Requires CE 0.2.40 or newer. Plugin catalog unchanged at 28; all seven coverage matrices unchanged.

Posted on: 12 August 2026 | 6:00 pm

NSAuditor AI 0.2.39 / Enterprise 0.34.0 — Severity Told You How Bad It Could Be. Exploit Intelligence Tells You What Is Actually Being Used.

A scan of a real environment returns more CRITICALs than anyone can fix this week, and severity ranks how bad a vulnerability would be — not whether anyone is exploiting it. Enterprise 0.34.0 joins every finding that carries a CVE against a local CISA KEV catalog and a local FIRST EPSS scores file, bands it KNOWN_EXPLOITED / ELEVATED / BASELINE, and reorders the queue exploit-first, so a KEV-listed MEDIUM outranks an unexploited CRITICAL — with the flag, the score and its percentile, the matched CVE ids and the store’s own as-of date shown beside every promoted finding. riskScore is untouched: this is a new axis, not a re-weighting. Both catalogs are free, public and operator-supplied, and the join runs entirely on your own machine, so no CVE, host or finding leaves your network to obtain the ranking — and the product tells you the as-of date of the catalog it ranked against, so the ordering is always something you can date. Community Edition 0.2.39 fixes a port scanner that probed zero ports under a global install and an NVD cache that broke CVE lookup under MCP. Requires CE ≥ 0.2.39.

Posted on: 10 August 2026 | 5:00 pm

NSAuditor AI 0.2.38 / Enterprise 0.33.1 — Auditor-Verifiable Proof, Now Stated in All Seven Framework Reports

Every assessor eventually asks the one question a scanner cannot answer for itself: how do I know this evidence file was not edited after it was produced? NSAuditor AI Enterprise 0.33.1 puts the answer in writing inside all seven auditor-shaped reports — SOC 2, HIPAA, NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8 and GDPR Article 32. Set NSAUDITOR_TSA_URL to a Time-Stamp Authority you choose, and every compliance artifact in the pack carries an RFC 3161 trusted-timestamp sidecar — opt-in, with no default ever — that your auditor verifies offline, with stock openssl, against that third party, with none of our software in the path. Leave it unset and nothing is timestamped and no outbound call is made, so an air-gapped environment is unaffected. Proven end to end on 7 August 2026 through the published npm binaries against a real public Time-Stamp Authority: Verification: OK on the compliance report, the scope attestation and the chain of custody — and Verification: FAILED after a single byte was appended. The failure is the half that makes the success mean something, because it proves the check is about those exact bytes rather than about a command having run. The agent skill and the Community Edition README now answer the same way, so every surface a reader can reach agrees with the pack. Matrix-neutral: all seven coverage matrices unchanged, 28 Enterprise plugins unchanged. Paired with Community Edition 0.2.38 and agent-skill 0.2.36; Enterprise 0.33.1 requires Community Edition 0.2.37 or newer.

Posted on: 7 August 2026 | 5:00 pm