Mapping Third party Vul entry Modified Severity to Custom field Risk Category

GauravT47983100
Tera Contributor
Hi all,
I need to map the modified Severity field from our third-party vulnerability entries to a new custom field, u_risk_category. I'm seeking advice on the best table structure to use for this customization.
Should the custom field be created on the Vulnerability Entry table (sn_vul_entry / its third-party extension) or on the Vulnerable Items table (sn_vul_vulnerable_item)?
Additionally, how will this choice affect data accuracy during the Tenable integration import? I want to ensure that when the Tenable plugin creates or updates records, the custom field maps properly based on where the source data is established.
Thanks in advance for your advice!
1 REPLY 1

kmohammed
Tera Guru

Short answer: put u_risk_category where the Tenable data first lands, on the third-party entry side, not only on the Vulnerable Item. That choice is what keeps the value accurate on re-import.

 

Why: the entry is the source record for a scanner finding, while a Vulnerable Item (sn_vul_vulnerable_item) is the CI-specific work item derived from it. If you put the derived category only on the Vulnerable Item, you have to copy it to every related Vulnerable Item and keep it in sync when the entry changes. That is where drift and stale categories usually come from.

 

Suggested pattern:

 

1. Create u_risk_category on sn_vul_entry, or on the third-party extension that your Tenable integration actually writes to in your instance. Confirm that target table first, because that is the table the import must populate.

2. Keep the original modified Severity field untouched. u_risk_category should be a derived field, not a replacement for the scanner severity, so a future Vulnerability Response update does not silently wipe your mapping.

3. Derive the value at import time, using an explicit value map, not free text. For example, map each modified Severity value to one choice in u_risk_category. Keep the choice list fixed so reporting stays consistent.

4. Recalculate on insert and on update. Tenable re-imports can update an existing entry, so a one-time manual value will go stale. The derivation should run whenever the entry is created or its modified Severity changes.

5. Handle unknown or blank severity explicitly. Do not let an unknown value fall through to a default high or low category. Map it to a distinct unclassified choice, or leave it blank and flag it for review, so you can see mapping gaps instead of hiding them.

6. If Vulnerable Item reporting needs the category, do not duplicate the mapping logic on the Vulnerable Item. Surface it by dot-walking from the Vulnerable Item to its entry where your reporting allows it, or copy it from the entry to the Vulnerable Item in the same entry logic, with the entry remaining the source of truth.

 

Before rolling this out, test a small Tenable import in a sub-production instance: check the entry value, check the related Vulnerable Item, then re-import with a changed modified Severity and confirm u_risk_category updates. That re-import check is the test that catches most mapping mistakes.