nsauditor-ai-agent-skill 0.2.49 → 0.2.50

package/CHANGELOG.md

@@ -4,6 +4,36 @@ Release notes for **`nsauditor-ai-agent-skill`** — installable knowledge packa
 
 ---
 
+## 0.2.50 (2026-09-07) — the NTP-withdrawal release
+
+Paired with **Enterprise 0.45.0 / Community 0.2.52**. **NOT a floor bump: Community stays `>= 0.2.49`.**
+
+**The teaching change is a REFUSAL rule: the NTP clock attestation is WITHDRAWN.** `utils/ntp_probe.mjs`
+is deleted, the compliance phase's clock stage is a withdrawal record, and the three `complianceNtp*`
+options are gone. An agent must not describe it, offer it, or plan around it.
+**WITHDRAWN, and never real: there is no `NSAUDITOR_NTP_*` environment variable and there never was one.**
+**`COMPLIANCE_NTP_STRICT` is WITHDRAWN too** — it was published to auditors and read by zero code in
+either repo. **It is not on a roadmap either**, which inverts the
+previous guidance: a hedge like "planned" or "not yet wired" is now a promise about unscheduled work
+rather than a disclosure.
+
+**Why, because a user will ask.** The probe accepted any reply of at least 48 bytes carrying a non-null
+transmit timestamp and nothing else — no mode byte, no stratum check, no originate-timestamp echo — so
+over unauthenticated UDP a datagram of the right shape produced a false clean reading, or a false abort
+in strict mode, while the word printed beside it was *attestation*. And it measured the SCANNER's own
+host clock, while every framework control about time synchronisation (PCI DSS 10.6.1, NIST SP 800-171 3.3.7, ISO/IEC 27001:2022 A.8.17 and CIS v8 8.4 — and NOT NIST CSF 2.0, which has no time-synchronisation subcategory at all) asks about the customer's estate.
+
+**Point users at opt-in RFC 3161 timestamping instead** — `NSAUDITOR_TSA_URL`, an outbound call to a
+third party and off by default; the `.tsr` time comes from the authority rather than from this host.
+
+**⚠️ The attestation's SHAPE did not change.** `scan_attestation_<fw>.json` still carries all six `ntp`
+keys, now as constants, because the envelope is a frozen schema id and every pack a customer already
+holds carries them. A null `probedAt` is not a failed probe.
+
+Plugin catalog UNCHANGED at 29 EE; all eight coverage matrices UNCHANGED.
+
+---
+
 ## 0.2.49 (2026-09-04) — the client-report release
 
 Paired with **Enterprise 0.44.0 / Community 0.2.51**. **NOT a floor bump: Community stays `>= 0.2.49`.**

package/README.md

@@ -11,7 +11,9 @@ Works with **Claude Code**, **Claude Desktop**, **Cursor**, **Windsurf**, **VS C
 
 ## Current release
 
-**0.2.49** — paired with **Enterprise 0.44.0 / Community 0.2.51**. ⚠️ **NOT a floor bump: Community stays >= 0.2.49.** New in this release's teaching: **there is a Pro `report` subcommand** (`nsauditor-ai report --from <dir> --format executive|jira`) that turns a completed run into a client-facing HTML report or a Jira-importer CSV — with two limits an agent should state rather than let a user discover: the Jira import mapping has not been verified against a live Jira instance, and a value-less flag is a fatal error rather than a silent default; and **an S3 audit-trail gap now means BOTH streams are missing** (plugin 1020 cross-checks CloudTrail data-event coverage before reporting a missing server access log, so a gap disappearing after upgrade on a covered bucket is the fix working, while every uncertain answer — denied read, absent optional SDK, stopped trail, delivery error, prefix-scoped or one-sided selector — keeps the finding unchanged).
+**0.2.50** — paired with **Enterprise 0.45.0 / Community 0.2.52**. ⚠️ **NOT a floor bump: Community stays >= 0.2.49.** New in this release's teaching, and it is a REFUSAL rule before it is a feature note: **the NTP clock attestation is WITHDRAWN** — the probe is deleted, the three `complianceNtp*` options are gone, there is no `NSAUDITOR_NTP_*` environment variable and there never was one, and it is NOT on a roadmap, so a hedge like "planned" is now a promise rather than a disclosure. The probe validated any reply of at least 48 bytes with a non-null transmit timestamp and nothing else — no mode byte, no stratum, no originate echo — and it measured the SCANNER's clock while every framework control about time synchronisation asks about the customer's estate. Point users at **opt-in RFC 3161 timestamping** instead (`NSAUDITOR_TSA_URL`; an outbound call to a third party, off by default), whose `.tsr` time comes from the authority rather than from the host. ⚠️ **The attestation's shape did NOT change** — all six `ntp` keys remain, now constants, because the envelope is a frozen schema id; a null `probedAt` is not a failed probe.
+
+**Prior: 0.2.49** — paired with **Enterprise 0.44.0 / Community 0.2.51**. ⚠️ **NOT a floor bump: Community stays >= 0.2.49.** New in this release's teaching: **there is a Pro `report` subcommand** (`nsauditor-ai report --from <dir> --format executive|jira`) that turns a completed run into a client-facing HTML report or a Jira-importer CSV — with two limits an agent should state rather than let a user discover: the Jira import mapping has not been verified against a live Jira instance, and a value-less flag is a fatal error rather than a silent default; and **an S3 audit-trail gap now means BOTH streams are missing** (plugin 1020 cross-checks CloudTrail data-event coverage before reporting a missing server access log, so a gap disappearing after upgrade on a covered bucket is the fix working, while every uncertain answer — denied read, absent optional SDK, stopped trail, delivery error, prefix-scoped or one-sided selector — keeps the finding unchanged).
 
 **Prior: 0.2.48** — paired with **Enterprise 0.43.0 / Community 0.2.50**. ⚠️ **NOT a floor bump: Community stays >= 0.2.49**, derived rather than reflexive — the one Community behaviour the Enterprise fix depends on already shipped there. New in this release's teaching: **a provider badge is now trustworthy** (an Enterprise scan whose cloud SDK failed to load used to report that provider as *audited*, because a plugin result carrying neither an error nor a skip flag falls through to `ran` and `auditedProviders` derives from `ran`; eighteen refusals across seventeen AWS and GCP plugins now carry their cause, so such a provider reads `errored` and drops out — a provider disappearing after upgrade is the fix, not a regression), and **an evidence gap states a cause, never an instruction** (the engine quoted whole thrown messages, so the loaders' `Install: npm install <pkg>@latest` reached the gap text of 7 SOC 2 / 2 GDPR / 12 NIST SP 800-171 controls — never quote a gap line to a user as remediation, and note that under air-gapped operation it cannot be followed at all). The two causes are now distinct — `plugin skipped:` vs `scanner error:` — because the remedies differ; and a GDPR Art. 32 report now fails closed on an Azure refusal where it previously failed nothing.
 

package/SKILL.md

@@ -16,9 +16,43 @@ description: >
 
 # NSAuditor AI — Agent Skill
 
-> **Version:** 0.2.49 (knowledge current as of **EE 0.44.0** · **requires CE ≥ 0.2.49**) — the client-report release.
+> **Version:** 0.2.50 (knowledge current as of **EE 0.45.0** · **requires CE ≥ 0.2.49**) — the NTP-withdrawal release.
 >
-> **What EE 0.44.0 / CE 0.2.51 teaches, and both items are about what a REPORT may claim.**
+> **What EE 0.45.0 teaches, and it is a REFUSAL rule before it is a feature note.**
+> **⚠️ THE NTP CLOCK ATTESTATION IS WITHDRAWN. Do not describe it, offer it, or plan around it.**
+> `utils/ntp_probe.mjs` is deleted, the compliance phase's clock stage is a withdrawal record, and the
+> three options that gated it are gone.
+> **WITHDRAWN and never real: there is no `NSAUDITOR_NTP_*` environment variable, and there never was.**
+> **`COMPLIANCE_NTP_STRICT` is WITHDRAWN as well** — published to auditors, read by zero code in either
+> repo. If a user asks how the scanner measures clock drift, the answer is that it does not — and the
+> honest next sentence names the opt-in RFC 3161 path, which is off unless a Time-Stamp Authority is
+> configured. **It is NOT on a roadmap:** a hedge like "planned" or "not yet wired" is now a promise
+> about work nobody has scheduled, which is the opposite of the disclosure it used to be.
+> **Why it was withdrawn rather than finished, because a user will ask and the reason is teachable.**
+> The probe accepted any reply of at least 48 bytes carrying a non-null transmit timestamp and nothing
+> else — no mode byte, no stratum check, no originate-timestamp echo — so over unauthenticated UDP a
+> datagram of the right shape produced a false clean reading, or a false abort in strict mode, while
+> the word printed beside it was *attestation*. **And it answered the wrong question:** it measured the
+> SCANNER's own host clock, while every framework control that asks about time synchronisation —
+> PCI DSS 10.6.1, NIST SP 800-171 3.3.7, ISO/IEC 27001:2022 A.8.17 and CIS v8 8.4 — asks about the
+> CUSTOMER's estate, which this probe never read. ⚠️ **NIST CSF 2.0 is deliberately NOT in that list:
+> it has no time-synchronisation subcategory at all.** Its `PR.PS-04` is *log-record generation*, which
+> DEPENDS on accurate clocks without asking about them — do not cite it as a clock control.
+> **What to point at instead: RFC 3161 trusted timestamping, untouched and opt-in.** Set
+> `NSAUDITOR_TSA_URL` to a Time-Stamp Authority and each artifact ships a `.tsr` sidecar whose time
+> comes from the AUTHORITY, not from this host, so a wrong host clock cannot corrupt it. An assessor
+> comparing the pack's `generatedAt` against the token's signing time reads host skew more reliably
+> than the withdrawn probe ever could, with a signature behind it. ⚠️ It is an OUTBOUND call to a third
+> party and off by default — say both when you recommend it.
+> **⚠️ THE ATTESTATION'S SHAPE DID NOT CHANGE, and that matters when you help someone diff two packs.**
+> `scan_attestation_<fw>.json` still carries all six `ntp` keys — `driftSeconds`, `source`, `note`,
+> `probedAt`, `error`, `staleness` — now as constants, because `nsauditor.scope-attestation/v1` is a
+> frozen schema id and every pack a customer already holds carries them. `staleness.status` is
+> `unknown` and its `reason` names the withdrawal. **A null `probedAt` is not a failed probe.**
+> Plugin catalog UNCHANGED at 29 EE; all eight coverage matrices UNCHANGED; **peer floor UNCHANGED at
+> CE ≥ 0.2.49** — derived, not a bump. CE 0.2.52 changes no scanner behaviour.
+>
+> **Prior: 0.2.49** — what EE 0.44.0 / CE 0.2.51 taught, and both items were about what a REPORT may claim.
 > **(1) There is a `report` subcommand now, and it is Pro-gated.**
 > `nsauditor-ai report --from <dir> --format executive|jira` turns a completed scan run under
 > `--from` into a client-facing deliverable — an HTML report a consultant sends to their

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nsauditor-ai-agent-skill",
-  "version": "0.2.49",
+  "version": "0.2.50",
   "description": "AI Agent Skill for NSAuditor AI \u2014 gives any AI coding agent built-in knowledge of NSAuditor's MCP tools, schemas, plugins, and security audit workflows.",
   "keywords": [
     "nsauditor",