[WenJing95]

Summary

Wiz vulnerability exports can report severity NONE. The importers currently reject that value, excluding otherwise valid findings. Import it as unknown so the finding is retained without assigning an informational severity.

ServiceNow's Wiz integration documentation describes NONE as no available severity values. Wiz's public vulnerability catalog also contains NONE records without a CVSS score; the value does not establish zero impact.

Changes

• Map the selected none value to the existing unknown severity in the Wiz JSON and CSV adapters.
• Keep severity-field precedence and original vendor evidence intact.
• Cover JSON vendor/fallback severity and all three CSV severity columns, including raw JSON evidence preservation.

Testing

• Wiz parsing/publication and local import suites: 219 tests passed, zero failures.
• SDK production build and full SDK type checks passed.
• SDK formatting and Markdown checks passed.
• Before/after parser probes reproduced the original exclusions and verified the corrected mapping, existing valid severities, and continued rejection of unrecognized values.
• Built the native host helper from the current source. Public CLI JSON and CSV imports into a synthetic local repository both succeeded; public CLI SQLite readback retained two unassessed records with unknown severity and the original NONE values.
• git diff --check: passed.

Risk and rollout

Previously excluded NONE records will now be retained as unassessed evidence with unknown severity. No severity is inferred from numeric scores. The tests use synthetic local data; no production tenant was modified. Full hosted platform and package CI remains required before merge.

Public disclosure review

• No customer, partner, prospect, or user identities, data, or identifying details are included.
• No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
• I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.

[mldangelo-oai]

Thank you for identifying these excluded records. The import failure is real, but NONE does not establish an informational or zero-impact assessment. I adjusted both adapters to retain the finding with the existing unknown severity, preserving the selected field and original vendor evidence.

The repaired change passed 219 focused tests, SDK build/type/format checks, and actual CLI JSON/CSV imports with SQLite readback using a native helper built from current source. Independent review found no remaining blockers. Required hosted CI will be checked separately before merge.