Hi, Sorry for the delay,
About point 4, you might be interested in this python-wrapper in CLI I developped this summer : https://github.com/YohanPipereau/python-openvas To make it short, this python-wrapper interacts wth openvassd (the scanner for OpenVAS) using the OTP protocol. as openvas-manager does. The main difference with Openvas manager is that you don't need to write any OMP or to run any other tool to make it work. The aim of this program is to use a straightforward communication between the scanner and my manager (python-openvas script). If you are not happy with the main program, feel free to use the library. If you want to use it just be careful that your OpenVAS version is at least 5.1.0. About point 3, disable as many firewall (all if possible) as you can between you and the target. The scanner runs nmaps scans first. About point 1, you can force retrieval of vulnerabilities using the openvas-sync-nvt or greenbone-sync-nvt script, i don't remember the exact name. Else, you can simply restart openvas-scanner service which will retrieve the list of NVTs. You can check that you get new NVTs by running the following in CLI: nc -U <path to openvas-scanner socket> < OTP/2.0> CLIENT <|> NVT_INFO <|> CLIENT It should reply with a different checksum whenever you have new vulnerabilities detected. SIncerely, Pipereau Yohan On 22/09/2017 07:04, Heena Thacker wrote: > Thanks for your reply. I by mistake sent this mail to python > developer. But your reply really helped. Thank you so much :) i will > check config files and test again. > > heena thacker > Tech lead- TDG > > ------------------------------------------------------------------------ > *From:* Fábio Fernandes <[email protected]> > *Sent:* Friday, September 22, 2017 1:54:22 AM > *To:* Heena Thacker > *Cc:* [email protected] > *Subject:* Re: [Openvas-discuss] Openvas Help > > 1. New NVT are added weekly to the feed so new vulnerabilities can be > detected. In some scans some NVTs can fail to detect vulnerabilities > because of network conditions, problems with a target, etc. > 2. I think nobody can help you without some more information about the > bug, daemon error and OpenVAS version. > 3. Some scans can take a lot of time because of network or scan target > machine problems. Try to understand what is happening. Check processes > running at the time, use log_whole_attack option in the scan configs. > 4. OpenVAS Manager exposes an extensive API using the OMP protocol > explained in http://openvas.org/protocol-doc.html. I see you mailed > python developers list there are several clients for several languages. > > Fabio > >> No dia 20/09/2017, às 10:53, Heena Thacker <[email protected] >> <mailto:[email protected]>> escreveu: >> >> Can you help? >> >> *From:* Heena Thacker >> *Sent:* 20 September 2017 03:16 PM >> *To:* '[email protected] >> <mailto:[email protected]>' >> <[email protected] <mailto:[email protected]>> >> *Subject:* Openvas Help >> >> Dear Sir/Madam, >> >> We need some Openvas support. There is no documentation help >> available. Can you please advise? >> >> We have made configuration as mentioned in Openvas site and seems to >> be setup perfectly, but I need some help with these issues: >> >> >> 1. When we run scan on Openvas , everyday the same task runs, there >> has been no change in site though the severity differs. >> 2. From recent month there is bug listed on Openvas site, scan >> doesn’t run somehow, its now running everyday but when I open >> Greenbone there is some daemon error, which never came before. Is >> there any solution for this? >> 3. Sometimes scan takes a long time , sometime stops at some %. Is >> there any reason behind that? >> 4. If there is any API from which we can fetch data quickly? >> >> >> >> Thanks in advance, >> >> Heena Thacker >> Technical Leader – TDG >> The information contained in this communication is confidential, may >> be privileged and is for the exclusive use of the above named >> addressee. If you are not the intended recipient, you are expressly >> prohibited from copying, distributing, or in any other way using any >> of the information contained within this communication. Any views or >> opinions expressed are solely those of the author and do not >> necessarily represent those of Turrem Data Group Limited. All >> reasonable precautions have been taken to ensure no viruses are >> present in this E-mail. Turrem Data Group Limited cannot accept >> responsibility for loss or damage arising from the use of this E-mail >> or attachments, we recommend that you subject these to your virus >> checking procedures prior to use. >> _______________________________________________ >> Openvas-discuss mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > > The information contained in this communication is confidential, may > be privileged and is for the exclusive use of the above named > addressee. If you are not the intended recipient, you are expressly > prohibited from copying, distributing, or in any other way using any > of the information contained within this communication. Any views or > opinions expressed are solely those of the author and do not > necessarily represent those of Turrem Data Group Limited. All > reasonable precautions have been taken to ensure no viruses are > present in this E-mail. Turrem Data Group Limited cannot accept > responsibility for loss or damage arising from the use of this E-mail > or attachments, we recommend that you subject these to your virus > checking procedures prior to use. > > > _______________________________________________ > Openvas-discuss mailing list > [email protected] > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
