Sponsored Content
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Securing your network with PacketFence Post 302239342 by Linux Bot on Tuesday 23rd of September 2008 11:10:03 AM
Old 09-23-2008
Securing your network with PacketFence

09-23-2008 08:00 AM
Network access control (NAC) aims to unify endpoint security, system authentication, and security enforcement in a more intelligent network access solution than simple firewalls. NAC ensures that every workstation accessing the network conforms to a security policy and can take remedial actions on workstations if necessary. For example, NACs can check if a workstation has antivirus software installed and, if not, NAC will limit the workstation's access to the network. In some cases, if NAC is capable of remedial measures, it can force-install an antivirus program on the workstation so that it will conform to the security policy. Although NAC can improve the security of your environment, most commercial NACs cost several thousand dollars. However, using NAC does not need to be that expensive. PacketFence, a free open source NAC application, gives you the security of NAC for free.



Source...
 
Logcheck(8)						      System Manager's Manual						       Logcheck(8)

NAME
logcheck -- program to scan system logs for interesting lines SYNOPSIS
logcheck [OPTIONS] DESCRIPTION
The logcheck program helps spot problems and security violations in your logfiles automatically and will send the results to you periodi- cally in an e-mail. By default logcheck runs as an hourly cronjob just off the hour and after every reboot. logcheck supports three level of filtering: "paranoid" is for high-security machines running as few services as possible. Don't use it if you can't handle its verbose messages. "server" is the default and contains rules for many different daemons. "workstation" is for shel- tered machines and filters most of the messages. The ignore rules work in additive manner. "paranoid" rules are also included at level "server". "workstation" level includes both "paranoid" and "server" rules. The messages reported are sorted into three layers, system events, security events and attack alerts. The verbosity of system events is controlled by which level you choose, paranoid, server or workstation. However, security events and attack alerts are not affected by this. EXAMPLES
logcheck can be invoked directly thanks to su(8) or sudo(8), which change the user ID. The following example checks the logfiles without updating the offset and outputs everything to STDOUT. sudo -u logcheck logcheck -o -t OPTIONS
A summary of options is included below. -c CFG Overrule default configuration file. -d Debug mode. -h Show usage information. -H Use this hostname string in the subject of logcheck mail. -l LOG Run logfile through logcheck. -L CFG Overrule default logfiles list. -m Mail report to recipient. -o STDOUT mode, not sending mail. -p Set the report level to "paranoid". -r DIR Overrule default rules directory. -R Adds "Reboot:" to the email subject line. -s Set the report level to "server". -S DIR Overrule default state directory. -t Testing mode does not update offset. -T Do not remove the TMPDIR. -u Enable syslog-summary. -v Print current version. -w Set the report level to "workstation". FILES
/etc/logcheck/logcheck.conf is the main configuration file. /etc/logcheck/logcheck.logfiles is the list of files to monitor. /usr/share/doc/logcheck-database/README.logcheck-database.gz for hints on how to write, test and maintain rules. EXIT STATUS
0 upon success; 1 upon failure SEE ALSO
logtail(8) AUTHOR
logcheck is developed by Debian logcheck Team at alioth: http://alioth.debian.org/projects/logcheck/. This manual page was written by Jon Middleton. Logcheck(8)
All times are GMT -4. The time now is 02:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy