Skip to main content

[Nov 2026] A typo in an optional field no longer blocks an imported finding

Structured import is now more forgiving with the values in your file, so a finding is not lost over a label.

  • Capitalization and spacing forgiven: In fields with a fixed set of values, such as Severity or Status, high, HIGH, and High all import as High, stored in the platform's own spelling.

  • Optional fields never fail a row: An unrecognized value in an optional field is skipped, and the finding imports with that field empty. Only Finding name, Severity, Summary, and the NIST ID can fail a row.

  • Clearer errors list: Each failed row names the field, your value, and the accepted values. When your value is close to one of them, the list suggests it: Did you mean "critical"?

Did this answer your question?