The filter 'wasVuln' is invalid (valid filters: acceptedRisk, acceptRiskStatus, assetID, auditFileID, benchmarkName, cceID, cpe, cveID, baseCVSSScore, cvssVector, cvssV3BaseScore, cvssV3Vector, dataFormat, daysMitigated, daysToMitigated, dnsName, exploitAvailable, exploitFrameworks, familyID, firstSeen, iavmID, ip, lastMitigated, lastSeen, mitigatedStatus, msbulletinID, outputAssets, patchPublished, pluginModified, pluginPublished, pluginID, pluginName, pluginText, pluginType, policyID, port, protocol, recastRisk, recastRiskStatus, repositoryIDs, responsibleUserIDs, vulnRoutedUserIDs, vulnRoutingRuleID, severity, solutionID, stigSeverity, tcpport, udpport, uuid, vulnPublished, wasMitigated, xref, vprScore, assetCriticalityRating, hostUUID, assetExposureScore, aesSeverity, netbiosName).

[zerokid]

was vuln is invalid in tsc...any idea how to modify this?

[SteveMcGrath]

This is related to running an older version of Security Center. pyTenable (the underlying library that drives the tenable side of the integration) requires version 6.2 or greater. The wasVuln filter relates to WAS capabilities that were added to SC in that version.

[zerokid]

what would be the recommended version to support wasvuln?

[SteveMcGrath]

You should likely update Security Center to a supported version, 6.4 is current, and Tenable supports down to 6.2