[25/48] INVESTIGATION: Verify Wiz server-side deduplication across the four CLI invocations

[anota-fernandocosta]

Severity estimate: Medium

Evidence / Indicators

• HuskyCI runs four independent WizCLI containers with independent wizcli auth and independent /tmp/wizResult.json files (api/config.yaml:573, :670, :744, :807).
• Whether Wiz SaaS deduplicates the four uploads or runs them as four independent scans cannot be determined from static analysis or repo state.

Impact

If Wiz already dedupes server-side, the cost of consolidating variants (Wiz-10/11) is mostly local; if it does not, consolidation is the biggest available cloud-cost win. We cannot judge the ROI of Wiz-10/11 without this data point.

Investigation

Run the four variants on the same target repository with correlation IDs (one per analysis, propagated into Wiz tags or scan metadata where the CLI allows). Then inspect Wiz-side scan records and quota counters for:

• whether the four uploads create four scan records or one
• whether result retrieval cost / latency scales linearly with variants
• any opportunity to share auth tokens or scan IDs

Document findings in docs/assessments/wizcli-server-dedup-01.md.

Dependencies

• Easier with Wiz-05/11 telemetry already in place.

Cross-references

• Assessment: docs/assessments/wizcli-performance-assessment-01.md — Probable finding docs: update README and CONTRIBUTING for current state #9.

Verifiable by: New written assessment document; reproducible Wiz-side correlation report.