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
TWFILES(5) File Formats Manual TWFILES(5) NAME
twfiles - overview of files used by Tripwire and file backup process DESCRIPTION
Configuration File default: /etc/tripwire/tw.cfg The configuration file stores system-specific information, such as the location of Tripwire data files. The configuration settings are gen- erated during the installation process, but can be changed by the system administrator at any time. See the twconfig(4) man page for a more complete discussion. Policy File default: /etc/tripwire/tw.pol The policy file consists of a series of rules specifying the system objects that Tripwire should monitor, and the data for each object that should be collected and stored in the database file. Should unexpected changes occur, the policy file can describe the person to be noti- fied and the severity of the violation. See the policyguide.txt file in the policy directory and the twpolicy(4) man page for a more com- plete discussion. Database File default: /var/lib/$(HOSTNAME).twd The database file serves as the baseline for integrity checking. After installation, Tripwire creates the initial database file, a "snap- shot" of the filesystem in a known secure state. Later, when an integrity check is run, Tripwire compares each system object described in the policy file against its corresponding entry in the database. A report is created, and if an object has changed outside of constraints defined in the policy file, a violation is reported. See the tripwire(8) and twprint(8) man pages for more information on creating and maintaining database files. Report Files default: /var/lib/tripwire/report/$(HOSTNAME)-$(DATE).twr Once the above three files have been created, Tripwire can run an integrity check and search for any differences between the current system and the data stored in the "baseline" Tripwire database. This information is archived into report files, a collection of rule violations discovered during an integrity check. With the appropriate settings, a report can also be emailed to one or more recipients. See the tripwire(8) and twprint(8) man pages for information on creating and printing report files. Key Files defaults: /etc/tripwire/site.key and /etc/tripwire/$(HOSTNAME)-local.key It is critical that Tripwire files be protected from unauthorized access--an attacker who is able to modify these files can subvert Trip- wire operation. For this reason, all of the above files are signed using public key cryptography to prevent unauthorized modification. Two separate sets of keys protect critical Tripwire data files. One or both of these key sets is necessary for performing almost every Tripwire task. The site key is used to protect files that could be used across several systems. This includes the policy and configuration files. The local key is used to protect files specific to the local machine, such as the Tripwire database. The local key may also be used for sign- ing integrity check reports. See the twadmin(8) man page for more information on keys. File Backup To prevent the accidental deletion of important data, Tripwire automatically creates backup files whenever any Tripwire file is overwrit- ten. The existing file will be renamed with a .bak extension, and the new version of the file will take its place. Only one backup copy for each filename can exist at any time. If a backup copy of a file already exists, the older backup file will be deleted and replaced with the newer one. File backup is an integral part of Tripwire, and cannot be removed or changed. VERSION INFORMATION
This man page describes Tripwire 2.4.1. 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
twintro(8), tripwire(8), twadmin(8), twprint(8), siggen(8), twconfig(4), twpolicy(4) 1 July 2000 TWFILES(5)