Ossec Manual

OSSEC Documentation
Release 2.8.1
Jeremy Rossi
October 04, 2014
Contents
Manual & FAQ

1.1 Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 User submitted Cookbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Development
97
2.1 Build, compile, and not much more . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
2.2 oRFC: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Reference
3.1 Syntax and Options . . . . . . . .
3.2 Output Formats . . . . . . . . . .
3.3 Man pages . . . . . . . . . . . .
3.4 Whats new . . . . . . . . . . . .
3.5 Rootcheck / Syscheck Reference .
3.6 Glossary . . . . . . . . . . . . .
Indices and tables
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
3
81
94
105
105
145
145
175
177
182
183
ii
OSSEC Documentation, Release 2.8.1
OSSEC is an Open Source Host-based Intrusion Detection System. It performs log analysis, integrity checking,
Windows registry monitoring, rootkit detection, real-time alerting and active response. It runs on most operating
systems, including Linux, OpenBSD, FreeBSD, Mac OS X, Solaris and Windows. A list with all supported platforms
is available at: Supported Systems
Contents
Contents
CHAPTER 1
Manual & FAQ
1.1 Manual
1.1.1 Getting started with OSSEC
OSSEC is a full platform to monitor and control your systems. It mixes together all the aspects of HIDS (host-based
intrusion detection), log monitoring and SIM/SIEM together in a simple, powerful and open source solution. It is also
backed and fully supported by Trend Micro.
Key Benefits
Compliance Requirements
OSSEC helps customers meet specific compliance requirements such as PCI, HIPAA etc. It lets customers detect and
alert on unauthorized file system modifications and malicious behavior embedded in the log files of COTS products as
well as custom applications. For PCI, it covers the sections of file integrity monitoring (PCI 11.5, 10.5), log inspection
and monitoring (section 10) and policy enforcement/checking.
Multi platform
OSSEC lets customers implement a comprehensive host based intrusion detection system with fine grained application/server specific policies across multiple platforms such as Linux, Solaris, AIX, BSD, Windows, Mac OS X and
VMware ESX.
Real-time and Configurable Alerts
OSSEC lets customers configure incidents they want to be alerted on which lets them focus on raising the priority of
critical incidents over the regular noise on any system. Integration with smtp, sms and syslog allows customers to be
on top of alerts by sending these on to e-mail and handheld devices such as cell phones and pagers. Active response
options to block an attack immediately is also available.
Integration with current infrastructure
OSSEC will integrate with current investments from customers such as SIM/SEM (Security Incident Management/Security Events Management) products for centralized reporting and correlation of events.
Centralized management
OSSEC provides a simplified centralized management server to manage policies across multiple operating systems.
Additionally, it also lets customers define server specific overrides for finer grained policies.
Agent and agentless monitoring
OSSEC offers the flexibility of agent based and agentless monitoring of systems and networking components such
as routers and firewalls. It lets customers who have restrictions on software being installed on systems (such as FDA
approved systems or appliances) meet security and compliance needs.
Key Features
File Integrity checking
There is one thing in common to any attack to your networks and computers: they change your systems in some way.
The goal of file integrity checking (or FIM - file integrity monitoring) is to detect these changes and alert you when
they happen. It can be an attack, or a misuse by an employee or even a typo by an admin, any file, directory or registry
change will be alerted to you.
Covers PCI DSS sections 11.5 and 10.5.5.
Log Monitoring
Your operating system wants to speak to you, but do you know how to listen? Every operating system, application,
and device on your network generate logs (events) to let you know what is happening. OSSEC collects, analyzes and
correlates these logs to let you know if something wrong is going on (attack, misuse, errors, etc). Do you want to know
when an application is installed on your client box? Or when someone changes a rule in your firewall? By monitoring
your logs, OSSEC will let you know of that.
Covers PCI DSS section 10 in a whole.
Rootkit detection
Criminals (also known as hackers) want to hide their actions, but using rootkit detection you can be notified when they
(or trojans, viruses, etc) change your system in this way.
Active response
Take immediate and automatic responses when something happens. Why wait for hours when you can alert your
admin and block an attack right way?
1.1.2 OSSEC Architecture

OSSEC is composed of multiple pieces. It has a central manager for monitoring and receiving information from
agents, syslog, databases, and from agentless devices.
Chapter 1. Manual & FAQ
Manager (or Server)

The manager is the central piece of the OSSEC deployment. It stores the file integrity checking databases, the logs,
events, and system auditing entries. All the rules, decoders, and major configuration options are stored centrally in the
manager; making it easy to administer even a large number of agents.
Note: The manager may be called the OSSEC server, or even just server in this documentation.
Agents
The agent is a small program, or collection of programs, installed on the systems to be monitored. The agent will
collect information and forward it to the manager for analysis and correlation. Some information is collected in real
time, others periodically. It has a very small memory and CPU footprint by default, not affecting the system?x80x99s
usage.
Agent security: It runs with a low privilege user (generally created during the installation) and inside a chroot jail
isolated from the system. Most of the agent configuration can be pushed from the manager.
Agentless
For systems that an agent cannot be installed on, the agentless support may allow integrity checks to be performed.
Agentless scans can be used to monitor firewalls, routers, and even Unix systems.
Virtualization/VMware
OSSEC allows you to install the agent on the guest operating systems. It may also be installed inside some versions
of VMWare ESX, but this may cause support issues. With the agent installed inside VMware ESX you can get alerts
about when a VM guest is being installed, removed, started, etc. It also monitors logins, logouts and errors inside the
ESX server. In addition to that, OSSEC performs the Center for Internet Security (CIS) checks for VMware, alerting
if there is any insecure configuration option enabled or any other issue.
Firewalls, switches and routers
OSSEC can receive and analyze syslog events from a large variety of firewalls, switches and routers. It supports
all Cisco routers, Cisco PIX, Cisco FWSM, Cisco ASA, Juniper Routers, Netscreen firewall, Checkpoint and many
others.
Architecture
This diagram shows the central manager receiving events from the agents and system logs from remote devices. When
something is detected, active responses can be executed and the admin is notified.
1.1. Manual
Internal Architecture
For technical and deep detailed information on how it works, please read the following documents:
OSSEC log analysis/inspection architecture (PDF) - by Daniel Cid
Support
Everyone knows that support and technical expertise are critical in ensuring the success of any product deployment.
With an open source project this is not different. If you need enterprise-class commercial support for OSSEC, Trend
Micro, the company behind this great open source project, offers this option to our users. For more information, visit
the OSSEC commercial support page.
1.1.3 Supported Systems

OSSEC supports the following operating systems and log formats.
Operating Systems
The following operating systems are supported by the OSSEC agent:
GNU/Linux (all distributions, including RHEL, Ubuntu, Slackware, Debian, etc)
Windows XP, 2003, Vista, 2008
VMWare ESX 3.0,3.5 (including CIS checks)
6
FreeBSD (all current versions)

OpenBSD (all current versions)
NetBSD (all current versions)
Solaris 2.7, 2.8, 2.9 and 10
AIX 5.2 and 5.3
Mac OS X 10.x
HP-UX 11
Devices supported via Syslog
These systems/devices are also supported via remote syslog:
Cisco PIX, ASA and FWSM (all versions)
Cisco IOS routers (all versions)
Juniper Netscreen (all versions)
SonicWall firewall (all versions)
Checkpoint firewall (all versions)
Cisco IOS IDS/IPS module (all versions)
Sourcefire (Snort) IDS/IPS (all versions)
Dragon NIDS (all versions)
Checkpoint Smart Defense (all versions)
McAfee VirusScan Enterprise (v8 and v8.5)
Bluecoat proxy (all versions)
Cisco VPN concentrators (all versions)
VMWare ESXi 4.x
Devices and Operating Systems via Agentless
Using OSSEC agentless options, the following systems are also supported (for log analysis and file integrity checking):
Cisco PIX, ASA and FWSM (all versions)
Cisco IOS routers (all versions)
Juniper Netscreen (all versions)
SonicWall firewall (all versions)
Checkpoint firewall (all versions)
All operating systems specified in the operating systems section
1.1.4 Installation
The best installation tutorial is available in the OSSEC book.
1.1. Manual
Installations requirements
For UNIX systems, OSSEC only requires gnu make, gcc, libc, and preferably OpenSSL. However, you always have
the option to pre-compile it on one system and move the binaries to the final box.
Ubuntu
On Ubuntu you will need the build-essential package in order to compile and install OSSEC.
To install the package run the following command.
# apt-get install build-essential
If database support is needed mysql-dev or postgresql-dev should be installed. Run the following command to install
these packages.
# apt-get install mysql-dev postgresql-dev
RedHat
RedHat should have all packages needed by default, but if database support is needed the package mysql-devel and/or
postgresql-devel will need to be installed.
# yum install mysql-devel postgresql-devel
Debian
Debian has replaced bash with dash, and this may cause issues during installation. Dash does not appear to support all
of the features available in other shells, and may display an error when trying to set the servers IP address on an agent
system. The error can be ignored, but the server ip address will need to be set.
Do this by making sure something like the following information is in the agents ossec.conf:
<ossec_config>
<client>
<server-ip>SERVERS IP</server-ip>
</client>
This can also be avoided by using bash to run install.sh:

# bash ./install.sh
Manager/Agent Installation
Installation of OSSEC HIDS is very simple, the install.sh shell script automating most of it. There are a few
questions to be answered before the installation will occur, one of the most important being which type of installation
is desired. It is important to choose the correct installation type: server, agent, local, or hybrid. More information on
thse can be found on the OSSEC Architecture page.
Note: In the following installation the commands follow the #. Everything else is either comments out output.
1. Download the latest version and verify its checksum.
Note: On some systems, the command md5, sha1, or wget may not exist. Try md5sum, sha1sum or lynx
respectively instead.
Warning:
manner.
wget cannot pull files from the OSSEC site. Obtain the checksum file by some other
# wget -U ossec http://www.ossec.net/files/ossec-hids-2.8.1.tar.gz

# wget -U ossec http://www.ossec.net/files/ossec-hids-2.8.1-checksum.txt
# cat ossec-hids-2.8.1-checksum.txt
MD5(ossec-hids-2.8.1.tar.gz)= c2ffd25180f760e366ab16eeb82ae382
SHA1(ossec-hids-2.8.1.tar.gz)= 0ecf1df09558dc8bb4b6f65e1fb2ca7a7df9817c
# md5sum ossec-hids-2.8.1.tar.gz
# sha1sum ossec-hids-2.8.1.tar.gz
2. Extract the compressed package and run the install.sh script. It will guide you through the installation.
# tar -zxvf ossec-hids-*.tar.gz (or gunzip -d; tar -xvf)
# cd ossec-hids-*
# ./install.sh
3. The OSSEC manager listens on UDP port 1514. Any firewall sbetween the agents and the manager will need to
allow this traffic.
4. The server, agent, and hybrid installations will require additional configuration. More information can be found
on the Managing the agents page.
5. Start OSSEC HIDS by running the following command:
# /var/ossec/bin/ossec-control start
Windows Agent Installation

Binary Installation
OSSEC is typically compiled on each system it is installed on, but this may not always be easy. To help in these cases
there are a few methods of binary installation available. OSSEC can be compiled on one system, and copied to the
destination systems. There are also plans for RPM and Debian packages.
Note: OSSEC has very limited cross compiling facilities. Windows binaries can be built on Linux systems, but
binaries for other systems should be built on a system of the same OS and CPU platform.
Compiling OSSEC for install on a second server
First download the OSSEC package corresponding to the version you want to install and unpack it (on the system with
a compiler).
# tar -zxvf ossec-hids-latest.tar.gz
Enter in the source directory of the downloaded package, and configure OSSEC to build the agent version. The
make commands should compile the correct binaries.
1.1. Manual
#
#
#
#
cd ossec-*/src
make setagent
make all
make build
Modify ossec-hids-*/etc/preloaded-vars.conf to set BINARY_INSTALL to yes.

# echo "USER_BINARYINSTALL=\"y\"" >> ossec-hids*/etc/preloaded-vars.conf
Finally create an OSSEC package.

# tar -cvf ossec-binary.tar ossec-hids*
Installation of the binary OSSEC package
On the target system (that does not have a C compiler) download your ossec-binary.tar created in the steps above.
Complete the installation by unarchiving the binary package and running ./install.sh.
# tar xfv ossec-binary.tar
# cd ossec-*
# ./install.sh
After following the installation prompts the install will be complete.

Server Virtual Appliance Installation
Overview:
The OSSEC virtual appliance is a virtual system in the Open Virtualized Format (OVF). It contains an OSSEC 2.7
server installation and the WebUI (0.8 Beta).
Accounts and passwords:
The default password for all accounts on the system is _0ssec_. The username from the WebUI is user, and for
phpMyAdmin it is root.
Convert OVF to a VMWare image:
Some VMWare desktop environments may not support the OVF images natively, for those systems VMWare created
the ovftool. Download the ovftool from VMWares site (registration required).
Convert the file using the following procedure:
# tar zxvf ossec_virtual_apliance.tar.gz
# cd ossec_virtual_appliance
# ovftool ossec.ovf ossec.vmx
Unattended Source Installation

OSSEC has the capability to be compiled and installed without the interactivity of install.sh. The install script
can collect the answers to its questions from the etc/preloaded-vars.conf configuration file.
10
Most of the questions asked by the installer are present in the configuration file, along with the default answers.
Uncommenting each variable will allow the script to know the answer. Any changes from the default install should be
made in the configuration file.
Note: If USER_NO_STOP="y" is not set, install.sh may prompt for confirmation.
Example preloaded-vars.conf:
#
#
#
#
#
#
preloaded-vars.conf, Daniel B. Cid (dcid @ ossec.net).
#
#
#
#
#
PLEASE NOTE:
When we use "n" or "y" in here, it should be changed
to "n" or "y" in the language your are doing the
installation. For example, in portuguese it would
be "s" or "n".
Use this file to customize your installations.

It will make the install.sh script pre-load some
specific options to make it run automatically
or with less questions.
# USER_LANGUAGE defines
# It can be "en", "br",
# In case of an invalid
# to English "en"
#USER_LANGUAGE="en"
#USER_LANGUAGE="br"
to language to be used.
"tr", "it", "de" or "pl".
language, it will default
# For english
# For portuguese
# If USER_NO_STOP is set to anything, the confirmation

# messages are not going to be asked.
#USER_NO_STOP="y"
# USER_INSTALL_TYPE defines the installation type to

# be used during install. It can only be "local",
# "agent" or "server".
#USER_INSTALL_TYPE="local"
#USER_INSTALL_TYPE="agent"
#USER_INSTALL_TYPE="server"
# USER_DIR defines the location to install ossec

#USER_DIR="/var/ossec"
# If USER_DELETE_DIR is set to "y", the directory

# to install OSSEC will be removed if present.
#USER_DELETE_DIR="y"
# If USER_ENABLE_ACTIVE_RESPONSE is set to "n",

# active response will be disabled.
#USER_ENABLE_ACTIVE_RESPONSE="y"
# If USER_ENABLE_SYSCHECK is set to "y",
1.1. Manual
11
# syscheck will be enabled. Set to "n" to

# disable it.
#USER_ENABLE_SYSCHECK="y"
# If USER_ENABLE_ROOTCHECK is set to "y",

# rootcheck will be enabled. Set to "n" to
# disable it.
#USER_ENABLE_ROOTCHECK="y"
# If USER_UPDATE is set to anything, the update

# installation will be done.
#USER_UPDATE="y"
# If USER_UPDATE_RULES is set to anything, the
# rules will also be updated.
#USER_UPDATE_RULES="y"
# If USER_BINARYINSTALL is set, the installation
# is not going to compile the code, but use the
# binaries from ./bin/
#USER_BINARYINSTALL="x"
### Agent Installation variables. ###

#
#
#
#
#
Specifies the IP address or hostname of the

ossec server. Only used on agent installations.
Choose only one, not both.
USER_AGENT_SERVER_IP="1.2.3.4"
USER_AGENT_SERVER_NAME
# USER_AGENT_CONFIG_PROFILE specifies the agents config profile

# name. This is used to create agent.conf configuration profiles
# for this particular profile name. Only used on agent installations.
# Can be any string. E.g. LinuxDBServer or WindowsDomainController
#USER_AGENT_CONFIG_PROFILE="generic"
### Server/Local Installation variables. ###

# USER_ENABLE_EMAIL enables or disables email alerting.
#USER_ENABLE_EMAIL="y"
# USER_EMAIL_ADDRESS defines the destination e-mail of the alerts.
#USER_EMAIL_ADDRESS="dcid@test.ossec.net"
# USER_EMAIL_SMTP defines the SMTP server to send the e-mails.
#USER_EMAIL_SMTP="test.ossec.net"
# USER_ENABLE_SYSLOG enables or disables remote syslog.

#USER_ENABLE_SYSLOG="y"
12
# USER_ENABLE_FIREWALL_RESPONSE enables or disables

# the firewall response.
#USER_ENABLE_FIREWALL_RESPONSE="y"
# Enable PF firewall (OpenBSD and FreeBSD only)

#USER_ENABLE_PF="y"
# PF table to use (OpenBSD and FreeBSD only).

#USER_PF_TABLE="ossec_fwtable"
# USER_WHITE_LIST is a list of IPs or networks

# that are going to be set to never be blocked.
#USER_WHITE_LIST="192.168.2.1 192.168.1.0/24"
#### exit ? ###
Compiling the OSSEC Windows Agent on Windows

Note: Originally posted Compiling the OSSEC Windows Agent on Windows by mstarks, duplicated here with
permission.
Most people that use the OSSEC Windows agent download a pre-compiled copy from the OSSEC site. While that
is a good option for many individual users, it may not suit those with more specific needs and/or those in enterprise
environments. Users who fall into those categories could benefit from customizing the agent and maintaining internal
builds in order to suit their individual needs.
There are already instructions on how to compile the Windows agent on Linux, but ironically the process doesnt work
so well on Windows. I had a need to make this work on Windows, so I thought I would share the process with you.
Requirements:
The Nullsoft Scriptable Install System (NSIS)

The Minimalist GNU for Windows (MinGW) compiler http://sourceforge.net/downloads/mingw/>_
My batch file. Simply rename from gen_win.txt to gen_win.cmd.
7-Zip for Windows
The public domain Unix2DOS utility
The latest OSSEC for Unix/Linux <http://www.ossec.net/main/downloads/>_ (this contains the Windows
source code)
Here are the steps:
1. Download and install the required programs. Be sure to pay special attention to the steps for properly installing
and configuring MinGW, particularly the part about modifying the PATH environment variable.
2. Next, we.re going to extract OSSEC using 7-Zip. To do so, simply right-click on the file and select 7-Zip, extract
to folder name.tar, where folder name is the name of the package. This decompresses the archive. Navigate
1.1. Manual
13
within that folder and repeat this step to untar the archive. At this point, you should see all of the files in the
package.
3. Place gen_win.txt in the srcwin32 folder and rename the extension to .cmd.
4. Download Unix2DOS and place it in the srcwin32 folder
5. Open a command prompt. Navigate to srcwin32, make any desired customizations, and execute gen_win.cmd.
This should gather all of the required files and place them in srcwin-pkg.
6. Next, we compile the Windows agent by navigating to srcwin-pkg and executing make.bat (I assume you have
the chops to know how to change directories :) ).
7. Now we have all of the files we need but no way to effectively install it. To generate the installer, simply execute
the NSIS compiler like so: "c:\Program Files\NSIS\makensis.exe" ossec-installer.nsi
If you see no errors and a binary named ossec-win32-agent.exe, everything was successful. Congratulations, you now
have a custom-made version of OSSEC!
Compiling OSSEC with ming:
OSSECs Windows agent is compiled using MinGW
It has always been a pain to generate snapshots for Windows because it required me to open up my Windows VM
(slow), push the code there, compile, etc. Well, until this week when I started to play with MinGW cross-compilation
feature to completely build an Windows agent from Linux.
How it works? First, you need to install MinGW and nsis (to build the installer). For OpenSSL support, an OpenSSL
MinGW package will also be necessary.
After that, download the source and generate the Windows package directory (replace 2.6 with the latest version or
download the latest source here):
Note: On some systems, the command md5, sha1, or wget may not exist. Try md5sum, sha1sum or lynx
respectively instead.
Warning:
manner.
wget cannot pull files from the OSSEC site. Obtain the checksum file by some other

# wget -U ossec http://www.ossec.net/files/ossec-hids-2.8.1-checksum.txt
# cat ossec-hids-2.8.1-checksum.txt
# md5sum ossec-hids-2.8.1.tar.gz
# sha1sum ossec-hids-2.8.1.tar.gz
And generate the Windows package directory:

# cd ossec-hids-2.8.1/src/win32
# ./gen-win.sh
Now, you will have the win-pkg directory under src. Just go there and run make.sh. Your Windows agent package
should be created in a few minutes:
Note: The make.sh script may require modification depending on the Linux distribution used.
14
# cd ../win-pkg
# sh ./make.sh
You will see the following in the screen:

Making windows agent
rootcheck/win-common.c: In function "__os_winreg_querykey":
rootcheck/win-common.c:279: warning: pointer targets in passing argument 7 of "RegEnumValueA" differ
win-registry.c: In function "os_winreg_querykey":
...
Output: "ossec-win32-agent.exe"
Install: 7 pages (448 bytes), 3 sections (3144 bytes), 379 instructions (10612 bytes), 247 strings (4
Uninstall: 5 pages (320 bytes),
1 section (1048 bytes), 301 instructions (8428 bytes), 166 strings (2646 bytes), 1 language table (29
Datablock optimizer saved 8371 bytes (~0.7%).
Which means that your agent executable ossec-win32-agent.exe has been created properly.
Intergration and Deployment with cfengine
I recently required a larger deployment of OSSEC-HIDS without too much manual intervention. Almost every
OSSEC-HIDS tutorial Ive across says this is possible, yet I was unable to find a tutorial demonstrating it. So, in
the spirit of open source, Im contributing a brief overview.
Prerequisites:
In order to facilitate the key request, I chose to generate a file with the relevant information and copy it back to my
cfmaster server. I developed the following tutorial to demonstrate a cfengine copy back scenario: Copy Back with
cfengine.
Configuring the cfengine clients:
I added a group to my cfagent.conf for my ossec server named: hg_ossec_server (host group). I then
created an ossec-hids.cf containing the following:
control
My control sections sets up the variables Ill be using in the rest of the file.
control:
any::
ossec_key_dir = (/usr/local/cfkeys/ossec)
ossec_req_dir = ( $(util_updir)/ossec )
package
Im using yum to automatically install OSSEC-HIDS from my local RPM Repository.
packages:
!hg_ossec_server::
ossec-hids
ossec-hids-client
action=install
action=install
links
1.1. Manual
15
The Links section just links ossec-agent.conf to ossec.conf on the clients.

links:
!hg_ossec_server::
/var/ossec/etc/ossec.conf -> /var/ossec/etc/ossec-agent.conf
copy
I manage the ossec-agent.conf in cfengine, because my cfengine configurations are all stored in a subversion
repository. The first stanza in copy just pushes the most recent copy of the ossec-agent.conf file to my network,
setting the dynamic class dc_restart_ossec if the copy occurs.
copy:
!hg_ossec_server::
$(distribute)/ossec-agent.conf
dest=/var/ossec/etc/ossec-agent.conf
server=$(policyhost)
mode=640
group=ossec
type=sum
define=dc_restart_ossec
This second stanza in the copy section copies a file from our ossec key directory to the client.keys file on the client.
This copy only happens if the two files are different. It also sets dc_restart_ossec if the copy occurs.
$(ossec_key_dir)/$(host).ossec
dest=/var/ossec/etc/client.keys
server=$(policyhost)
mode=640
group=ossec
type=sum
define=dc_restart_ossec
processes
My processes block checks to ensure that OSSEC-HIDS is running the correct daemons.
processes:
!hg_ossec_server::
"ossec-agentd" elsedefine=dc_restart_ossec
hg_ossec_server::
"ossec-remoted" elsedefine=dc_restart_ossec
shellcommands
This section is where the certificate request occurs through some devious mechanisms I designed for no other reason than to amuse myself. Hopefully, it amuses others as well. The first thing it does is issue a command that
echos the client eth0 ipv4 address to a file named host.ossec in the ossec request directory I defined. The
hg_ossec_server class will use this to generate a cert to place in the aforementioned copy block.
shellcommands:
!hg_ossec_server::
"/usr/bin/ssh util@$(policyhost) -i $(util_privkey) echo $(global.ipv4[eth0]) > $(ossec_req_di
The last statement checks to see if anyone defined dc_restart_ossec, and restart ossec-hids if it was defined.
dc_restart_ossec::
"/sbin/service ossec-hids restart"
16
Ok, so who cares?
Well, now, our clients are setup to install, configure, and run OSSEC-HIDS as well as issuing a request for their
certificate. However, the certificate directory on the server is empty and so none of them will actually run. This is a
problem.
Configuring the OSSEC Server w/cfengine
The cfengine part of this was a pain for me because of the order of the actions I had defined and the extent of work I
had done incorrectly in the past. I could have figured out an interesting way to handle this, but I didnt want to scrap my
entire cfengine config and start from scratch. So I created a perl script that allowed me to use the manage_agents
script without interaction. It does require the Expect.pm & Regexp::Common from CPAN, but is otherwise stock
Perl 5.8.x. I also wrote a shell script wrapper to handle running the perl script and culminating the results. I saved
these two scripts in /root/security, so if you put them elsewhere, make sure to update the shell script wrapper.
The scripts for managing keys can be downloaded here < http://db0.us/~brad/cfengine-ossec-scripts.tar.gz>_
The cfengine bit was really simple, it just had to call my wrapper shell script and set the class. I did this with a control
block:
control:
hg_ossec_server::
AddClasses = ( ExecResult(/root/security/ossec-scan.sh) )
The combination of the two scripts and this one line in the cfengine configuration handle creating, removing, and
exporting the keys, as well as configuring the dc_restart_ossec class if there have been changes.
OSSEC Updates
Updating OSSEC is as easy as it can get. Just download the latest package and follow the installation instructions as
usual. It will detect that you already have it installed and ask:
- You already have OSSEC installed. Do you want to update it? (y/n): y
Just answer yes to this question and the script will update the OSSEC binaries.
local_decoder.xml will not be modified during this upgrade.
local_rules.xml and
The script will also prompt for an answer to the following question:
- Do you want to update the rules? (y/n): y
Answering yes to this question updates the <rules> section of the systems ossec.conf.
1.1.5 Agents
There are two types of agents within OSSEC: installable agents and agentless agents. Installable agents are installed
on hosts, and they report back to a central OSSEC server via the OSSEC encrypted message protocol. Agentless
agents require no installation on remote hosts. They are processes initiated from the OSSEC manager, which gather
information from remote systems, and use any RPC method (e.g. ssh, snmp rdp, wmi).
Agent
1.1. Manual
17
Managing Agents
To add an agent to an OSSEC manager with manage_agents you need to follow the steps below.
1. Run manage_agents on the OSSEC server.
2. Add an agent.
3. Extract the key for the agent.
4. Copy that key to the agent.
5. Run manage_agents on the agent.
6. Import the key copied from the manager.
7. Restart the managers OSSEC processes.
8. Start the agent.
manage_agents on the OSSEC server
The server version of manage_agents provides an interface to:

add an OSSEC agent to the OSSEC server
extract the key for an agent already added to the OSSEC server
remove an agent from the OSSEC server
list all agents already added to the OSSEC server.
Running manage_agents and start screen manage_agents should be run as a user with the appropriate privileges (e.g. root).
Run manage_agents:
# /var/ossec/bin/manage_agents
The manage_agents menu:

****************************************
* OSSEC HIDS v2.5-SNP-100809 Agent manager.
* The following options are available: *
****************************************
(A)dd an agent (A).
(E)xtract key for an agent (E).
(L)ist already added agents (L).
(R)emove an agent (R).
(Q)uit.
Choose your action: A,E,L,R or Q:
Typing the appropriate letter and hitting enter will initiate that function.
Adding an agent To add an agent type a in the start screen:
Choose your action: A,E,L,R or Q: a
You are then prompted to provide a name for the new agent. This can be the hostname or another string to identify the
system. In this example the agent name will be agent1.
18
- Adding a new agent (use \q to return to the main menu).

Please provide the following:
* A name for the new agent: agent1
After that you have to specify the IP address for the agent. This can either be a single IP address (e.g. 192.168.1.25), a
range of IPs (e.g. 192.168.2.0/24), or any. Using a network range or any is preferable when the IP of the agent may
change frequently (DHCP), or multiple systems will appear to come from the same IP address (NAT).
* The IP Address of the new agent: 192.168.2.0/24
Warning: If you use a specific IP address it must be unique. Duplicate IP addresses will cause issues. Multiple
systems can use the same IP range or any.
The last information you will be asked for is the ID you want to assign to the agent. manage_agents will suggest a
value for the ID. This value should be the lowest positive number that is not already assigned to another agent. The ID
000 is assigned to the OSSEC server. To accept the suggestion, simply press ENTER. To choose another value, type it
in and press ENTER.
* An ID for the new agent[001]:
As the final step in creating an agent, you have to confirm adding the agent:
Agent information:
ID:002
Name:agent1
IP Address:192.168.2.0/24
Confirm adding it?(y/n): y
Agent added.
After that manage_agents appends the agent information to /var/ossec/etc/client.keys and goes back to the start screen.
Warning: If this is the first agent added to this server, the servers OSSEC processes should be restarted using
/var/ossec/bin/ossec-control restart.
Extracting the key for an agent
After adding an agent, a key is created. This key must be copied to the agent. To extract the key, use the e option in
the manage_agents start screen. You will be given a list of all agents on the server. To extract the key for an agent,
simply type in the agent ID. It is important to note that you have to enter all digits of the ID.
Choose your action: A,E,L,R or Q: e
Available agents:
ID: 001, Name: agent1, IP: 192.168.2.0/24
Provide the ID of the agent to extract the key (or \q to quit): 001
Agent key information for 001 is:
MDAyIGFnZW50MSAxOTIuMTY4LjIuMC8yNCBlNmY3N2RiMTdmMTJjZGRmZjg5YzA4ZDk5m
** Press ENTER to return to the main menu.
The key is encoded in the string (shortened for this example) MDAyIGFnZW50MSAxOTIuMTY4LjIuMC8yNCBlNmY3N2RiMTdmMTJ
and includes information about the agent. This string can be added to the agent through the agent version of
manage_agents.
1.1. Manual
19
Removing an agent
If you want to remove an OSSEC agent from the server, use the r option in the manage_agents start screen. You will
be given a list of all agents already added to the server. To remove an agent, simply type in the ID of the agent, press
enter, and finally confirm the deletion. It is important to note that you have to enter all digits of the ID.
Choose your action: A,E,L,R or Q: r
Available agents:
ID: 001, Name: agent1, IP: 192.168.2.0/24
Provide the ID of the agent to be removed (or \q to quit): 001
Confirm deleting it?(y/n): y
Agent 001 removed.
manage_agents then invalidates the agent information in /var/ossec/etc/client.keys. Only the values
for ID and the key are kept to avoid conflicts when adding agents. The deleted agent can no longer communicate with
the OSSEC server.
manage_agents on OSSEC agents
The agent version provides an interface for importing authentication keys.

****************************************
* OSSEC HIDS v2.5-SNP-100809 Agent manager.
* The following options are available: *
****************************************
(I)mport key from the server (I).
(Q)uit.
Choose your action: I or Q: i
* Provide the Key generated by the server.

* The best approach is to cut and paste it.
*** OBS: Do not include spaces or new lines.
Paste it here (or \q to quit): [key extracted via manage_agents on the server]
Agent information:
ID:001
Name:agent1
IP Address:192.168.2.0/24
Confirm adding it?(y/n): y
Added.
** Press ENTER to return to the main menu.
For the changes to be in effect you have to restart the server and start the agent.
Agent systems behind NAT or with dynamic IPs (DHCP)
If you want to install the agent on systems without a static IP address or behind a NAT device, you need to configure
the agent using a CIDR address or the ip address of any.
20
DHCP Example
To add an agent that can receive any IP address in the 192.168.2.0/24 network, just provide the IP address of the agent
as 192.168.2.0/24. Example (taken from manage_agents):
* A name for the new agent: test
NAT Example
The same applies to systems behind a NAT device. The OSSEC server will see all agents behind the NAT as if they
have the same IP address.
For example, you have systems 192.168.1.2, 192.168.1.3 and 192.168.1.4 behind a nat server that connects to network
10.1.1.0/24 with the ossec server on it.
In this case, you need to config the agents as if their IP was 10.1.1.0/24, because this is the IP that the server is seeing
(not their original IP). Using any instead of an IP address or range is also a valid option, allowing the agent to connect
from any IP address.
On the manage_agents tool, add each one of those agents on the server using the following format:
* A name for the new agent: agent-1
* A name for the new agent: agent-2
* The IP Address of the new agent: any
Note: Make sure to use one separate key for each agent.
Adding an agent with ossec-authd

It is possible to add a key to a system via an automated method. ossec-authd and agent-auth provide this functionality.
ossec-authd
ossec-authd will run on the server adding agents and distributing authentication keys.
Warning: There is currently no authentication, so any host that can cannot to the port ossec-authd listens to
can obtain an OSSEC agent key. It is recommended that the OSSEC managers firewall be used to help limit
connections.
Run ossec-authd, listening on port 1515:
/var/ossec/bin/ossec-authd -p 1515
agent-auth
agent-auth will connect to an ossec-authd instance to receive, and install an agent key.
1.1. Manual
21
Run agent-auth connecting to the manager on IP 192.168.1.12 port 1515:

/var/ossec/bin/agent-auth -m 192.168.1.12 -p 1515
Centralized agent configuration

If you ever wanted to be able to configure your agents remotely, you will be happy to know that starting on version 2.1
you will be able to do so. We allow centralized configuration for file integrity checking (syscheckd), rootkit detection
(rootcheck) and log analysis.
This is how it works.
Create agent configuration
First Create the file /var/ossec/etc/shared/agent.conf.

Inside the file you can configure the agent just as you would normally at ossec.conf
<agent_config>
<localfile>
<location>/var/log/my.log</location>
<log_format>syslog</log_format>
</localfile>
</agent_config>
But you have a few more options. You can restrict the config by agent name, operating system, or profile:
<agent_config name="agent1">
<localfile>
<location>/var/log/my.log</location>
</localfile>
</agent_config>
<agent_config os="Linux">
<localfile>
<location>/var/log/my.log2</location>
</localfile>
</agent_config>
<agent_config os="Windows">
<localfile>
<location>C:\myapp\my.log</location>
</localfile>
</agent_config>
And only the proper agent will read them, giving us great granularity to push the configuration to all your agents.
After you configured, the manager will push it to the agents. Note that it can take a while for it to complete (since the
manager caches the shared files and only re-reads them every few hours). If you restart the manager the configuration
will be pushed much quicker.
22
Restart the agent
Once the configuration file is pushed, you can run the command agent_control to see if the agent received the config
and restart the agent remotely.
# md5sum /var/ossec/etc/shared/agent.conf
MD5 (/var/ossec/etc/shared/agent.conf) = ee1882236893df851bd9e4842007e7e7
# /var/ossec/bin/agent_control -i 200
OSSEC HIDS agent_control. Agent information:
Agent ID: 200
Agent Name: ourhome
IP address: 192.168.0.0/16
Status: Active
Operating system: Linux ourhome 2.6.24-23-generic #1 SMP Mon Jan 26 00..
Client version: OSSEC HIDS v2.1 / ee1882236893df851bd9e4842007e7e7
Last keep alive: Tue Jun 30 08:29:17 2009
Syscheck last started at: Tue Jun 30 04:29:32 2009
Rootcheck last started at: Tue Jun 30 06:03:08 2009
When the agent received the configuration, the Client Version field will have the md5sum of the agent.conf file.
Note: Linux systems generally use md5sum, but other systems may use md5 as the name of the application to check
the hash of the file.
To restart the agent:
# /var/ossec/bin/agent_control -R 200 (where 200 is the agent id)
OSSEC HIDS agent_control: Restarting agent: 200
Agentless
Agentless Monitoring
Agentless monitoring allows you to run integrity checking on systems without an agent installed (including routers,
firewalls, switches and even Linux/BSD systems). It can be executed just like our normal file integrity checking
(alerting of checksum changes) or doing diffs and showing exactly what has changed.
Agentless configuration options
agentless
This is the section that will contain the agentless configuration.
frequency
This controls the number of seconds between each run.
host
This defines the username and agentless host.
Example:
<host>root@linux.server.example.com</host>
1.1. Manual
23
state
This determines whether the checks are periodic or periodic_diff.
periodic: The output from the scripts is processed by the OSSEC processes.
periodic_diff: The output from the scripts is compared to the output of previous runs.
arguments
This defines the arguments passed to the script.
Check _manual-agentless-scripts for more information.
Getting started with agentless
After you installed OSSEC, you need to enable the agentless monitoring:
# /var/ossec/bin/ossec-control enable agentless
And provide the SSH authentication to the host you want to access. For Cisco devices (PIX, routers, etc), you need
to provide an additional parameter for the enable password. The same thing applies if you want to add support for
su, it must be the additional parameter. In this example, I am adding a Linux box (example.net) and a PIX firewall
(pix.fw.local):
# /var/ossec/agentless/register_host.sh add root@example.net mypass1
*Host root@example.netl added.
# /var/ossec/agentless/register_host.sh add pix@pix.fw.local pixpass enablepass
*Host pix@pix.fw.local added.
# /var/ossec/agentless/register_host.sh list
*Available hosts:
pix@pix.fw.local
root@example.net
Note: register_host.sh is a shell script, special characters may need to be escaped to not be interpreted by the
shell.
If you want to use public key authentication instead of passwords, you need to provide NOPASS as the password and
create the public key:
# sudo -u ossec ssh-keygen
It will create the public keys inside /var/ossec/.ssh . After that, just scp the public key to the remote box and your
password less connection should work.
Configuring agentless
Once you have added all your systems, you need to configure OSSEC to monitor them. By default, we have 4 agentless
types (but we plan to add more soon):
ssh_integrity_check_bsd
ssh_integrity_check_linux
ssh_generic_diff
ssh_pixconfig_diff
24
For the first two, you give a list of directories in the configuration and OSSEC will do the integrity checking of them on
the remote box. On the ssh_generic_diff, you give a set of commands to run on the remote box and OSSEC will alert
when the output of them changes. The ssh_pixconfig_diff will alert when a Cisco PIX/router configuration changes.
So, for my first system (root@example.net), I will monitor the /bin, /etc and /sbin directories every 10 hours (if I was
using the ssh_integrity_check_bsd, the argument would be the directories as well):
<agentless>
<type>ssh_integrity_check_linux</type>
<frequency>36000</frequency>
<host>root@example.net</host>
<state>periodic</state>
<arguments>/bin /etc/ /sbin</arguments>
</agentless>
For my PIX, the configuration looks like:

<agentless>
<type>ssh_pixconfig_diff</type>
<host>pix@pix.fw.local</host>
<state>periodic_diff</state>
</agentless>
And just to exemplify the ssh_generic_diff I will also monitor ls -la /etc; cat /etc/passwd on the root@example.net.
Note that if you want to monitor any network firewall or switch, you can use the ssh_generic_diff and just specify
the commands in the arguments option. To use su, you need to set the value use_su before the hostname (eg:
<host>use_su root@example.net</host>).
<agentless>
<type>ssh_generic_diff</type>
<host>root@example.net</host>
<state>periodic_diff</state>
<arguments>ls -la /etc; cat /etc/passwd</arguments>
</agentless>
Running the completed setup
Once the configuration is completed, you can restart OSSEC. You should see something like Started ossec-agentlessd
in the output. Before each agentless connection is started, OSSEC will do a configuration check to make sure everything is fine. Look at /var/ossec/logs/ossec.log for any error. If you see:
2008/12/12 15:20:06 ossec-agentlessd: ERROR: Expect command not found (or bad arguments) for ssh_int
2008/12/12 15:20:06 ossec-agentlessd: ERROR: Test failed for ssh_integrity_check_bsd (127). Ignorin
It means that you dont have the expect library installed on the server (it is not necessary to install anything on the
agentless systems to monitor). On Ubuntu you can do the following to install:
# apt-get install expect
After installing expect, you can restart OSSEC and you should see:
2008/12/12 15:24:12 ossec-agentlessd: INFO: Test passed for ssh_integrity_check_bsd.
When it connects to the remote system, you will also see:
1.1. Manual
25
2008/12/12 15:25:19 ossec-agentlessd: INFO: ssh_integrity_check_bsd: root@example.net: Starting.

2008/12/12 15:25:46 ossec-agentlessd: INFO: ssh_integrity_check_bsd: root@example.net: Finished.
Alerts
These are some of the alerts you will get:

For the ssh_generic_diff:
OSSEC HIDS Notification.
2008 Dec 12 01:58:30
Received From: (ssh_generic_diff) root@example.net->agentless
Rule: 555 fired (level 7) -> "Integrity checksum for agentless device changed."
Portion of the log(s):
ossec: agentless: Change detected:
35c35
< -rw-r-r- 1 root wheel 34 Dec 10 03:55 hosts.deny
-> -rw-r-r- 1 root wheel 34 Dec 11 18:23 hosts.deny
-END OF NOTIFICATION
For the PIX:

2008 Dec 01 15:48:03
Received From: (ssh_pixconfig_diff) pix@pix.fw.local->agentless
Rule: 555 fired (level 7) -> "Integrity checksum for agentless device changed."
ossec: agentless: Change detected:
48c48
< fixup protocol ftp 21
-> no fixup protocol ftp 21
100c100
< ssh timeout 30
-> ssh timeout 50
More changes..
-END OF NOTIFICATION
Contents
Writing Agentless Scripts
Agentless Script Types
* Periodic diff Specification
* Periodic Specification
Example of real FWD: command.
Agentless Script: ssh_integrity_check_linux
Modifying to make own Agentless Script: ssh_dmz_linux
26
Writing Agentless Scripts

All scripts that work with OSSEC agentless security monitoring use stdout for communication and reporting to the
OSSEC server. This makes writing scripts for OSSEC simple as you do not need to do anything more then print or
echo to stdout. The format of the output does need to meet the OSSEC specification, but that is a very simple thing to
do.
Agentless Script Types
Before we move to the specification details I need to explain that OSSEC agentless runs to different types of scripts.
Namely the following:
periodic_diff
Scripts output data to the OSSEC agentless process that will then be compared to past runs and if there are
differences an OSSEC alert will be generated.
periodic
Scripts output controlled messages to the OSSEC agentless process that will then be processed accordingly.
Periodic diff Specification The output for periodic_diff is very simple, any and all output after the agentless command STORE: now and before the next OSSEC Command will be stored and compared for differences. This type of
script is mostly used for hardware devices such as Cisco IOS, Juniper JunOS, and other products.
Scripts that use the periodic_diff make use of the following commands:
INFO:
The string following INFO will be logged to /var/ossec/logs/ossec.log by OSSEC for debugging.
ERROR:
Error needs to be reported. The string following this command is forwarded to the OSSEC manager, and
the OSSEC process closes down the script.
STORE:
All the lines that follows this command will be added stored and compared to previous runs of the script
Here is an example of a periodic_diff script that comes with OSSEC. (Please note with all agentless scripts you must
be in the root of the OSSEC install for them to function correctly.)
obsd46#( cd /var/ossec && ./agentless/ssh_pixconfig_diff cisco@172.17.0.1 show hardware )
spawn ssh -c des cisco@172.17.0.1
No valid ciphers for protocol version 2 given, using defaults.
Password:
a.zfw.tss>INFO: Starting.
enable
Password:
a.zfw.tss#ok on enable pass
STORE: now
no pager
^
% Invalid input detected at ^ marker.
a.zfw.tss#term len 0
a.zfw.tss#terminal pager 0
1.1. Manual
27
^
a.zfw.tss#show version | grep -v Configuration last| up
^
a.zfw.tss#show running-config
Building configuration...
Current configuration : 14631 bytes

!
version 12.4
[................SNIP CONFIG.................]
a.zfw.tss#show hardware
Cisco IOS Software, 3800 Software (C3845-ADVENTERPRISEK9-M), Version 12.4(24)T1, RELEASE SOFTWARE (fc
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Fri 19-Jun-09 19:21 by prod_rel_team
ROM: System Bootstrap, Version 12.3(11r)T2, RELEASE SOFTWARE (fc1)
a.zfw.tss uptime is 1 week, 5 days, 7 hours, 29 minutes
System returned to ROM by reload at 13:34:26 UTC Thu Oct 22 2009
System image file is "flash:c3845-adventerprisek9-mz.124-24.T1.bin"
This product contains cryptographic features and is subject to United

States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
export@cisco.com.
Cisco 3845 (revision 1.0) with 1007615K/40960K bytes of memory.
Processor board ID FTX1043A2CR
2 Gigabit Ethernet interfaces
1 ATM interface
1 Virtual Private Network (VPN) Module
4 CEM T1/E1 ports
DRAM configuration is 64 bits wide with parity enabled.
479K bytes of NVRAM.
492015K bytes of USB Flash usbflash0 (Read/Write)
62720K bytes of ATA System CompactFlash (Read/Write)
Configuration register is 0x2102
28
a.zfw.tss#exit
Connection to 172.17.0.1 closed by remote host.
Connection to 172.17.0.1 closed.
INFO: Finished.
In this example above the script would store the contents between STORE: now and INFO: Finished.. If this
is the first time that OSSEC agentless has run this command no alerts would be generated and the contents would have
been saved for later comparisons. If OSSEC agentless has a stored copy from a previous execution it will compare the
files and if there are any differences it will generate an alert.
Periodic Specification The periodic specification has more options and gives more control to the script writer on
what actions OSSEC will take. Once again stdout is used for communication so script writing is easy.
INFO:
The string following INFO will be logged to /var/ossec/logs/ossec.log by OSSEC for debugging.
ERROR:
Error needs to be reported. The string following this command is forwarded to the OSSEC manager, and
the OSSEC process closes down the script.
FWD:
The string following FWD is a colon delimited list of stats on a given file.
LOG:
The string following LOG: will be passed into ossec-analysisd and processed like all other log messages.
Example of real FWD: command.
FWD: 19419:600:0:0:fb30de5b02029950ae05885a3d407c8c:017cd6118cdc166ee8eba8af1b7fdad6763203d3 ./.bash_
The Fields break down in to the following:

FWD:
The OSSEC Command
19419
Total size of file, in bytes
600
Access rights of file in octal
0
User ID of file owner
0
Group ID of file owner
fb30de5b02029950ae05885a3d407c8c
MD5 Hash of file
017cd6118cdc166ee8eba8af1b7fdad6763203d3
SHA1 Hash of file
1.1. Manual
29
./.bash_history
Path and name of file
Using this format OSSEC can store the information about a file and then in the future run compare that they are the
same. If for some reason they are not the same an alert will be generated. Here is an example of a password change
on a linux system:
2009 Sep 21 15:19:00
Received From: (ssh_integrity_check_linux) root@172.17.20.20->syscheck
Rule: 550 fired (level 7) -> "Integrity checksum changed."
Integrity checksum changed for: /etc/shadow
Old md5sum was: 0d92e12c92f3edcf9d8876ea57c5f677
New md5sum is : 2bd51b61dea17c5682fb2c0cf4f92c63
Old sha1sum was: 2270c03a920ef8dd50e11cefdef046a8660f7a29
New sha1sum is : d9518ea9022b10d07f81925c6d7f2abb4364b548
--END OF NOTIFICATION
Agentless Script: ssh_integrity_check_linux
Now that we have an understanding of how agentless scripts communicate with the parent OSSEC process, lets move
on to a working example. The OSSEC supplied script ssh_integrity_check_linux is a great place to start,
so lets open it up and see what is going on.
obsd46# cat /var/ossec/agentless/ssh_integrity_check_linux
#!/usr/bin/env expect
#
#
#
#
#
#
#
#
#
#
@(#) $Id: ssh_integrity_check_linux,v 1.11 2009/06/24 17:06:21 dcid Exp $

Agentless monitoring
Copyright (C) 2009 Trend Micro Inc.
All rights reserved.
This program is a free software; you can redistribute it
and/or modify it under the terms of the GNU General Public
License (version 3) as published by the FSF - Free Software
Foundation.
# Main script.
source "agentless/main.exp"
# SSHing to the box and passing the directories to check.

if [catch {
spawn ssh $hostname
} loc_error] {
send_user "ERROR: Opening connection: $loc_error.\n"
exit 1;
}
source $sshsrc
30
source $susrc
set timeout 600
send "echo \"INFO: Starting.\"; for i in find $args 2>/dev/null;do tail \$i >/dev/null 2>&1 &&
md5=md5sum \$i | cut -d \" \" -f 1 && sha1=sha1sum \$i | cut -d \" \" -f
1 && echo FWD: stat --printf \"%s:%a:%u:%g\" \$i:\$md5:\$sha1 \$i; done; exit\r"
send "exit\r"
expect {
timeout {
send_user "ERROR: Timeout while running commands on host: $hostname .\n"
exit 1;
}
eof {
send_user "\nINFO: Finished.\n"
exit 0;
}
}
exit 0;
The comments in the script hints to what is going on, but everything up to and including set timeout 600 is related to
setting up the expect functions and code for handling the ssh subprocess and connecting to the remote host. I am not
going to spend any time with this section, I am just going to make use of it.
The meat of what is getting processed on the remote end all happens in two lines.
send "echo \"INFO: Starting.\"; for i in find $args 2>/dev/null;do tail \$i >/dev/null 2>&1 &&
md5=md5sum \$i | cut -d \" \" -f 1 && sha1=sha1sum \$i | cut -d \" \" -f
1 && echo FWD: stat --printf \"%s:%a:%u:%g\" \$i:\$md5:\$sha1 \$i; done; exit\r"
Lets break this down to see what is happening.

The send command pushes the following string to the ssh subprocess which gets run on the remote end of the connection. Before the script is sent to the remote host expect internally processes the string. This includes searching for
variables and removing any control characters.
The control characters are first taken into account, and in the case of our example all escaped special characters are
processed. , r, and $ would be replaced with , carriage return, and & respectively. The reason the escape characters
are needed so that they will not interfere with expects own string processing and control. We will need to handle control
characters in this way when we begin writing our own script.
While special characters were being handled by expect it also looked for variables to replace, in this case it will
find $args and replace it with what ever arguments were passed to the script by the OSSEC agentless process. If
we specified the following in /var/ossec/etc/ossec.conf the $args variable would be replaced with /bin
/etc /sbin.
<agentless>
<type>ssh_integrity_check_linux</type>
<host>root@172.17.20.20</host>
<state>periodic</state>
<arguments>/bin /etc /sbin</arguments>
</agentless>
Back to the commands that get run. Once expect has completed replacement we are left with this command.
echo "INFO: Starting."; for i in find /bin /etc /sbin 2>/dev/null;do tail $i >/dev/null 2>&1 &&
md5=md5sum $i | cut -d " " -f 1 && sha1=sha1sum $i | cut -d " " -f
1.1. Manual
31
1 && echo FWD: stat --printf "%s:%a:%u:%g" $i:$md5:$sha1 $i; done; exit
exit
This script then goes and uses the Unix find command to locate all files in the specified path (from the arguments
passed) and generates an OSSEC FWD: command for each one and prints it to stdout. Making use of the commands
stat, md5sum, and sha1sum to generate the data needed. Here is an example of the output checking.
spawn ssh root@172.17.20.20

Last login: Wed Nov 4 11:32:51 2009 from 172.17.20.131^M
[linux26 ~]#
INFO: Started.
echo "INFO: Starting."; for i in find {/bin /etc /sbin} 2>/dev/null;do tail $i >/dev/null 2>&1 &&
md5=md5sum $i | cut -d " " -f 1 && sha1=sh a1sum $i | cut -d " " -f
1 && echo FWD: stat --printf "%s:%a:%u:%g" $i:$md5:$sha1 $i; done; exit
INFO: Starting.
FWD: 833:644:0:0:4148adea745af5121963f6b731b60013:60877a6f6981b16c0d53d32bcd3f07d41cfb5bd4 /etc/modpr
glib2.sh
[...........SNIP............]
FWD: 1696:644:0:0:c2bd306b205ad9e81fb02ce6b225d384:5244d65815cb228a4fac7bc4c1c7774508fb7505 /etc/nssw
FWD: 85179:644:0:0:8db574225cd1068b47e77ceccd96f8ff:b5ef6183b35ee9d1b66ed2cefe98003c5bd99192 /etc/sen
FWD: 49:644:0:0:52c3df2f1edf30ca3db82174be3a68d2:1934648f2429b70b1f729d343a6956fb0ea73136 /etc/php.d/
FWD: 873:644:0:0:04559d1fe27ecd079b69df8b319f937e:e5cab1bf1f9e4bc4386309f4e00a9b7be3e543a2 /etc/php.d
FWD: 59:644:0:0:94636ba6c4bac9d8d49d9de1a513ae0c:41d5164a2c6e332e40edf55c59a2d0df8a260964 /etc/php.d/
FWD: 49:644:0:0:917dbbafbfaaa20f660063d627123dae:0e829d4ffc69f58dc258510b4b8452412e31ccc5 /etc/php.d/
FWD: 0:644:0:0:d41d8cd98f00b204e9800998ecf8427e:da39a3ee5e6b4b0d3255bfef95601890afd80709 /etc/wvdial.
logout
INFO: Finished.
Modifying to make own Agentless Script: ssh_dmz_linux
Using the built in OSSEC agentless scripts are great, but sometimes we need more focused scanning and checking. So
lets modify the ssh_integrity_check_linux for our environment.
The goals for this new script will be to watch for changes to files based on the following criteria:
All setuid and setgid files
All files related to authentication (including .htaccess and ssh files)
All application specific files (apache, ssh)
Finding all setuid and setgid files
Lets first start by identifying a method to locate all files with their setuid or setgid bits enabled. To do this we will ssh
to the host 172.17.20.20 and use find to locate the files.
obsd46# sudo -u ossec ssh root@172.17.20.20
[linux26 ~]# find / -type f $ -perm -4000 -o -perm -2000 $
/sbin/umount.nfs
/sbin/netreport
/sbin/unix_chkpwd
/sbin/mount.nfs
/sbin/pam_timestamp_check
/sbin/mount.nfs4
/sbin/umount.nfs4
/bin/ping6
/bin/su
32
/bin/umount
/bin/ping
/bin/mount
/lib/dbus-1/dbus-daemon-launch-helper
/usr/libexec/openssh/ssh-keysign
/usr/libexec/utempter/utempter
/usr/sbin/usernetctl
/usr/sbin/postqueue
/usr/sbin/userhelper
/usr/sbin/userisdnctl
/usr/sbin/postdrop
/usr/sbin/suexec
/usr/bin/chsh
/usr/bin/chfn
/usr/bin/sudo
/usr/bin/locate
/usr/bin/wall
/usr/bin/sudoedit
/usr/bin/gpasswd
/usr/bin/lockfile
/usr/bin/newgrp
/usr/bin/write
/usr/bin/screen
/usr/bin/passwd
/usr/bin/chage
/usr/bin/sperl5.8.8
/usr/bin/crontab
/usr/bin/ssh-agent
Finding all files related to authentication and applications specific files

Finding all files with setuid and setgid was simple, but finding all files related to authentication is more involved. This
of course will vary from system to system, but this should be good starting point.
obsd46# sudo -u ossec ssh root@172.17.20.20

[linux26 ~]# find / $ -name ".ssh" -o -name "ssh" -o -name "sshd" -o -name "httpd" -o -name ".htacce
-o -name "pam.d" $ -exec find {} \;
/var/www/html/admin/modules/framework/var/www/html/admin/modules/.htaccess
/etc/httpd
/etc/httpd/conf
/etc/httpd/conf.d
/etc/httpd/conf.d/php.conf
/etc/httpd/conf.d/proxy_ajp.conf
/etc/httpd/conf.d/README
/etc/httpd/conf.d/ssl.conf
/etc/httpd/conf.d/welcome.conf
/etc/httpd/conf/httpd.conf
/etc/httpd/conf/magic
/etc/httpd/logs
/etc/httpd/modules
/etc/httpd/run
/etc/logrotate.d/httpd
/etc/pam.d
/etc/pam.d/authconfig
[...................SNIP PAM Files.....................]
/etc/pam.d/system-config-network-cmd
/etc/pam.d/vsftpd
/etc/rc.d/init.d/httpd
/etc/rc.d/init.d/sshd
1.1. Manual
33
/etc/ssh
/etc/ssh/ssh_config
/etc/ssh/sshd_config
/etc/ssh/ssh_host_dsa_key
/etc/ssh/ssh_host_dsa_key.pub
/etc/ssh/ssh_host_key
/etc/ssh/ssh_host_key.pub
/etc/ssh/ssh_host_rsa_key
/etc/ssh/ssh_host_rsa_key.pub
/etc/sysconfig/httpd
/root/.ssh
/root/.ssh/authorized_keys
/usr/bin/ssh
/usr/lib/httpd
/usr/lib/httpd/modules
/usr/lib/httpd/modules/libphp5.so
[...................SNIP Apache modules................]
/usr/lib/httpd/modules/mod_vhost_alias.so
/usr/sbin/httpd
/usr/sbin/sshd
/usr/src/tbm-pbxconfig-5.5.1/amp_conf/htdocs/admin/modules/framework/htdocs/admin/modules/.htaccess
/usr/src/tbm-pbxconfig-5.5.1/amp_conf/htdocs/admin/modules/.htaccess
/var/empty/sshd
/var/empty/sshd/etc
/var/empty/sshd/etc/localtime
/var/www/html/admin/modules/framework/var/www/html/admin/modules/.htaccess
/var/www/html/admin/modules/.htaccess
Merging finds
Now we have two basic find methods that identify the files we want to monitor for changes, but our finds were a little
greedy so we should create a way to strip out unwanted files from the list. As this is a unix system egrep is the king for
finding or removing items from a list. To simplify things we can use egrep with the -v command line argument which
tells egrep NOT to print any matching items.
Just to make sure that we do not end up double processing files we can make use of the sort command with -u argument
to remove any duplicates.
Here is how we would put together both finds, egrep, and sort to locate and filter what is needed.
( find / -type f $ -perm -4000 -o -perm -2000 $ && \find / $ -name ".ssh" -o -name "ssh" -o -name
-o -name "httpd" -o -name ".htaccess" -o -name "pam.d" $ -exec find {} \; ) 2>/dev/null | egrep
-v "known_hosts|moduli|var\/log|var\/lock" | sort -u
The above command we have found all files and paths that we would like to monitor, but this still needs to be integrated
into a script on the OSSEC server.
Creating ssh_dmz_linux
We dont want to make changes to ssh_integrity_check_linux directly so we will need to make a copy.
obsd46# (cd /var/ossec/agentless && cp ssh_integrity_check_linux ssh_dmz_linux)
Integrating our new command line into the script we must pay close attention to special characters that expect will
process. Due to this we will need to escape all / and by proceeding them with . Once we are done escaping we just
insert our new line in place of find $args 2>/dev/null in our new file.
Here is what the completed script will look like.
34
obsd56# cat /var/ossec/agentless/ssh_dmz_linux

#!/usr/bin/env expect
#
#
#
#
#
#
#
#
#
#
@(#) $Id: ssh_integrity_check_linux,v 1.11 2009/06/24 17:06:21 dcid Exp $

Agentless monitoring
Copyright (C) 2009 Trend Micro Inc.
All rights reserved.
This program is a free software; you can redistribute it
and/or modify it under the terms of the GNU General Public
License (version 3) as published by the FSF - Free Software
Foundation.
# Main script.
source "agentless/main.exp"
# SSHing to the box and passing the directories to check.

if [catch {
spawn ssh $hostname
} loc_error] {
send_user "ERROR: Opening connection: $loc_error.\n"
exit 1;
}
source $sshsrc
source $susrc
set timeout 600

send "echo \"INFO: Starting.\"; for i in (find / \$ -name \".ssh\" -o -name \"ssh\" -o -name \"sshd
-o -name \"httpd\" -o -name \".htaccess\" -o -name \"pam.d\" \$ -exec find {} \\; && find / -type f
\$ -perm -4000 -o -perm -2000 \$; ) 2>/dev/null | egrep -v \"known_hosts|moduli|var\\/log|var\\/loc
do tail \$i >/dev/null 2>&1 && md5=md5sum \$i | cut -d \" \" -f 1 && sha1=sha1sum \$i | cut -d \"
-f 1 && echo FWD: stat --printf \"%s:%a:%u:%g\" \$i:\$md5:\$sha1 \$i; done; exit\r"
send "exit\r"
expect {
timeout {
send_user "ERROR: Timeout while running commands on host: $hostname .\n"
exit 1;
}
eof {
send_user "\nINFO: Finished.\n"
exit 0;
}
}
exit 0;
Testing
Before we add this new script to OSSEC configuration we need to test it.
obsd46# (cd /var/ossec && sudo -u ossec ./agentless/ssh_dmz_linux root@172.17.20.20 )
ERROR: ssh_integrity_check <hostname> <arguments>
1.1. Manual
35
Due to not making use of the of the $arg variable in the way that ssh_integrity_check_linux wants use too, this caused
this the problem above. Solving this problem would require making changes to files that will effect other built in
scripts. So a quick solution is to just pass anything as an argument to the script. This will have no effect on our script
as we do not make use of the $arg variable.
obsd46# (cd /var/ossec && sudo -u ossec ./agentless/ssh_dmz_linux root@172.17.20.20 NOTUSED)

spawn ssh root@172.17.20.20
Last login: Wed Nov 4 13:46:32 2009 from 172.17.20.131^M
[linux26 ~]#
INFO: Started.
echo "INFO: Starting."; for i in (find / $ -name ".ssh" -o -name "ssh" -o -name "sshd" -o -name "ht
-o -name ".htaccess" -o -name "pam.d" $ -exec find {} \; && find / -type f $ -perm -4000 -o -perm
$; ) 2>/dev/null | egrep -v "known_hosts|moduli|var\/log|var\/lock";do tail $i >/dev/null 2>&1 &&
md5=md5s ^Mum $i | cut -d " " -f 1 && sha1=sha1sum $i | cut -d " " -f 1 && echo FWD: stat --pri
"%s:%a:%u:%g" $i:$md5:$sha1 $i; done; exit
INFO: Starting.
FWD: 14:775:100:101:3bc0a3e92f8170084dd102eda9a474b1:25a1783a3c6bdd9745ec245ec1bfa0414ee05d23 /var/ww
FWD: 3519:644:0:0:e4ca381035a34b7a852184cc0dd89baa:6e43d0b5a46ed5ba78da5c7e9dcf319b27d769e7 /var/empt
FWD: 560:644:0:0:58370830ecfa056421ad21aff9c18905:d115bb5aeefaab97c53fbbd5df84ebcb9170d796 /etc/httpd
[...................SNIP.............................]
FWD: 392:644:0:0:e92bea7e9d70a9ecdc61edd7c0a2f59a:d77b61dac010c60589b4d8a2039e3b8a5bed18b2 /etc/httpd
FWD: 70888:4711:0:0:9046bd13339e7ef22266067b633e601a:3fc41029ddb14fe4ed613f479fa9e89c944f04dd /usr/bi
FWD: 315416:6755:0:0:4c63a9709fb7f0f97c30aa29d204859c:c379efa658de72866b8f6de5767906ff78d127b0 /usr/b
FWD: 88964:2755:0:99:baf3ebef6377d6ef42858776c33621b0:62394bf57d18c3fd49adeb39a1da61661cabc3c8 /usr/b
logout
INFO: Finished.
1.1.6 Log monitoring/analysis

Log Analysis (or log inspection) is done inside OSSEC by the logcollector and analysisd processes. The first one
collects the events and the second one analyzes (decodes, filters and classifies) them.
It is done in real time, so as soon as an event is written OSSEC will process them. OSSEC can read events from
internal log files, from the Windows event log and also receive them directly via remote syslog.
What is log analysis?
Inside OSSEC we call log analysis a LIDS, or log-based intrusion detection. The goal is to detect attacks, misuse or
system errors using the logs.
LIDS - Log-based intrusion detection or security log analysis are the processes or techniques used to detect attacks
on a specific network, system or application using logs as the primary source of information. It is also very useful to
detect software misuse, policy violations and other forms of inappropriate activities.
Quick Facts
How often are logs monitored?
In real time.
Where are the events analyzed?
In the manager.
How long are they stored?
36
For as long as your policy dictates (it is user configurable).

Where does this help me with compliance?
(PCI DSS, etc) It helps with the whole section 10 (log monitoring) of PCI.
How much CPU does it use?
On the agent, it uses very little CPU/memory since it just read the events and forwards them to the manager.
On the manager, it depends on the number of events per second (EPS).
How does it deal with false positives?
False positives can be eliminated using local rules.
Configuration Options
These options should be specified locally in each agents ossec.conf file or the share agent.conf.
<localfile> element, you can have the following options.
Inside the
localfile
location
Specify the location of the log to be read. strftime formats may be used for log file names. For instance,
a log file named file.log-2011-01-22 could be referenced with file.log-%Y-%m-%d. Wildcards
may be used on non-Windows systems. When wildcards are used, the log files must exist at the time
ossec-logcollector is started. It will not automatically begin monitoring new log files. strftime
and wildcards cannot be used on the same entry.
Default: Multiple (eg /var/log/messages)
Allowed: Any log file
log_format
The format of the log being read.
Note: If the log has one entry per line, use syslog.
Default: syslog
Allowed:
syslog This format is for plain text files in a syslog-like format. It can also be used when there
is no support for the logging format, and the logs are single line messages.
snort-full This is used for Snorts full output format.
snort-fast This is used for Snorts fast output format.
squid
iis
eventlog This is used for Microsoft Windows eventlog format.
1.1. Manual
37
eventchannel This is used for Microsoft Windows eventlogs, using the new EventApi. This
allows OSSEC to monitor both standard Windows eventlogs and more recent Application
and Services logs. This support was added in 2.8.
Warning: eventchannel cannot be used on Windows systems older than Vista.
mysql_log This is used for MySQL logs. It does not support multi-line logs.
postgresql_log This is used for PostgreSQL logs. It does not support multi-line logs.
nmapg This is used for monitoring files conforming to the grepable output from nmap.
apache
This format is for apaches default log format.
Example:
command This format will be the output from the command (as run by root) defined by command. Each line of output will be treated as a separate log.
full_command This format will be the output from the commandi (as run by root) defined by
command. The entire output will be treated as a single log.
Warning: command and full_command cannot be used in the agent.conf, and must be
configured in each systems ossec.conf.
djb-multilog
multi-line This option will allow applications that log multiple lines per event to be monitored.
This format requires the number of lines to be consistent. multi-line: is followed by
the number of lines in each log entry. Each line will be combined with the previous lines
until all lines are gathered. There may be multiple timestamps in a finalized event.
Allowed: <log_format>multi-line: NUMBER</log_format>
Example: Log messages:
Aug
Aug
Aug
Aug
Aug
9
9
9
9
9
14:22:47
14:22:47
14:22:47
14:22:47
14:22:47
hostname
hostname
hostname
hostname
hostname
log
log
log
log
log
line
line
line
line
line
one
two
three
four
five
Log message as analyzed by ossec-analysisd_:

Aug
9 14:22:47 hostname log line one Aug
9 14:22:47 hostname log line two Aug
command
The command to be run. All output from this command will be read as one or more log messages depending on
whether command or full_command is used.
Allowed: Any commandline and arguments.
38
9 1
alias
An alias to identify the command. This will replace the command in the log message.
For example <alias>usb-check</alias> would replace:
ossec: output: reg QUERY HKLM\SYSTEM\CurrentControlSet\Enum\USBSTOR:
with:
ossec: output: usb-check:
Allowed: Any string.

frequency
The minimum time in seconds between command runs. The command will probably not run every frequency
seconds exactly, but the time between runs will not be shorter than this setting. This is used with command and
full_command.
Allowed: Time in seconds.
check_diff
The output from an event will be stored in an internal database. Every time the same event is received, the output
is compared to the previous output. If the output has changed an alert will be generated.
only-future-events
Only used with the eventchannel log format. By default, when OSSEC starts the eventchannel log
format will read all events that ossec-logcollector missed since it was last stopped. It is possible to set
only-future-events to yes in order to prevent this behaviour. When set to yes, OSSEC will only
receive events that occured after the start of logcollector.
<localfile>
<loation>System</location>
<log_format>eventchannel</log_format>
<only-future-events>yes</only-future-events>
</localfile>
query
Only used with the eventchannel log format. It is possible to specify an XPATH query following the event
schema (see Microsofts documentation) in order to filter the events that OSSEC will process.
For example, the following configuration will only process events with an ID of 7040:
<localfile>
<location>System</location>
<query>Event/System[EventID=7040]</query>
</localfile>
Monitoring logs
With in OSSEC their is two major methods for monitoring logs: file and process. Each method has its own page and
examples.
Process Monitoring
Overview We love logs. Inside OSSEC we treat everything as if it is a log and parse it appropriately with our rules.
However, some information is not available in log files but we still want to monitor it. To solve that gap, we added the
1.1. Manual
39
ability to monitor the output of commands via OSSEC, and treat the output of those commands just like they were log
files.
Configuration examples
Disk space utilization (df -h) example For example, if you wanted to monitor the disk space utilization, you would
need to setup a cron job to dump the output of df -h to a log file (maybe /var/log/df.log) and configure OSSEC to
look at it.
As of OSSEC version 2.3 you can monitor commands directly in OSSEC following configuration (in
/var/ossec/etc/ossec.conf):
<localfile>
<log_format>command</log_format>
<command>df -h</command>
</localfile>
Since we already have a sample rule for df -h included with OSSEC you would see the following when any partition
reached 100%:
** Alert 1257451341.28290: mail - ossec,low_diskspace,
2009 Nov 05 16:02:21 (home-ubuntu) 192.168.0.0->df -h
Rule: 531 (level 7) -> "Partition usage reached 100% (disk space monitor)."
Src IP: (none)
User: (none)
ossec: output: df -h: /dev/sdb1 24G 12G 11G 100% /var/backup
Load average (uptime) Example Another example, if you want to monitor the load average, you can configure
OSSEC to monitor the uptime command and alert when it is higher than 2, for example:
<localfile>
<log_format>command</log_format>
<command>uptime</command>
</localfile>
And in the rule (in /var/ossec/rules/local_rules.xml):

<rule id="100101" level="7" ignore="7200">
<if_sid>530</if_sid>
<match>ossec: output: uptime: </match>
<regex>load averages: 2.</regex>
<description>Load average reached 2..</description>
</rule>
There are lots of possibilities with this feature. If you have ideas for commands to monitor and rules, please comment.
Alerting when output of a command changes If you want to create alerts when a log or the output of a command
changes, take a look at the new <check_diff /> option in the rules (available on the latest snapshot).
To demonstrate with an example, we will create a rule to alert when there is a new port open in listening mode on our
server.
First, we configure OSSEC to run the netstat -tan |grep LISTEN command by adding the following to
ossec.conf:
40
<localfile>
<log_format>full_command</log_format>
<command>netstat -tan |grep LISTEN|grep -v 127.0.0.1</command>
</localfile>
After that, I add a rule to alert when its output changes:

<rule id="140123" level="7">
<match>ossec: output: netstat -tan |grep LISTEN</match>
<check_diff />
<description>Listened ports have changed.</description>
</rule>
Note that we use the <check_diff /> option. The first time it receives the event, it will store in an internal
database. Every time it receives the same event, it will compare against what we have store and only alert if the output
changes.
In our example, after configuring OSSEC, I started netcat to listen on port 23456 and thats the alert I got:
2010 Mar 11 19:56:30
Received From: XYZ->netstat -tan |grep LISTEN|grep -v 127.0.0.1
Rule: 140123 fired (level 7) -> "Listened ports have changed."
ossec: output: netstat -tan |grep LISTEN|grep -v 127.0.0.1:
tcp4
0
0 *.23456
LISTEN
*.*
tcp4
0
0 *.3306
LISTEN
*.*
tcp4
0
0 *.25
LISTEN
*.*
Previous output:
ossec: output: netstat -tan |grep LISTEN|grep -v 127.0.0.1:
tcp4
0
0 *.3306
LISTEN
*.*
tcp4
0
0 *.25
LISTEN
*.*
Detecting USB Storage Usage Xavier Mertens wrote a very interesting article on Detecting USB Storage Usage
with OSSEC. He used our policy auditing module for that, but I think USB monitoring can be done in a much easier
way with our new check_diff feature.
To get started, first configure your Windows agents to monitor the USBSTOR registry entry using the reg command:
<agent_config os="windows">
<localfile>
<command>reg QUERY HKLM\SYSTEM\CurrentControlSet\Enum\USBSTOR</command>
</localfile>
</agent_config>
Next create a local rule for that command:

<rule id="140125" level="7">
<match>ossec: output: reg QUERY</match>
<check_diff />
<description>New USB device connected</description>
</rule>
1.1. Manual
41
Now after a few minutes you will see a directory at /var/ossec/queue/diff/[agent_name]/[rule_id]

with the current snapshot of this command. Once someone adds a new USB device you will get this alert:
** Alert 1268687754.35062: mail - local,syslog,
2010 Mar 15 18:15:54 (xx-netbook) any->reg QUERY HKLMSYSTEMCurrentControlSetEnumUSBSTOR
Rule: 140125 (level 7) -> New USB device connected
Src IP: (none)
User: (none)
ossec: output: reg QUERY HKLMSYSTEMCurrentControlSetEnumUSBSTOR:! REG.EXE VERSION 3.0
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTOR
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_&Prod_USB_Flash_Memory&Rev_5.00
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_Generic&Prod_Flash_Disk&Rev_8.0
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_Hitachi&Prod_HTS543225L9A300&Rev_
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_LEXAR&Prod_JD_FIREFLY&Rev_1100
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_SAMSUNG&Prod_HM160JC&Rev_0000
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_Sony&Prod_DSC&Rev_1.00
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_TomTom&Prod_ONE_XXL_IQ_Rts
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_USB_2.0&Prod_USB_Flash_Drive&Rev_0.00
Previous output:
ossec: output: reg QUERY HKLMSYSTEMCurrentControlSetEnumUSBSTOR:
! REG.EXE VERSION 3.0
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTOR
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_&Prod_USB_Flash_Memory&Rev_5.00
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_Generic&Prod_Flash_Disk&Rev_8.07
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_Hitachi&Prod_HTS543225L9A300&Rev_
HKEY_LOCAL_ACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_SAMSUNG&Prod_HM160JC&Rev_0000
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_Sony&Prod_DSC&Rev_1.00
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_TomTom&Prod_ONE_XXL_IQ_Rts
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSBSTORDisk&Ven_USB_2.0&Prod_USB_Flash_Drive&Rev_0.00
File Monitoring
Overview OSSEC has a process named ossec-logcollector that monitors the configured log files for new
events. When new log messages arrive, it forwards them to other processes for analysis or transport to an OSSEC
server.
Configuration The configuration for ossec-logcollector exists in /var/ossec/etc/ossec.conf in the
<ossec_config> section. The syntax can be found in the localfile syntax page
Configuration examples
Simple example Configuring a log file to be monitored is simple. Just provide the name of the file to be monitored
and the format:
<localfile>
<location>/var/log/messages</location>
</localfile>
42
Windows EventLog Example To monitor a Windows event log, you need to provide the format as eventlog and
the location is the name of the event log. Example:
<localfile>
<location>Security</location>
<log_format>eventlog</log_format>
</localfile>
Windows EventChannel Example To monitor a Windows event log on Windows Vista or later, you have the possibility to use the eventchannel log format. The location is the name of the event log. This is the only way to monitor
Applications and Services logs. If the file name contains a %4, replace it with /. Example:
<localfile>
<location>Microsoft-Windows-PrintService/Operational</location>
</localfile>
Multiple Files Example To check multiple files, OSSEC supports posix regular expressions. For example, to analyze every file that ends with a .log inside the /var/log directory, use the following configuration:
<localfile>
<location>/var/log/*.log</location>
</localfile>
Date Based Example For log files that change according to the date, you can also specify a strftime format to replace
the day, month, year, etc. For example, to monitor the log C:\Windows\app\log-08-12-15.log, where 08 is the year, 12
is the month and 15 the day (and it is rolled over every day), do:
<localfile>
<location>C:\Windows\app\log-%y-%m-%d.log</location>
</localfile>
Warning: Wildcards cannot be combined with the date based format.
IIS Logs Example Support for IIS (5 and 6) is available for the NCSA format (web only) and the W3C extended
format (for Web, FTP and SMTP). By default, the installation scripts will attempt to configure OSSEC to monitor the
first virtual hosts for web (W3SVC1 to W3SVC254), ftp (MSFTPSVC1 to MSFTPSVC254) and smtp (SMTPSVC1
to SMTPSVC254). To monitor any other file you need to add a new entry manually.
In addition to that, make sure to set the log time period to daily.
1.1. Manual
43
And using the local time for file naming and rollover.
44
In the extended logging properties, configure it to log the Date, Time and all the extended properties.
The following is an example of configuration to monitor the virtual server 2 of IIS web
1.1. Manual
45
<localfile>
<location>%WinDir%\System32\LogFiles\W3SVC3\ex%y%m%d.log</location>
<log_format>iis</log_format>
</localfile>
1.1.7 Syscheck
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.
Why Integrity checking?
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.
Quick facts
How often does it run?
By default every 6 hours, but the frequency or time/day are configurable.
Where is the database stored?
On the manager in /var/ossec/queue/syscheck.
How does it help with compliance? (PCI DSS, etc)
It helps with sections 11.5 (install FIM software) and 10.5 (integrity checking of log files) of PCI.
How much CPU does it use?
The scans are performed slowly to avoid using too much CPU/memory.
How are false positives handled?
Files can be ignored manually in the configuration or using rules. By default when a file has changed 3
times further changes are automatically ignored.
Realtime options
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.
46
Configuration options
These configuration options can be specified in each agents 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.
directories
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 should be set on the system you wish to monitor (or in the agent.conf if
appropriate).
Default: /etc,/usr/bin,/usr/sbin,/bin,/sbin
Attributes:
realtime: Value=yes
This will enable realtime/continuous monitoring on Linux (using the inotify system calls) and Windows systems.
report_changes: Value=yes
Report diffs of file changes. This is limited to text files at this time.
Note: This option is only available on Unix-like systems.
check_all: Value=yes
All the following check_* options are used together.
check_sum: Value=yes
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
check_sha1sum: Value=yes
When used only the sha1 hash of the files will be checked.
check_md5sum: Value=yes
The md5 hash of the files will be checked.
check_size: Value=yes
The size of the files will be checked.
check_owner: Value=yes
Check the owner of the files selected.
check_group: Value=yes
Check the group owner of the files/directories selected.
check_perm: Value=yes
Check the UNIX permission of the files/directories selected. On windows this will only check the
POSIX permissions.
restrict: Value=string
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)
1.1. Manual
47
ignore
List of files or directories to be ignored (one entry per element). The files and directories are still checked, but
the results are ignored.
Default: /etc/mtab
Attributes:
type: Value=sregex
This is a simple regex pattern to filter out files so alerts are not generated.
Allowed: Any directory or file name
frequency
Frequency that the syscheck is going to be executed (in seconds).
The default is 6 hours or 21600 seconds
Default: 21600
Allowed: Time in seconds
scan_time
Time to run the scans (can be in the formats of 21pm, 8:30, 12am, etc)
Allowed: Time to run scan
scan_day
Day of the week to run the scans (can be in the format of sunday, saturday, monday, etc)
Allowed: Day of the week
auto_ignore
Specifies if syscheck will ignore files that change too often (after the third change)
Default: yes
Allowed: yes/no
Valid: server, local
alert_new_files
Specifies if syscheck should alert on new files created.
Default: no
Allowed: yes/no
Note: New files will only be detected on a full scan, this option does not work in realtime.
scan_on_start
Specifies if syscheck should do the first scan as soon as it is started.
Default: yes
Allowed: yes/no
windows_registry
Use this option to add Windows registry entries to be monitored (Windows-only).
Default: HKEY_LOCAL_MACHINESoftware
Allowed: Any registry entry (one per element)
48
Note: New entries will not trigger alerts, only changes to existing entries.
registry_ignore
List of registry entries to be ignored.
Default: ..CryptographyRNG
refilter_cmd
Command to run to prevent prelinking from creating false positives.
Example:
<prefilter_cmd>/usr/sbin/prelink -y</prefilter_cmd>
Note: This option can potentially impact performance negatively. The configured command will be run for
each and every file checked.
Configuration Examples
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.
Example:
<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.
1.1. Manual
49
Real time Monitoring

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.
Warning: 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 a while for this to finish (wait for the log
ossec-syscheckd: INFO: Starting real time file monitoring ).
Note: 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.
Note: Both rootcheck and syscheck runs on the same thread, so when rootcheck is running, the inotify events would
get queued until it finishes.
Report Changes
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. For
example:
<syscheck>
<directories report_changes="yes" check_all="yes">/etc</directories>
<directories check_all="yes">/bin,/sbin</directories>
</syscheck>
Note:
Report Changes can only work with text files, and the changes are stored on the agent inside
/var/ossec/queue/diff/local/dir/file.
If OSSEC has not been compiled with libmagic support, report_changes will copy any file designated, e.g. mp3, iso,
executable, /chroot/dev/urandom (which would fill your hard drive). So unless libmagic is used, be very carefull on
which directory you enable report_changes.
Syscheck: FAQ
50
How to force an immediate syscheck scan?

How to tell syscheck not to scan the system when OSSEC starts?
How to ignore a file that changes too often?
Why does OSSEC still scan a file even though its been ignored?
How to know when the syscheck scan ran?
How to get detailed reporting on the changes?
Syscheck not sending any file data to the server?
Why arent new files creating an alert?
Can OSSEC include information on who changed a file in the alert?
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.
1.1. Manual
51
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 youd 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 its 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 default 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 managers 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. Alerting on new files does not work in realtime,
a full scan will be necessary to detect them.
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:

<syscheck>
<alert_new_files>yes</alert_new_files>
<directories check_all="yes">/etc,/bin,/sbin</directories>
</syscheck>
52
In short, no. OSSEC does not track this information. You could use your OSs auditing facilities to track this information, and create a rule to alert when an appropriate log is created.
1.1.8 Rootcheck Manual

Rootcheck
OSSEC HIDS will perform rootkit detection on every system where the agent is installed. The rootcheck (rootkit
detection engine) will be executed every X minutes (user specified - by default every 2 hours) to detect any possible rootkit installed. Used with the log analysis and the integrity checking engine, it will become a very powerful
monitoring solution.
Checks that rootcheck preforms
1. Read the rootkit_files.txt which contains a database of rootkits and files commonly used by them. It will try to
stats, fopen and opendir each specified file. We use all these system calls because some kernel-level rootkits
hide files from some system calls. The more system calls we try, the better the detection. This method is more
like an anti-virus rule that needs to be updated constantly. The chances of false-positives are small, but false
negatives can be produced by modifying the rootkits.
2. Read the rootkit_trojans.txt which contains a database of signatures of files trojaned by rootkits. This technique
of modifying binaries with trojaned versions was commonly used by most of the popular rootkits available. This
detection method will not find any kernel level rootkit or any unknown rootkit.
3. Scan the /dev directory looking for anomalies. The /dev should only have device files and the Makedev script.
A lot of rootkits use the /dev to hide files. This technique can detect even non-public rootkits.
4. Scan the whole filesystem looking for unusual files and permission problems. Files owned by root, with write
permission to others are very dangerous, and the rootkit detection will look for them. Suid files, hidden directories and files will also be inspected.
5. Look for the presence of hidden processes. We use getsid() and kill() to check if any pid is being used or not.
If the pid is being used, but ps cant see it, it is the indication of kernel-level rootkit or a trojaned version of
ps. We also verify that the output of kill and getsid are the same.
6. Look for the presence of hidden ports. We use bind() to check every tcp and udp port on the system. If we cant
bind to the port (its being used), but netstat does not show it, we probably have a rootkit installed
7. Scan all interfaces on the system and look for the ones with promisc mode enabled. If the interface is in
promiscuous mode, the output of ifconfig should show that. If not, we probably have a rootkit installed.
Configuration options
These configuration options can be specified in each agents ossec.conf, except auto_ignore and
alert_new_file which are manager side options. If the ignore option is specified on the manager the setting becomes global for all agents.
base_directory
The base directory that will be appended to the following options:
rootkit_files
rootkit_trojans
1.1. Manual
53
windows_malware
windows_audit
windows_apps
systems_audit
Allowed: Path to a directory Default: /var/ossec
rootkit_files
This option can be used to change the location of the rootkit files database.
Allowed: A file with the rootkit files signatures
Default: /etc/shared/rootkit_files.txt
rootkit_trojans
This option can be used to change the location of the rootkit trojans database.
Default: /etc/shared/rootkit_trojans.txt
Allowed: A file with the trojans signatures
windows_audit
system_audit
windows_apps
windows_malware
scanall
Tells rootcheck to scan the whole system (may lead to some false positives).
Default: no
Allowed: yes/no
frequency
Frequency that the rootcheck is going to be executed (in seconds).
Defaults: 36000 (10 hours)
Allowed: Time (in seconds)
disabled
Disables the execution of rootcheck.
Default: no
Allowed: yes/no
check_dev
Enable or disable the checking of something
Default: yes
Allowed: yes or no
check_files
Default: yes
Allowed: yes or no
54
check_if
Default: yes
Allowed: yes or no
check_pids
Default: yes
Allowed: yes or no
check_policy
Default: yes
Allowed: yes or no
check_ports
Enable or disable the checking of network ports.
Default: yes
Allowed: yes or no
check_sys
Default: yes
Allowed: yes or no
check_trojans
Enable or disable the checking of trojans.
Default: yes
Allowed: yes or no
check_unixaudit
Default: yes
Allowed: yes or no
check_winapps
Default: yes
Allowed: yes or no
check_winaudit
Default: 1
Allowed: 1 or 0
check_winmalware
Enable or disable the checking of Windows malware.
Default: yes
1.1. Manual
55
Allowed: yes or no
Understanding the Unix policy auditing on OSSEC
OSSECs policy monitor allows you to verify that all your systems conform to a set of policies regarding configuration
settings and applications usage. They are configured centrally on the ossec server and pushed down to the agents. It
also checks if a system in in compliance with the CIS Security Benchmarks and VMware security hardening guidelines.
The following systems are tested for the CIS and VMware guidelines:
Debian and Ubuntu
Red Hat and Fedora
Red Hat Enterprise Linux 5
VMWare ESX 3.0 and 3.5
Receiving Audit and Application alerts via Email
By default, both the policy auditing and application checks are logged as level 3, so you will not receive any e-mail
alerts with the original configuration.
If you wish to receive e-mail alerts for any (or both of the two) types of events, you need to create local rules with a
higher severity or with the alert_by_email option set.
Example1: Sending e-mail for every Audit event
Add to your local_rules.xml the following:

<pre>
<match>^System Audit</match>
<description>System Audit event.</description>
<group>rootcheck,</group>
</rule>
</pre>
Listing entries per agent
To control the policy database, use the rootcheck_control tool.

This page was originally authored by Daniel Cid for the OSSEC wiki.
1.1.9 Rules and Decoders

Testing OSSEC rules/decoders
The first problem most people have when troubleshooting OSSEC or trying to write new rules and decoders is how to
test them. In the past, this would require manually restarting OSSEC or creating a testing installation. As of version
1.6, there is a tool to simplify this task (ossec-logtest).
56
Testing using ossec-logtest
The tool ossec-logtest is installed into /var/ossec/bin. It will read the current rules and decoder (from
/var/ossec ) and accept log input from stdin:
# /var/ossec/bin/ossec-logtest
2008/07/04 09:57:28 ossec-testrule: INFO: Started (pid: 12683).
ossec-testrule: Type one log per line.
Jul 4 09:42:16 enigma sshd[11990]: Accepted password for dcid from 192.168.2.10 port 35259 ssh2
**Phase 1: Completed pre-decoding.

full event: "Jul 4 09:42:16 enigma sshd[11990]: Accepted password for dcid from 192.168.2.10 port 352
hostname: "enigma"
program_name: "sshd"
log: "accepted password for dcid from 192.168.2.10 port 35259 ssh2"
**Phase 2: Completed decoding.
decoder: sshd
dstuser: dcid
srcip: 192.168.2.10
**Phase 3: Completed filtering (rules).
Rule id: 10100
Level: 4
Description: First time user logged in.
**Alert to be generated.
In the above example, we provided an authentication success log and ossec-logtest showed us how it would be decoded,
what information was extracted and which rule fired. In the next example, we can see how it would extract a user logoff
message from Windows:
WinEvtLog: Security: AUDIT_SUCCESS(538): Security: lac: OSSEC-HM: OSSEC-HM: User Logoff: User Name: l

full event: WinEvtLog: Security: AUDIT_SUCCESS(538): Security: lac: OSSEC-HM: OSSEC-HM: User Logoff:
hostname: enigma
program_name: (null)
log: WinEvtLog: Security: AUDIT_SUCCESS(538): Security: lac: OSSEC-HM: OSSEC-HM: User Logoff: User N
decoder: windows
status: AUDIT_SUCCESS
id: 538
extra_data: Security
dstuser: lac
system_name: OSSEC-HM
Rule id: 18149
Level: 3
Description: Windows User Logoff.
In addition to the information above, ossec-logtest -f can be used to follow the log through the rule path:
1.1. Manual
57
# /var/ossec/bin/ossec-logtest -f
Jul 4 10:05:30 enigma sshd[27588]: Failed password for invalid user test2 from 127.0.0.1 port 19130 s

full event: Jul 4 10:05:30 enigma sshd[27588]: Failed password for invalid user test2 from 127.0.0.1
hostname: enigma
program_name: sshd
log: Failed password for invalid user test2 from 127.0.0.1 port 19130 ssh2
decoder: sshd
srcip: 127.0.0.1
**Rule debugging:
Trying rule: 1 - Generic template for all syslog rules.
*Rule 1 matched.
*Trying child rules.
Trying rule: 5500 - Grouping of the pam_unix rules.
Trying rule: 5700 - SSHD messages grouped.
*Rule 5700 matched.
Trying rule: 5709 - Useless SSHD message without an user/ip.
Trying rule: 5711 - Useless SSHD message without a user/ip.
Trying rule: 5707 - OpenSSH challenge-response exploit.
Trying rule: 5701 - Possible attack on the ssh server (or version gathering).
Trying rule: 5706 - SSH insecure connection attempt (scan).
Trying rule: 5713 - Corrupted bytes on SSHD.
Trying rule: 5702 - Reverse lookup error (bad ISP or attack).
Trying rule: 5710 - Attempt to login using a non-existent user
*Rule 5710 matched.
Trying rule: 5712 - SSHD brute force trying to get access to the system.
Rule id: 5710
Level: 5
Description: Attempt to login using a non-existent user
CDB List lookups from within Rules

Allow for CDB lookups from within rules in OSSEC (ossec-analysisd) of all possible fields.
Use cases
Anything that has a large number of items. Some examples:

named with recursive logs checking the www.malwaredomains.com list for suspicious domains
lists of approved users by server
mstark (on irc) originally came up with suggestion for approved software based on a md5 list
58
IP address lookups - there are a large number of lists of suspicious or known bad IP addresses to match inside
of ossec rules
Syntax for Lists
Rules A rule would use the following syntax to look up a key within a CDB database.
Positive key match This example is a search for the key within the rules/cdb_record_file and will match
if they key is present:
<list field="program_name" lookup="match_key">rules/records</list>
The lookup="match_key" is the default and can be left out as in this example:
<list field="program_name">rules/records</list>
Negative key match This example is a search for the key stored in field attribute and will match if it IS NOT present
in the database:
<list field="program_name" lookup="not_match_key">rules/records</list>
Key and Value match This example is a search for a key stored in the field attribute, and on a positive match the
returned value of the key will be processed using the regex in the check_value attribute:
<list field="program_name" lookup="match_key_value" check_value="^reject">rules/records</list>
Positive IP address match This example is a search for the IP address stored in the field attribute and will match if
it IS present in the database.
<list field="srcip" lookup="address_match_key">rules/records</list>
Negative IP address match This example is a search for the IP address stored in the field attribute and will match
if it IS NOT present in the database.
<list field="srcip" lookup="not_address_match_key">rules/records</list>
Key and Value Address Match This example is a search for a key stored in the field attribute, and on a positive
match the returned value of the key will be processed using the regex in the check_value attribute:
<list field="srcip" lookup="address_match_key_value" check_value="^reject">rules/records</list>
ossec.conf Each list will need to be defined and told to be available using the ossec.conf file. Using the following
syntax:
<ossec_config>
<rules>
<list>rules/records</list>
1.1. Manual
59
Commands CDB files must be compiled before they can be used. ossec-makelists is used to compile lists.
The command ossec-makelists will process and compile all lists if the master text rules have been changed. Basicly
logic is as follows:
Read ossec.conf for all lists
Check the mtime of each list and compare it to the mtime of the compiled .cdb file
if mtime is newer create new database file ending in .tmp
use atomic rename to change the .tmp to .cdb. This will invalidate all mmap pages currently in use by ossecanalysisd and will cause them to be reloaded with the new data as needed
List text file format Creating cdb lists the following file format is specified:
key1:value
key2:value
key3:diff value
Each key must be unique and is terminated with a colon :.

For IP addresses the dot notation is used for subnet matches
key
10.1.1.1
192.168.
172.16.19.
CIDR
10.1.1.1/32
192.168.0.0/16
172.16.19.0/24
Possible matches
10.1.1.1
192.168.0.0 - 192.168.255.255
172.16.19.0 - 172.16.19.255
Due to address lookups being based on the class boundary extra scripts are suggested for creating lists that need fine
control. Example of IP address list file:
192.168.: RFC 1918 Address space
172.16.:RFC 1918 Address space
10.:RFC 1918 Address space
Note:
Previous versions of this page page orginally was created by @j_hen on her blog
http://jentalkstoomuch.blogspot.com/2010/09/writing-custom-ossec-rules-for-your.html Some content may be
the same, but examples have been updated.
Note: In the xml based examples, any text between  are comments. In the console based examples,
anything after # may be an example. For more information on OSSECs non-standard regular expression (regex)
syntax, refer to the regex page.
60
Create Custom decoder and rules

One of the main features of OSSEC is monitoring system and application logs. Many popular services have logs and
decoders, but there are hundreds that are not covered. Custom applications and services will also not be covered.
Adding decoders and rules for services is generally very easy.
Adding a File to be Monitored
Adding a log file to the configuration for monitoring is simple. In the systems ossec.conf add an entry like this:
<localfile>
<location>/path/to/log/file</location>
</localfile>
syslog is a generic format, consisting of a singular line of text appended to the log file. There are other formats
available, they are detailed on the localfile syntax page.
Note: Additional examples can be found here. More detailed syntax can be found here.
After adding a localfile entry, the OSSEC processes must be restarted.
Create a Custom Decoder
The following log messages will be used for most of the examples in this section:
2013-11-01T10:01:04.600374-04:00 arrakis ossec-exampled[9123]: test connection from 192.168.1.1 via t

2013-11-01T10:01:05.600494-04:00 arrakis ossec-exampled[9123]: successful authentication for user tes
The first log message is broken down as follows:

2013-11-01T10:01:04.600374-04:00 - timestamp from rsyslog
arrakis - hostname of the system
ossec-exampled - daemon creating the log
[9123] - process ID of the ossec-exampled instance
test connection from 192.168.1.1 via test-protocol1 - log message
ossec-logtest will be used to test the custom decoder and any custom rules.
Custom decoders are added to the local_decoder.xml file, typically found in /var/ossec/etc on a standard
installation. The basic syntax is listed here, but this page is not well documented at the moment.
Using ossec-logtest on this sample rule results in the following output:
2013/11/01 10:39:07 ossec-testrule: INFO: Reading local decoder file.

full event: 2013-11-01T10:01:04.600374-04:00 arrakis ossec-exampled[9123]: test connection fr
hostname: arrakis
1.1. Manual
61
program_name: ossec-exampled
log: test connection from 192.168.1.1 via test-protocol1
No decoder matched.
There is not a lot of output here because OSSEC does not understand this log. Creating a decoder for this log message
will provide OSSEC much more information.
Phase 1 pre-decodes some information. The hostname is the system that generated the log message, program_name
is the name of the application that created the log, and log is the rest of the log message.
The following is a very basic decoder for ossec-exampled:
<decoder name="ossec-exampled">
<program_name>ossec-exampled</program_name>
</decoder>
This decoder simply looks for any log messages generated by ossec-exampled. Using a very generic decoder like
this can allow an OSSEC user to create more specific child decoders for services with less consistant log messages.
Here is the ossec-logtest output after adding this decoder:

hostname: arrakis
decoder: ossec-exampled
Phase 2 now correctly identifies this log message as coming from ossec-exampled. There is still some very important
information in the log message that should be decoded, namely the source IP and test-protocol1. To decode
these a child decoder will be added. It will set the ossec-exampled decoder as a parent, and use prematch to
limit its use to the correct log message.
<decoder name="ossec-exampled-test-connection">
<parent>ossec-exampled</parent>
<prematch offset="after_parent">^test connection </prematch> 
</command>
<active-response>
<!-active-response options here
-->
</active-response>
</ossec_config>
Command Options
command
In the commands configuration you create new commands to be used as responses. You can have as many
commands as you want. Each one should be inside their own command element. command is required.
name
Used to link the command to the response. name is required.
executable
It must be a file (with exec permissions) inside /var/ossec/active-response/bin. executable is
required.
You dont need to provide the whole path.
expect
The arguments this command is expecting (options are srcip and username). If a field is not within the expect
option it will be passed as a dash (-) instead of the actual value. For instance, if srcip is required for an
active-response script to work it must be inside of an expect option. expect is required.
Note: expect is required, but it is not reqiured to populate it. <expect></expect> is valid if no options
need to be passed to the active-response script.
timeout_allowed
Specifies if this command supports a timeout. This is optional, and defaults to yes.
Active-response Options
active-response
In the active-response configuration, you bind the commands (created) to events. You can have as many responses as you want. Each one should be inside their own active-response element.
114
disabled
Disables active response if set to yes. If this is not defined active response is enabled.
command
Used to link the response to the command
location
Where the command should be executed. You have four options:
Allowed:
local: on the agent that generated the event
server: on the OSSEC server
defined-agent: on a specific agent (when using this option, you need to set the agent_id to use)
all: or everywhere.
agent_id
The ID of the agent to execute the response (when defined-agent is set).
level
The response will be executed on any event with this level or higher.
rules_group
The response will be executed on any event in the defined group. Multiple groups can be defined if separated by
a comma.
rules_id
The response will be executes on any event with the defined ID. Multiple IDs can be specified if separated by a
comma.
timeout
How long in seconds until the reverse command is executed (IP unblocked, for example).
repeated_offenders
A comma separated list of increasing timeouts in minutes for repeat offenders. There can be a maximum of 5
entries. This should be set in the ossec.conf of an agent in an agent/server setup.
Example:
<active-response>
<command>firewall-block</command>
<location>defined-agent</location>
<agent_id>001</agent_id>
<rules_group>authentication_failed,authentication_failures</rules_group>
<repeated_offenders>30,60,120</repeated_offenders>
</active-response>
<active-response>
</active-response>
Example active response configurations:
Command: Restart OSSEC on *nix systems: This command can be used to restart the OSSEC processes. Its
commonly used to automatically restart agent processes when an agent.conf is modified. Since no parameters are
necessary the <expect> is empty.
115
<command>
<name>restart-ossec</name>
<executable>restart-ossec.sh</executable>
<expect></expect>
</command>
Active-Response: Restart the OSSEC processes: This active response will restart the OSSEC processes using the
restart-ossec command above. It is runs when rule 510010 is triggered, and it runs on the system where the
rule was triggered.
<active-response>
<command>restart-ossec</command>
</active-response>
Here is an example rule checking for changes to the agent.conf.

<rule id="510011" level="10">
<match>/var/ossec/etc/shared/agent.conf</match>
<description>agent.conf has been modified</description>
</rule>
Command: Block an IP with pf.sh: pf.sh adds an ip (srcip) to an ossec_fwtable packet filter table.
Information on pf tables can be found here.
<command>
<name>pf-block</name>
<executable>pf.sh</executable>
</command>
This is the minimum configuration necessary to utilize pf.sh:

table <ossec_fwtable> persist #ossec_fwtable
block in log quick from <ossec_fwtable>
Active-Response:
Block an IP with pf: This active-response blocks an IP triggering an
authentication_failed or authentication_failures alert. This active-response will run on
agent 001 only.
<active-response>
<command>pf-block</command>
<location>defined-agent</location>
<agent_id>001</agent_id>
</active-response>
Command:
Run
the
makelists.sh
script: The
makelists.sh
script
runs
/var/ossec/bin/ossec-makelists to update cdb lists. This command can be triggered by changes
in configured cdb lists.
116
<command>
<name>makelists</name>
<executable>makelists.sh</executable>
<expect>hostname</expect>
</command>
Active-Response: Update cdb lists: This active-response will run the makelists command to update the cdb
lists. This active-response should run only on the OSSEC server since agents do not have cdb lists.
<active-response>
<command>makelists</command>
<location>server</location>
</active-response>
Rule 510011: This example rule looks for changes to /var/ossec/lists/blocked.txt based on syscheck
alerts.
<rule id="510011" level="10">
<match>/var/ossec/lists/blocked.txt</match>
<description>blocked.txt has been modified</description>
</rule>
Command: firewall-drop: This is a command to run the firewall-drop.sh script to block the srcip.
<command>
<name>firewall-drop</command>
<executable>firewall-drop.sh</executable>
</command>
Active-Response: Block a srcip: This active-response will use the firewall-drop command to block an IP
address that has triggered an authentication_failed or authentication_failures alert. It will run on
all agents, and has a timeout of 600 seconds. It also uses the repeated_offenders option blocking an IP for 30
minutes on the second infraction, 60 minutes on the third, etc.
<active-response>
<command>firewall-block</command>
<location>all</location>
</active-response>
ossec.conf: Agentless Options

Overview
Supported types Agentless options are available in the the following installation types:
server
local
117
Location All agentless options must be configured in the /var/ossec/etc/ossec.conf and used within the <ossec_config> tag.
<ossec_config>
<agentless>
<!-agentless options here
-->
</agentless>
</ossec_config>
Options
agentless
This is the section that will contain the agentless configuration.
frequency
This controls the number of seconds between each run.
host
This defines the username and agentless host.
Example:
<host>root@linux.server.example.com</host>
state
This determines whether the checks are periodic or periodic_diff.
periodic: The output from the scripts is processed by the OSSEC processes.
periodic_diff: The output from the scripts is compared to the output of previous runs.
arguments
This defines the arguments passed to the script.
ossec.conf: Alerts Options
Overview
Supported types Alerts options are available in the the following installation types:
server
local
Location All alerts options must be configured in the /var/ossec/etc/ossec.conf and used within the <ossec_config>
tag.
<ossec_config>
<alerts>
<!-alerts options here
-->
118
</alerts>
</ossec_config>
Options
alerts
email_alert_level
Minimum alert level to send e-mail notifications.
Default: 7
Note: This is the minumum level for an alert to trigger an email. This overrides granular email alert levels.
Setting this to 10 would prevent emails for alerts at levels lower than 10 to be sent despite settings in the granular
email configuration. Individual rules can override this with the alert_by_email option.
log_alert_level
Minimum alert level to store the log messages.
Default: 1
use_geoip
Enable or disable GeoIP lookups.
Default: Disabled
Allowed: yes/no
ossec.conf: Client Options
Overview
Supported types client options are available in the the following installation types:
agent
Location All client options must be configured in the /var/ossec/etc/ossec.conf and used within the <ossec_config>
tag.
<ossec_config>
<client>
<!-client options here
-->
</client>
</ossec_config>
119
Options
server-ip
Specify the IP address of the analysis server
Allowed: Any Valid IP Address
server-hostname
Specify the hostname of the analysis server
Allowed: Any Valid hostname
port
Specifies the port to send the events (must be the same to the one used by the analysis server).
Default: 1514
Allowed: Any port number from 1 to 65535
config-profile
Specifies the agent.conf profiles to be used by the agent. Multiple profiles can be included, separated by a
comma and a space.
Example:
<client>
<config-profile>webserver, lowmemory</config-profile>
</client>
notify_time
Specifies the time in seconds between information messages sent by the agents to the server.
time-reconnect
Time in seconds until a reconnection attempt. This should be set to a higher number than notify_time.
ossec.conf: Database Output options
Overview
Supported types Database Output options are available in the the following installation types:
server
local
Location All database_output options must be configured in the /var/ossec/etc/ossec.conf and used within the <ossec_config> tag.
<ossec_config>
<database_output>
<!-Database Output options here
-->
</database_output>
</ossec_config>
120
Options
database_output
hostname
IP Address of the database server.
username
Username to access the database.
Allowed: Any Valid Username
password
Password to access the database.
Allowed: Any Password
database
Database name to store the alerts.
Allowed: database name
type
Type of database (Mysql or PostgreSQL).
Note: OSSEC must be compiled with the database type that is to be used.
Allowed: mysql/postgresql
ossec.conf: Granular Email options
Overview
Supported types Global options are available in the the following installation types:
server
local
Notes Global email configuration is necessary to use the granular email options.
Location All global options must be configured in the /var/ossec/etc/ossec.conf and used within the <ossec_config>
tag.
<ossec_config>
<email_alerts>
<!-Email_alerts options here
-->
</email_alerts>
</ossec_config>
121
Options
email_alerts
email_to
E-Mail recipients of alerts
Allowed: Any valid e-mail address
level
Minimum alerting level to forward the e-mails.
Allowed: Any alert level 0 to 16
Note: level should be set at or above the email_alert_level in the <alerts> section of the configuration.
group
The alert that must match this group to be forwarded.
Allowed: One group or category
event_location
The alert must match this event location to be forwarded. If multiple <event_location> options are specified, the last will be used.
Allowed: Any single agent name, hostname, ip address, or log file
format
Specifies the format of the e-mail
full: for normal e-mails
sms: for reduced size suitable for SMS
Default: full
Allowed: full/sms
rule_id
Option to send granular emails based on rule id.
Allowed:* One or more rule IDs can be used here, separated by a comma and space (, ).
Example:
<rule_id>5701, 5702</rule_id>
do_not_delay
Option to send the e-mail right away (no delay).
Example:
<do_not_delay />
do_not_group
Option to do not group alerts for this e-mail.
Example:
<do_not_group />
122
Examples
Example email alerts configurations:
Global Configuration:
<global>
<email_to>admin@example.com</email_to>
<smtp_server>127.0.0.1</smtp_server>
<email_from>ossecm@example.com</email_from>
</global>
Global Configuration with a larger maximum emails per hour:

<global>
<email_to>admin@example.com</email_to>
<smtp_server>127.0.0.1</smtp_server>
<email_from>ossecm@example.com</email_from>
<email_maxperhour>100</email_maxperhour>
</global>
Granular Email alert: Level 12 and above:

<email_alerts>
<email_to>other_admin@example.com</email_to>
<level>12</level>
</email_alerts>
Syscheck alerts to syscheck admin address:

<email_alerts>
<email_to>syscheck-admin@example.com</email_to>
</email_alerts>
Level 15 alerts from agent007 without delay or grouping:

<email_alerts>
<email_to>bond@example.com</email_to>
<event_location>agent007</event_location>
<level>15</level>
<do_not_delay />
<do_not_group />
</email_alerts>
ossec.conf: Global options

Overview
Supported types Global options are available in the the following installation types:
server
local
123
tag.
<ossec_config>
<global>
<!-Global options here
-->
</global>
</ossec_config>
Options
global
email_notification
Enable or disable e-mail alerting.
Default: no
Allowed: yes/no
email_to
E-mail recipient of the alerts.
Note: To use granular email configurations, a base configuration is necessary in the <global> section.
email_from
E-mail source of the alerts.
smtp_server
SMTP server.
Allowed: Any valid hostname or IP Address
email_maxperhour
Specifies the maximum number of e-mails to be sent per hour. All emails in excess of this setting will be queued
for later distribution.
Default: 12
Note: At the end of the hour any queued emails will be sent together in one email. This is true whether the
mail grouping is enabled or disabled.
email_idsname
If set, X-IDS-OSSEC: will be added to the email headers with the specified value.
Allowed: Any name
Note: This was added in OSSEC 2.8.
124
custom_alert_output
Specifies the format of alerts written to the logfile.
Variables:
"$TIMESTAMP"
"$FTELL"
"$RULEALERT"
"$HOSTNAME"
"$LOCATION"
"$RULEID"
"$RULELEVEL"
"$RULECOMMENT"
"$SRCIP"
"$DSTUSER"
"$FULLLOG"
"$RULEGROUP"
The time the event was processed by OSSEC.

Unknown
Unknown
Hostname of the system generating the event.
The file the log messages was saved to.
The rule id of the alert.
The rule level of the alert.
Unknown
The source IP specified in the log message.
The destination user specified in the log message.
The original log message.
The groups containing the rule.
stats
Alerting level for the events generated by the statistical analysis.
Default: 8
logall
States if we should store all the events received.
Default: no
Allowed: yes/no
memory_size
Sets the memory size for the event correlation.
Default: 1024
Allowed: Any size from 16 to 5096
white_list
List of IP addresses that should never be blocked by the active response (one per element). This option is only
valid in server and local installs.
Multiples Allowed: yes
Allowed: Any IP address or netblock
host_infomation
Alerting level for the events generated by the host change monitor.
Default: 8
prelude_output
Enables or disables prelude output.
Default: no
Allowed: yes/no
picviz_output
Enable picviz output.
Warning: PicViz is experimental.
125
Allowed: yes
picviz_socket
The full path of the socket that ossec will write alerts/events to. This will then be read by picviz for processing.
Allowed: File and path that ossec will create and feed events to.
zeromq_output
Enable ZeroMQ Output
Warning: ZeroMQ is experimental and will likely change drasticly from vesion to version.
Allowed: yes/no
zeromq_uri
This is zeromq URI that the publisher socket will bind to.
Warning: This URI format is defined by the ZeroMQ project.
<zeromq_uri>tcp://localhost:11111/</zeromq_uri>
This will listen for zeromq subscribers on ip address 127.0.0.1 port 11111
<zeromq_uri>tcp://eth0:21212/</zeromq_uri>
This will listen for zeromq subscribers on the ip address assiged to eth0 port 21212
<zeromq_uri>ipc:///alerts-zmq</zeromq_uri>
This will listen for zeromq on the Unix Domain socket /alerts-zmq.
geoip_db_path
The full path to the GeoIP IPv4 database file location.
Example:
<geoip_db_path>/etc/GeoLiteCity.dat</geoip_db_path>
ossec.conf: Localfile options

Overview
Supported types Localfile options are available in the the following installation types:
server
local
Location All localfile options must be configured in the /var/ossec/etc/ossec.conf or /var/ossec/etc/shared/agent.conf
and used within the <ossec_config> or <agent_config> tags.
<ossec_config>
<localfile>
<!-Localfile options here
-->
126
</localfile>
</ossec_config>
Options
localfile
location
Specify the location of the log to be read. strftime formats may be used for log file names. For instance,
a log file named file.log-2011-01-22 could be referenced with file.log-%Y-%m-%d. Wildcards
may be used on non-Windows systems. When wildcards are used, the log files must exist at the time
ossec-logcollector is started. It will not automatically begin monitoring new log files. strftime
and wildcards cannot be used on the same entry.
Default: Multiple (eg /var/log/messages)
Allowed: Any log file
log_format
The format of the log being read.
Note: If the log has one entry per line, use syslog.
Default: syslog
Allowed:
syslog This format is for plain text files in a syslog-like format. It can also be used when there
is no support for the logging format, and the logs are single line messages.
snort-full This is used for Snorts full output format.
snort-fast This is used for Snorts fast output format.
squid
iis
eventlog This is used for Microsoft Windows eventlog format.
eventchannel This is used for Microsoft Windows eventlogs, using the new EventApi. This
allows OSSEC to monitor both standard Windows eventlogs and more recent Application
and Services logs. This support was added in 2.8.
Warning: eventchannel cannot be used on Windows systems older than Vista.
mysql_log This is used for MySQL logs. It does not support multi-line logs.
postgresql_log This is used for PostgreSQL logs. It does not support multi-line logs.
nmapg This is used for monitoring files conforming to the grepable output from nmap.
127
apache
This format is for apaches default log format.
Example:
command This format will be the output from the command (as run by root) defined by command. Each line of output will be treated as a separate log.
full_command This format will be the output from the commandi (as run by root) defined by
command. The entire output will be treated as a single log.
Warning: command and full_command cannot be used in the agent.conf, and must be
configured in each systems ossec.conf.
djb-multilog
multi-line This option will allow applications that log multiple lines per event to be monitored.
This format requires the number of lines to be consistent. multi-line: is followed by
the number of lines in each log entry. Each line will be combined with the previous lines
until all lines are gathered. There may be multiple timestamps in a finalized event.
Allowed: <log_format>multi-line: NUMBER</log_format>
Example: Log messages:
Aug
Aug
Aug
Aug
Aug
9
9
9
9
9
14:22:47
14:22:47
14:22:47
14:22:47
14:22:47
hostname
hostname
hostname
hostname
hostname
log
log
log
log
log
line
line
line
line
line
one
two
three
four
five
Log message as analyzed by ossec-analysisd_:

Aug
9 14:22:47 hostname log line one Aug
9 14:22:47 hostname log line two Aug
command
The command to be run. All output from this command will be read as one or more log messages depending on
whether command or full_command is used.
Allowed: Any commandline and arguments.
alias
An alias to identify the command. This will replace the command in the log message.
For example <alias>usb-check</alias> would replace:
ossec: output: reg QUERY HKLM\SYSTEM\CurrentControlSet\Enum\USBSTOR:
with:
ossec: output: usb-check:
128
9 1
frequency
The minimum time in seconds between command runs. The command will probably not run every frequency
seconds exactly, but the time between runs will not be shorter than this setting. This is used with command and
full_command.
Allowed: Time in seconds.
check_diff
The output from an event will be stored in an internal database. Every time the same event is received, the output
is compared to the previous output. If the output has changed an alert will be generated.
only-future-events
Only used with the eventchannel log format. By default, when OSSEC starts the eventchannel log
format will read all events that ossec-logcollector missed since it was last stopped. It is possible to set
only-future-events to yes in order to prevent this behaviour. When set to yes, OSSEC will only
receive events that occured after the start of logcollector.
<localfile>
<loation>System</location>
<only-future-events>yes</only-future-events>
</localfile>
query
Only used with the eventchannel log format. It is possible to specify an XPATH query following the event
schema (see Microsofts documentation) in order to filter the events that OSSEC will process.
For example, the following configuration will only process events with an ID of 7040:
<localfile>
<location>System</location>
<query>Event/System[EventID=7040]</query>
</localfile>
ossec.conf: Remote Options

Overview
Supported types remote options are available in the the following installation types:
server
Location All remote options must be configured in the /var/ossec/etc/ossec.conf and used within the <ossec_config>
tag.
<ossec_config>
<remote>
<!-remote options here
-->
</remote>
</ossec_config>
129
Options
remote
connection
Specify the type of connection being enabled: secure or using syslog.
Default: secure
Allowed: secure/syslog
port
Specifies the port to listen for events.
Default:
1514: if connection is set to secure
514: if connection is set to syslog
Allowed: Any port number from 1 to 65535
protocol
Specifies the protocol to use for syslog events.
Default: udp
Allowed: udp or tcp
allowed-ips
List of IP addresses that are allowed to send syslog messages to the server (one per element).
Allowed: Any IP address or network
Note: It is necessary to allow at least one IP address when using the syslog connection type.
deny-ips
List of IP addresses that are not allowed to send syslog messages to the server(one per element).
Allowed: Any IP address or network
local_ip
Local ip address to listen for connections.
Default: all interfaces
Allowed: Any internal ip address
ipv6
Local ipv6 address to listen for connections.
Default: None
Allowed: Any IPv6 address.
Note: This is not well tested. For the time being I recommend using the full IPv6 address instead of one of the
many shortcuts.
ossec.conf: Reports options

Overview
130
Supported types Reports options are available in the the following installation types:
server
local
Location All reports options must be configured in the /var/ossec/etc/ossec.conf and used within the <ossec_config>
tag.
<ossec_config>
<reports>
<!-Reports options here
-->
</reports>
</ossec_config>
Options
reports
group
categories
rule
level
location
srcip
user
131
title
Allowed: Any Text
email_to
showlogs
Allowed: yes/no
Default: no
ossec.conf: Rootcheck options
Overview
Supported types rootcheck options are available in the the following installation types:
server
local
agent
Location All
rootcheck
options
must
be
configured
in
/var/ossec/etc/shared/agents.conf and used within the <ossec_config> tag.
the
/var/ossec/etc/ossec.conf
or
XML excerpt to show location if part of ossec.conf:

<ossec_config>
<rootcheck>
<!-rootcheck options here
-->
</rootcheck>
</ossec_config>
XML excerpt to the Location if part of agent.conf

<agent_config>
<rootcheck>
<!-rootcheck options here
-->
</rootcheck>
</agent_config>
132
Options
base_directory
The base directory that will be appended to the following options:
rootkit_files
rootkit_trojans
windows_malware
windows_audit
windows_apps
systems_audit
Allowed: Path to a directory Default: /var/ossec
rootkit_files
This option can be used to change the location of the rootkit files database.
Allowed: A file with the rootkit files signatures
Default: /etc/shared/rootkit_files.txt
rootkit_trojans
This option can be used to change the location of the rootkit trojans database.
Default: /etc/shared/rootkit_trojans.txt
Allowed: A file with the trojans signatures
windows_audit
system_audit
windows_apps
windows_malware
scanall
Tells rootcheck to scan the whole system (may lead to some false positives).
Default: no
Allowed: yes/no
frequency
Frequency that the rootcheck is going to be executed (in seconds).
Defaults: 36000 (10 hours)
Allowed: Time (in seconds)
disabled
Disables the execution of rootcheck.
Default: no
Allowed: yes/no
check_dev
Default: yes
Allowed: yes or no
133
check_files
Default: yes
Allowed: yes or no
check_if
Default: yes
Allowed: yes or no
check_pids
Default: yes
Allowed: yes or no
check_policy
Default: yes
Allowed: yes or no
check_ports
Enable or disable the checking of network ports.
Default: yes
Allowed: yes or no
check_sys
Default: yes
Allowed: yes or no
check_trojans
Enable or disable the checking of trojans.
Default: yes
Allowed: yes or no
check_unixaudit
Default: yes
Allowed: yes or no
check_winapps
Default: yes
Allowed: yes or no
check_winaudit
Default: 1
134
Allowed: 1 or 0
check_winmalware
Enable or disable the checking of Windows malware.
Default: yes
Allowed: yes or no
ossec.conf: Rules options
Overview
Supported types Rules options are available in the the following installation types:
server
local
tag.
<ossec_config>
<rules>
<!-Rules options here
-->
</rules>
</ossec_config>
Options
include
Load a single rule file.
Allowed: Path and file name of rule to load example: rules/config.xml
rule
Load a single rule file.
Allowed: Path and file name of rule to load example: rules/config.xml
Note: This is the same as include, but created to keep the syntax constant with other sections of the rules config.
rule_dir
Load a directory of rules. The order of loaded files will be in alphebical order and will not load any files that
have been loaded before.
Attributes:
pattern: is a regex match string use to determine if a file needs to be loaded.
Defaults: regex _rules.xml$ is used unless another one is specified.
Allowed: Path to a directory of rule files
Example:
135
1.Loading all rules in directory /var/ossec/rules ending ending with _rules.xml

<ossec_config>
<rules>
</rules>
</ossec_config>
2.Loading all rules in directory /var/ossec/rules/plugins ending with .xml

<ossec_config>
<rules>
<rule_dir pattern=".xml$">rules</rule_dir>
</rules>
</ossec_config>
decoder
Load a single decoder file. The path should be relative to the install directory, typically /var/ossec.
Note:
If no decoders are specified in ossec.conf the legacy etc/decoder.xml and
etc/local_decoder.xml are loaded
Warning: If <decoder> or <decoder_dir> are used, the default decoder.xml will not be used. It
must be specified explicitly.
Allowed: Path and file name of decoder to load example: rules/decoder/decoder.xml
decoder_dir
Load a directory of decoders. The order of loaded files will be in alphebics order and will not load any files that
have been loaded before. The path should be relative to the install directory, typically /var/ossec.
Attributes:
pattern: is a regex match string use to detemine if a file needs to be loaded.
Defaults: regex _decoder.xml$ is used unless another one is specified.
Allowed: Path to a directoy of decoder files
Example:
1.Loading all decoders in directory /var/ossec/rules ending ending with _decoder.xml
<ossec_config>
<rules>
<decoder_dir>rules</decoder_dir>
</rules>
</ossec_config>
2.Loading all decoders in directory /var/ossec/rules/plugins/plugins/decoders ending with .xml

<ossec_config>
<rules>
<decoder_dir pattern=".xml$">rules/plugins/decoders</decoder_dir>
</rules>
</ossec_config>
136
Warning: If <decoder> or <decoder_dir> are used, the default decoder.xml will not be used. It
must be specified explicitly.
list
Load a single cdb references for inclusion by other rules.
Note: Due to the way cdb files are compiled using tmp files by the ossec-makelists program the file extension
should not be include in this directive. ossecs tools will correctly append the correct .cdb or .txt extension as
needed.
Allowed: Path to a list file to be loaded and compiled.
<rules>
<list>rules/lists/blocked_hosts</list>
</rules>
ossec.conf: Syscheck Options

Overview
Supported types Syscheck options are available in the the following installation types:
server
local
agent
tag.
<ossec_config>
<syscheck>
<!-Syscheck options here
-->
</syscheck>
</ossec_config>
Options
directories
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 should be set on the system you wish to monitor (or in the agent.conf if
appropriate).
Default: /etc,/usr/bin,/usr/sbin,/bin,/sbin
Attributes:
realtime: Value=yes
137
This will enable realtime/continuous monitoring on Linux (using the inotify system calls) and Windows systems.
report_changes: Value=yes
Report diffs of file changes. This is limited to text files at this time.
Note: This option is only available on Unix-like systems.
check_all: Value=yes
All the following check_* options are used together.
check_sum: Value=yes
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
check_sha1sum: Value=yes
When used only the sha1 hash of the files will be checked.
check_md5sum: Value=yes
The md5 hash of the files will be checked.
check_size: Value=yes
The size of the files will be checked.
check_owner: Value=yes
Check the owner of the files selected.
check_group: Value=yes
Check the group owner of the files/directories selected.
check_perm: Value=yes
Check the UNIX permission of the files/directories selected. On windows this will only check the
POSIX permissions.
restrict: Value=string
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)
ignore
List of files or directories to be ignored (one entry per element). The files and directories are still checked, but
the results are ignored.
Default: /etc/mtab
Attributes:
type: Value=sregex
This is a simple regex pattern to filter out files so alerts are not generated.
Allowed: Any directory or file name
frequency
Frequency that the syscheck is going to be executed (in seconds).
The default is 6 hours or 21600 seconds
138
Default: 21600
Allowed: Time in seconds
scan_time
Time to run the scans (can be in the formats of 21pm, 8:30, 12am, etc)
Allowed: Time to run scan
scan_day
Day of the week to run the scans (can be in the format of sunday, saturday, monday, etc)
Allowed: Day of the week
auto_ignore
Specifies if syscheck will ignore files that change too often (after the third change)
Default: yes
Allowed: yes/no
alert_new_files
Specifies if syscheck should alert on new files created.
Default: no
Allowed: yes/no
Note: New files will only be detected on a full scan, this option does not work in realtime.
scan_on_start
Specifies if syscheck should do the first scan as soon as it is started.
Default: yes
Allowed: yes/no
windows_registry
Use this option to add Windows registry entries to be monitored (Windows-only).
Default: HKEY_LOCAL_MACHINESoftware
Note: New entries will not trigger alerts, only changes to existing entries.
registry_ignore
List of registry entries to be ignored.
Default: ..CryptographyRNG
refilter_cmd
Command to run to prevent prelinking from creating false positives.
Example:
<prefilter_cmd>/usr/sbin/prelink -y</prefilter_cmd>
139
Note: This option can potentially impact performance negatively. The configured command will be run for
each and every file checked.
ossec.conf: Syslog Output options

Overview
Supported types Syslog Output options are available in the the following installation types:
server
local
Location All syslog_output options must be configured in the /var/ossec/etc/ossec.conf and used within the <ossec_config> tag.
<ossec_config>
<syslog_output>
<!-Syslog Output options here
-->
</syslog_output>
</ossec_config>
Options
syslog_output
server
IP Address of the syslog server.
port
Port to forward alerts to.
Default 514
Allowed: Any valid port
level
Minimum alert level of the alerts to be forwarded.
Allowed: 1 - 16
group
Alerts belonging to this group will be forwarded.
Allowed: Any valid group. Separate multiple groups with the pipe (|) character.
Examples:
140
<group>authentication_failure|authentication_success</group>
rule_id
Alerts matching this rule_id will be forwarded.
Allowed: Any valid rule_id
location
Alerts from this location will be forwarded.
Allowed: Any valid logfile location
format
Format of alert output. The default format is default, or full syslog output.
CEF is the ArcSight Common Event Format.
json can be used with a variety of tools.
The splunk option is for sending data to a Splunk server.
Allowed default, cef, splunk, json
<syslog_output>
<port>514</port>
</syslog_output>
3.1.4 agent.conf
Overview
More information on using the agent.conf can be found here
Supported types
The agent.conf is valid on the server install only.

Location
The agent.conf exists in /var/ossec/etc/shared. It should be readable by the ossec user.

<agent_config>
...
</agent_config>
141
Options
agent_config_options
agent_config
Defines the beginning or end of an agent configuration block.
name
This option to agent_config allows you to assign the block the one particular agent by using the agents
name.
Example: <agent_config name=agent007>
os
This option to agent_config allows you to assign the block to an operating system.
Example: <agent_config os=Windows>
Allowed: Any OS family (Windows, Linux, OpenBSD, etc.)
profile
This option to agent_config allows you to assign a profile name to the the block. Any agent may use this
block if it is configured to use the defined profile.
Example: <agent_config profile=webservers>
3.1.5 internal_options.conf: syntax and options

internal_options.conf: analysisd
analysisd.default_timeframe
Analysisd default rule timeframe
Default: 360
Allowed: Any interger
analysisd.stats_maxdiff
Default: 25000
analysisd.stats_mindiff
Default: 250
analysisd.stats_percent_diff
Default: 30
analysisd.fts_list_size
Default: 32
analysisd.fts_min_size_for_str
Default: 14
142
analysisd.log_fw
Default: 1
analysisd.debug
Default: 0
internal_options.conf: agent
agent.debug
Run the agents processes in debug mode.
Default: 0
internal_options.conf: dbd
dbd.reconnect_attempts
The number of times ossec-dbd will attempt to reconnect to the database.
Default: 10
internal_options.conf: logcollector
logcollector.loop_timeout
Default: 2
logcollector.open_attempts
Default: 8
logcollector.remote_commands=0
Allow the agents to run commands defined in agent.conf.
Allowed: 0,1
Default: 0
Note: This option first appeared in OSSEC 2.7.
internal_options.conf: maild
maild.strict_checking
Default: 1
Allowed: 0 or 1
maild.groupping
If set to 1 alerts will be grouped together in one email. These alerts may be of different types or levels, and may
be from different systems.
Default: 1
Allowed: 0 or 1
143
maild.full_subject
If set to 1 maild will use a full subject when sending alert emails. If set to 0 the subject is shortened.
Default: 0
Allowed: 0 or 1
maild.geoip
If set to 1 mails will display GeoIP data in alert emails.
Default: 1
Allowed: 0 or 1
internal_options.conf: monitord
monitord.day_wait
Amount of time OSSEC will wait before compressing/signing log files.
Default: 10
monitord.compress
If set to 1 ossec-monitord will compress old log files.
Default: 1
Available: 0 or 1
monitord.sign
If set to 1 ossec-monitord will sign old log files.
Default: 1
monitord.monitor_agents
Default: 1
internal_options.conf: remoted
remoted.recv_counter_flush
Default: 128
remoted.comp_average_printout
Default: 19999
remoted.verify_msg_id
Default: 1
remoted.debug
Default: 0
internal_options.conf: syscheck
syscheck.sleep
ossec-syscheckd uses this setting to determine how long to sleep after reading
syscheck.sleep_after number of files. By default ossec-syscheckd sleeps for 2 seconds
after checking 15 files.
Default: 2
144
syscheck.sleep_after
ossec-syscheckd reads this many files before sleeping for syscheck.sleep seconds.
Default: 15
internal_options.conf: windows
windows.debug
Default: 0 Allowed: 0 or 1
3.2 Output Formats

3.2.1 JSON Format
At this time we have one alert JSON formatted messages.
{
"rule":1000,
"level":1,
"comment":"This is a comment",
"sidid":1111,
"cve":"cve-1001-1000",
"action":"drop",
"srcip":"10.1.1.1",
"srcport":"1000",
"srcuser":"root",
"dstip":"10.2.2.2",
"dstport":"2000",
"dstuser":"root",
"location":"/var/log/auth.log",
"full_log":"This is the full log message",
"file":{
"path":"/etc/",
"md5_before":"XXXXXXXXXXXXXXXXXXXX",
"md5_after":"YYYYYYYYYYYYYYYYYYYY",
"sha1_before":"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"sha1_after":"YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY",
"owner_before":"root",
"owwer_after":"nobody",
"gowner_before":"root",
"gowner_after":"nodody",
"perm_before":660,
"perm_after":777,
}
}
3.3 Man pages

3.3.1 agent-auth
The agent-auth program is the client application used with ossec-authd to automatically add agents to an OSSEC
manager.
3.2. Output Formats
145
Warning: By default there is no authentication or authorization involved in this transaction, so it is recommended

that this daemon only be run when a new agent is being added.
agent-auth argument options

-A <agent_name>
Agent name to be used. Default hostname
-D
Directory where OSSEC is installed. Default /var/ossec
-d
Execute agent-auth in debug mode. This option can be used multiple times to increase the verbosity of the debug
messages.
-g <group>
Run as group.
-h
Display the help message
-k <path>
Full path to the agent key.
-m <manager_ip>
IP address of the manager.
-p <port>
Port ossec-authd is running on.
Default 1515
-V
Display OSSEC Version and license information.
-v <path>
Full path to the CA certificate used to verify the server.
-x <path>
Full path to the agent certificate.
Note: The following options are only necessary if verification of server or client certificates is desired. See Optional
Server Authentication and Optional Client Authentication below.
-x </path/to/certificate>
Load the PEM encoded certificate that will be presented to ossec-authd during establishment of the SSL connection.
-k </path/to/private_key>
Load the certificates corresponding PEM encoded private key.
-v </path/to/CA_certificate>
Load the PEM encoded CA Certificate that will be used to verify ossec-authd if desired. If this option is used
then ossec-authd must present a valid certificate signed by this CA.
146
Optional Server Authentication

agent-auth can verify that the server its connecting to presents a valid X.509 certificate when requesting a key.
This is optional and is only useful if hosts in your environment have access to the root certificate of the CA that signed
the certificate presented by ossec-authd. If server certificate verification is desired then the relevant CA certificate
must be loaded with the -v option, then if the server does not present a valid certificate the agent will not be allocated
a key.
A certificate presented by the server may be found to be invalid for the following reasons:
It was not signed by the specified CA.
It doesnt contain the IP address or hostname given with the -m option in the subjects common name field or a
subject alternative name extension field.
It is expired.
While server authentication is optional it is highly recommended that it be used if possible when running ossec-authd
and agent-auth.
Optional Client Authentication
agent-auth can present its own certificate to the server for verification. This is mandatory if ossec-authd was run
with the -v option and optional otherwise. This is only useful if hosts in your environment are assigned certificates
when theyre provisioned (or at some point before being added to OSSEC). Use the -x and -k options to load a
certificate and private key.
agent-auth example usage
Example: Adding an agent with a hostname
# /var/ossec/bin/agent-auth -m 192.168.1.1 -p 1515 -A example-agent
INFO: Connected to 192.168.1.1:1515
INFO: Using agent name as: melancia
INFO: Send request to manager. Waiting for reply.
INFO: Received response with agent key
INFO: Valid key created. Finished.
INFO: Connection closed.
Example: Adding an agent and verifying the certificate presented by ossec-authd
# /var/ossec/bin/agent-auth -m ossec-manager.localdomain -p 1515 -v /etc/pki/CA/certs/internal_CA.cer

INFO: Verifing managers certificate
...
Example: Adding an agent and presenting a certificate to ossec-authd
# /var/ossec/bin/agent-auth -m ossec-manager.localdomain -p 1515 -x /var/ossec/etc/client.cert -k /va

...
3.3. Man pages
147
3.3.2 agent_control
The agent_control tool allows you to query and get information from any agent you have configured on your server
and it also allows you to restart (run now) the syscheck/rootcheck scan on any agent.
Enabling active response will be necessary to start scans remotely and possibly other functions.
agent_control argument options
-h
-l
List available (active or not) agents
-lc
List active agents
-i <agent_id>
Extracts information from an agent
-R <agent_id>
Restarts the OSSEC processes on the agent
Note: Requires active response to be enabled.
-r
Run the integrity/rootcheck checking on agents.
agent_control -u
Must be utilized with agent_control -a or
Note: Requires active response to be enabled.

-a
Utilizes all agents.
-u <agent_id>
<agent_id> that will perform the requested action.
agent_control example usage
Example 1: Listing all active agents
The first interesting argument is agent_control -lc, to list the connected (active agents). To list all of them, use
agent_control -l only.
# /var/ossec/bin/agent_control -lc
OSSEC HIDS agent_control. List of available agents:
ID: 000, Name: enigma.ossec.net (server), IP: 127.0.0.1, Active/Local
ID: 002, Name: winhome, IP: 192.168.2.190, Active
ID: 005, Name: jul, IP: 192.168.2.0/24, Active
ID: 165, Name: esqueleto2, IP: 192.168.2.99, Active
ID: 174, Name: lili3win, IP: 192.168.2.0/24, Active
148
Example 2: Querying information from agent 002
To query an agent, just use the agent_control -i option followed by the agent id.
# /var/ossec/bin/agent_control -i 002
OSSEC HIDS agent_control. Agent information:
Agent ID: 002
Agent Name: winhome
IP address: 192.168.2.190
Status: Active
Operating system: Microsoft Windows XP Professional (Build 2600)
Client version: OSSEC HIDS v1.5-SNP-080412
Last keep alive: Fri Apr 25 14:33:03 2008
Syscheck last started at: Fri Apr 25 05:07:13 2008
Rootcheck last started at: Fri Apr 25 09:04:12 2008
Example 3: Executing syscheck and rootcheck scan immediately
To execute the syscheck/rootcheck scan immediately, use the agent_control -r option followed by the
agent_control -u with the agent id.
# /var/ossec/bin/agent_control -r -u 000
OSSEC HIDS agent_control: Restarting Syscheck/Rootcheck locally.
3.3.3 clear_stats
Clear the events stats
clear_stats argument options
-h
Print and display a help message of all available options to clear_stats
-a
Clear all the stats (averages).
-d
Clear the daily averages.
-w
Clear the weekly averages.
3.3.4 list_agents
OSSEC HIDS list_agents: List available agents.
list_agents is only available on OSSEC servers or local mode installations. It can be used to retrieve
a list of all OSSEC agents that successfully connected to the server in the past
a list of all OSSEC agents currently connected to the server
3.3. Man pages
149
a list of all OSSEC agents that were connected to the server in the past but are currently not connected.
If an agent was added via the manage_agents tool but has not yet been connected to the server, it will not show up in
the output of list_agents.
list_agents argument options
-h
Display the help message.
-a
List all agents.
-c
List the connected (active) agents.
-n
List the not connected (active) agents.
3.3.5 manage_agents
manage_agents is available in two versions:
a version for OSSEC server installations
a version for OSSEC agent installations
The purpose of manage_agents is to provide an easy-to-use interface to handle authentication keys for OSSEC agents.
These authentication keys are required for secure (encrypted and authenticated) communication between the OSSEC
server and its affiliated agent instances.
manage_agents argument options
-V
Display OSSEC Version.
-h
-l
List available agents.
-e <agent_id>
Extracts key for an agent (Manager only).
-r <agent_id>
Remove an agent (Manager only).
-i <key>
Import authentication key (Agent only).
-f
<file>
Generate clients in bulk from <file> (Manager only). The file is a comma delimited file containing the IP
addresses and agent names to be added. This file should be located within /var/ossec, and referenced by its
path relative to /var/ossec.
Example:
150
# cat /var/ossec/k
192.168.1.2,host02
192.168.1.3,host03
# /var/ossec/bin/manage_agents -f /k
Bulk load file: /k
Opening: [/k]
Agent information:
ID:002
Name:host02
IP Address:192.168.1.2
Agent added.
Agent information:
ID:003
Name:host03
IP Address:192.168.1.3
Agent added.
Usage
The OSSEC manual goes into details on usage of this command at Managing Agents
3.3.6 ossec-agentd
ossec-agentd is the client side daemon that communicates with the server. It runs as ossec and is chrooted to
/var/ossec by default.
ossec-agentd argument options
-c <config>
Run ossec-agentd using <config> as the configuration file.
Default: /var/ossec/etc/ossec.conf
-D <dir>
Chroot to <dir>.
Default: /var/ossec
-d
Run in debug mode. This option can be used multiple times to increase the verbosity of the debug messages.
-f
Run ossec-agentd in the foreground.
-g <group>
Run ossec-agentd as <group>.
-h
-t
Test configuration.
3.3. Man pages
151
-u <user>
Run ossec-agentd as <user>.
Default: ossecm
-V
Version and license information.
3.3.7 ossec-agentlessd
ossec-agentlessd argument options
-c <config>
Read the configuration from file <config>.
-D <dir>
chroot to <dir>.
-d
Execute ossec-agentlessd in debug mode. This option can be used multiple times to increase the verbosity of
the debug messages.
-f
Run ossec-agentlessd in the foreground.
-g <group>
Run as group.
-h
Display a help message.
-t
Test the configuration.
-u
Run as user.
-V
3.3.8 ossec-analysisd
ossec-analysisd recveives the log messages and compares them to the rules. It will create alerts when a log
message matches an applicable rule.
ossec-analysisd argument options
-c <config>
Configuration file ossec-analysisd should use.
-D <dir>
Chroot to <dir>.
-d
Execute ossec-analysisd in debug mode. This can be used more than once to increase the verbosity of the debug
messages.
152
-f
-g <group>
Run as group.
-h
-t
-u
Run as user.
-V
Display the version and license information.
3.3.9 ossec-authd
The ossec-authd daemon will automatically add an agent to an OSSEC manager and provide the key to the agent.
The agent-auth application is the client application used with ossec-authd. ossec-authd will create an agent with an ip
address of any instead of using its actual IP.
Warning: By default there is no authentication or authorization involved in this transaction, so it is recommended
that this daemon only be run when a new agent is being added.
ossec-authd argument options

-D <dir>
chroot to <dir>.
-d
Execute ossec-authd in debug mode. This option can be used multiple times to increase the verbosity of the
debug messages.
-g <group>
Run as group.
-h
-i
Add agents with a specific IP address instead of using any.
-k <path>
Full path to the server key.
-p <port>
Listen on port.
Default 1515
-t
-V
3.3. Man pages
153
-v <path>
Full path to the CA certificate used to verify the clients.
-x <path>
Full path to the server certificate.
Creating SSL keys
ossec-authd requires SSL keys to run. This process will create the necessary keys in /var/ossec/etc and
allow ossec-authd to start:
# openssl genrsa -out /var/ossec/etc/sslmanager.key 2048

# openssl req -new -x509 -key /var/ossec/etc/sslmanager.key -out /var/ossec/etc/sslmanager.cert -days
Without the key ossec-authd will give the following error:
[user@ossec-manager] :; sudo /var/ossec/bin/ossec-authd

2012/04/18 11:05:01 ossec-authd: INFO: Started (pid: 20669).
2012/04/18 11:05:01 ossec-authd: ERROR: Unable to read certificate file (not found): /var/ossec/etc/s
2012/04/18 11:05:01 ossec-authd: ERROR: SSL error. Exiting.
If the default locations of /var/ossec/etc/sslmanager.cert and /var/ossec/etc/sslmanager.key are not suitable then the -x
and -k options can be used to specify alternative locations.
Optional Client Authentication
ossec-authd can verify that connecting agents present a valid X.509 certificate when requesting a key. This is
optional and is only useful if hosts in your environment are assigned certificates when theyre provisioned (or at some
point before being added to OSSEC). If agent certificate verification is desired then the relevant CA certificate must
be loaded with the -v option. This will cause ossec-authd to verify that agents present a valid certificate when
requesting a key. If an agent does not present a certificate or presents an invalid certificate then the agent will not be
allocated a key.
A certificate presented by an agent may be found to be invalid for the following reasons:
It was not signed by the specified CA.
It is expired.
ossec-authd example usage
Example: Running ossec-authd
# /var/ossec/bin/ossec-authd -p 1515 >/dev/null 2>&1 &
And the logs when an agent is added:

2011/01/19
2011/01/19
2011/01/19
2011/01/19
154
15:04:40
15:04:41
15:04:41
15:04:41
ossec-authd:
ossec-authd:
ossec-authd:
ossec-authd:
INFO:
INFO:
INFO:
INFO:
New connection from 192.168.10.5

Received request for a new agent (example-agent) from: 192.168
Agent key generated for example-agent (requested by 192.168.10
Agent key created for example-agent (requested by 192.168.10.5
Example: Running ossec-authd with client authentication

# /var/ossec/bin/ossec-authd -v /var/ossec/etc/CA.cert -d
If debug output is enabled then Peer verification requested will be displayed when starting.
2014/06/07
2014/06/07
2014/06/07
2014/06/07
2014/06/07
2014/06/07
2014/06/07
2014/06/07
2014/06/07
2014/06/07
17:04:56
17:04:56
17:04:56
17:04:56
17:04:56
17:04:58
17:04:58
17:04:58
17:04:58
17:04:58
ossec-authd:
ossec-authd:
ossec-authd:
ossec-authd:
ossec-authd:
ossec-authd:
ossec-authd:
ossec-authd:
ossec-authd:
ossec-authd:
DEBUG: Starting ...

INFO: Started (pid: 2043).
DEBUG: Peer verification requested.
DEBUG: Returning CTX for server.
DEBUG: Going into listening mode.
INFO: New connection from 192.168.10.5
INFO: Received request for a new agent (example-agent) from: 192.168
INFO: Agent key generated for example-agent (requested by 192.168.10
INFO: Agent key created for example-agent (requested by 192.168.10.5
DEBUG: Process 2044 exited
3.3.10 ossec-control
ossec-control is a script to start, stop, configure, or check on the status of OSSEC processes. ossc-control
can enable or disable client-syslog, database logging, agentless configurations, and debug mode.
ossec-control argument options
start Start the OSSEC processes.
stop Stop the OSSEC processes.
restart Restart the OSSEC processes.
reload Restart all OSSEC processes except ossec-execd. This allows an agent to reload without
losing active response status.
Note: This is only available on an OSSEC agent.
status Determine which OSSEC processes are running.
enable Enable OSSEC functionality.
database Enable the ossec-dbd daemon for logging to a database.
Available: Server and local installs only.
Note: Database support must be compiled in at install time.
client-syslog Enable ossec-csyslogd for logging to remote syslog.
agentless Enable ossec-agentlessd for running commands on systems without OSSEC agents.
debug Run all OSSEC daemons in debug mode.
disable Disable OSSEC functionality.
3.3. Man pages
155
database Disable the ossec-dbd daemon for logging to a database.

Note: Database support must be compiled in at install time.
client-syslog
Disable ossec-csyslogd for logging to remote syslog.
agentless Disable ossec-agentlessd for running commands on systems without OSSEC agents.
debug Turn off debug mode.
ossec-control example usage
Example: Running ossec-control
# /var/ossec/bin/ossec-control
Usage: /var/ossec/bin/ossec-control {start|stop|restart|status|enable|disable}
3.3.11 ossec-csyslogd
ossec-csyslogd is a daemon that forwards the OSSEC alerts via syslog. Configuration is done in the
<syslog_output> section of the ossec.conf. (see ossec.conf: Syslog Output options)
ossec-csyslogd argument options
-c <config>
Run ossec-csyslogd using <config> as the configuration file.
-D <dir>
Chroot to <dir>.
Default: /var/ossec
-d
Execute ossec-csyslogd in debug mode. This option can be used multiple times to increase the verbosity of the
debug messages.
-f
Run ossec-csyslogd in the foreground.
-g <group>
Run ossec-csyslogd as <group>.
-h
156
-t
Test configuration.
-u <user>
Run ossec-csyslogd as <user>.
Default: ossecm
-V
3.3.12 ossec-dbd
The ossec-dbd daemon inserts the alert logs into a database, either postgresql or mysql. ossec-dbd is configured
in ossec.conf. (see ossec.conf: Database Output options)
ossec-dbd argument options
-c <config>
Run ossec-dbd using <config> as the configuration file.
-D <dir>
Chroot to <dir>.
Default: /var/ossec
-d
Execute ossec-dbd in debug mode. This option can be used multiple times to increase the verbosity of the debug
messages.
-f
Run ossec-dbd in the foreground.
-g <group>
Run ossec-dbd as <group>.
-h
-t
Test configuration.
-u <user>
Run ossec-dbd as <user>.
Default: ossecm
-V
3.3.13 ossec-execd
ossec-execd executes active responses by running the configured scripts. ossec-execd is configured in the
ossec.conf. (see ossec.conf: Active Response Options)
3.3. Man pages
157
ossec-execd argument options

i .. option:: -c <config>
Run ossec-execd using <config> as the configuration file.
-d
Execute ossec-execd in debug mode. This option can be used multiple times to increase the verbosity of the
debug messages.
-f
Run ossec-execd in the foreground.
-g
Run as group.
-h
-t
Test configuration.
-V
3.3.14 ossec-logcollector
The ossec-logcollector daemon monitors configured files and commands for new log messages.
ossec-logcollector is configured in ossec.conf. (see ossec.conf: Localfile options)
ossec-logcollector argument options
-c <config>
Run ossec-logcollector using <config> as the configuration file.
-d
Execute ossec-logcollector in debug mode. This option can be used multiple times to increase the verbosity of
the debug messages.
-f
Run ossec-logcollector in the foreground.
-h
-t
Test configuration.
-V
158
3.3.15 ossec-logtest
ossec-logtest is the single most useful tool when working with ossec. This tool allows oneself to test and verify log
files in the exact same way that ossec-anaylistd does.
Something ossec-logtest can help with:
Writing rules (Debugging your custom rules)
Troubleshooting false positives or false negatives
ossec-logtest accepts standard input for all log to test.
osssec-logtest argument options
-a
Analyze of input lines as if they are live events.
-c <config>
<config> is the path and filename to load in place of the default /var/ossec/etc/ossec.conf.
-D <dir>
This is the path that ossec-logtest will chroot to before it completes loading all rules, decoders, and lists and
processing standard input.
-d
Print debug output to the terminal. This option can be used multiple times to increase the verbosity of the debug
messages.
-h
Print the help message to the console.
-t
Test configuration. This will print file details on the ossec-anaylistd rules, decoders, and lists as they are loaded
and the order they were processed.
-U <rule-id:alert-level:decoder-name>
This option will cause ossec-logtest to return with an exit status other then zero unless the last line tested matches
the arguments passed.
Note: This only works for the last, line so passing many lines into ossec-logtest with this argument may not
provide the desired results.
Note: This ossec-logtest code requires access to all ossec configuation files. This is a bug and will be corrected.
It is documented in issue #61 <https://bitbucket.org/jbcheng/ossec-hids/issue/61/ossec-logtest-must-be-usedwith-a-full>_
%
%
0
%
%
3
echo "Aug 29 15:33:13 ns3 named[464]: client 217.148.39.3#1036: query (cache) denied" | sudo /
echo $?
echo "Aug 29 15:33:13 ns3 XXXXXX[464]: client 217.148.39.3#1036: query (cache) denied" | sudo
echo $?
-V
Print the Version and license message for OSSEC and ossec-logtest.
3.3. Man pages
159
-v
Full output of all details and matches.
Note: This the key argument to troubleshoot a rule, decoder problem.
Note: This is argument was incorrectly displayed as running in the foreground in all version before version 2.5
Caveats
Some log formats will be processed differently than they appear in the log file. MySQL log files for instance will have
MySQL log: prepended to the log message before analysis. If using ossec-logtest to test MySQL logs, please add
this string to the beginning.
Example:
Given the following MySQL log message:
130218 12:07:52 [Warning] Unsafe statement written to the binary log using statement format since BIN
The message that should be pasted into ossec-logtest is:
MySQL log: 130218 12:07:52 [Warning] Unsafe statement written to the binary log using statement forma
ossec-logtest example usage

Example 1: Testing standard rules
# echo "Aug 29 15:33:13 ns3 named[464]: client 217.148.39.3#1036: query (cache) denied" | /var/ossec/
2010/08/10 06:57:06 ossec-testrule: INFO: Reading decoder file loadables/decoders/00_decoders.xml.
2010/08/10 06:57:06 ossec-testrule: INFO: Reading decoder file loadables/decoders/50_named.xml.
2010/08/10 06:57:06 ossec-testrule: INFO: Reading decoder file loadables/decoders/50_pam.xml.
2010/08/10 06:57:06 ossec-testrule: INFO: Reading decoder file loadables/decoders/50_sshd.xml.
2010/08/10 06:57:06 ossec-testrule: INFO: Reading loading the lists file: loadables/lists/rfc1918-pr

full event: Aug 29 15:33:13 ns3 named[464]: client 217.148.39.3#1036: query (cache) denied
hostname: ns3
program_name: named
log: client 217.148.39.3#1036: query (cache) denied
decoder: named
srcip: 217.148.39.3
**Rule debugging:
Trying rule: 1 - Generic template for all syslog rules.
*Rule 1 matched.
Trying rule: 30100 - Apache messages grouped.
Trying rule: 7200 - Grouping of the arpwatch rules.
Trying rule: 6200 - Asterisk messages grouped.
160
Trying rule: 9600 - cimserver messages grouped.

Trying rule: 4700 - Grouping of Cisco IOS rules.
Trying rule: 3900 - Grouping for the courier rules.
Trying rule: 9700 - Dovecot Messages Grouped.
Trying rule: 11100 - Grouping for the ftpd rules.
Trying rule: 9300 - Grouping for the Horde imp rules.
Trying rule: 3600 - Grouping of the imapd rules.
Trying rule: 3700 - Grouping of mailscanner rules.
Trying rule: 3800 - Grouping of Exchange rules.
Trying rule: 6300 - Grouping for the MS-DHCP rules.
Trying rule: 6350 - Grouping for the MS-DHCP rules.
Trying rule: 11500 - Grouping for the Microsoft ftp rules.
Trying rule: 50100 - MySQL messages grouped.
Trying rule: 12100 - Grouping of the named rules
*Rule 12100 matched.
Trying rule: 12107 - DNS update using RFC2136 Dynamic protocol.
Trying rule: 12101 - Invalid DNS packet. Possibility of attack.
Trying rule: 12109 - Named fatal error. DNS service going down.
Trying rule: 12102 - Failed attempt to perform a zone transfer.
Trying rule: 12103 - DNS update denied. Generally mis-configuration.
Trying rule: 12104 - Log permission misconfiguration in Named.
Trying rule: 12105 - Unexpected error while resolving domain.
Trying rule: 12106 - DNS configuration error.
Trying rule: 12108 - Query cache denied (maybe config error).
*Rule 12108 matched.
Rule id: 12108
Level: 4
Description: Query cache denied (maybe config error).
Info - Link: http://www.reedmedia.net/misc/dns/errors.html
Example 2: Using OSSEC for the forensic analysis of log files
If you have one old log file that you want to check or if you are doing a forensics analysis of a box and wants to check
the logs with OSSEC, we now have a solution too.
Lets say you have a file /var/log/secure that you want to analyze with OSSEC. You need to use the ossec-logtest tool
with the -a flag to reproduce the alerts:
# cat /var/log/secure | /var/ossec/bin/ossec-logtest -a
** Alert 1264788284.11: - syslog,sshd,authentication_success,
2010 Jan 29 14:04:44 enigma->stdin
Rule: 5715 (level 3) -> SSHD authentication success.
Src IP: a.b.2.15
User: dcid
Jan 15 10:25:01 enigma sshd[17594]: Accepted password for dcid from a.b.2.15 port 47526 ssh2
** Alert 1264788284.12: - syslog,sshd,authentication_success,
2010 Jan 29 14:04:44 enigma->stdin
Rule: 5715 (level 3) -> SSHD authentication success.
Src IP: 127.0.0.1
User: dcid
Jan 15 11:19:20 enigma sshd[18853]: Accepted publickey for dcid from 127.0.0.1 port 6725 ssh2
3.3. Man pages
161
You will get the alerts just like you would at /var/ossec/logs/alerts.log. The benefit now is that you can pipe this output
to ossec-reported to get a better view of what is going on:
# cat /var/log/secure | /var/ossec/bin/ossec-logtest -a |/var/ossec/bin/ossec-reported
Report completed. ==
-------------------------------->Processed alerts: 522
->Post-filtering alerts: 522
Top entries for Source ip:
-------------------------------89.200.169.170 |41 |
127.0.0.1 |33 |
83.170.106.142 |20 |
204.232.206.109 |16 |
..
Top entries for Username:
-------------------------------root |247 |
Top entries for Level:
-------------------------------Severity 5 |406 |
Severity 3 |41 |
Severity 10 |32 |
Top entries for Group:
-------------------------------syslog |522 |
sshd |509 |
authentication_failed |369 |
invalid_login |146 |
Top entries for Rule:
-------------------------------5716 - SSHD authentication failed. |223 |
5710 - Attempt to login using a non-existent.. |146 |
5715 - SSHD authentication success. |41 |
5702 - Reverse lookup error (bad ISP or atta.. |37 |
To get a report of all brute force attacks (for example) that scanned my box:
# cat /var/log/secure | /var/ossec/bin/ossec-logtest -a |/var/ossec/bin/ossec-reported -f group authe

-------------------------------->Processed alerts: 522
Top entries for Source ip:
-------------------------------83.170.106.142 |2 |
89.200.169.170 |2 |
114.255.100.163 |1 |
117.135.138.183 |1 |
124.205.62.36 |1 |
173.45.108.230 |1 |
200.182.99.59 |1 |
162
202.63.160.50 |1 |
210.21.225.202 |1 |
211.151.64.220 |1 |
213.229.70.12 |1 |
218.30.19.48 |1 |
221.12.12.3 |1 |
59.3.239.114 |1 |
61.168.227.12 |1 |
61.233.42.47 |1 |
67.43.61.80 |1 |
72.52.75.228 |1 |
77.245.148.196 |1 |
79.125.35.214 |1 |
85.21.83.170 |1 |
92.240.75.6 |1 |
94.198.49.185 |1 |
-------------------------------root |24 |
-------------------------------Severity 10 |25 |
-------------------------------authentication_failures |25 |
sshd |25 |
syslog |25 |
Top entries for Location:
-------------------------------enigma->stdin |25 |
-------------------------------5720 - Multiple SSHD authentication failures. |24 |
5712 - SSHD brute force trying to get access.. |1 |
3.3.16 ossec-maild
The ossec-maild daemon sends OSSEC alerts via email. ossec-maild is started by ossec-control. Configuration for ossec-maild is handled in the ossec.conf. (see ossec.conf: Global options)
ossec-maild argument options
-c <config>
Run ossec-maild using <config> as the configuration file.
-D <dir>
Chroot to <dir>.
Default: /var/ossec
3.3. Man pages
163
-d
Execute ossec-maild in debug mode. This option can be used multiple times to increase the verbosity of the
debug messages.
-f
Run ossec-maild in the foreground.
-g <group>
Run ossec-maild as <group>.
-h
-t
Test configuration.
-u <user>
Run ossec-maild as <user>.
Default: ossecm
-V
3.3.17 ossec-makelists
The ossec-makelists utility to compile cdb databases. ossec-makelists will scan ossec.conf for database
files, check the mtime, and recompile all out of date databases.
See CDB List lookups from within Rules for more information.
ossec-makelists argument options
-c <config>
Run with configuration file of <config>.
Default /var/ossec/etc/ossec.conf
-d
Execute ossec-makelists in debug mode. This option can be used multiple times to increase the verbosity of the
debug messages.
-F
Force the rebuild of all configured databases.
-g <group>
Run as <group>.
-h
-t
-u <user>
Run as <user>.
-V
Diplay the version and license information.
164
ossec-makelists example usage

Example: Running ossec-makelists and an update is necessary
# /var/ossec/bin/ossec-makelists
* File lists/blocked.txt.cdb need to be updated
Example: Running ossec-makelists when no update is necessary

# /var/ossec/bin/ossec-makelists
* File lists/blocked.txt.cdb does not need to be compiled
3.3.18 ossec-monitord
The ossec-monitord daemon monitors agent connectivity and compress daily log files. ossec-monitord is
configured in ossec.conf. (see ossec.conf: Localfile options)
ossec-monitord argument options
-c <config>
Run ossec-monitord using <config> as the configuration file.
-D <dir>
Chroot to <dir>.
Default: /var/ossec
-d
Execute ossec-monitord in debug mode. This option can be used multiple times to increase the verbosity of the
debug messages.
-f
Run ossec-monitord in the foreground.
-g <group>
Run ossec-monitord as <group>.
-h
-t
Test configuration.
-u <user>
Run ossec-monitord as <user>.
Default: ossecm
-V
3.3. Man pages
165
3.3.19 ossec-regex
ossec-regex is a simple program that will validate a regex expression.a The pattern should be enclosed in single
quotes to help prevent any strange interactions with the shell.
The syntax for ossec-regex is simple: /var/ossec/bin/ossec-regex <pattern> It then reads
strings from stdin and outputs matches to stdout. +OSRegex_Execute and +OS_Regex are printed if a match
is successful.
Example 1: A siple digit match:
# /var/ossec/bin/ossec-regex ^\d\d\d
333
+OSRegex_Execute: 333
+OS_Regex
: 333
f44
222
+OSRegex_Execute: 222
+OS_Regex
: 222
3.3.20 ossec-remoted
ossec-remoted is the server side daemon that communicates with the agents. It can listen to port 1514/udp (for
OSSEC communications) and/or 514 (for syslog). It runs as ossecr and is chrooted to /var/ossec by default.
ossec-remoted is configured in the <remote> section of ossec.conf. (see ossec.conf: Remote Options)
ossec-remoted argument options
-c <config>
Run ossec-remoted using <config> as the configuration file.
-D <dir>
Chroot to <dir>.
Default: /var/ossec
-d
Execute ossec-remoted in debug mode. This can be used more than once to increase the verbosity of the debug
messages.
-f
-g <group>
Run ossec-remoted as <group>.
-h
-t
Test configuration.
-u <user>
Run ossec-remoted as <user>.
166
Default: ossecm
-V
3.3.21 ossec-reportd
ossec-reportd is a program to create reports from OSSEC alerts. ossec-reportd accepts alerts
on stdin, and outputs a report on stderr.
Note: Since ossec-reportd outputs to stderr some utilities like less will not work if you do not
redirect the output. End the ossec-reportd with 2>&1 to redirect stderr to stdout. more or less can be
easily used after the stderr redirect.
ossec-reportd argument options

-D <dir>
chroot to <dir>.
-d
Execute ossec-reportd in debug mode. This option can be used multiple times to increase the verbosity of the
debug messages.
-f <filter> <value>
Filter the results.
Note: Allowed filters: group, rule, level, location, user, srcip, and filename.
-h
-n <string>
Create a description for the report.
-r <filter> <value>
Show related entries.
-s
Show the alerts related to the summary.
-V
ossec-reportd example usage
Example 1: Show Successful Logins
# cat /var/ossec/logs/alerts/alerts.log | /var/ossec/bin/ossec-reportd -f group authentication_succes
3.3. Man pages
167
Example 2: Show Alerts Level 10 and Greater

# cat /var/ossec/logs/alerts/alerts.log | /var/ossec/bin/ossec-reportd -f level 10
Example 3: Show the srcip for all users
# cat /var/ossec/logs/alerts/alerts.log | /var/ossec/bin/ossec-reportd -f group authentication -r use
Example 4: Show Changed files as reported by Syscheck

# cat /var/ossec/logs/alerts/alerts.log | /var/ossec/bin/ossec-reportd -f group syscheck -r location
Example output
# cat /var/ossec/logs/alerts/alerts.log | /var/ossec/bin/ossec-reportd 2>&1 | more
2011/07/11 21:01:36 ossec-reportd: INFO: Started (pid: 1444).
2011/07/11 21:01:41 ossec-reportd: INFO: Report completed. Creating output...
------------------------------------------------>Processed alerts: 17
->First alert: 2011 Jul 11 00:00:46
->Last alert: 2011 Jul 11 00:16:52

-----------------------------------------------_nrpe
|6
SYSTEM
|2
|
|

-----------------------------------------------Severity 3
|13
Severity 2
|4
|
|

-----------------------------------------------syslog
|10
sudo
|6
dropbearrecon
|4
ossec
|4
sshd
|4
authentication_success
|2
windows
|2
clamd
|1
freshclam
|1
virus
|1
|
|
|
|
|
|
|
|
|
|
168
Top entries for Location:

-----------------------------------------------ix->/var/log/secure
|4
ix->ossec-logcollector
|3
(vistapc) 192.168.17.0->WinEvtLog
|2
buffalo1->/var/log/secure
|2
buffalo2->/var/log/secure
|2
(junction) 192.168.17.17->/var/log/secure
|1
(junction) 192.168.17.17->ossec-logcollector
|1
ix->/var/log/local6
|1
junction->/var/log/secure
|1
|
|
|
|
|
|
|
|
|

-----------------------------------------------5402 - Successful sudo to ROOT executed
|6
51006 - Client exited before authentication.
|4
591 - Log file rotated.
|4
18107 - Windows Logon Success.
|2
52507 - ClamAV database update
|1
|
|
|
|
|
3.3.22 ossec-syscheckd
The ossec-syscheckd daemon checks configured files for changes to the checksums, permissions or ownership.
ossec-syscheckd is started by ossec-control. Configuration for ossec-syscheckd is handled in the ossec.conf.
See Syscheck for more detailed configuration information.
ossec-syscheckd argument options
-c <config>
Run ossec-syscheckd using <config> as the configuration file.
-d
Execute ossec-syscheckd in debug mode. This can be used more than once to increase the verbosity of the debug
messages.
-f
Run ossec-syscheckd in the foreground.
-h
-t
Test configuration.
-V
3.3.23 rootcheck_control
The rootcheck_control tool allows you to manage the policy monitoring and system auditing database that is stored
on the server (manager) side. You can list anomalies detected by the rootcheck functionality, categorized into resolved
and outstanding issues. Moreover you can find out when ossec-rootcheck was run the last time.
3.3. Man pages
169
rootcheck_control argument options

-h
-l
-lc
List only currently connected agents.
-u <id>
Updates (clear) the database for the agent.
-u all
Updates (clear) the database for all agents.
-i <agent_id>
Prints database for the agent.
-r
Used with -i, prints all the resolved issues.
-q
Used with -i, prints all the outstanding issues.
-L
Used with -i, prints the last scan.
-s
Changes the output to CSV (comma delimited).
rootcheck_control example usage
Example 1: Getting a list of system auditing/policy monitoring events
To get a list of all auditing/policy monitoring events for a specific agent, you can run rootcheck_control -i.
To retrieve the agent id you can use any of the following commands:
rootcheck_control -l,
agent_control -l
syscheck_control -l
syscheck_update -l
manage_agents -l
# /var/ossec/bin/rootcheck_control -i 002
Policy and auditing events for agent ossecagent (002) - 192.168.1.86:
Resolved events:
2010 Jun 15 13:01:22 (first time detected: 2009 Dec 10 18:48:43)

System Audit: System Audit: CIS - Debian Linux 8.8 - GRUB Password not set. File: /boot/grub/menu.lst
Outstanding events:
170

System Audit: System Audit: CIS - Testing against the CIS Debian Linux Benchmark v1.0. File: /etc/deb

System Audit: System Audit: CIS - Debian Linux 1.4 - Robust partition scheme - /tmp is not on its own

System Audit: System Audit: CIS - Debian Linux 2.3 - SSH Configuration - Root login allowed. File: /e
As you can see the detected events are shown in two categories, resolved events and outstanding event. To only show
resolved events, run rootcheck_control -ri. To only show outstanding events, run rootcheck_control
-ri. To only show the results of the last scan and time of that scan, run rootcheck_control -Li.
To gain that kind of information for the OSSEC server, run rootcheck_control -i 000.
Example 2: Clearing the system auditing/policy database
To clear the system auditing/policy monitoring database for a certain agent run the following command:
# /var/ossec/bin/rootcheck_control -u 002
** Policy and auditing database updated.
To clear the database for all agents and the server run the following command:
# /var/ossec/bin/rootcheck_control -u all
** Policy and auditing database updated.
The next time rootcheck is run, the database will be populated again.
3.3.24 syscheck_control
syscheck_control provides an interface for managing and viewing the integrity checking database.
syscheck_control argument options
-h
-l
-lc
List only currently connected agents.
-u <agent_id>
Updates (clear) the database for the agent.
-u all
Updates (clear) the database for all agents.
-i <agent_id>
Prints database for the agent.
-r -i
List modified registry entries for the agent (Windows only).
3.3. Man pages
171
-f <file>
Used with -i. Prints information about a modified file.
-z
Used with -f, zeroes the auto-ignore counter.
-d
Used with -f, ignores that file.
-s
Changes the output to CSV (comma delimited).
syscheck_control example usage
Example 1: Getting a list of modified files for an agent
To retrieve information about files that were monitored by OSSEC and modified after OSSEC was deployed, run
syscheck_control -i.
# /var/ossec/bin/syscheck_control -i 002
Integrity changes for agent ossec-agent (002) - 192.168.1.86:
Changes for
2009 Dec 21
2009 Dec 21
2009 Dec 21
2009 Dec 21
2009 Dec 21:

13:52:40,0 13:52:42,0 13:52:42,0 13:52:58,0 -
/etc/authorization
/etc/cups/printers.conf
/etc/cups/printers.conf.O
/etc/postfix/main.cf.default
Changes for 2010 Jan 04:

2010 Jan 04 10:13:58,0 - /etc/authorization
2010 Jan 06 09:45:43,0 - /etc/postfix/main.cf.default
2010 Jan 18 09:18:51,0 - /etc/cups/printers.conf
2010 Jan 18 09:18:51,0 - /etc/cups/printers.conf.O
Changes for 2010 Feb 23:
2010 Feb 23 09:17:22,2 - /etc/cups/printers.conf
2010 Feb 23 09:17:22,2 - /etc/cups/printers.conf.O
Changes for 2010 Mar 24:
2010 Mar 24 08:42:52,3 - /etc/cups/printers.conf
2010 Mar 24 08:42:52,3 - /etc/cups/printers.conf.O
As you can see this command provides an overview about file modifications.
Example 2: Getting more detailed information about a modified file
If you need to get more detailed information about a file that was modified you can use syscheck_control to view
the time stamp when the file was added to the syscheck database
the integrity checking values when the file was added to the syscheck database
the time stamps when OSSEC detected a modification
172
the integrity checking values for every time OSSEC detected a modification.
The integrity checking values include
how often the file has changed
file size
file permissions
owner and group id of the file
MD5 and SHA1 hashes of the file.
To retrieve this information, run syscheck_control -i:
# /var/ossec/bin/syscheck_control -i 002 -f /etc/authorization
Detailed information for entries matching: /etc/authorization
2009 Dec 21 13:52:40,0 - /etc/authorization
File added to the database.
Integrity checking values:
Size: 27771
Perm: rw-r--r-Uid: 0
Gid: 0
Md5: dd62912576ae05d611d7469be809cf1d
Sha1: 530df0283df52f0152b9e7ce1a518119b06ceebc
2010 Jan 04 10:13:58,0 - /etc/authorization
File changed. - 1st time modified.
Integrity checking values:
Size: >28050
Perm: rw-r--r-Uid: 0
Gid: 0
Md5: >50da55def41bcede7d42ac5ee8fe12c9
Sha1: >97f4b2b48a97321a3e245221e0ea4353cf4fa8ef
Example 3: Clearing the syscheck database
To clear the syscheck database for a certain agent run the following command:
# /var/ossec/bin/syscheck_control -u 002
** Integrity check database updated.
syscheck_control -i 002 will now show that no modified files for that agent are in the database:
# /var/ossec/bin/syscheck_control -i 002
** No entries found.
To clear the database for all agents and the server run the following command:
3.3. Man pages
173
# /var/ossec/bin/syscheck_control -u all
** Integrity check database updated.
The next time syscheck is run, the database will be populated again.
3.3.25 syscheck_update
syscheck_update: Updates the integrity check database. This means that all information about files that were added
to the integrity check database will be dismissed and leave an empty database which will be populated again the next
time the syscheck daemon runs on agents or the server.
It does the same thing as syscheck_control -u(cf.
:ref:syscheck_control).
syscheck_update argument options

-h
-l
-a
Updates the database for all agents.
-u <agent_id>
Updates the database for the agent.
-u local
Updates the local database.
3.3.26 util.sh
The util.sh shell script can add a file to be monitored by ossec-logcollector.
full_command to check for changes to a website, or for changes to the name server of a domain.
It can also add a
A blogpost from Daniel Cid (for 3WoO) introduced this utility.

util.sh argument options
addfile <filename> [<format>]
Add a file to be monitored by ossec-logtest. A localfile will be added to the ossec.conf.
addsite <domain>
Monitor a website for changes. A full_command will be added to the ossec.conf using lynx to dump the
initial page. A rule can be written to monitor this output for changes.
Note: Requires lynx.
Warning: This may not be useful on pages with dynamic content.
174
adddns <domain>
Monitor the name server of a domain for changes. A full_command will be added to the ossec.conf using
host
Note: Requites the host command.
util.sh example usage

Example: Running util.sh
Running the following command:

# /var/ossec/bin/util.sh adddns ossec.net
will add the folling to that systems ossec.conf:

<ossec_config>
<localfile>
<command>host -W 5 -t NS ossec.net; host -W 5 -t A ossec.net | sort</command>
</localfile>
</ossec_config>
3.3.27 verify-agent-conf
verify-agent-conf verifies the OSSEC agent.conf configuration. It exits silently if the configuration is correct.
verify-agent-conf example usage
Example 1: Running verify-agent-conf on a working agent.conf
# /var/ossec/bin/verify-agent-conf
#
Example 2: Running verify-agent-conf on a non-working agent.conf
# /var/ossec/bin/verify-agent-conf
2011/07/12 21:22:07 ossec-config(1226): ERROR: Error reading XML file /var/ossec/etc/shared/agent.co
3.4 Whats new

3.4.1 2.8.1
Released Sept 9, 2014:
Note: This is a bug fix release.
SECURITY fix for CVE-2014-5284 found by Jeff Petersen of Roka Security LLC.
3.4. Whats new
175
Bug fixes
3.4.2 2.8
Bug fixes
manage_agents: Added manage_agents -r <id> to remove an agent (awiddersheim)
Windows: Added eventchannel support for Windows agent on Vista or later (gaelmuller)
syscheckd: Extended filesize from an integer to a long integer
Active Response: Fix active-response on MAC OS Firewall (jknockaert)
Log monitoring/analysis: Add option to allow the outputing of all alerts to a zeromq PUB socket in JSON
format, using cJSON library (jrossi, justintime32)
Log monitoring/analysis: Add TimeGenerated to the output of Windows Event logs (awiddersheim)
Rules/decoders: Added some additional sshd rules in sshd_rules.xml (joshgarnett)
Rules/decoders: Removed bro-ids_rules.xml (ddpbsd)
Removed event ID 676, 672 in msauth_rules.xml (mstarks01)
contrib: zeromq_pubsub.py - No description (jrossi)
contrib: ossec-eps.sh, a script to calculate events-per-second (mstarks01)
3.4.3 2.7.1
Bug fixes
Extended filesize from an integer to a long integer in syscheck
Heartbeat interval is now configurable:
notify_time
time-reconnect
custom_alert_output added
ip-customblock.sh active-response script added
ossec2snorby scripts added to contrib
3.4.4 2.7
agent profiles
ossec.conf
agent.conf
Allow the agents to run remote commands in agent.conf again internal_options.conf
New utility: util.sh
New hybrid mode: server + agent functionality on the same system (NOT REALLY DOCUMENTED, ARE
ANY OF THE INSTALLATION TYPES WELL DOCUMENTED?)
contrib/ossec2rss.php: ossec alerts in an rss format
176
GeoIP data in alerts

OSSEC server can be specified by hostname in the agents ossec.conf server-hostname
ossec-authd can now add IP addresses to the client.keys file instead of using any with the -i flag from Jason
Stelzer
support for prelink to reduce false positives refilter_cmd
Added knowbs to turn on or off rootcheck features check_*
Added support for json and splunk output (along with syslog and cef) format
Changed -f to -v in ossec-logtest
Added -f to manage_agents to create agent keys in bulk
3.5 Rootcheck / Syscheck Reference

3.5.1 Information about the Beastkit Rootkit
This rootkit was found on a RedHat 7.2 System in 01/2002. The rootkit setup script includes the line #Beastkit 7.0 X-Org edition. Due to this fact, we call it as Beastkit 7.0.
More Information
For more info, look at this analyse (author unknown): analysis-beastkit
Files
usr/include/rpc/ ../kit
usr/include/rpc/ ../kit2
usr/doc/.sl
usr/doc/.sp
usr/doc/.statnet
usr/doc/.logdsys
usr/doc/.dpct
usr/doc/.gifnocfi
usr/doc/.dnif
usr/doc/.nigol
*biba
*sniff/lins
Note: All files with an * need to be search in all system
If you have any more Information about this rootkits sent to rootkits at ossec.net
3.5. Rootcheck / Syscheck Reference
177
3.5.2 Information about the Knark Rootkit

Knark is a kernel-based rootkit for Linux 2.2/2.4. It hide ports, files and processes from the administrator. This rootkit
is very powerfull and had been used by crackers in a lot of compromised machines.
More Information
A complete analysis, done by Toby Miller, can be found here: analysis-knack
Knark README can be found readme-knack
Download: http://www.ossec.net/rootkits/files/knark-2.4.3.tgz MD5: ca1ebe26ab1138ebe431751f526df817
Files
/dev/.pizda
/dev/.pula
/proc/knark
*/taskhack
*/rootme
*/nethide
*/hidef
*/ered
3.5.3 Information about Old Rootkits

These Old Rootkits are some old (obvious) rootkits, found in some systems years ago. They are not very well
documented and because of that we call them only as Old.
Files
usr/include/rpc/ ../kit
usr/include/rpc/ ../kit2
usr/doc/.sl
usr/doc/.sp
usr/doc/.statnet
usr/doc/.logdsys
usr/doc/.dpct
usr/doc/.gifnocfi
usr/doc/.dnif
178
usr/doc/.nigol
*biba
*sniff/lins
3.5.4 Information about Suspicious files

The files listed here were found in some infected/owned machines. They are not part of any rootkit, but some crackers use them. They can be a log of some sniffer, a sniffer or a lot of other things.
Take a careful look if you find any of these files in your system.
More Information
N/A
Origin of Rule
N/A
File
etc/rc.d/init.d/rc.modules
lib/ldd.so
usr/man/muie
usr/X11R6/include/pain
usr/bin/sourcemask
usr/bin/ras2xm
usr/bin/ddc
usr/bin/jdc
usr/sbin/in.telnet
sbin/vobiscum
usr/sbin/jcd
usr/sbin/atd2
usr/bin/ishit
usr/bin/.etc
usr/bin/xstat
var/run/.tmp
usr/man/man1/lib/.lib
179
usr/man/man2/.man8
var/run/.pid
lib/.so
lib/.fx
lib/lblip.tk
usr/lib/.fx
var/local/.lpd
dev/rd/cdb
dev/.rd/
usr/lib/pt07
usr/bin/atm
tmp/.cheese
dev/.arctic
dev/.xman
dev/srd0
dev/ptyzx
dev/ptyzg
dev/xdf1
dev/ttyop
dev/ttyof
dev/hd5
dev/hd6
dev/hd7
dev/hdx1
dev/hdx2
dev/xdf2
dev/ptyp
dev/ptyr
*/.src
*last.cgi
*nobody.cgi
*void.cgi
*all4one.cgi
*xntps
*/.xman
*/.arctic
180
*psybnc
*mech.session
*sshdu
3.5.5 Information about the T.R.K rootkit

This rootkit as a mix of some others.
More Information
No more information is available.
Orgin of Rule
This rootkit was taken from chkrootkit:
### T.R.K
expertmode_output "${find} ${ROOTDIR}usr/bin -name soucemask -o -name ct"
File
usr/bin/soucemask
usr/bin/sourcemask
3.5.6 Information about the Tuxkit Rootkit

This is a rootkit written by a Dutch group called Tuxtendo. It was found in some infected Redhat 6.0/7.0 systems.
More Information
A complete analyse of Tuxkit, done by Spoonfork (spoonfork@hackinthebox.org). For more info, look at this analyse
(author unknown): analysis-tuxkit
Files
dev/tux usr/bin/xsf usr/bin/xchk */.log */.file */.addr
Entries to search on file /etc/rc.d/rc.sysinit:
/usr/bin/xsf /usr/bin/xchk
181

3.6 Glossary
HIDS First of all, Intrusion Detection is the process or techniques used to detect attacks on a specific network, system
or application. Most intrusion detection tools not only detect attacks, but also software misuse, policy violations
and other forms of inappropriate activities.
A Host-based IDS performs intrusion detection from within the systems you want to protect. Some of these
tools perform log analysis, others spyware detection, while others perform virus detection.
LIDS LIDS (Log-based intrusion detection systems) is just a fancy term for tools that perform security log analysis
(specified above). Its goal is to detect misuse (or attacks) using logs as the primary source of information. It is
not a replacement for NIDS (Network-based IDS) or any other security solution, but an addition to them.
182
CHAPTER 4
Indices and tables
genindex
modindex
search
183
184
Chapter 4. Indices and tables
Index
Symbols
-A <agent_name>
agent-auth command line option, 146
-D
-D <dir>
ossec-agentd command line option, 151
ossec-agentlessd command line option, 152
ossec-analysisd command line option, 152
ossec-authd command line option, 153
ossec-csyslogd command line option, 156
ossec-dbd command line option, 157
ossec-logtest command line option, 159
ossec-maild command line option, 163
ossec-monitord command line option, 165
ossec-remoted command line option, 166
ossec-reportd command line option, 167
-F
ossec-makelists command line option, 164
-L
rootcheck_control command line option, 170
-R <agent_id>
agent_control command line option, 148
-U <rule-id:alert-level:decoder-name>
-V
manage_agents command line option, 150
ossec-execd command line option, 158
ossec-logcollector command line option, 158

ossec-syscheckd command line option, 169
-a
clear_stats command line option, 149
syscheck_update command line option, 174
-c
-c <config>
-d
185

syscheck_control command line option, 172
-e <agent_id>
-f
-f <file>
-f <file>
-f <filter> <value>
-g
-g <group>
-h
186

-i
-i <agent_id>
-i <key>
-k </path/to/private_key>
-k <path>
-l
-lc
-m <manager_ip>
-n
-n <string>
-p <port>
-q
-r
-r -i
-r <agent_id>
-r <filter> <value>
-s
-t
Index

-u
-u <agent_id>
-u <id>
-u <user>
-u all
-u local
-v
-v </path/to/CA_certificate>
-v <path>
-w
-x </path/to/certificate>
-x <path>
-z
A
active-response, 114
Index
adddns <domain>
util.sh command line option, 174
addfile <filename> [<format>]
addsite <domain>
agent-auth command line option
-A <agent_name>, 146
-D, 146
-V, 146
-d, 146
-g <group>, 146
-h, 146
-k </path/to/private_key>, 146
-k <path>, 146
-m <manager_ip>, 146
-p <port>, 146
-v </path/to/CA_certificate>, 146
-v <path>, 146
-x </path/to/certificate>, 146
-x <path>, 146
agent.debug, 143
agent_config, 142
agent_config_options, 142
agent_control command line option
-R <agent_id>, 148
-a, 148
-h, 148
-i <agent_id>, 148
-l, 148
-lc, 148
-r, 148
-u <agent_id>, 148
agent_id, 115
agentless, 23, 118
alerts, 119
alias, 38, 128
allowed-ips, 130
analysisd.debug, 143
analysisd.default_timeframe, 142
analysisd.fts_list_size, 142
analysisd.fts_min_size_for_str, 142
analysisd.log_fw, 142
analysisd.stats_maxdiff, 142
analysisd.stats_mindiff, 142
analysisd.stats_percent_diff, 142
arguments, 24, 118
B
base_directory, 53, 133
C
categories, 70, 74, 131
category, 107
187
check_dev, 54, 133

check_diff, 39, 112, 129
check_files, 54, 133
check_if, 54, 134
check_pids, 55, 134
check_policy, 55, 134
check_ports, 55, 134
check_sys, 55, 134
check_trojans, 55, 134
check_unixaudit, 55, 134
check_winapps, 55, 134
check_winaudit, 55, 134
check_winmalware, 55, 135
clear_stats command line option
-a, 149
-d, 149
-h, 149
-w, 149
command, 38, 114, 115, 128
config-profile, 120
connection, 130
custom_alert_output, 124
D
database, 71, 121
database_output, 71, 121
dbd.reconnect_attempts, 143
decoded_as, 107
decoder, 112, 136
decoder.accumulate, 112
decoder.fts, 113
decoder.ftscomment, 113
decoder.order, 113
decoder.parent, 112
decoder.prematch, 113
decoder.program_name, 113
decoder.regex, 113
decoder_dir, 136
deny-ips, 130
description, 109
disabled, 54, 114, 133
do_not_delay, 122
do_not_group, 122
dstip, 107
E
email_alert_level, 119
email_alerts, 122
email_from, 124
email_idsname, 124
email_maxperhour, 124
email_notification, 124
email_to, 71, 74, 122, 124, 132
environment variable
188
DATABASE, 99
DEBUG, 98
DEBUGAD, 98
LUA_PLAT, 99
MAXAGENTS, 98
OSSEC_GROUP, 99
OSSEC_USER, 99
OSSEC_USER_MAIL, 99
OSSEC_USER_REM, 99
PREFIX, 98
TARGET, 98
USE_GEOIP, 99
USE_PRELUDE, 99
USE_ZEROMQ, 99
V, 98
event_location, 122
executable, 114
expect, 114
extra_data, 107
F
format, 68, 122, 141
frequency, 23, 39, 54, 118, 128, 133
G
geoip_db_path, 126
global, 124
group, 67, 70, 74, 112, 122, 131, 140
H
HIDS, 182
host, 23, 118
host_infomation, 125
hostname, 71, 108, 121
I
id, 108
if_group, 108
if_level, 108
if_matched_group, 109
if_matched_sid, 108
if_sid, 108
include, 135
info, 111
ipv6, 130
L
level, 67, 70, 74, 115, 122, 131, 140
LIDS, 182
list, 109, 137
local_ip, 130
localfile, 37, 127
location, 37, 68, 71, 74, 115, 127, 131, 141
Index
log_alert_level, 119
log_format, 37, 127
logall, 125
logcollector.loop_timeout, 143
logcollector.open_attempts, 143
logcollector.remote_commands=0, 143
M
maild.full_subject, 143
maild.geoip, 144
maild.groupping, 143
maild.strict_checking, 143
manage_agents command line option
-V, 150
-a, 150
-c, 150
-e <agent_id>, 150
-f <file>, 150
-h, 150
-i <key>, 150
-l, 150
-n, 150
-r <agent_id>, 150
match, 107
memory_size, 125
monitord.compress, 144
monitord.day_wait, 144
monitord.monitor_agents, 144
monitord.sign, 144
N
name, 114, 142
notify_time, 120
O
only-future-events, 39, 129
options, 111
os, 142
ossec-agentd command line option
-D <dir>, 151
-V, 152
-c <config>, 151
-d, 151
-f, 151
-g <group>, 151
-h, 151
-t, 151
-u <user>, 151
ossec-agentlessd command line option
-D <dir>, 152
-V, 152
-c <config>, 152
-d, 152
-f, 152
Index
-g <group>, 152
-h, 152
-t, 152
-u, 152
ossec-analysisd command line option
-D <dir>, 152
-V, 153
-c <config>, 152
-d, 152
-f, 152
-g <group>, 153
-h, 153
-t, 153
-u, 153
ossec-authd command line option
-D <dir>, 153
-V, 153
-d, 153
-g <group>, 153
-h, 153
-i, 153
-k <path>, 153
-p <port>, 153
-t, 153
-v <path>, 153
-x <path>, 154
ossec-csyslogd command line option
-D <dir>, 156
-V, 157
-c <config>, 156
-d, 156
-f, 156
-g <group>, 156
-h, 156
-t, 156
-u <user>, 157
ossec-dbd command line option
-D <dir>, 157
-V, 157
-c <config>, 157
-d, 157
-f, 157
-g <group>, 157
-h, 157
-t, 157
-u <user>, 157
ossec-execd command line option
-V, 158
-d, 158
-f, 158
-g, 158
-h, 158
-t, 158
ossec-logcollector command line option
189
-V, 158
-c <config>, 158
-d, 158
-f, 158
-h, 158
-t, 158
ossec-logtest command line option
-D <dir>, 159
-U <rule-id:alert-level:decoder-name>, 159
-V, 159
-a, 159
-c <config>, 159
-d, 159
-h, 159
-t, 159
-v, 159
ossec-maild command line option
-D <dir>, 163
-V, 164
-c <config>, 163
-d, 163
-f, 164
-g <group>, 164
-h, 164
-t, 164
-u <user>, 164
ossec-makelists command line option
-F, 164
-V, 164
-c <config>, 164
-d, 164
-g <group>, 164
-h, 164
-t, 164
-u <user>, 164
ossec-monitord command line option
-D <dir>, 165
-V, 165
-c <config>, 165
-d, 165
-f, 165
-g <group>, 165
-h, 165
-t, 165
-u <user>, 165
ossec-remoted command line option
-D <dir>, 166
-V, 167
-c <config>, 166
-d, 166
-f, 166
-g <group>, 166
-h, 166
-t, 166
190
-u <user>, 166
ossec-reportd command line option
-D <dir>, 167
-V, 167
-d, 167
-f <filter> <value>, 167
-h, 167
-n <string>, 167
-r <filter> <value>, 167
-s, 167
ossec-syscheckd command line option
-V, 169
-c <config>, 169
-d, 169
-f, 169
-h, 169
-t, 169
P
password, 71, 121
picviz_output, 125
picviz_socket, 126
port, 67, 120, 130, 140
prelude_output, 125
profile, 142
program_name, 108
protocol, 130
Q
query, 39, 129
R
regex, 107
remote, 130
remoted.comp_average_printout, 144
remoted.debug, 144
remoted.recv_counter_flush, 144
remoted.verify_msg_id, 144
repeated_offenders, 115
reports, 70, 74, 131
rootcheck_control command line option
-L, 170
-h, 170
-i <agent_id>, 170
-l, 170
-lc, 170
-q, 170
-r, 170
-s, 170
-u <id>, 170
-u all, 170
rootkit_files, 54, 133
rootkit_trojans, 54, 133
rule, 70, 74, 106, 131, 135
Index
rule_dir, 135
rule_id, 67, 122, 141
rules_group, 115
rules_id, 115
S
same_dst_port, 109
same_id, 109
same_location, 109
same_source_ip, 109
same_source_port, 109
same_user, 109
scanall, 54, 133
server, 67, 140
server-hostname, 120
server-ip, 120
showlogs, 71, 74, 132
smtp_server, 124
srcip, 71, 74, 107, 131
state, 23, 118
stats, 125
syscheck.sleep, 144
syscheck.sleep_after, 144
syscheck_control command line option
-d, 172
-f <file>, 171
-h, 171
-i <agent_id>, 171
-l, 171
-lc, 171
-r -i, 171
-s, 172
-u <agent_id>, 171
-u all, 171
-z, 172
syscheck_update command line option
-a, 174
-h, 174
-l, 174
-u <agent_id>, 174
-u local, 174
syslog_output, 67, 140
system_audit, 54, 133
use_geoip, 119
user, 71, 74, 108, 131
username, 71, 121
util.sh command line option
adddns <domain>, 174
addfile <filename> [<format>], 174
addsite <domain>, 174
W
weekday, 108
white_list, 125
windows.debug, 145
windows_apps, 54, 133
windows_audit, 54, 133
windows_malware, 54, 133
Z
zeromq_output, 126
zeromq_uri, 126
T
time, 108
time-reconnect, 120
timeout, 115
timeout_allowed, 114
title, 71, 74, 131
type, 72, 121
U
url, 108
Index
191

Ossec Manual

Uploaded by

Copyright:

Available Formats

Ossec Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ossec Manual

Uploaded by

Copyright:

Available Formats

OSSEC Documentation

October 04, 2014

Manual & FAQ

Indices and tables

OSSEC Documentation, Release 2.8.1

OSSEC Documentation, Release 2.8.1

Manual & FAQ

OSSEC Documentation, Release 2.8.1

1.1.2 OSSEC Architecture

Chapter 1. Manual & FAQ

OSSEC Documentation, Release 2.8.1

Manager (or Server)

OSSEC Documentation, Release 2.8.1

the OSSEC commercial support page.

1.1.3 Supported Systems

Chapter 1. Manual & FAQ

OSSEC Documentation, Release 2.8.1

FreeBSD (all current versions)

OSSEC Documentation, Release 2.8.1

This can also be avoided by using bash to run install.sh:

Chapter 1. Manual & FAQ

OSSEC Documentation, Release 2.8.1

# wget -U ossec http://www.ossec.net/files/ossec-hids-2.8.1.tar.gz

Windows Agent Installation

Compiling OSSEC for install on a second server

OSSEC Documentation, Release 2.8.1

Modify ossec-hids-*/etc/preloaded-vars.conf to set BINARY_INSTALL to yes.

Finally create an OSSEC package.

Installation of the binary OSSEC package

After following the installation prompts the install will be complete.

Unattended Source Installation

Chapter 1. Manual & FAQ

OSSEC Documentation, Release 2.8.1

preloaded-vars.conf, Daniel B. Cid (dcid @ ossec.net).

Use this file to customize your installations.

# If USER_NO_STOP is set to anything, the confirmation

# USER_INSTALL_TYPE defines the installation type to

# USER_DIR defines the location to install ossec

# If USER_DELETE_DIR is set to "y", the directory

# If USER_ENABLE_ACTIVE_RESPONSE is set to "n",

# If USER_ENABLE_SYSCHECK is set to "y",

OSSEC Documentation, Release 2.8.1

# syscheck will be enabled. Set to "n" to

# If USER_ENABLE_ROOTCHECK is set to "y",

# If USER_UPDATE is set to anything, the update

### Agent Installation variables. ###

Specifies the IP address or hostname of the

# USER_AGENT_CONFIG_PROFILE specifies the agents config profile

### Server/Local Installation variables. ###

# USER_ENABLE_SYSLOG enables or disables remote syslog.

Chapter 1. Manual & FAQ

OSSEC Documentation, Release 2.8.1

# USER_ENABLE_FIREWALL_RESPONSE enables or disables

# Enable PF firewall (OpenBSD and FreeBSD only)

# PF table to use (OpenBSD and FreeBSD only).

# USER_WHITE_LIST is a list of IPs or networks

#### exit ? ###

Compiling the OSSEC Windows Agent on Windows

The Nullsoft Scriptable Install System (NSIS)