Monitor your network's security 24/7 with a free and open-source solution that collects, analyzes and reports logs of the events on your network.
Networks and information systems are increasingly exposed to attacks that are becoming more sophisticated and sustained over time, such as the so-called APT (Advanced Persistent Threats).
Information security experts agree on the fact that no organization, even the best equipped to protect itself from these attacks, can be considered immune, and that the issue is not whether its systems will be compromised, but rather when and how it will happen.
It is essential to be able to detect attacks in a timely manner and implement the relative countermeasures, following appropriate procedures to respond to incidents, thus minimizing the effects and the damages they can cause. In order to detect intrusions and attacks, system administrators and information security analysts make use of tools, such as IDS/IPS (Intrusion Detection/Prevention System) and analysis of logs (event records) of servers and network devices, looking for any significant events from a security point of view.
A network of an organization of average size produces, as a whole, such a quantity of logs that it is very difficult (and still very expensive) to check them all, one by one, to obtain meaningful information.
A further difficulty is that there is no single standard used to record the logs and often, depending on the type and size, they are not immediate or easy to understand.
It is even more difficult to relate other logs produced by many different systems to each other manually, to highlight anomalies in the network that would not be detectable by analyzing the logs of each machine separately.
SIEM (Security Information and Event Management) software, therefore, is not limited to being a centralized solution for log management, but also (and especially) it has the ability to standardize logs in a single format, analyze the recorded events, highlight the most important information and relate the logs to each other (correlation), allowing analysts to detect anomalies and attacks more easily.
For example, for log management software, three failed attempts to log in to the same user account from three different clients will be only three lines in your log file and not obviously related to each other. For an analyst, instead, it may be a sequence of events worthy of further analysis, and its correlation (looking for patterns in the log files) can generate alerts when these types of events occur.
OSSIM is a SIEM software platform, free and open-source, developed by AlienVault and based on a Debian 64-bit Linux distribution. OSSIM has four major components:
You can install these components on a single physical machine (the default installation), on a single virtual machine, on different virtual machines and/or physical machines, depending on the size and configuration of the network to monitor.
For a relatively small network, installation on a single machine, which is the simplest configuration, may be the right solution. For larger networks, it is advisable to install the Sensor and the Database separately. Figure 1 shows the OSSIM architecture.
The Sensor has two main components:
The rsyslog service, which listens on TCP/UDP port 514, receives the logs from network devices and stores them locally, according to the configuration.
The Ossim-agent, using a series of modules called plugins, one for each type of log, performs log analysis and normalization, and sends that to the Server component.
Plugins are of two types: detectors, which detect anomalies and possible attacks (such as Snort, P0f, Arpwatch), and monitors to monitor the network status (like Ntop and Nagios).
The Server performs the essential SIEM functions: aggregation, risk assessment and correlation of events that are received from the sensor through TCP port 40001. The server also sends the information concerning the events to the Database for storage.
The Framework connects and manages the OSSIM components and security tools included, and it provides the system administration Web interface. It is the component that needs the least hardware resources and is usually installed together with the Server component.
The Database is a MySQL server instance that stores events and system configuration data.
Following is a brief description of OSSIM's main features and functionalities concerning the collection, analysis and correlation of logs and the primary tools included in the system for network security monitoring.
Collection and Normalization of Logs:
You can collect logs from the devices on your network in two ways:
Install a software agent (like Snare or SysLogAgent) in the source machine and configure it to read certain types of logs and send them to the Sensor component.
Configure the source machine to send the logs upon request of the appropriate Sensor plugins (for example, via WMI for Windows machines). Once the Sensor records the logs, the OSSIM Agent performs the analysis and converts them to a single format (normalization). Each log represents an event that will be sent to the server for analysis (Figure 2).
Prioritization of Events and Risk Assessment:
The prioritization process involves assigning priority values to the recorded events, which is done by the Server component. It depends on the structure of the network and it needs, as prerequisites, the definition of security policies and the inventory of information assets on the network, which can be managed in the Web administration panel. It sets the priority of an event based on the machine that generated it and the type of event to which it belongs.
The risk assessment of events is calculated in real time and is based on three main factors:
The value or level of importance of the machine that generated the event.
The type of threat posed by the event.
The probability that this event occurs.
The formula used for calculating risk is the following (Figure 3): Risk = value * (reliability * Priority / 25).
Analysis and Correlation of Events:
The correlation of events essentially relates events to each other to achieve a comprehensive view of network security and to detect possible attacks or anomalies.
The correlation process is performed via two methods:
Correlation using sequence of events, using directives, consisting of rules that relate events to patterns of known attacks. This method is similar to using Snort for intrusion detection (signature-based detection).
Correlation using heuristic algorithms can be detected by these abnormal situations that do not detect the preceding rules and may or may not be attacks (abnormality detection).
Directives are located in the /etc/ossim/server/directives.xml file. Directives are specified in XML using tags like Id, Name, Priority, Type, Reliability, Occurrence, Timeout, Source, Destination, Source port, destination port, protocol, PluginSid and Sensor.
Reliability is a measure of the probability that the considered event truly represents the attack referred to by the directive and is generally based on the number of occurrences of the event.
For example, consider the following directive to detect brute-force SSH attacks:
<directive id="20" name="Possible SSH brute force login ↪attempt against DST_IP" priority="5"> <rule type="detector" name="SSH Authentication failure" ↪reliability="3" occurrence="1" from="ANY" to="ANY" ↪port_from="ANY" port_to="ANY" time_out="10" ↪plugin_id="4003" plugin_sid="1,2,3,4,5,6"> <rules> <rule type="detector" name="SSH Authentication failure (3 times)" ↪reliability="+1" occurrence="3" from="1:SRC_IP" to="ANY" ↪port_from="ANY" time_out="15" port_to="ANY" ↪plugin_id="4003" plugin_sid="1,2,3,4,5,6" sticky="true"> <rules> <rule type="detector" name="SSH Authentication failure (5 times)" ↪reliability="+2" occurrence="5" from="1:SRC_IP" to="ANY" ↪port_from="ANY" time_out="20" port_to="ANY" ↪plugin_id="4003" plugin_sid="1,2,3,4,5,6" sticky="true"> <rules> <rule type="detector" name="SSH Authentication failure (10 times)" ↪reliability="+2" occurrence="10" from="1:SRC_IP" to="ANY" ↪port_from="ANY" time_out="30" port_to="ANY" ↪plugin_id="4003" plugin_sid="1,2,3,4,5,6" sticky="true"> </rule> </rules> </rule> </rules> </rule> </rules> </rule> </directive>
The directive assigns a value of reliability equal to 3 (30% probability) when the number of occurrences of the event detected by the sensor (SSH authentication error) is equal to 1, then increments it by 1 at the third occurrence of the event, by 2 at the fifth occurrence and by an additional 2 at the tenth, thereby achieving a reliability of 8 (80% of probability) when the incorrect authentication attempts are 10.
OSSIM also has the ability to correlate different types of logs, generated by various plugins (cross-correlation). The cross-correlation allows you to change the event reliability and risk assessment. For example, suppose that Nessus or OpenVAS has identified a vulnerability in a server. If Snort detects an event that indicates a possible attack on that server, the correlation engine increases the level of risk associated with the event.
Generation of Alarms and Response Actions:
The directives can create alarms, which either are generated by a single event or by a specific sequence of events under certain conditions. The alarms can be displayed in the Web administration panel, under the menu item Incidents→Alarms.
Furthermore, alarms can activate response actions, such as sending an alert by e-mail to the system administrator and/or the execution of appropriate scripts.
Vulnerability Analysis, Intrusion Detection and Network Monitoring:
OSSIM includes many valuable tools, which also are open-source, that are among the most known and used for intrusion detection, vulnerability analysis and network management and monitoring:
Arpwatch: used for monitoring ARP traffic on the LAN and for related attack detection.
P0f: used for operating system identification and analysis.
Pads: used for detecting anomalies of the services running on a host.
Nessus and OpenVAS: the most widely used and popular vulnerability scanners.
Nmap: the most famous and powerful network scanner.
Snort: the most popular intrusion detection system (IDS).
Tcptrack: used for TCP connection monitoring.
Nagios and Ntop: used to monitor the status of the network, the hosts and the availability of services.
Osiris and OSSEC: intrusion detection software for individual hosts (HIDS—Host-Based IDS).
Snare: a software agent for collecting logs on Windows systems.
You can download the ISO file for the installation from the AlienVault Web site download page at www.alienvault.com/free-downloads-services.
The most recent version (February 2014) is 4.3.4, only for 64-bit architectures. You can choose the Automatic or Custom installation. The automatic installation is fairly simple, in graphical mode by default, and it installs all components of OSSIM on the same machine. The custom installation allows you to select the mode (graphical or textual) and which components to install. The custom installation is a little more complex because it has more configuration options. For instructions on how to install OSSIM, refer to the Installation Guide: https://alienvault.bloomfire.com/posts/525575-installation-guide/public.
The minimum hardware requirements are:
64-bit processor or virtualization software with support for 64-bit operating systems (at least a quad-core processor is recommended).
4GB of RAM.
500GB of free disk space.
Network adapter with support for the Intel e1000 Ethernet driver.
Of course, the hardware requirements will be directly proportional to the size of the network (number of hosts and network devices connected) and consequently to the amount of logs produced and recorded.
You can perform the system configuration and administration through the console, a Linux shell or through a more convenient and intuitive Web interface.
Configuration through the Console:
To configure the system through the console, you need to log in as root with the password you set during the installation process. The directory that contains the system's configuration files is /etc/ossim.
The main configuration file is /etc/ossim/ossim_setup.conf, which contains the system's main settings, such as IP addresses and ports of the hosts on which components are installed, the active plugins and the password used by the root user of MySQL, randomly generated by the system during the installation procedure.
For example, if you want to change your password or other data, you need to edit the file with the command:
# vi /etc/ossim/ossim_setup.conf
Then run the following command:
To change the main configuration file more easily, there is also a command called ossim_setup, which presents a graphical interface, shown in Figure 5.
Configuring the Sensor and Plugins:
With the ossim_setup command, you can set the parameters of the previously shown configuration file, such as enabling or disabling plugins. To get a list of plugins that can be turned on or off, select the option Change sensor settings→Select detector plugins (Figure 6).
The OSSIM agent runs as a background service (dæmon), and you can start it with this command:
# /etc/init.d/ossim-agent start
Its configuration file is /etc/ossim/agent/config.cfg. The plugins' configuration files also are text files with the .cfg extension and are in the /etc/ossim/agent/plugins/ directory. When you activate new plugins, you must restart the server:
# /etc/init.d/ossim-server restart
More than 2,000 plugins are available (www.alienvault.com/docs/AlienVault%20Plugin%20List%20-%20June-20-2010.pdf), which you can download and install via the Plugin Wizard. For example, run the following commands:
# cd /usr/share/ossim/scripts ; # plugin_wizard.pl -s "oracle"
and you will get the plugins that contain the word “Oracle” in the name.
With the command:
# ./plugin_wizard.pl -g -s "oracle"
these plugins will be extracted to a directory called win_plugins.
Next, you have to move them to the default directory /etc/ossim/agent/plugins/:
# mv win_plugins/*.cfg /etc/ossim/agent/plugins/
Files with the .sql extension must be added to the MySQL database with the following command:
# ossim-db < ./win_plugins/*.sql
If the database server is not installed on the same machine, you need to copy the files on the server:
# scp win_plugins/*.sql root@<IP Database>:/root/
and run the ossim-db command from the database server.
The configuration directory for the Server component is /etc/ossim/server. The main file is directives.xml, which specifies the configuration file directives, grouped by type of attack, such as malware, brute force and so on.
When you create new guidelines, they should be specified in user.xml rather than in the file containing the default directives (Figure 7).
rsyslog's Dæmon Configuration and Log Rotation:
The /var/log/ossim directory contains the log files of OSSIM's components. The dæmon that keeps track of the logs is, as already mentioned, rsyslog, whose configuration file is /etc/rsyslog.conf.
During the installation process, you configure rsyslog to accept logs from remote machines and store them in different log files, depending on the type and the host that created them.
To achieve this, rsyslog uses filters based on expressions, which are .conf files usually placed in the /etc/rsyslog.d/ directory. For example, to save the logs from a Fortinet firewall in the file /var/log/ossim/fortinet.log, the expression would be:
if ($source == '192.168.1.100' and $msg contains 'fortinet ') ↪and $severity <= '6' then /var/log/ossim/fortinet.log
Adding new hosts that send the logs to rsyslog, you quickly can run out of disk space. Therefore, it is important to define a policy for log rotation in /etc/logrotate.conf. This involves the regular archiving, at predefined intervals, of the existing log files. After a predefined period, the archived log files are deleted or stored on external devices for backup.
Administration through the Web Interface:
OSSIM also can be configured and managed through a nice Web interface, connecting with the browser to the IP address of the machine on which you installed the Server/Framework component (Figure 8).
The default user and password are admin/admin. When you log in for the first time, you are prompted to change your password.
Through the Web interface, you can perform the following tasks:
System configuration (users, update, backups and so on).
Creation and configuration of directives, policies and actions.
Real-time monitoring of network security.
Vulnerability management and incident response.
Management and optimization of network traffic.
The Web interface includes several sections:
Dashboard: provides an overview of detected security events. Displays the visual counters and statistics of the most important security events (Figure 9).
Incidents: shows the list of security events and generated alarms with specific information, such as date, priority, risk, status and a brief history of the actions taken by system administrators.
Analysis: shows a table with the latest events detected, the type, date, origin, destination, the OSSIM node that detected it and the risk. From here, the user can search for patterns in the events according to different criteria (for example, the source IP address). This includes a real-time list of detected events that is updated every two seconds.
Report: allows you to generate reports about security events and network status.
Activities: this interface allows you to run and manage network inventory, identify and add new machines from which to record the logs.
Intelligence: this section handles the system logic—definition and management of policies/actions, directives, event correlation and statistics of the network and of the OSSIM nodes.
Configuration: this section allows you to manage all the system configurations (Figure 10).
OSSIM is a viable open-source SIEM solution and a free alternative to other commercial SIEM products (including AlienVault USM, the commercial version of OSSIM), which are much more expensive, and it is supported by a community of developers and users through forums and documentation available on the AlienVault's Web site.