1TWFILES(5)                    File Formats Manual                   TWFILES(5)
2
3
4

NAME

6       twfiles - overview of files used by Tripwire and file backup process
7

DESCRIPTION

9   Configuration File
10       default: /etc/tripwire/tw.cfg
11       The configuration file stores system-specific information, such as the
12       location of Tripwire data files. The configuration settings are gener‐
13       ated during the installation process, but can be changed by the system
14       administrator at any time.  See the twconfig(4) man page for a more
15       complete discussion.
16
17   Policy File
18       default: /etc/tripwire/tw.pol
19       The policy file consists of a series of rules specifying the system
20       objects that Tripwire should monitor, and the data for each object that
21       should be collected and stored in the database file.  Should unexpected
22       changes occur, the policy file can describe the person to be notified
23       and the severity of the violation.  See the policyguide.txt file in the
24       policy directory and the twpolicy(4) man page for a more complete dis‐
25       cussion.
26
27   Database File
28       default: /var/lib/$(HOSTNAME).twd
29       The database file serves as the baseline for integrity checking.  After
30       installation, Tripwire creates the initial database file, a "snapshot"
31       of the filesystem in a known secure state.  Later, when an integrity
32       check is run, Tripwire compares each system object described in the
33       policy file against its corresponding entry in the database.  A report
34       is created, and if an object has changed outside of constraints defined
35       in the policy file, a violation is reported.  See the tripwire(8) and
36       twprint(8) man pages for more information on creating and maintaining
37       database files.
38
39   Report Files
40       default: /var/lib/tripwire/report/$(HOSTNAME)‐$(DATE).twr
41       Once the above three files have been created, Tripwire can run an
42       integrity check and search for any differences between the current sys‐
43       tem and the data stored in the "baseline" Tripwire database.  This
44       information is archived into report files, a collection of rule viola‐
45       tions discovered during an integrity check.  With the appropriate set‐
46       tings, a report can also be emailed to one or more recipients.  See the
47       tripwire(8) and twprint(8) man pages for information on creating and
48       printing report files.
49
50   Key Files
51       defaults: /etc/tripwire/site.key and /etc/tripwire/$(HOST‐
52       NAME)‐local.key
53       It is critical that Tripwire files be protected from unauthorized
54       access‐‐an attacker who is able to modify these files can subvert Trip‐
55       wire operation.  For this reason, all of the above files are signed
56       using public key cryptography to prevent unauthorized modification.
57       Two separate sets of keys protect critical Tripwire data files.  One or
58       both of these key sets is necessary for performing almost every Trip‐
59       wire task.
60
61       The site key is used to protect files that could be used across several
62       systems.  This includes the policy and configuration files.  The local
63       key is used to protect files specific to the local machine, such as the
64       Tripwire database.  The local key may also be used for signing
65       integrity check reports.  See the twadmin(8) man page for more informa‐
66       tion on keys.
67
68   File Backup
69       To prevent the accidental deletion of important data, Tripwire automat‐
70       ically creates backup files whenever any Tripwire file is overwritten.
71       The existing file will be renamed with a .bak extension, and the new
72       version of the file will take its place.  Only one backup copy for each
73       filename can exist at any time.  If a backup copy of a file already
74       exists, the older backup file will be deleted and replaced with the
75       newer one.
76
77       File backup is an integral part of Tripwire, and cannot be removed or
78       changed.
79

VERSION INFORMATION

81       This man page describes Tripwire 2.4.1.
82

AUTHORS

84       Tripwire, Inc.
85

COPYING PERMISSIONS

87       Permission is granted to make and distribute verbatim copies of this
88       man page provided the copyright notice and this permission notice are
89       preserved on all copies.
90
91       Permission is granted to copy and distribute modified versions of this
92       man page under the conditions for verbatim copying, provided that the
93       entire resulting derived work is distributed under the terms of a per‐
94       mission notice identical to this one.
95
96       Permission is granted to copy and distribute translations of this man
97       page into another language, under the above conditions for modified
98       versions, except that this permission notice may be stated in a trans‐
99       lation approved by Tripwire, Inc.
100
101       Copyright 2000 Tripwire, Inc. Tripwire is a registered trademark of
102       Tripwire, Inc. in the United States and other countries. All rights
103       reserved.
104

SEE ALSO

106       twintro(8), tripwire(8), twadmin(8), twprint(8), siggen(8), twcon‐
107       fig(4), twpolicy(4)
108
109
110
111                                  1 July 2000                       TWFILES(5)
Impressum