The Port Scan Attack Detector i find useful asf!! if you want to find it useful as well here are the details you morbidly obese basement dwelling cuks....
The Port Scan Attack Detector or "psad" is a lightweight system daemon designed to work with Linux iptables/ip6tables/firewalld firewalling code to detect suspicious traffic such as port scans and sweeps, backdoors, botnet command and control communications, and loads more. It features a set of highly configurable danger thresholds with sensible defaults provided, verbose alert messages that include the source, destination, scanned port range, begin and end times, TCP flags and corresponding nmap options, reverse DNS info, email and syslog alerting, automatic blocking of offending IP addresses via dynamic configuration of iptables rulesets, passive operating system fingerprinting, and DShield reporting.yayuhh!!!!
In addition, psad incorporates many of the TCP, UDP, and ICMP signatures included in the Snort intrusion detection system. to detect highly suspect scans for various backdoor programs (e.g. EvilFTP, GirlFriend, SubSeven), DDoS tools (Mstream, Shaft), and advanced port scans (SYN, FIN, XMAS) which are easily leveraged against a machine via nmap. psad can also alert on Snort signatures that are logged via fwsnort, which makes use of the iptables string match extension to detect traffic that matches application layer signatures. i believe the 2.4.4 release, psad can also detect the IoT default credentials scanning phase of the Mirai botnet.
as that being said lets get right into the damn!!
Features Detection for TCP SYN, FIN, NULL, and XMAS scans as well as UDP scans. Support for both IPv4 and IPv6 logs generated by iptables and ip6tables respectively. Detection of many signature rules from the Snort intrusion detection system. Forensics mode iptables/ip6tables logfile analysis (useful as a forensics tool for extracting scan information from old iptables/ip6tables logfiles). Passive operating system fingerprinting via TCP syn packets. Two different fingerprinting strategies are supported; a re-implementation of p0f that strictly uses iptables/ip6tables log messages (requires the –log-tcp-options command line switch), and a TOS-based strategy. Email alerts that contain TCP/UDP/ICMP scan characteristics, reverse dns and whois information, snort rule matches, remote OS guess information, and more. When combined with fwsnort and the iptables string match extension, psad can generate alerts for application layer buffer overflow attacks, suspicious application commands, and other suspect layer 7 traffic. Icmp type and code header field validation. Configurable scan thresholds and danger level assignments. Iptables ruleset parsing to verify “default drop” policy stance. IP/network danger level auto-assignment (can be used to ignore or automatically escalate danger levels for certain networks). DShield alerts. Auto-blocking of scanning IP addresses via iptables/ip6tables and/or tcpwrappers based on scan danger level. (This feature is NOT enabled by default.) Parsing of iptables/ip6tables log messages and generation of CSV output that can be used as input to AfterGlow. This allows iptables/ip6tables logs to be visualized. Gnuplot is also supported. Status mode that displays a summary of current scan information with associated packet counts, iptables/ip6tables chains, and danger levels. All information psad analyzes is gathered from iptables log messages. psad by default reads the /var/log/messages file for new iptables messages and optionally writes them out to a dedicated file (/var/log/psad/fwdata). psad is then responsible for applying the danger threshold and signature logic in order to determine whether or not a port scan has taken place, send appropriate alert emails, and (optionally) block offending ip addresses. psad includes a signal handler such that if a USR1 signal is received, psad will dump the contents of the current scan hash data structure to /var/log/psad/scan_hash.$$ where “$$” represents the pid of the running psad daemon.
Depending on the Linux distribution, psad may already be available in the default package repository. For example, on Debian or Ubuntu systems, installation is done with a simple:
apt-get install psad If psad is not available in the package repository, it can be installed with the install.pl script bundled in the psad sources. The install.pl script also handles upgrades if psad is already installed. psad requires several perl modules that may or may not already be installed on your Linux system. These modules are included in the deps/ directory in the psad sources, and are automatically installed by the install.pl script. The list of modules is:
Bit::Vector Date::Calc IPTables::ChainMgr IPTables::Parse NetAddr::IP Storable Unix::Syslog
psad also includes a whois client written by Marco d’Itri (see the deps/whois directory).psad generally runs on Linux systems, and is available in the package repositories of many major Linux distributions.
documentation found at http://www.cipherdyne.org/psad/docs/
download at https://github.com/mrash/psad