Creating Playbooks & Logic Apps (part 3)

By Ashwin Venugopal -

 



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





Logic Apps Settings Page

You can get to the logic app settings page by simply clicking on logic app where you can easily create, edit, or delete an individual logic, and find more information as well as the history of your logic app's runs. It's various sections are discussed below:
  • The Menu Bar- It is the most important bar and allows you to perform various actions and is further divided into various sections.

  • The Header Bar- It offers following buttons to manage the logic app-  

  1. The Run trigger button can run the logic app and is not much useful with most of the playbooks as it requires an alert's trigger information to run.
  2. The Refresh button to refresh the page while also showing when a playbook has finished running.
  3. The Edit button helps you to edit the logic app's workflow.
  4. The Delete button can delete the logic app after confirming that you actually want to perform the action.
  5. The Disable button can disable the logic app so that it cannot run even after triggering the connector and after disabling this button will be called Enable. 
  6. The Update Schema button can only be enabled when there is a change in the logic app requiring the update of underlying schema. 
  7. The Clone button helps you to make a copy of the logic app so that you can try out some changes without losing the original one.
  8. The Export button can export the logic app to Power Automate and Power Apps.

  • The Essentials Section- As the name suggests, it contains all the essential information for the logic app and all its fields are self-explanatory, some of them are as follows-

  1. The Definition field can show the number of triggers as well as actions that make up the logic app.
  2. The Integration Account field can show the integration account being used while using enterprise integrations.

  • The Summary Section- It shows the information specific to the logic apps and broken down into two sections i.e. Triggers and Actions. Each field is given below-

  1. The Trigger field can show the name as well as description of the trigger used by the logic app.
  2. The FREQUENCY field can tell the number of time a logic app can run if you set a timer but, it will be empty for playbooks as they are triggered on creation of an alert.
  3. The EVALUATION field show you what has happened if and when the logic app has run in the last 24 hours.
  4. The COUNT field can tell you the number of actions required for the workflow of a logic app.  

  • The Runs History Section- It provides you all the information regarding the times the logic app has run and is divided into following-

  1. The Status field shows if an instance of the logic app is running, has failed, or has succeeded.
  2. The Start time field tells the starting time and date of the logic app instance. 
  3. The Identifier field has a unique ID representing the logic app that can be needed to debug a logic app issue with Microsoft. 
  4. The Duration field can also show the time taken by an instance to run.
  5. The Static Results field can show all the static results that are set up to test the logic app.

Creating a New Playbook

Firstly, you have to click on the Add Playbook link on the Microsoft Sentinel Playbooks page to open the Logic App Screen. It's different fields are as follows:
  • The Logic App name field allows a descriptive name (without any space but underscores can be used) so that the other users can also identify what the playbook can do.
  • The Subscription dropdown allows you to choose an appropriate subscription which should be same as the location of your Log Analytics Workspace. 
  • The Resource group field helps you to either choose an existing resource group or create a new one while still following your organization's Azure architecture design policies, if any.
  • The Location dropdown helps you the select an appropriate location which should be the same as your Log Analytics workspace's location to avoid the egress charges.
  • The Log Analytics field can store all the information of a playbook's runtime which will prove useful if you want to allow another system, like Microsoft Sentinel, to perform queries against an information.   

After successfully filling all your information, and clicking Review + create button will help you to create a logic app. 







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