1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
|
##############################################
# Configuration for the Prelude LML Sensor #
##############################################
include = @LIBPRELUDE_CONFIG_PREFIX@/default/idmef-client.conf
# Address where the Prelude Manager Server is listening on.
# if value is "127.0.0.1", the connection will occur through
# a UNIX socket.
#
# This entry is disabled. The default is to use the entry
# located in the Prelude system-wide clients.conf. You may
# overwrite the default address for this sensor by uncommenting
# this entry.
#
# [prelude]
# server-addr = 127.0.0.1
# FILES TO MONITOR
#
# You should define the log message prefix-regex and time-format within
# a [format] section. If not specified, the default syslog format will
# be used.
#
# The prefix-regex should contain PCRE named subpatterns to pick out the
# information available in your syslog's prefix.
#
# The available field names are:
# - hostname
# - process
# - pid
# - timestamp
#
# Please see pcrepattern(3) manpage for help writing the prefix-regex.
# In order to set the time-format, please have a look at the strptime(3)
# manpage.
#
# Example configuration for syslog output:
#
# Each [format] section might have several file entries.
# Each [format] section might have several udp-server entries.
#
# If a file or udp-server entry is listed across different formats,
# then the first matching format for a given log entry will be used.
#
# Additionally, you can specify a pattern in a file entry. LML will then
# search for all the pathnames matching the pattern according to the rules
# used by the shell (see glob(7)).
#
# Example: file = /var/log/*/*.log
#
# CHARACTER ENCODING
#
# For each file added to a format, a character encoding can be specified
# using the 'charset' option. Example:
#
# [format=MyFormat]
# charset = ISO-8859-1
# file = /var/log/log1
# file = /var/log/log2
# charset = UTF-8
# file = /var/log/log3
# file = /var/log/*.log
# udp-server = 0.0.0.0
#
# This will set the character set for 'log1' and 'log2' to ISO-8859-1, and
# to UTF-8 for 'log3', any file that matches '/var/log/*.log', and any log
# entry read from the '0.0.0.0' integrated UDP server.
#
# Note that if no character encoding is specified, the system will attempt
# to automatically detect the encoding used. If the detection fails, then
# the system-wide default (retrieved from locale LC_CTYPE) will be used.
#
# ALTERING GENERATED IDMEF EVENTS
#
# Within each format, you might use the 'idmef-alter' option to modify
# generated events:
#
# Example: idmef-alter = alert.analyzer(-1).node.location = MyLocation;
#
# Note that 'idmef-alter' will never overwrite an IDMEF path that is
# already set. Use 'idmef-alter-force' if this is what you intend to do.
#
[format=syslog]
time-format = "%b %d %H:%M:%S"
prefix-regex = "^(?P<timestamp>.{15}) (?P<hostname>\S+) (?:(?P<process>\S+?)(?:\[(?P<pid>[0-9]+)\])?: )?"
file = /var/log/messages
file = /var/log/auth.log
# udp-server = 0.0.0.0
# tcp-server = 0.0.0.0
# tcp-tls-server = 0.0.0.0
# Two TLS modes are available:
# x509: x509 based certificate authentication
# anonymous: Anonymous TLS connection using ANON-ECDH or ANON-DH
#
# Both modes can be combined, and the default value is x509.
# tls-mode = x509 anonymous
# Path for client key, certificate, and certificate authority files.
# tls-key-file = /path/to/client.key
# tls-cert-file = /path/to/client.cert
# tls-ca-file = /path/to/server.ca
# TLS verification options:
#
# When a list of trusted fingerprints and/or a list of trusted names
# is provided, the connecting client has to match one of the provided
# fingerprints/names, otherwise the connection will be refused.
#
# List of trusted client fingerprints (SHA1 and MD5 formats accepted)
# If this option is used, then the connecting peers have to match one of the specified fingerprints.
# tls-trusted-fingerprint = SHA1:ae:8a:e5:97:66:2d:6d:cd:85:29:05:95:31:84:81:f1:27:3b:d1:73
#
# List of trusted client names (takes into account wildcards, and the
# DNSName/IPAddress subject alternative name PKIX extension)
# tls-trusted-name =
#
# Client certificate verification option (default is client-cert-required):
# client-cert-required: client has to provide a valid certificate for the authentication to succeed.
# client-cert-optional: client may connect without providing a valid x509 certificate.
# tls-verify = client-cert-required
#
# Sample configuration for metalog:
#
#[format=metalog]
#prefix-regex = "^(?P<timestamp>.{15}) \[(?P<process>\S+)\] "
#time-format = "%b %d %H:%M:%S"
#file = /var/log/everything/current
#
# Sample configuration for apache:
#
# Note: For apache >= 2.4, you need to force ErrorLogFormat in apache configuration:
# ErrorLogFormat "[%t] [%l] [pid %P] %F: %E: [client %a] %M"
[format=apache]
time-format = "%d/%b/%Y:%H:%M:%S"
prefix-regex = "(?P<hostname>\S+) \S+ \S+ \[(?P<timestamp>.{20}) [+-].{4}\] "
file = /var/log/apache2/access.log
[format=apache-error]
time-format = "%a %b %d %H:%M:%S %Y"
prefix-regex = "^\[(?P<timestamp>.{24})\] \S+ (\[client (?P<hostname>\S+)\] )?"
file = /var/log/apache2/error.log
#
# Sample configuration for asterisk:
#
#[format=asterisk]
#time-format = "%b %d %H:%M:%S"
#prefix-regex = "^(?P<timestamp>.{15}) (?P<hostname>\S+) (?:(?P<process>\S+?)(?:\[(?P<pid>[0-9]+)\])? (\S*): )?"
#file = /var/log/asterisk/messages
#
# Specifies the maximum length of logs, in bytes.
# If the log exceeds this size, it will be split into several parts,
# each one processed successively et independently of each other.
#
# log-max-length = 8192
#
# Specifies the maximum difference, in seconds and/or size, between
# the interval of two logfile rotations. If this difference is reached,
# a high severity alert will be emitted. The K (kbytes) or M (mbytes)
# suffix might be used for size definition.
#
#max-rotation-size-offset = 1024
#max-rotation-time-offset = 300
#
# Maximum number of warnings a given source should emit in case it can
# not parse log entries with the provided prefix_regex and time_format.
#
# -1 == unlimited number of warnings
# 0 == no warning at all
# X == print at most X warnings.
#
# warning-limit = -1
#####################################
# Here starts plugins configuration #
#####################################
[Pcre]
ruleset=@configdir@/ruleset/pcre.rules
# [Debug]
#
# This plugin issues an alert for each packet.
# Careful to the logging activity it generates.
#
# Trigger reporting to the console.
# stderr
#######################
# Global TLS settings #
#######################
#
# Number of bits for the prime used in the Diffie-Hellman key exchange.
# Note that the value should be one of 768, 1024, 2048, 3072 or 4096.
# The default is 1024.
#
# dh-prime-length = 1024
#
# How often to regenerate the parameters used in the Diffie-Hellman key
# exchange. These should be discarded and regenerated once a day, once
# a week or once a month, depending on the security requirements.
#
# Generation is a CPU-intensive operation. The value is in hours,
# 0 disables regeneration entirely. The default is 24 hours.
#
# dh-parameters-regenerate = 24
|
