Azure Monitor - Log Analytics (part 3 of 4)

By Ashwin Venugopal -

 



To read part 1, please click here
To read part 2, please click here
To read part 4, please click here


Enabling Azure Sentinel

After successfully creating Log Analytics workspace to work with Azure Sentinel, you can easily perform the following tasks:
  1. If Azure Sentinel is not enabled for your tenant, then you have to sign in to Azure portal, enter Azure Sentinel in the search box, and select the Azure Sentinel entry.
  2. Click the Add button for an extra workspace.
  3. You can easily choose an appropriate workspace from the list provided or click Create a new workspace to add a new workspace and then select it. Now you can click Add Azure Sentinel button at the bottom of the screen to continue further.
  4. After creating a new workspace, the News & guide page of Azure Sentinel will provide some easy steps to set up the workspace. 

Now, you have successfully created your Azure Sentinel environment and ready to use it.

Exploring the Azure Sentinel Overview page 

You will be automatically sent to the Overview page after linking it with Log Analytics workspace which offers you the general knowledge about your Azure Sentinel environment and will look like following picture:



The page's different sections are described below:

  • The header bar

It helps you to refresh the screen to see any updates and choose how far back in time to look for data by selecting a clock like looking icon.

  • The summary bar

It will show you the amount of data being ingested, alerts raised, and the number of incidents those alerts have created in a particular time period along with the incidents broken down by their status.

  • The events & alerts over time section

It will allow to see the logs responsible for ingesting the most data and the number of incidents created in a particular time frame. Due to this section's interactive nature, whenever you select a specific time, it will automatically show you the filtered information about anything happened in that time period.

  • The recent incident section 

It will show the last five incidents created as well as the number of alerts responsible for generating those incidents. You can get more information about any incident by simply clicking on its name.

  • The data source anomalies section

The two different data sources that Azure Sentinel's Machine Learning has recognized as anomalies can be seen in this section and by simply clicking on the log name, you can get more details about the anomaly.

  • The potential malicious events section 

Although this section is not visible, it can highlight you any potential malicious events with the help of an interactive map and you can just zoom in get precise indication of the occurrence of the event.

  • The democratize ML for your SecOps section

Another invisible section which is capable of providing you with the general knowledge on Azure Sentinel's Machine Learning as well as a link for more information.

The Azure Sentinel's Overview page is a great place to get an overview of your Azure Sentinel's environment.




To read part 1, please click here
To read part 2, please click here
To read part 4, please click here


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