RayVentory Scan Engine differentiates between five different credential types:
•Windows
•SSH
•Oracle DB
•SNMP
•vSphere
Windows and SSH Credentials
The types Windows and SSH are used for OS / Device inventory and during Discovery for discovering / probing Oracle databases. The remote execution based inventory methods for Oracle use these credentials too, in order to find evidence for Oracle instances in the host file system and services and for authentication to the host system.
Oracle DB Credentials
The type Oracle DB is used for authentication against Oracle databases for creating the Oracle inventory.
SNMP Credentials
The type SNMP is used for selecting an SNMP community or authentication by SNMP v3.
vSphere Credentials
The type vSphere is used for authentication against the VMware management API for the creation of inventories of vSphere / ESX virtualization hosts.
In general, the application of credentials to a target system / service happens in the order they appear in the credentials list. If certain credentials have been set for a device / service then these are tried first, before other credentials are tried. On a successful inventory, RayVentory Scan Engine remembers which credentials have been used for a device or service and tries these first the next time an inventory is run.
Credentials may be restricted to be applied to certain devices. To restrict credentials to a specific hostname enter that hostname or IP address into the field Target name pattern. This field supports Regular Expressions.
|
WARNING Whilst the idea of creating a list of credentials to try on each host may sound handy (especially if you are not certain which credentials actually belong to a certain device / service), keep in mind that such brute-forcing of credentials may trigger alarms in your security and network monitoring solution. In case of an Oracle database you may even lock a user as by default, as three failed authentication attempts in a row will lock the user / login that has been used. It is highly recommended to use as few generic credentials as possible, by either selecting concrete credentials for devices or setting up filters to limit their application. |
