Azure Monitor - Log Analytics (part 1 of 4)

By Ashwin Venugopal -

 


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



Introduction to Azure Monitor Log Analytics

Azure Monitor can accumulate logs as well as metrics and then use them to make insights, visualizations, and automated responses while Log Analytics is an important service that can analyze the collected logs. 

An Azure Analytics workspace can be created with the help of Azure subscription which is entirely based on a specific geographic location that can tie the data storage to that region. The region selection can be based on your required data storage location and also impact the costs related with both Log Analytics and Azure Sentinel.

After creating the workspace, it can collect the information from several different sources like:

  1. Azure resources in the same subscription
  2. Azure resources in different subscriptions
  3. Data from other cloud services (such as Amazon Web Services, and Google Cloud Platform)
  4. Data from your private data center (on-premises or third-party hosted)
  5. Data from on-premises resources (through secure internet connections)
  6. Data from IoT and industrial control systems

Log Analytics services can manage your data in a secure cloud data repository while making sure that it is secured with multiple layers of protection including the following:

  1. Data segregation and isolation, with geographic sovereignty
  2. Data retention and deletion policies, per data source type
  3. Internationally certified standards for physical security, inherited from the Azure subscription (commercial and government)
  4. Microsoft-managed incident management processes 
  5. Certified conformity to multiple compliance and regulatory standards
  6. Secure channels for sending data to Log Analytics: certificate-based authentication, and SSL via port 443
  7. Workspace and role-based access permissions, managed by the customer 

Planning a Workspace

You plan the configuration of a workspace beforehand by keeping in mind the following aspects:
  • The name of the workspace- It should be unique and describe the types of services offered by a particular workspace just by looking at it. It is recommended to use your company's name and the word "Sentinel" in the name. 

  • The subscription the workspace belongs to- You should create a separate subscription only for Azure Sentinel to limit its access or you can also choose an appropriate subscription for it.

  • The location of the workspace- The workspace should be located in the same place as the resources to prevent egress charges for sending the data from one location to another. There also might be some laws to denote where the data must reside.

  • Which resource group will the workspace reside in- All the Azure Sentinel resources should be located in the same resource group, however, it is not mandatory and will not affect the performance of Azure Sentinel at all.

  • Which pricing tier to use- If the workspace being used is created before April 2, 2018, or the subscription is a part of an Enterprise Agreement before February 1, 2019, then legacy pricing tiers will be used otherwise, only per GB (2018) is permitted and charges will be for ingestion and retention per GB. 

By planning your workspace in advance you ensure the selection of a unique as well as meaningful name, the proper location to avoid egress charges, the correct resource group, and other decisions that will prevent you from frustration or complete rework later. 




To read part 2, 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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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...
Read more