fcheck(8) [debian man page]
FCHECK(8) User Contributed Perl Documentation FCHECK(8) NAME
fcheck - IDS filesystem baseline integrity checker SYNOPSIS
fcheck [OPTIONS] OPTIONS
The options to fcheck are defined below: -a Automatic mode, do all directories in configuration file. -c Create a new base line database for the given directory. -d Directory names are to be monitored for changes also. -f filename Use alternate 'filename' as the configuration file. -i Ignore creation times, check permissions, adds, deletes only. -h Append the $HOSTNAME to the configuration filename. -l Log information to logger rather than stdout messages. -r Report mode, great for emailed status reports. -s Sign each file with a CRC/hash signature. -v Verbose mode, not used for report generation. -x eXtended unix checks, # of links, UID, GID, Major/Minor checks. DESCRIPTION
Overview The fcheck utility is an IDS (Intrusion Detection System) which can be used to monitor changes to any given filesystem. Essentially, fcheck has the ability to monitor directories, files or complete filesystems for any additions, deletions, and modifications. It is configurable to exclude active log files, and can be ran as often as needed from the command line or cron making it extremely difficult to circumvent. Operation and Getting Started Flag passing is a fairly simple process. Primarily you will be using two commands. One builds (or rebuilds) your baseline database files (system snapshots). The second runs in a scanning comparison mode. "fcheck -ac" Builds the baseline database. "fcheck -a" Comparison scans the system against the baseline database. For normal operation: Initially you will run fcheck by issuing the command "fcheck -ac" to create the initial baseline file used for comparison. Any runs after the creation of the basline will normally be with the following flags "fcheck "-a"" to scan for any system modifications. After a scan is completed, you will probably want to have fcheck re-create its baseline database for the next comparison cycle. Otherwise you will be seeing every system modification since the last baseline re-build. In other words, run the "fcheck -ac" command again. (Advanced Note:) A more intensive system check would be accomplished by building your database to include GID/UID checks, directories, and CRC checks by using the following sample syntax: "fcheck -cadsxlf /etc/fcheck/fcheck.cfg" And provide periodic integrity scans from cron by using the following sample syntax: "fcheck -adsxlf /etc/fcheck/fcheck.cfg" AUTHOR
Author: Copyright (C) 1996 Michael A. Gumienny <gumienny@hotmail.com> Debianized by: Graham Simpson <gsi@eggconnect.net> SEE ALSO
Please also refer to the excellent README and INSTALL instructions provided with the package /usr/share/doc/fcheck. perl v5.14.2 2012-02-18 FCHECK(8)
Check Out this Related Man Page
TWINTRO(8) System Manager's Manual TWINTRO(8) NAME
twintro - introduction to Tripwire software DESCRIPTION
Tripwire 2.4 is a file integrity assessment product for Linux networks. Rather than preventing an intruder or virus from attacking system files, Tripwire detects intrusions when they do occur. By comparing system files and directories against a previously stored "baseline" database, Tripwire finds any additions, deletions, or changes to specified properties. This allows the system administrator to determine the extent of the problem and begin necessary damage control. After Tripwire is installed on a system, the following four commands are used: tripwire(8) is used for most of the basic operations of the software. This includes creation of the Tripwire database, and checking the integrity of the filesystem against that database. twadmin(8) is used to create, encode, and sign Tripwire policy, configuration, and key files, and for various administrative functions. twprint(8) prints Tripwire database and report files in a plain text format. siggen(8) is a file utility that displays hash values for files. In addition to the command references listed above, the following three man pages provide information on important components of the Trip- wire package. twfiles(5) provides an overview of the various files created and used by Tripwire, including default locations and settings. twconfig(4) explains the configuration file, which is used to set system-specific information that affects Tripwire operation. twpolicy(4) explains the policy file, which specifies the files and directories Tripwire should check, and how they should be scanned. Using the --help flag with any Tripwire command (e.g. tripwire --help) will print a short summary of the command modes for that command. If a mode selector is also specified (e.g. tripwire --check --help), a mode-specific usage message will be displayed. Using the all argu- ment with the --help flag (e.g. tripwire --help all) will print detailed usage messages for all modes of the specified command. VERSION INFORMATION
This man page describes Tripwire 2.4. AUTHORS
Tripwire, Inc. COPYING PERMISSIONS
Permission is granted to make and distribute verbatim copies of this man page provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this man page under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this man page into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by Tripwire, Inc. Copyright 2000 Tripwire, Inc. Tripwire is a registered trademark of Tripwire, Inc. in the United States and other countries. All rights reserved. SEE ALSO
tripwire(8), twadmin(8), twprint(8), siggen(8), twconfig(4), twpolicy(4), twfiles(5) The Design and Implementation of Tripwire: A UNIX File Integrity CheckerbyGeneKimandEugeneSpafford.PurdueTechnicalReportCSD-TR-93-071. 1 July 2000 TWINTRO(8)