Pages : 1
#1 Le 12/06/2015, à 18:25
- Arnold59
Ubuntu : Utilisation de ll'IDS SNORT :
Bonjour,
J'ai réussi à installer Snort 2.9.7 sous Linux Ubuntu 15.04
1) Une fois installé, j'ai vérifié si le service est bien activé et configuré ;
La commande sudo /etc/init.d/snort status
sudo /etc/init.d/snort status
● snort.service - LSB: Lightweight network intrusion detection system
Loaded: loaded (/etc/init.d/snort)
Active: active (running) since ven. 2015-06-12 18:06:53 CEST; 5min ago
Docs: man:systemd-sysv-generator(8)
CGroup: /system.slice/snort.service
└─5871 /usr/sbin/snort -m 027 -D -d -l /var/log/snort -u snort -g ...
juin 12 18:06:49 freemantux snort[5852]: WARNING: /etc/snort/rules/community-w...e.
juin 12 18:06:49 freemantux snort[5852]: WARNING: /etc/snort/rules/community-w...e.
juin 12 18:06:49 freemantux snort[5852]: WARNING: /etc/snort/rules/community-w...e.
juin 12 18:06:49 freemantux snort[5852]: WARNING: /etc/snort/rules/community-w...e.
juin 12 18:06:49 freemantux snort[5852]: WARNING: /etc/snort/rules/community-w...e.
juin 12 18:06:49 freemantux snort[5852]: WARNING: /etc/snort/rules/community-w...e.
juin 12 18:06:49 freemantux snort[5852]: WARNING: /etc/snort/rules/community-w...e.
juin 12 18:06:49 freemantux snort[5852]: WARNING: /etc/snort/rules/community-w...e.
juin 12 18:06:49 freemantux snort[5852]: WARNING: /etc/snort/rules/community-w...e.
juin 12 18:06:53 freemantux systemd[1]: Started LSB: Lightweight network intru...m.
Hint: Some lines were ellipsized, use -l to show in full. 2) Vérification des règles "Rules" Snort :
ls /etc/snort/rules
ls /etc/snort/rules
attack-responses.rules community-web-dos.rules policy.rules
backdoor.rules community-web-iis.rules pop2.rules
bad-traffic.rules community-web-misc.rules pop3.rules
chat.rules community-web-php.rules porn.rules
community-bot.rules ddos.rules rpc.rules
community-deleted.rules deleted.rules rservices.rules
community-dos.rules dns.rules scan.rules
community-exploit.rules dos.rules shellcode.rules
community-ftp.rules experimental.rules smtp.rules
community-game.rules exploit.rules snmp.rules
community-icmp.rules finger.rules sql.rules
community-imap.rules ftp.rules telnet.rules
community-inappropriate.rules icmp-info.rules tftp.rules
community-mail-client.rules icmp.rules virus.rules
community-misc.rules imap.rules web-attacks.rules
community-nntp.rules info.rules web-cgi.rules
community-oracle.rules local.rules web-client.rules
community-policy.rules misc.rules web-coldfusion.rules
community-sip.rules multimedia.rules web-frontpage.rules
community-smtp.rules mysql.rules web-iis.rules
community-sql-injection.rules netbios.rules web-misc.rules
community-virus.rules nntp.rules web-php.rules
community-web-attacks.rules oracle.rules x11.rules
community-web-cgi.rules other-ids.rules
community-web-client.rules p2p.rulesQuestion : Snort met-il à jour les règles ou doit-on les définir ?
3) Consultation de l'aide : snort -h
snort -h
snort: option requires an argument -- 'h'
,,_ -*> Snort! <*-
o" )~ Version 2.9.7.0 GRE (Build 149)
'''' By Martin Roesch & The Snort Team: http://www.snort.org/contact#team
Copyright (C) 2014 Cisco and/or its affiliates. All rights reserved.
Copyright (C) 1998-2013 Sourcefire, Inc., et al.
Using libpcap version 1.6.2
Using PCRE version: 8.35 2014-04-04
Using ZLIB version: 1.2.8
USAGE: snort [-options] <filter options>
Options:
-A Set alert mode: fast, full, console, test or none (alert file alerts only)
"unsock" enables UNIX socket logging (experimental).
-b Log packets in tcpdump format (much faster!)
-B <mask> Obfuscated IP addresses in alerts and packet dumps using CIDR mask
-c <rules> Use Rules File <rules>
-C Print out payloads with character data only (no hex)
-d Dump the Application Layer
-D Run Snort in background (daemon) mode
-e Display the second layer header info
-f Turn off fflush() calls after binary log writes
-F <bpf> Read BPF filters from file <bpf>
-g <gname> Run snort gid as <gname> group (or gid) after initialization
-G <0xid> Log Identifier (to uniquely id events for multiple snorts)
-h <hn> Set home network = <hn>
(for use with -l or -B, does NOT change $HOME_NET in IDS mode)
-H Make hash tables deterministic.
-i <if> Listen on interface <if>
-I Add Interface name to alert output
-k <mode> Checksum mode (all,noip,notcp,noudp,noicmp,none)
-K <mode> Logging mode (pcap[default],ascii,none)
-l <ld> Log to directory <ld>
-L <file> Log to this tcpdump file
-M Log messages to syslog (not alerts)
-m <umask> Set umask = <umask>
-n <cnt> Exit after receiving <cnt> packets
-N Turn off logging (alerts still work)
-O Obfuscate the logged IP addresses
-p Disable promiscuous mode sniffing
-P <snap> Set explicit snaplen of packet (default: 1514)
-q Quiet. Don't show banner and status report
-Q Enable inline mode operation.
-r <tf> Read and process tcpdump file <tf>
-R <id> Include 'id' in snort_intf<id>.pid file name
-s Log alert messages to syslog
-S <n=v> Set rules file variable n equal to value v
-t <dir> Chroots process to <dir> after initialization
-T Test and report on the current Snort configuration
-u <uname> Run snort uid as <uname> user (or uid) after initialization
-U Use UTC for timestamps
-v Be verbose
-V Show version number
-X Dump the raw packet data starting at the link layer
-x Exit if Snort configuration problems occur
-y Include year in timestamp in the alert and log files
-Z <file> Set the performonitor preprocessor file path and name
-? Show this information
<Filter Options> are standard BPF options, as seen in TCPDump
Longname options and their corresponding single char version
--logid <0xid> Same as -G
--perfmon-file <file> Same as -Z
--pid-path <dir> Specify the directory for the Snort PID file
--snaplen <snap> Same as -P
--help Same as -?
--version Same as -V
--alert-before-pass Process alert, drop, sdrop, or reject before pass, default is pass before alert, drop,...
--treat-drop-as-alert Converts drop, sdrop, and reject rules into alert rules during startup
--treat-drop-as-ignore Use drop, sdrop, and reject rules to ignore session traffic when not inline.
--process-all-events Process all queued events (drop, alert,...), default stops after 1st action group
--enable-inline-test Enable Inline-Test Mode Operation
--dynamic-engine-lib <file> Load a dynamic detection engine
--dynamic-engine-lib-dir <path> Load all dynamic engines from directory
--dynamic-detection-lib <file> Load a dynamic rules library
--dynamic-detection-lib-dir <path> Load all dynamic rules libraries from directory
--dump-dynamic-rules <path> Creates stub rule files of all loaded rules libraries
--dynamic-preprocessor-lib <file> Load a dynamic preprocessor library
--dynamic-preprocessor-lib-dir <path> Load all dynamic preprocessor libraries from directory
--dynamic-output-lib <file> Load a dynamic output library
--dynamic-output-lib-dir <path> Load all dynamic output libraries from directory
--create-pidfile Create PID file, even when not in Daemon mode
--nolock-pidfile Do not try to lock Snort PID file
--no-interface-pidfile Do not include the interface name in Snort PID file
--disable-attribute-reload-thread Do not create a thread to reload the attribute table
--pcap-single <tf> Same as -r.
--pcap-file <file> file that contains a list of pcaps to read - read mode is implied.
--pcap-list "<list>" a space separated list of pcaps to read - read mode is implied.
--pcap-dir <dir> a directory to recurse to look for pcaps - read mode is implied.
--pcap-filter <filter> filter to apply when getting pcaps from file or directory.
--pcap-no-filter reset to use no filter when getting pcaps from file or directory.
--pcap-loop <count> this option will read the pcaps specified on command line continuously.
for <count> times. A value of 0 will read until Snort is terminated.
--pcap-reset if reading multiple pcaps, reset snort to post-configuration state before reading next pcap.
--pcap-reload if reading multiple pcaps, reload snort config between pcaps.
--pcap-show print a line saying what pcap is currently being read.
--exit-check <count> Signal termination after <count> callbacks from DAQ_Acquire(), showing the time it
takes from signaling until DAQ_Stop() is called.
--conf-error-out Same as -x
--enable-mpls-multicast Allow multicast MPLS
--enable-mpls-overlapping-ip Handle overlapping IPs within MPLS clouds
--max-mpls-labelchain-len Specify the max MPLS label chain
--mpls-payload-type Specify the protocol (ipv4, ipv6, ethernet) that is encapsulated by MPLS
--require-rule-sid Require that all snort rules have SID specified.
--daq <type> Select packet acquisition module (default is pcap).
--daq-mode <mode> Select the DAQ operating mode.
--daq-var <name=value> Specify extra DAQ configuration variable.
--daq-dir <dir> Tell snort where to find desired DAQ.
--daq-list[=<dir>] List packet acquisition modules available in dir. Default is static modules only.
--dirty-pig Don't flush packets and release memory on shutdown.
--cs-dir <dir> Directory to use for control socket.
--ha-peer Activate live high-availability state sharing with peer.
--ha-out <file> Write high-availability events to this file.
--ha-in <file> Read high-availability events from this file on startup (warm-start).
--suppress-config-log Suppress configuration information output--> Par quoi commencer ?
D'avance merci.
Bon week-en
http://doc.ubuntu-fr.org/snort
Hors ligne
Pages : 1