Azure Monitor - Log Analytics (part 2 of 4)

By Ashwin Venugopal -

 



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


Exploring the Overview Page

You may have created your Log Analytics workspace by any means, but the further work will be done only on Azure Portal:
  1. Open the portal and go to the Log Analytics Solution page.
  2. Locate your new Analytics workspace for Azure Sentinel and click on it which will take you to the overview screen.
  3. The Essentials list present at the top of the page will help you to review the following-    

  • Resource group- it is where the workspace resides and by selecting [change] you can move to another one.
  • Status- it should show Active.
  • Location- it is the Azure location where the workspace resides.
  • Subscription name- it is the subscription this resource is associated with.
  • Subscription ID- it is a unique GUID for the preceding subscription and is useful while calling Microsoft for technical support.
  • Workspace name- it's the name of the Log Analytics workspace.
  • Workspace ID- it's the GUID for the workspace and is useful when calling Microsoft for technical support.
  • Pricing tier- the pricing tier for the workpspace.
  • Management services- view the activity log for the workspace.
  • Access control mode- permissions can be given to access the information in this workspace.

Managing the Permissions of the Workspace

Azure offers three main levels of access to resources:

  • Owner- Highest level of access to resources.
  • Contributor- Can create and modify resources, but can't grant or revoke access.
  • Reader- Can view all resources.

 These permissions can be granted at four different levels:

  • Subscription- It's the highest level of access and applies to all resources within the subscription.
  • Resource group- Applies to the specific resource group, which may contain multiple workspaces. 
  • Workspace- Applies only to the specific workspace.
  • Table level RBAC- Applies to individual tables within the log. 

You can apply the permissions with the help of built-in roles or create your own custom role for a particular access. Some of the built-in user roles are given below:

  • Engineering developing new queries and data connectors-  

  1. Azure Sentinel Contributor- helps you to create and edit dashboards, analytics rules, and other Azure Sentinel resources. 
  2. Log Analytics Reader- it offers read-only visibility to all Azure resources and Azure Sentinel logs.

  • Analysts running daily operations-

  1. Azure Sentinel Responder- it helps you to manage incidents, view data, workbooks, and other Azure Sentinel resources. 
  2. Log Analytics Reader- offers read-only visibility to all Azure resources as well as Azure Sentinel logs.

For additional permissions, you can provide minimal permissions and apply them only for  particular resources which is also safer than providing  broad and excessive permissions. 



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

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