Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add nmap parameter used by the module, for security team if need

...

 Without rules, the raw data that is being generated by the discovery scripts is useless. The rules are defined in the /etc/shinken/discovery_rules.cfg file.

Here is an example of how to

...

set the ftp host template host for anything that is detected by nmap with the TCP/21 port open:

Code Block
define discoveryrule {
   discoveryrule_name         FtpRule
   creation_type              host
   openports                  ^21$
   +use                        ftp
}

...

  • discoveryrule_nameshould be unique
  • creation_type: should be host
  • openports: regexp about the port that will be match. The and $ is for the regexp thing, so 21 and only 21 will be match, and not 210 for example. 
  • +use: This mentions the template from which the generated object will inherit from. You can add as many properties as you want.

...

PortHost template 
27017mongodb 
53dns 
25smtp 
465smtps 
3306mysql 
22ssh 
110pop3 
995pop3s 
9100printer-hp 
1521oracle 
80http 
443https 
1433mssql 
2301hp-asm 
143imap 
993imaps 
389ldap 
636ldaps 

...

Security: nmap command parameters

Here are the the parameters used by the nmap command used by this module:

  • -sU
  • -sT
  • --min-rate 1000
  • --max-retries 3
  • -T4
  • -O