...
- Match the Opmantek UUID (not configurable).
- Match the Google Cloud ID (not configurable).
- match_hostname_uuid
- match_hostname_dbus
- match_hostname_serial
- match_dbus
- match_dns_fqdn
- match_dns_hostname
- match_fqdn
- match_serial_type
- match_serial
- match_sysname_serial
- match_sysname
- match_mac (ip table)
- match_mac (network table)
- match_mac (addresses)
- match_ip
- match_hostname
| Note | ||
|---|---|---|
| ||
As at Open-AudIT 3.3.0 we will be implementing a match routine that essentially says "If all I have is an IP, and that IP belongs to a device in the database and that device has not been audited, match that device regardless of the match_ip rule. The reason for this is in the case of a discovered device that we don't have credentials for, we have virtually no information except the IP and maybe the DNS Hostname. Neither are considered unique (think DHCP). But in the case where we have a device with that lack of data already preset in the database, assume it is the same device so that we don't create many false duplicates. This configuration item will be called match_ip_no_data and will be set to YES by default. |
Match Properties
These properties are stored in Open-AudIT's configuration; to access them select Admin -> Configuration -> Discovery from Open-AudIT's menu. The default values of 'y' and 'n' simply mean YES and NO. We will use YES and NO in the description, rather than 'y' and 'n'. The stored value should always be either a lowercase y or n.
...