Hi Elias, welcome to the Greenbone community forum. My immediate thought is that what you are seeing is not a brute force VT , but rather more likely to be a VT that is testing for default credentials.
Even if a VT or a VT family is disabled, the VTs may get pulled in and executed via dependencies.
To disable brute force checks fully, please edit the scan config, go to the VT family “Settings”, make sure the VT “Options for Brute Force NVTs”, is included, edit it and set the option “Disable brute force checks” to “Yes” and save.
Depending on your requirements, you may also want to set the option “Disable default account checks” to “Yes”.
Thank you for your replies.
I tried activating the option “Disable brute force checks” programmatically but the base64 value of “yes” string is not passed to the VT script.
I’ll try to activating “Disable default account checks” and watch the log on my target machine.
@cfi I agree but I have a use case where I need to disable this.
I tried to set preferences “Disable brute force checks” and “Disable default account checks” to “yes” but the value is not passed to the NVT. I’ll try to disable the “Default accounts” family.
It would have made sense to mention that GMP is used as not everyone in this forum is familiar with that protocol and the specific requirements of it.
To make sure that this is not a problem of the usage of GMP to set the preferences (maybe the settings are not applied on the expected / used scan config, the changes scan config is not assigned to the correct task, …) i would first try to do the change manually / without using the API.