Connect Syslog Data Sources to Azure Sentinel

By Ashwin Venugopal -

 



Plan for the Syslog Connector

The events from Linux-based, Syslog-supporting machines or appliances can be streamed into Azure Sentinel using the Log Analytics agent for Linux. The host's native Syslog daemon will collect local events of the specified types and forward them locally to the agent, which will stream them to your Log Analytics workspace.

Log Analytics also helps in collecting the messages sent by the rsyslog or syslog-ng daemons, where rsyslog is the default that's on version 5 of Red Hat Enterprise Linux (RHEL), CentOS, and Oracle except for the Linux version sysklog Syslog event collection and the rsyslog daemon should be installed and configured to replace sysklog for these versions of Linux.

How it works?

Syslog is an event logging protocol that is common to Linux and when the Log Analytics agent for Linux is installed on your VM or appliance, the installation routine configures the local Syslog daemon to forward messages to the agent on TCP port 25224 which in turn sends the message to your Log Analytics workspace over HTTPS, where it can be parsed into an event log entry in the Syslog table in the Azure Sentinel Logs.  

Collect data from Linux-based sources using Syslog

To view the connector page:
  1. Select Data connector page.
  2. Select Syslog.
  3. Then select the Open connector page on the preview pane.
  4. Verify that you have the appropriate permissions.
  5. Select the Choose where to install the agent option to expand the instructions.  

For an Azure Linux VM:

To install the agent on an Azure Linux VM:
  1. Install agent on Azure Linux Virtual Machine.
  2. Select the link Download and install agent for Azure Linux VMs.
  3. Select Connect on teh row of the Linux VM. 

For any other Linux machine:

To install the agent on non-Azure Linux virtual hosts:
  1. Install agent on non-Azure Linux Machine.
  2. Select the link Download and install agent for non-Azure Linux machines.
  3. In the Agents management blade, select the Linux servers tab.
  4. Copy the command for Download and onboard agent for Linux and run it on your Linux machine.
  5. The page also displays your Workspace ID, primary key, and secondary key.  

Configure the log analytics agent

The Log Analytics Agent for Linux can only collect events with the facilities and severities that are specified in its configuration and to configure the Log Analytics agent for syslog facilities you should:
  • Access the Log Analytics Workspace Advanced Settings page- 

  1. From the Syslog Data connector page, select Open your Workspace advanced settings configuration.
  2. From the Azure Sentinel portal, select Settings in the Configuration area. Select Workspace Settings Tab. Select Advanced settings in the Settings area.        

  • Select Data.
  • Select Syslog.
  • Select the option Apply below configuration to my machines
  • Enter the facility name and select + for each facility. 

If you want to configure Syslog manually on each Linux agent, then uncheck the box Apply below configuration to my machines. The following facilities are supported with the Syslog collector:

  • kern
  • user
  • mail
  • daemon
  • auth
  • syslog
  • lpr
  • news
  • uucp
  • cron
  • authpriv
  • ftp
  • local0-local7

Parse syslog data with KQL

The Syslog collector writes log data to the Syslog table whereas the CEF Connector writes to the CommonSecurityLog with the fields already parsed. A parser is known as a KQL Function that is a query saved as a function and then referenced with the function name which is like accessing any other table. After creating the parses, you only need to write the SyslogMessage parsing once. 

In the Logs window, create query, select the Save button, and select Function from the drop-down, after that specify function name and alias. For example, if we create the Function named MyParser, we then can access the table using the name MyParser.










Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more