Introducing Workbooks (part 2)

By Ashwin Venugopal -


 

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



Creating Workbooks

You can create your own workbook using following ways:
  • Creating a workbook using a template- By following the steps given below, you can create your own workbook using a template which is easier as you have a basis to start from-

  1. Click on the Save button on the templates's details page. 
  2. A pop-up window will ask you about the location to save the new workbook which should be the same where your Log Analytics workspace resides. 
  3. Now you can click OK to create a new workbook under My workbooks, with the same name as the template.

This is a very simple method to create a workbook that can be modified as required.

  • Creating a new workbook from scratch- This method is a bit more complicated as it requires creating a workbook, and then its editing as it is already saved with a default query assigned to it. You have to perform the following steps-  

  1. Click the Add workbook button on the header which will create a workbook.
  2. The new workbook consists of texts and a query step already to give you a headstart. 
  3. Now you can click on the Save icon in the header to save the workbook which will open a Save dialog box.

Now, you just have to edit the workbook so that you can modify the existing steps or add your own steps.

Editing a Workbook

If you want to edit your workbook, you have to perform following steps:
  1. Go to either of the tabs.
  2. Select the workbook in question.
  3. Now, select the View saved workbook button on the workbook's detail pane. 

Note- You cannot edit a workbook template directly as it must be saved first and then edited, but if you have created a workbook from scratch, then, you have to go to the My workbooks tab to edit it.

At the top of the page where header of buttons is shown, the first one on the left is Edit button which change the workbook view to edit mode. Each step in a workbook have its own Edit button so that the changes can be individually.

After you are finished with the editing, you can click on the Done Editing button in the header barto revert to the view mode. Now you can easily ensure that the edits you have just made are working properly or not before Saving them. 

Managing Workbooks

Managing a workbook involves deleting, moving, and sharing workbooks. Click on the Open button while looking for a saved workbook which will open a Saved workbooks blade. At the top of it is the New button which can create a new workbook, the Refresh button to refresh the view, and the Save all button to save all the changes. Below this is the Subscription drop-down menu to change the subscription you are looking at along with a search box to search for particular workbooks. 

There is a list of all the workbooks below named as My reports, which only you can see, and Shared reports which everyone can see. Each workbook will be shown in a separate row with its name and an icon to show if the workbook is created from a template or not. There is a context-sensitive menu icon which help you to delete, rename, move, or pin the workbook to a dashboard (to offer a shortcut).





To read part 1, please click here
To read part 3, 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

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...
Read more