Syscheck is the name of the integrity checking process inside OSSEC. It runs periodically to check if any configured file (or registry entry on Windows) has changed.
This is the explanation from the OSSEC book:
There are multiple types of attacks and many attack vectors, but there is one thing unique about all of them: they leave traces and always change the system in some way. From viruses that modify a few files, to kernel-level rootkits that alters the kernel, there is always some change in the integrity of the system.
Integrity checking is an essential part of intrusion detection, that detects changes in the integrity of the system. OSSEC does that by looking for changes in the MD5/SHA1 checksums of the key files in the system and on the Windows registry.
The way it works is that the agent scans the system every few hours (user defined) and send all the checksums to the server. The server stores the checksums and look for modifications on them. An alert is sent if anything changes.
ossec-syscheckd is able to check file integrity in near realtime on Windows and modern Linux distros. Windows comes with support out of the box, but on Linux systems inotify packages may need to be installed. Check for inotify dev packages, and possibly an inotify-tools package.
These configuration options can be specified in each agent’s ossec.conf file, except for the auto_ignore and alert_new_file which apply to manager and local installs. The ignore option applies to all agents if specified on the manager.
Use this option to add or remove directories to be monitored (they must be comma separated). All files and subdirectories will also be monitored. Drive letters without directories are not valid. At a minimum the ‘.’ should be included (D:\.).
- This will enable realtime/continuous monitoring on Linux (using the inotify system calls) and Windows systems.
- Report diffs of file changes. This is limited to text files at this time.
This option is only available on Unix-like systems.
- All the following check_* options are used together.
Check the md5 and sha1 hashes of the of the files will be checked.
This is the same as using both check_sha1sum=”yes” and check_md5sum=”yes”
- When used only the sha1 hash of the files will be checked.
- The md5 hash of the files will be checked.
- The size of the files will be checked.
- Check the owner of the files selected.
- Check the group owner of the files/directories selected.
- Check the UNIX permission of the files/directories selected. On windows this will only check the POSIX permissions.
- A string that will limit checks to files containing that string in the file name.
Allowed: Any directory or file name (but not a path)
List of files or directories to be ignored (one entry per element). The files and directories are still checked, but the results are ignored.
- This is a simple regex pattern to filter out files so alerts are not generated.
Allowed: Any directory or file name
Frequency that the syscheck is going to be executed (in seconds).
The default is 6 hours or 21600 seconds
Allowed: Time in seconds
Time to run the scans (can be in the formats of 21pm, 8:30, 12am, etc)
Allowed: Time to run scan
Day of the week to run the scans (can be in the format of sunday, saturday, monday, etc)
Allowed: Day of the week
Specifies if syscheck will ignore files that change too often (after the third change)
Valid: server, local
Specifies if syscheck should alert on new files created.
Valid: server, local
Specifies if syscheck should do the first scan as soon as it is started.
Use this option to add Windows registry entries to be monitored (Windows-only).
Allowed: Any registry entry (one per element)
List of registry entries to be ignored.
Allowed: Any registry entry (one per element)
Command to run to prevent prelinking from creating false positives.
This option can potentially impact performance negatively. The configured command will be run for each and every file checked.
To configure syscheck, a list of files and directories must be provided. The check_all option checks md5, sha1, owner, and permissions of the file.
<syscheck> <directories check_all="yes">/etc,/usr/bin,/usr/sbin</directories> <directories check_all="yes">/root/users.txt,/bsd,/root/db.html</directories> </syscheck>
Files and directories can be ignored using the ignore option (or registry_ignore for Windows registry entries):
<syscheck> <ignore>/etc/random-seed</ignore> <ignore>/root/dir</ignore> <ignore type="sregex">.log$|.tmp</ignore> </syscheck>
The type attribute can be set to sregex to specify a Regular Expression Syntax in the ignore option.
<syscheck> <ignore type="sregex">^/opt/application/log</ignore> </syscheck>
A local rule can be used to modify the severity for changes to specific files or directories:
<rule id="100345" level="12"> <if_matched_group>syscheck</if_matched_group> <match>/var/www/htdocs</match> <description>Changes to /var/www/htdocs - Critical file!</description> </rule>
In the above example, a rule was created to alert with high severity (12) for changes to the files in the htdocs directory.
OSSEC supports realtime (continuous) file integrity monitoring on Linux (support was added kernel version 2.6.13) and Windows systems.
The configuration is very simple. In the <directories> option where you specify what directories to monitor, adding realtime="yes" will enable it. For example:
<syscheck> <directories realtime="yes" check_all="yes">/etc,/usr/bin,/usr/sbin</directories> <directories check_all="yes">/bin,/sbin</directories> </syscheck>
In this case, the directories /etc, /usr/bin and /usr/sbin will be monitored in real time. The same applies to Windows too.
The real time monitoring will not start immediately. First ossec-syscheckd needs to scan the file system and add each sub-directory to the realtime queue. It can take up to 30 minutes for this to finish (wait for the log “ossec-syscheckd: INFO: Starting real time file monitoring” ).
Real time only works with directories, not individual files. So you can monitor the /etc or C:\program files directory, but not an individual file like /etc/file.txt.
Both rootcheck and syscheck runs on the same thread, so when rootcheck is running, the inotify events would get queued until it finishes.
OSSEC supports sending diffs when changes are made to text files on Linux and unix systems.
Configuring syscheck to show diffs is simple, add report_changes="yes" to the <directories option.
<syscheck> <directories report_changes="yes" check_all="yes">/etc</directories> <directories check_all="yes">/bin,/sbin</directories> </syscheck>
Run agent control tool to perform a integrity checking immediately (option -a to run on all the agents and -u to specify an agent id)# /var/ossec/bin/agent_control -r -a # /var/ossec/bin/agent_control -r -u <agent_id>
For more information see the agent_control documentation.
Set the option <scan_on_start> to “no” on ossec.conf
Set the file/directory name in the <ignore> option or create a simple local rule.
The following one will ignore files /etc/a and /etc/b and the directory /etc/dir for agents mswin1 and ubuntu-dns:<rule id="100345" level="0" > <if_group>syscheck</if_group> <description>Changes ignored.</description> <match>/etc/a|/etc/b|/etc/dir</match> <hostname>mswin1|ubuntu-dns</hostname> </rule>
No idea. So if there are some directories you do not want scanned at all, make sure they are not included in a <directories> configuration.
Use the agent_control tool on the manager, to see this information.
More information see the agent_control documentation.
Use the syscheck_control tool on the manager or the web ui for that.
More information see the syscheck_control documentation.
With ossec 1.3 and Fedora you may run into this problem:
You have named files you’d like ossec to monitor so you add:
<ossec_config> <syscheck> <directories check_all="yes">/var/named</directories>
to ossec.conf on the client. Fedora – at least as of version 7 – runs named in a chroot jail under /var/named/chroot. However, part of that chroot jail includes /var/named/chroot/proc. The contents of that directory are purely ephemeral; there is no value to checking their integrity. And, at least in ossec 1.3, your syscheck may stall trying to read those files.
The symptom is a syscheck database on the server that never grows beyond a file or two per restart of the client. The log monitoring continues to work, so you know it’s not a communication issue, and you will often see a slight increase in syscheck database file size after the client has restarted (in one case about 20 minutes after). But the database will never be completely built; there will only be a couple files listed in datebase.
The solution is to add an ignore clause to ossec.conf on the client:
<ossec_config> <syscheck> <ignore>/var/named/chroot/proc</ignore>
By deffault OSSEC does not alert on new files. To enable this functionlity, <alert_new_files> must be set to yes inside the <syscheck> section of the manager’s ossec.conf. Also, the rule to alert on new files (rule 554) is set to level 0 by default. The alert level will need to be raised in order to see the alert.
Add the following to local_rules.xml:
<rule id="554" level="10" overwrite="yes"> <category>ossec</category> <decoded_as>syscheck_new_entry</decoded_as> <description>File added to the system.</description> <group>syscheck,</group> </rule>
The <alert_new_files> entry should look something like this:
In short, no. OSSEC does not track this information. You could use your OS’s auditing facilities to track this information, and create a rule to alert when an appropriate log is created.