Agent Exist field setting the value to True for all discovered items from Tenable scDescriptionIssue Definition: Why Agent exist value field is been set to true when this value is not been sent by TenableSteps to Reproduce Go to the discovered item tableSource integration should be Tenable.scCheck the field Agent existsThe value would be true for all the items discovered via Tenable.sc This screenshot shows an example of a discovery scan for the Tenable.sc integration source, highlighting that the Agent exists field is set to true. WorkaroundThis problem has no workaround, is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available. Meanwhile, If you would like to change this behavior, the script includes TenableSCVulnerabilitiesProcessor maps the agent exists value to true. This behavior was implemented in agreement with Tenable and is considered out-of-the-box (OOB), meaning the value will always be set to true. Any change to this logic—specifically to the code block around lines 236–240—would be treated as a customization and would need to be implemented in line with your internal development and governance processes.Related Problem: PRB1978013