Closed armudgal closed 3 years ago
Please refer to the query filters supported: https://docs.tenable.com/tenablesc/api/Query.htm
In your scenario, you would need to use acceptRiskStatus
not acceptedRisk
.
You are absolutely right. acceptRiskStatus
works as expected.
The following error is badly worded I guess which threw me off
"error_msg":"The filter 'acceptRisk' 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, severity, stigSeverity, tcpport, udpport, vulnPublished, wasMitigated, xref, uuid, vprScore)
This includes acceptedRisk
as a valid filter.
Thanks a lot for the quick reply
Reading the Query documentation of the Tenable API is very helpful, thanks for sharing @SteveMcGrath.
Describe the bug If I include
acceptedRisk
in filters, then pyTenable throws an errorTo Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
System Information (please complete the following information):
pyTenable==1.1.4
Additional context Add any other context about the problem here.