<h2>Vulnerability Response - CI Lookup Condition Custom Creation</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Issue </h3><section><ul><li>Is it possible to create a CI Lookup rule based on a serial number of an asset whereas the serial number data is not a part of asset import but available on the corresponding vulnerable item detection record of the Vulnerable Item that gets created through the tenable import? </li><li>Is it possible to bring the Serial Number data as a part of the Tenable.sc Asset Import from Tenable?</li></ul></section></div><div ><h3 >Release</h3><section><ul><li>All</li></ul></section></div><div ><h3 >Cause</h3><section><ul><li>On OOB, we can't unless we customize it.</li><li>Whatever the column is present in this table only those can be used in CI lookup condition builder = sn_vul_tenable_sc_asset_attrb_list</li></ul></section></div><div ><h3 >Resolution</h3><section><ul><li>Here's what you need to do in order to customize:</li><li>Line No: 352 prepareRecord function of the script include "TenableUtil".</li><li>Add the field in the sn_vul_tenable_sc_asset_attrb table.</li><li>When you prepare a record, the column should be binded with the sourceGR argument.</li><li>In this case, gr is nothing is but the record of the table.</li><li>The table sn_vul_tenable_sc_asset_attrb is binded with the value coming from the tenable scanner (payload attribute).<br /></li><li>Also, to the second question: here is the doc <a href="https://docs.tenable.com/tenablesc/api/Asset.htm." rel="nofollow">https://docs.tenable.com/tenablesc/api/Asset.htm.</a> Furthermore, we can check the payload attached in the integration process, which will let us know what all columns we have.</li></ul></section></div></article></div>