Creating Playbooks & Logic Apps (part 2)

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 Playbooks Page

It provides the list of all the logic apps in the selected subscription(s) and if the Trigger kind column situated on the far right states Microsoft Sentinel, then you can use this logic app as a playbook. The different fields of this page are described below:

  • The Header Bar contains the following buttons-

  1. Add Playbook button helps you to add a new playbook.
  2. Refresh button will refresh the display.
  3. The time dropdown button.
  4. The Enable, Disable, and Delete buttons which are only available for the selection of one or more logic apps.
  5. The Logic Apps documentation button will send you to the page containing more information on logic apps as well as the way to create them. 

The given information proves that the header bar can be used to create new playbooks, change the time frame, and offer more documentation on how to work with logic apps. 

  • The Summary Bar is present below the header bar and the information offered uses time dropdown except for the number of security playbooks-

  1. The Security Playbooks number is located on the left side shows the number of all the logic apps in your selected subscription.
  2. The Total runs present to the right that contains the total number of times all the logic apps have run which is the sum of Succeeded runs + Running playbooks + Failed runs.
  3. Succeeded runs is after that which tells all the number of times the various logic apps have run as well as how many of them were successful.
  4. The Running playbooks is to the right showing how many logic apps are actually running, and not just playbooks.  
  5. Lastly, it is Failed runs showing how many times a running logic app failed. 

  • Logic App Listing is present below the summary bar showing a selection checkbox, Name, status (Enabled or Disabled), the number of total runs, number of instances of the logic app running, number of times the logic app succeeded as well as failed, the subscription it belongs to, the location of the logic app, and the trigger kind for each of the listed logic app. But, the numbers in the Runs, Running, Succeeded, and Failed columns is based on the time selected in the time dropdown for the status bar. 






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