![how to use nessus api how to use nessus api](https://avleonov.com/wp-content/uploads/2016/06/nessus_switch_off-300x207.png)
After a bit of time I had something usable.īelow are screenshots of the script in action: Python has a nice XML library that makes this simple enough. Given the simplicity of the REST API calls, the hard part was then to parse the XML for the data that I wanted. csv file to be used as a lookup file in Splunk csv: this downloads all the plugin (vulnerability check) data to a.
#HOW TO USE NESSUS API DOWNLOAD#
![how to use nessus api how to use nessus api](https://securityonline.info/wp-content/uploads/2017/08/Capture-15.png)
Overall, I found the REST API simpler to write and easier to understand. So where I was making XML-RPC requests in IP360, I was using HTTP GETs and POSTs to communicate in Nessus. The major difference between the two APIs is that Nessus uses a REST API. The only API I’ve used is IP360’s so I was excited to check out the Nessus API to see how it differed and to give me more experience writing Python. I found a couple projects but nothing that did exactly what I was looking for, namely enterprise-level reporting and scoring. Nessus is arguably more popular than IP360 given it’s starting cost (free) so I figured there might already be some kind of Splunk integration already available. At the same time, the more I used Securit圜enter the more the engineer in me felt I could probably script up something to perform a lot of the same reporting myself. We didn’t have PVS or LCE as part of our implementation so Securit圜enter was strictly used as a management and reporting tool for our Nessus scanners. The interface was modern and I liked that Securit圜enter performed simple load balancing across multiple Nessus scanners. In a previous role I implemented Nessus + Securit圜enter and for the most part had a positive experience. The key of the request header is X-Cookie, with the value of token=xxxx.Inspired by my IP360 and Splunk integration project ( here and here), I wanted to do the same for Tenable Nessus. In the subsequent request, put the token into the request header information. Its interface is defined as follows: POST /sessionĮnter the correct user name and password, and a token will be returned after successful login The first one is to obtain token after login This method can be found in the entry. Nessus provides two authentication methods. Nessus provides a rich secondary development interface, which is very convenient to access other systems or to realize automatic scanning.Īt the same time, Nessus also provides complete API documents, which can be found in settings - > my account - > API keys - > API documentation In the previous project, you need to access the nessus scanner, study the nessus api, and now share your achievements.