This bucket is for completed tasks.
options (and potentially other things such as correctness of psad alerts).
the danger level calculaion. A SYN packet to tcp/22 is worse than a stray SYN packet to an arbitrary high port (as long as there isn’t a backdoor, etc.). There are (probably) historically more vulnerabilities in sshd than for some service that isn’t even listed in /etc/services.
packets (i.e. the iptables box was used as a zombie host).
- HTML output mode, and ability to create IP directories/pages under a web root directory.
- Add the ability to install.pl to restore the “latest” syslog config backup file (fwknop may have been installed for example) at uninstall time.
- Play with SHOW_ALL_SIGNATURES = “Y” since this may not really cause hugely long email alerts. This trick would be to perhaps associate a “last seen” timestamp with each old signature.
:<2012-12-01 Sat>
:<2012-12-01 Sat>
Extend install.pl to provide an option to dowload the latest perl modules (Date::Calc, Unix::Syslog, etc.) from CPAN.
Extend passive OS fingerprinting to include signatures from Xprobe from http://www.sys-security.com.
- Add a density calculation for a range of scanned ports, and also add a “verbose” mode that will display which of the scanned ports actually resolve to something in the IANA spec.
Include a verbose message in the body of certain emails that as of psad-1.0.0-pre2 only contain a subject line.
- Deal with the possibility that psad could eat lots of memory over time if $ENABLE_PERSISTENCE=”Y”. This should involve periodically deleting entries in %scan (or maybe the entire hash), but this should be done in a way that allows some scan data to persist.
- Possibly add a daemon to take into account ACK PSH, ACK FIN, RST etc. packets that the client may generate after the ip_conntrack module is reloaded. Without anticipating such packets psad will interpret them as a belonging to a port scan. NOTE: This problem is mostly corrected by the conntrack patch to the kernel. Also, the IGNORE_CONNTRACK_BUG_PKTS variable was added to mitigate this problem.
- Improve check_firewall_rules() to check for a state rule (iptables) since having such a rule greatly improves the quality of the data stream provided to psad by kmsgsd since more packet types will be denied without requiring overly complicated firewall rules to detect odd tcp flag combinations.
- Handle “pass” action on Snort rules in the signatures file. This will allow ignore rules to be written in the Snort rules language itself (this will far more powerful than any of the IGNORE_* keywords).
:<2012-11-21 Wed>
:<2012-11-21 Wed>
:<2012-11-21 Wed>
:<2012-11-21 Wed>
:<2012-11-21 Wed>