In this guide, we are going to learn how to install OSSEC agent on Mac OS X. We have covered similar setups in our other guides. You can check them by following the links below;
How to Install OSSEC Agent on Mac OS X
Well as usual, we are going to install OSSEC agent on Mac OS X from the source code. As a result ensure that you have C compiler (gcc) installed.
To verify that the the GNU Compiler collection is installed, run the command below;
which gcc /usr/bin/gcc
If, however, you are prompted to install the developer tools during OSSEC agent installation, please do install and proceed with installation.
Next, download OSSEC agent for Unix from the downloads page.
Once the download completes, extract the source archive.
tar xzf 3.1.0.tar.gz
Navigate to extracted source directory and run the OSSEC install script.
cd ossec-hids-3.1.0/ ./install.sh
When the install script runs, you will be prompted to choose the installation language. In this case, English is chosen.
... (en/br/cn/de/el/es/fr/hu/it/jp/nl/pl/ru/sr/tr) [en]: en
Press Enter again to proceed with the installation. Choose
agent as the type of installation.
1- What kind of installation do you want (server, agent, local, hybrid or help)? agent - Agent(client) installation chosen.
/var/ossec as the installation directory for OSSEC.
2- Setting up the installation environment. - Choose where to install the OSSEC HIDS [/var/ossec]: - Installation will be made at /var/ossec .
Set the IP address of the OSSEC server. This can be OSSEC server itself or the AlienVault.
3- Configuring the OSSEC HIDS. 3.1- What's the IP Address or hostname of the OSSEC HIDS server?: 192.168.43.22 - Adding Server IP 192.168.43.22
Enable system integrity check.
3.2- Do you want to run the integrity check daemon? (y/n) [y]: y - Running syscheck (integrity check daemon).
Enable Rootkit detection.
3.3- Do you want to run the rootkit detection engine? (y/n) [y]: y - Running rootcheck (rootkit detection).
Disable active response
3.4 - Do you want to enable active response? (y/n) [y]: n - Active response disabled.
3.5- Setting the configuration to analyze the following logs: -- /var/log/system.log - If you want to monitor any other file, just change the ossec.conf and add a new localfile entry. Any questions about the configuration can be answered by visiting us online at http://www.ossec.net . --- Press ENTER to continue ---
If the installation is successful, you should the output stating that configuration finished properly.
- Configuration finished properly. - To start OSSEC HIDS: /var/ossec/bin/ossec-control start - To stop OSSEC HIDS: /var/ossec/bin/ossec-control stop - The configuration can be viewed or modified at /var/ossec/etc/ossec.conf Thanks for using the OSSEC HIDS. If you have any question, suggestion or if you find any bug, contact us at [email protected] or using our public maillist at [email protected] ( http://www.ossec.net/main/support/ ). More information can be found at http://www.ossec.net --- Press ENTER to finish (maybe more information below). --- - You first need to add this agent to the server so they can communicate with each other. When you have done so, you can run the 'manage_agents' tool to import the authentication key from the server. /var/ossec/bin/manage_agents More information at: http://www.ossec.net/en/manual.html#ma
Once the installation is done, add the agent to the server to ensure that they can communicate. After that extract the agent-server key and import. Run the command below to install the key on the agent.
Press I to import the key. Paste the key and press Enter to add it.
**************************************** * OSSEC HIDS v3.1.0 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): OTYgbHVhbmRtaSAxOTIuMTY4LjM1LjEwOCA2NzA4N2ZmNjhiZDhjZGQ3NjgwMjlhODA0ZmNjMzQyOTUyODE0YTM1NTdhNjRkOWIxNGFhNDljYTJhOTJhNzhh
If all is well, you should be able to see the details of the agent as is on the server.
Agent information: ID:96 Name:amosmibey IP Address:192.168.43.108
Type y and Press Enter to confirm adding the key.
Confirm adding it?(y/n): y Added. ** Press ENTER to return to the main menu. **************************************** * OSSEC HIDS v3.1.0 Agent manager. * * The following options are available: * **************************************** (I)mport key from the server (I). (Q)uit. Choose your action: I or Q: q ** You must restart OSSEC for your changes to take effect. manage_agents: Exiting.
Next start OSSEC agent service.
Starting OSSEC HIDS v3.1.0 (by Trend Micro Inc.)... Started ossec-execd... 2019/01/22 11:26:06 ossec-agentd: INFO: Using notify time: 600 and max time to reconnect: 1800 Started ossec-agentd... Started ossec-logcollector... Started ossec-syscheckd... Completed.
To verify that the agent has started and connected to the server, tail the OSSEC agent logs. You should be able to see a line stating that the agent is connected to the server.
tail /var/ossec/logs/ossec.log | grep -i connected
2019/01/23 17:06:58 INFO: Connected to 192.168.43.22 at address 192.168.43.22, port 1514 2019/01/23 17:23:54 INFO: Connected to 192.168.43.22 at address 192.168.43.22, port 1514
That is all. Now to ensure that the service runs in case the system reboots, create a start up service as shown below;
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>autostartossec</string> <key>ProgramArguments</key> <array> <string>/Users/amos/myscripts/autostartossec.sh</string> </array> <key>RunAtLoad</key> <true/> <key>StandardErrorPath</key> <string>/var/ossec/logs/ossec.err</string> <key>StandardOutPath</key> <string>/var/ossec/logs/ossec.out</string> </dict> </plist>
The lauch daemon is created. Next create the service startup script.
#!/bin/sh /var/ossec/bin/ossec-control start
Make the script executable.
chmod u+x /Users/amos/myscripts/autostartossec.sh
To test if this works, reboot the system and check the status of OSSEC agent.
ossec-logcollector is running... ossec-syscheckd is running... ossec-agentd is running... ossec-execd not running...
The service should now running. Great and congratulations. Up-to that far, you have learnt how to install OSSEC agent on Mac OS X. Thank you for reading.