Query Logs in Azure Sentinel

By Ashwin Venugopal -

 



Query Logs in Logs Page

In Azure Sentinel, the logs page provides access to the query window while allowing you to run queries, save queries, run saved queries, create a new alert rule, and export.  If  you want to run a query, first of all enter a query text and then press the run button. The query results can be seen at the bottom section of the form.

Understand Azure Sentinel Table

Azure Sentinel consists of Analytic Rules that will generate alerts and incidents based on querying the tables within Log Analytics while simultaneously providing tables to be a repository of indicators and watchlists. Some of the Sentinel Data Connectors are capable of ingesting alerts directly. The table below is the Azure Sentinel feature related tables:

Table

Description

SecurityAlert

Contains alerts generated from Sentinel Analytical Rules. Also, it includes alerts created directly from Sentinel Data Connector.

SecurityIncident

Alerts can generate incidents. Incidents are related to alert(s).

ThreatIntelligenceIndicator

Contains user-created or data connector ingested indicators such as File Hashes, IP Addresses, Domain.

Watchlist

An Azure Sentinel watchlist contains imported data.

 Understand Common Tables

When Sentinel ingests data from the Data Connectors, the following table lists the most commonly used tables:

Table

Description

AzureActivity

Entries from the Azure Activity log that provides insights into any subscription-level or management group level events that have occurred in Azure.

AzureDiagnostics

Stores resource logs for Azure Services that use Azure Diagnostics mode. Resource logs describes the internal operation of Azure resources.

AuditLogs

Audit Logs for Azure Active Directory includes system activity information about user and group management managed applications as well as directory activities.

CommonSecurityLog

Syslog messages using the Common Event Format (CEF).

McasShadowltReporting

Microsoft Cloud App Security logs.

OfficeActivity

Audit logs for Office 365 tenants collected by Azure Sentinel. Including Exchange, SharePoint, and Teams Logs.

SecurityEvent

Security events collected from Windows machines by Azure Security Center or Azure Sentinel.

SigninLogs

Azure Active Directory Sign in logs.

Syslog

Syslog events on Linux computers using the Log Analytics agent.

Event

Sysmon Events collected from a Windows host.

WindowsFirewall

Windows Firewall Events.

 Understand Microsoft 365 Defender Tables

The Microsoft 365 Defender Sentinel Data Connector can populate tables with raw data collected from the Microsoft 365 Defender solutions. Microsoft Defender for Endpoint tables:

Table

Description

DeviceEvents

The miscellaneous device events table contains information about various event types including, events triggered by security controls, such as Microsoft Defender Antivirus and exploit protection.

DeviceFileEvents

This table contains information about file creation, modification, and other file system events.

DeviceImageLoadEvents

This table contains information about DLL loading events.

DeviceInfo

This table contains information about devices in the organization, including their OS version, active users, and computer name.

DeviceLogonEvents

This table contains information about user logons and other authentication events.

DeviceNetworkInfo

This table contains information about networking configuration of devices, including network adapters, IP and MAC addresses, and connected networks or domains.

DeviceProcessEvents

This table contains information about process creation and related events.

DeviceRegistryEvents

This table contains information about the creation and modification of registry entries.

DeviceNetworkEvents

This table contains information about network connection and related events.

 









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