Windows Local Security ChecksDebian Local Security ChecksConfigure the local security checks in OpenVAS-Client <= 2.0.1Configure the local security checks in OpenVAS-Client >= 2.0.2

Configure the local security checks in OpenVAS-Client >= 2.0.2

Next, create a task and scope for your local checks. In the Credentials tab, select 'SSH Authorization' from the list in the upper part of the window.

You can now select a key pair that was created with the OpenVAS Credentials Manager for each target that is defined in the targets text field or file. Additionally you can define patterns that are matched against the target names. For example if you want to use a certain user for the systems "office1-desktop", "office2-desktop" and "reception-desktop" you can define the pattern "*desktop". Patterns can be deleted using the buttons next to their name. Furthermore you can select a user for the 'Default' case that is used in case you did not specify a key for the target directly and no mattern matches.

In order for this mechanism to work, be sure to have the checkbox "User per-host login information" checked. If you do not want that, proceed as described in the section about configuration of older Clients.

Next, make sure you select at least these plugins:

or ensure dependencies are resolved at runtime (see checkboxes) if you select only some local security checks.

Note: You can only use the key-based login mechanism if you want to use per-host specification for local logins. If you want to use password based logins, you have to use one and the same user for every target system. In this case make sure that the checkbox "Use per-host login information" is not checked.


Windows Local Security ChecksDebian Local Security ChecksConfigure the local security checks in OpenVAS-Client <= 2.0.1Configure the local security checks in OpenVAS-Client >= 2.0.2