Getting Started with Microsoft Sentinel- Connect Your Data

By Ashwin Venugopal -

 






Overview

Data is sent to the Microsoft Sentinel workspace after configuring the provided data connectors, which are generally present in Out-Of-The-Box (OOTB), or built-in Content Hub solutions for Microsoft 365 services, Azure, and third-party specific.

Ingest Log Data with Data Connectors

  • Connect the data sources with Microsoft Sentinel Data Connectors, which are in the Content Hub Solutions provided by Microsoft Sentinel.

  • After installing the Content Hub Solution, the Configuration | Data Connectors menu section will show the installed Data Connectors.

  • Now, select the Open Connector page to view the detailed connector page split in left and right halves.

    • The left half contains all the information regarding the connector, its status, and the last time a log was received when connected. Whereas, the bottom part displays the Data Types with the lists of tables that the connector writes to.

    • The right half has an instructions tab that can vary according to the connector, and generally contains Prerequisites and Configuration. The Configuration tab can connect with the data source, while the Next Step tab offers a quick look through workbooks, query samples, and analytical templates. However, Data Connectors can only be disconnected or deactivated, they cannot be deleted.

Understand Data Connector Providers

Microsoft 365 Defender

It provides alerts, incidents, and raw data from Microsoft 365 Defender products including (but not limited to):
  1. Microsoft Defender for Endpoint
  2. Microsoft Defender for Identity
  3. Microsoft Defender for Office 365
  4. Microsoft Defender for Cloud Apps
Microsoft Azure Services

Its connectors include (but not limited to):
  1. Azure AD
  2. Azure Activity
  3. Azure AD Identity Protection
  4. Azure DDoS Protection
  5. Microsoft Defender for IoT
  6. Azure Information Protection
  7. Azure Firewall
  8. Microsoft Defender for Cloud
  9. Azure Web Application Firewall (WAF) 
  10. Domain name server
  11. Office 365
  12. Windows firewall
  13. Security Events

Vendor Connectors

There is an ever-growing list of vendor-specific data connectors:
  • Custom connectors using the Log Analytics API- Log Analytics Data Connector API can be used to send data to the Microsoft Sentinel Log Analytics workspace.

  • Logstash plugin- Microsoft Sentinel's output plugin for Logstash data collection engine can be used to send any log to the Log Analytics workspace. The logs are written to a custom table defined via the output login. 

Common Event Format and Syslog Connector

The generic Common Event Format (CEF) and Syslog Connector can be used in case of no vendor-provided connector. Syslog, common to Linux, is an event logging protocol where applications send messages that may be either stored on the local machine or Syslog collector. However, Common Event Format (CEF) is an industry-standard format on top of Syslog messages, and is used by many security vendors to allow event interoperability among different platforms. 

CEF has always been the first choice as log data is stored into the predefined fields of the CommonSecurityLog table, whereas, Syslog offers header fields and the raw log messages are stored in SyslogMessage field in the Syslog table. To query a Syslog data, a parser should be written to extract the specific field. 

View Connected Hosts

The Data Connector page shows the installed connectors and to view the connected hosts, following steps should be taken:
  1. Select Settings
  2. Workspace settings transfers to Log Analytics
  3. Now, select Agents in the Log Analytics Settings area
  4. Two tabs will be displayed, one for Windows and another one for Linux.
































Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more