Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

whisper_nessus:Identified 0 scans to be processed #198

Open
chrisalexander2019 opened this issue Nov 13, 2019 · 1 comment
Open

whisper_nessus:Identified 0 scans to be processed #198

chrisalexander2019 opened this issue Nov 13, 2019 · 1 comment
Labels

Comments

@chrisalexander2019
Copy link

Describe the bug
INFO:vulnWhispererNessus:init:Attempting to connect to tenable...
DEBUG:NessusAPI:init:Using tenable API keys
DEBUG:NessusAPI:request:Requesting to url https://cloud.tenable.com:443/scans
DEBUG:NessusAPI:get_scan_ids:Found 0 scan_ids
INFO:vulnWhispererNessus:init:Connected to tenable on cloud.tenable.com:443
INFO:vulnWhispererNessus:scan_count:Gathering all scan data... this may take a while...
INFO:vulnWhispererNessus:whisper_nessus:Identified 0 scans to be processed
WARNING:vulnWhispererNessus:whisper_nessus:No new scans to process..

The URL Looks to be the issue
The call to tenable looks to be attempting to pull scans from https://cloud.tenable.com:443/scans when I review our configuration it looks like the scan data resides in https://cloud.tenable.com/app.html#/scans/folders.

Fix
We are attempting to figure out where in the code it sets the URl

@qmontal
Copy link
Contributor

qmontal commented Feb 4, 2020

Hi @chrisalexander2019,

I am afraid we don't have any instance of that in order to do thorough testing and fix the issue with the cloud version. Anyway, we are currently working on a heavy refactoring to make the project modular and easy to integrate for other developers, but will be something very easily implementable when we get this priority goals done. Sorry for not being that much help on the short term with the issue.

Cheers!

@qmontal qmontal added the bug label Feb 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants