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

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