NSAuditor AI EE 0.6.0 Milestone — NEW Plugin 1160 AWS VPC Endpoints / PrivateLink Auditor Opens v0.6.x Line With Plugin-Breadth Expansion (Plugin Count 20 → 21)
EE 0.6.0 milestone — NEW plugin 1160 AWS VPC Endpoints / PrivateLink Auditor (plugin count 20 → 21; first new plugin since 0.4.7). 4 SOC 2 dimensions including CRITICAL unconditional-wildcard-breaks-PrivateLink-isolation closure. 11th consecutive trio-publish.
What’s new: Nsasoft US LLC has shipped NSAuditor AI Enterprise Edition 0.6.0 — the minor-version milestone bump opening the v0.6.x line with NEW plugin 1160 AWS VPC Endpoints / PrivateLink Auditor. Plugin count grows 20 → 21 — the first plugin growth since EE 0.4.7 (plugin 1190 SES). The release is the eleventh consecutive trio-publish across EE + paired CE 0.1.54 + agent-skill 0.1.21.
Why 0.6.0 is a milestone
The v0.5.x line (5 cycles, 9 cumulative false-CLEAN closures) was about evidence-quality — widening the audit surface on existing plugins. v0.6.x opens with plugin-breadth expansion: the first new plugin since EE 0.4.7 audits the AWS PrivateLink isolation boundary — the canonical primitive that governs how VPC traffic reaches managed services (SQS / SNS / SES / KMS / S3 / DynamoDB) WITHOUT traversing the public internet.
EE-RT.19 v1 — plugin 1160 AWS VPC Endpoints / PrivateLink Auditor
Plugin 1160 (aws-vpc-endpoints-auditor) complements plugin 1170 (layer-4 SG perimeter) by auditing the SERVICE-LAYER perimeter — the VPC-to-managed-service path. Fills the cross-service evidence gap between SG ingress and per-service application-layer policies.
4 SOC 2 substrate-evidence dimensions
| Dim | Control | Highest severity | Closure |
|---|---|---|---|
| 1. Endpoint resource policy permissive principals | CC6.6 | CRITICAL | Unconditional wildcard breaks PrivateLink isolation |
| 2. PrivateDNS enabled | CC6.6 | MEDIUM | Silent-bypass class — clients still resolve service-public hostname |
| 3. Endpoint state | A1.2 + CC7.2 | HIGH | failed state silent-failure (timeouts or public-internet fallthrough) |
| 4. Endpoint type substrate disclosure | Privacy + CC6.6 | INFO | PrivateLink connectivity attestation |
Dim 1 — The CRITICAL closure
Wildcard-Principal classifier mirroring plugin 1150 SNS topic-policy discipline. NotPrincipal-Allow + Action-sensitivity filter via _VPCE_SENSITIVE_ACTIONS frozen Set (covers * + per-service wildcards s3:* / kms:* / sns:* / sqs:*). Unconditional wildcard on sensitive action = CRITICAL — PrivateLink isolation BROKEN at the policy layer; any AWS principal in any account can route traffic through the endpoint, defeating the VPC-isolation guarantee. With Condition narrowing = HIGH (auditor walkthrough verifies aws:SourceVpc / aws:SourceVpce / aws:PrincipalOrgID actually constrain the grant).
Dim 2 — MEDIUM silent-bypass class
PrivateDnsEnabled=false on Interface endpoints is a common operator misconfig: the endpoint exists in the VPC but clients using default DNS still resolve the SERVICE-PUBLIC hostname → traffic routes over the public internet (defeating the PrivateLink purpose entirely). The endpoint costs money for nothing.
Dim 3 — HIGH silent-failure class
failed state means the endpoint exists in metadata but is NOT accepting traffic; clients hit timeouts OR fall through to public-internet routing for the service. Unknown enum value routes to LOW + evidenceGap per conservative_classifier_principle (AWS may extend the state machine in future SDK versions).
Dim 4 — Substrate evidence disclosure
INFO substrate evidence per endpoint: type / VPC ID / subnet IDs (Interface) / route-table IDs (Gateway). Records the PrivateLink connectivity attestation for the auditor evidence pack.
Clean reviewer pass — second consecutive cycle
0 R-CRITICAL + 0 R-HIGH + 2 folded same-session. 1 R-MEDIUM contract gap (unknown endpoint type fail-safe — defaults to Interface for safer fall-through) + 1 R-NIT coverage pin (Effect case-insensitivity regression).
Stats
- Plugin count 20 → 21 (first growth since 0.4.7)
- +59 new tests (57 plugin 1160 base + 2 reviewer-fold pins)
- EE full regression: 5044/5044 across 792 suites (was 4982/4982 across 778 at 0.5.4)
- 51-session 100% green streak preserved
- 7 new
aws-vpc-endpoints-auditorsoc2.json mapping rules (5 CC6.6 + 2 CC7.2/A1.2 dual-mapped) - Plugin manager registration:
PLUGIN_ID_1160inCLOUD_PLUGIN_SOURCE_MAPper EE-RT.13 SSOT discipline - Memory closures:
conservative_classifier_principlereinforced in 4 new fold sites;emit_literal_set_driftextended with 4 new frozen Sets + 14 named emission category constants
Coverage matrix unchanged at 10/4/33
Institutional honesty per the matrix-shift discipline. New plugin adds substrate evidence depth on already-covered controls (CC6.6 segmentation + A1.2 availability + CC7.2 monitoring), no NEW control coverage.
Who’s affected
AWS architects using VPC Endpoints / PrivateLink for managed-service connectivity; SOC 2 readiness teams covering CC6.6 segmentation evidence; SRE / DevSecOps teams running multi-account AWS organizations; cloud auditors building evidence packs for the SERVICE-LAYER perimeter; AI-coding-agent users (Claude Code, Cursor, Windsurf, VS Code Copilot — agent-skill 0.1.21 reflects plugin 1160).
Recommended install (0.6.0)
npm install -g nsauditor-ai@0.1.54 @nsasoft/nsauditor-ai-ee@0.6.0
nsauditor-ai scan --host aws --plugins all --compliance soc2 --out evidence.json
# AI-coding-agent users also pull the refreshed skill:
npm install nsauditor-ai-agent-skill@0.1.21
