Share via

[Deprecated] OSSEC via Legacy Agent connector for Microsoft Sentinel

  • Article

Important

Log collection from many appliances and devices is now supported by the Common Event Format (CEF) via AMA, Syslog via AMA, or Custom Logs via AMA data connector in Microsoft Sentinel. For more information, see Find your Microsoft Sentinel data connector.

OSSEC data connector provides the capability to ingest OSSEC events into Microsoft Sentinel. Refer to OSSEC documentation for more information.

Connector attributes

Connector attribute Description
Log Analytics table(s) CommonSecurityLog (OSSEC)
Data collection rules support Workspace transform DCR
Supported by Microsoft Corporation

Query samples

Top 10 Rules

OSSECEvent

| summarize count() by RuleName

| top 10 by count_

Vendor installation instructions

Note

This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias OSSEC and load the function code or click here, on the second line of the query, enter the hostname(s) of your OSSEC device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update.

  1. Linux Syslog agent configuration

Install and configure the Linux agent to collect your Common Event Format (CEF) Syslog messages and forward them to Microsoft Sentinel.

Notice that the data from all regions will be stored in the selected workspace

1.1 Select or create a Linux machine

Select or create a Linux machine that Microsoft Sentinel will use as the proxy between your security solution and Microsoft Sentinel this machine can be on your on-prem environment, Azure or other clouds.

1.2 Install the CEF collector on the Linux machine

Install the Microsoft Monitoring Agent on your Linux machine and configure the machine to listen on the necessary port and forward messages to your Microsoft Sentinel workspace. The CEF collector collects CEF messages on port 514 TCP.

  1. Make sure that you have Python on your machine using the following command: python -version.
  1. You must have elevated permissions (sudo) on your machine.

Run the following command to install and apply the CEF collector:

sudo wget -O cef_installer.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_installer.py&&sudo python cef_installer.py {0} {1}

  1. Forward Common Event Format (CEF) logs to Syslog agent

Follow these steps to configure OSSEC sending alerts via syslog.

  1. Validate connection

Follow the instructions to validate your connectivity:

Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.

It may take about 20 minutes until the connection streams data to your workspace.

If the logs are not received, run the following connectivity validation script:

  1. Make sure that you have Python on your machine using the following command: python -version
  1. You must have elevated permissions (sudo) on your machine

Run the following command to validate your connectivity:

sudo wget -O cef_troubleshoot.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_troubleshoot.py&&sudo python cef_troubleshoot.py {0}

  1. Secure your machine

Make sure to configure the machine's security according to your organization's security policy

Learn more >

Next steps

For more information, go to the related solution in the Azure Marketplace.