Skip to content
After Kenna

GLOSSARY, read 10 Nov 2026

field mapping

All termsGuides

Start from the export's field list, not the vendor's feature list. Fields that have no home in the target, such as custom attributes, need a decision before load: map to a tag, store as a note, or drop with sign-off.

Dates and statuses need the most care. Kenna writes closed_at, status_changed_at and first_found_on on vulnerabilities, and each should land in the field the target uses for age, because SLA clocks read from them.

A sourced example

Brinqa's CSV connector documentation states that attributes are derived dynamically from the header row, that columns can be typed or merged across rows, and that the target data model defaults to Record.

Sources

  1. Source for the example: field mapping, read 10 Nov 2026

Last reviewed 10 Nov 2026.