# field mapping

GLOSSARY, read 10 Nov 2026

**Definition.** Field mapping is the table that says which source field feeds which field in the target platform, with any transform. Brinqa's CSV connector builds its schema from the header row of a file, lets each column be typed, and sends parsed records to a configurable target data model.

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.

## Related terms

- [risk score mapping](/glossary/risk-score-mapping/)
- [JSON Lines](/glossary/json-lines/)
- [asset identity matching](/glossary/asset-identity-matching/)
- [closed-finding history](/glossary/closed-finding-history/)

## Sources

- Source for the example: field mapping: https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/field-mapping/
