📄 snort.conf
字号:
# Note that these hosts are still watched as scanned hosts. The# 'ignore_scanners' option is used to tune alerts from very active# hosts such as NAT, nessus hosts, etc. The 'ignore_scanned' option # specifies the IP(s) to ignore as scanned hosts. Note that these hosts# are still watched as scanner hosts. The 'ignore_scanned' option is# used to tune alerts from very active hosts such as syslog servers, etc.# detect_ack_scans# This option will include sessions picked up in midstream by the stream# module, which is necessary to detect ACK scans. However, this can lead to# false alerts, especially under heavy load with dropped packets; which is why# the option is off by default.## Disabled by default## preprocessor sfportscan: proto { all } \# memcap { 10000000 } \# sense_level { low }# arpspoof#----------------------------------------# Experimental ARP detection code from Jeff Nathan, detects ARP attacks,# unicast ARP requests, and specific ARP mapping monitoring. To make use of# this preprocessor you must specify the IP and hardware address of hosts on# the same layer 2 segment as you. Specify one host IP MAC combo per line.# Also takes a "-unicast" option to turn on unicast ARP request detection. # Arpspoof uses Generator ID 112 and uses the following SIDS for that GID:# SID Event description# ----- -------------------# 1 Unicast ARP request# 2 Etherframe ARP mismatch (src)# 3 Etherframe ARP mismatch (dst)# 4 ARP cache overwrite attack#preprocessor arpspoof#preprocessor arpspoof_detect_host: 192.168.40.1 f0:0f:00:f0:0f:00# ssh#----------------------------------------# EXPERIMENTAL CODE!!!## THIS CODE IS STILL EXPERIMENTAL AND MAY OR MAY NOT BE STABLE!# USE AT YOUR OWN RISK! DO NOT USE IN PRODUCTION ENVIRONMENTS.# YOU HAVE BEEN WARNED.## The SSH preprocessor detects the following exploits: Gobbles, CRC 32,# Secure CRT, and the Protocol Mismatch exploit.## Both Gobbles and CRC 32 attacks occur after the key exchange, and are# therefore encrypted. Both attacks involve sending a large payload# (20kb+) to the server immediately after the authentication challenge.# To detect the attacks, the SSH preprocessor counts the number of bytes# transmitted to the server. If those bytes exceed a pre-defined limit# within a pre-define number of packets, an alert is generated. Since# Gobbles only effects SSHv2 and CRC 32 only effects SSHv1, the SSH# version string exchange is used to distinguish the attacks.## The Secure CRT and protocol mismatch exploits are observable before# the key exchange.## SSH has numerous options available, please read README.ssh for help# configuring options.###### Per Step #2, set the following to load the ssh preprocessor# dynamicpreprocessor <full path to libsf_ssh_preproc.so># or use commandline option# --dynamic-preprocessor-lib <full path to libsf_ssh_preproc.so>##preprocessor ssh: server_ports { 22 } \# max_client_bytes 19600 \# max_encrypted_packets 20# DCE/RPC#----------------------------------------## The dcerpc preprocessor detects and decodes SMB and DCE/RPC traffic.# It is primarily interested in DCE/RPC data, and only decodes SMB# to get at the DCE/RPC data carried by the SMB layer.# # Currently, the preprocessor only handles reassembly of fragmentation# at both the SMB and DCE/RPC layer. Snort rules can be evaded by# using both types of fragmentation; with the preprocessor enabled# the rules are given a buffer with a reassembled SMB or DCE/RPC# packet to examine.# # At the SMB layer, only fragmentation using WriteAndX is currently# reassembled. Other methods will be handled in future versions of# the preprocessor.# # Autodetection of SMB is done by looking for "\xFFSMB" at the start of# the SMB data, as well as checking the NetBIOS header (which is always# present for SMB) for the type "SMB Session".# # Autodetection of DCE/RPC is not as reliable. Currently, two bytes are# checked in the packet. Assuming that the data is a DCE/RPC header,# one byte is checked for DCE/RPC version (5) and another for the type# "DCE/RPC Request". If both match, the preprocessor proceeds with that# assumption that it is looking at DCE/RPC data. If subsequent checks# are nonsensical, it ends processing.## DCERPC has numerous options available, please read README.dcerpc for help# configuring options.###### Per Step #2, set the following to load the dcerpc preprocessor# dynamicpreprocessor <full path to libsf_dcerpc_preproc.so># or use commandline option# --dynamic-preprocessor-lib <full path to libsf_dcerpc_preproc.so>preprocessor dcerpc: \ autodetect \ max_frag_size 3000 \ memcap 100000# DNS#----------------------------------------# The dns preprocessor (currently) decodes DNS Response traffic# and detects a few vulnerabilities.## DNS has a few options available, please read README.dns for# help configuring options.###### Per Step #2, set the following to load the dns preprocessor# dynamicpreprocessor <full path to libsf_dns_preproc.so># or use commandline option# --dynamic-preprocessor-lib <full path to libsf_dns_preproc.so>preprocessor dns: ports { 53 } enable_rdata_overflow##################################################################### Step #4: Configure output plugins## Uncomment and configure the output plugins you decide to use. General# configuration for output plugins is of the form:## output <name_of_plugin>: <configuration_options>## alert_syslog: log alerts to syslog# ----------------------------------# Use one or more syslog facilities as arguments. Win32 can also optionally# specify a particular hostname/port. Under Win32, the default hostname is# '127.0.0.1', and the default port is 514.## [Unix flavours should use this format...]# output alert_syslog: LOG_AUTH LOG_ALERT## [Win32 can use any of these formats...]# output alert_syslog: LOG_AUTH LOG_ALERT# output alert_syslog: host=hostname, LOG_AUTH LOG_ALERT# output alert_syslog: host=hostname:port, LOG_AUTH LOG_ALERT# log_tcpdump: log packets in binary tcpdump format# -------------------------------------------------# The only argument is the output file name.## output log_tcpdump: tcpdump.log# database: log to a variety of databases# ---------------------------------------# See the README.database file for more information about configuring# and using this plugin.## output database: log, mysql, user=root password=test dbname=db host=localhost# output database: alert, postgresql, user=snort dbname=snort# output database: log, odbc, user=snort dbname=snort# output database: log, mssql, dbname=snort user=snort password=test# output database: log, oracle, dbname=snort user=snort password=test# unified: Snort unified binary format alerting and logging# -------------------------------------------------------------# The unified output plugin provides two new formats for logging and generating# alerts from Snort, the "unified" format. The unified format is a straight# binary format for logging data out of Snort that is designed to be fast and# efficient. Used with barnyard (the new alert/log processor), most of the# overhead for logging and alerting to various slow storage mechanisms such as# databases or the network can now be avoided. ## Check out the spo_unified.h file for the data formats.## Two arguments are supported.# filename - base filename to write to (current time_t is appended)# limit - maximum size of spool file in MB (default: 128)## output alert_unified: filename snort.alert, limit 128# output log_unified: filename snort.log, limit 128# prelude: log to the Prelude Hybrid IDS system# ---------------------------------------------## profile = Name of the Prelude profile to use (default is snort).## Snort priority to IDMEF severity mappings:# high < medium < low < info## These are the default mapped from classification.config:# info = 4# low = 3# medium = 2# high = anything below medium## output alert_prelude# output alert_prelude: profile=snort-profile-name## Include classification & priority settings# Note for Windows users: You are advised to make this an absolute path,# such as: c:\snort\etc\classification.config#include classification.config## Include reference systems# Note for Windows users: You are advised to make this an absolute path,# such as: c:\snort\etc\reference.config#include reference.config##################################################################### Step #5: Configure snort with config statements## See the snort manual for a full set of configuration references## config flowbits_size: 64## New global ignore_ports config option from Andy Mullican## config ignore_ports: <tcp|udp> <list of ports separated by whitespace># config ignore_ports: tcp 21 6667:6671 1356# config ignore_ports: udp 1:17 53##################################################################### Step #6: Customize your rule set## Up to date snort rules are available at http://www.snort.org## The snort web site has documentation about how to write your own custom snort# rules.#=========================================# Include all relevant rulesets here # # The following rulesets are disabled by default:## web-attacks, backdoor, shellcode, policy, porn, info, icmp-info, virus,# chat, multimedia, and p2p# # These rules are either site policy specific or require tuning in order to not# generate false positive alerts in most enviornments.# # Please read the specific include file for more information and# README.alert_order for how rule ordering affects how alerts are triggered.#=========================================include $RULE_PATH/local.rules# include $RULE_PATH/bad-traffic.rulesinclude $RULE_PATH/exploit.rules# include $RULE_PATH/scan.rules# include $RULE_PATH/finger.rulesinclude $RULE_PATH/ftp.rulesinclude $RULE_PATH/telnet.rulesinclude $RULE_PATH/rpc.rulesinclude $RULE_PATH/rservices.rulesinclude $RULE_PATH/dos.rulesinclude $RULE_PATH/ddos.rulesinclude $RULE_PATH/dns.rules# include $RULE_PATH/tftp.rulesinclude $RULE_PATH/web-cgi.rulesinclude $RULE_PATH/web-coldfusion.rulesinclude $RULE_PATH/web-iis.rulesinclude $RULE_PATH/web-frontpage.rulesinclude $RULE_PATH/web-misc.rulesinclude $RULE_PATH/web-client.rulesinclude $RULE_PATH/web-php.rulesinclude $RULE_PATH/sql.rulesinclude $RULE_PATH/x11.rules# include $RULE_PATH/icmp.rulesinclude $RULE_PATH/netbios.rulesinclude $RULE_PATH/misc.rulesinclude $RULE_PATH/attack-responses.rulesinclude $RULE_PATH/oracle.rulesinclude $RULE_PATH/mysql.rules# include $RULE_PATH/snmp.rulesinclude $RULE_PATH/smtp.rulesinclude $RULE_PATH/imap.rulesinclude $RULE_PATH/pop2.rulesinclude $RULE_PATH/pop3.rulesinclude $RULE_PATH/nntp.rules# include $RULE_PATH/other-ids.rules# include $RULE_PATH/web-attacks.rulesinclude $RULE_PATH/backdoor.rules# include $RULE_PATH/shellcode.rules# include $RULE_PATH/policy.rules# include $RULE_PATH/porn.rules# include $RULE_PATH/info.rules# include $RULE_PATH/icmp-info.rules# include $RULE_PATH/virus.rules# include $RULE_PATH/chat.rules# include $RULE_PATH/multimedia.rules# include $RULE_PATH/p2p.rulesinclude $RULE_PATH/spyware-put.rulesinclude $RULE_PATH/specific-threats.rules# include $RULE_PATH/experimental.rules# include $RULE_PATH/content-replace.rulesinclude $RULE_PATH/voip.rules# If your using the so rules you need to do something like the following# cd into the so_rules directory where you built the so rules# cat *.rules >> so-rules.rules# cp to $RULE_PATH/so-rules.rules# uncomment this line# include $RULE_PATH/so-rules.rules# Include any thresholding or suppression commands. See threshold.conf in the# <snort src>/etc directory for details. Commands don't necessarily need to be# contained in this conf, but a separate conf makes it easier to maintain them. # Note for Windows users: You are advised to make this an absolute path,# such as: c:\snort\etc\threshold.conf# Uncomment if needed.# include threshold.conf
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -