Incident Management (part 2)

By Ashwin Venugopal -

 





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




Exploring the Full Details Page

As the name suggests, this page can show you lots of information about an incident like details on the alert(s) that make up the incident, any bookmarks associated with this incident, details on any entity, and any comments added to this incident. You can get to the Full Details page by simply clicking on the View Full Details button in the incident details pane, where the right side of the page is divided into the tabs that can show information about the alert itself, any bookmarks for this incident, the entities for this incident, and a  list of all the comments. Each of the sections are described below:
  • The Alerts Tab- This tab can show one or more alert(s) that make up an incident. There is a colored strip that shows the alert's severity. At the far right of this screen is the View playbooks link which can open a new pane showing all the playbooks. By clicking on the Run button in each playbook's row, you can run the playbook against the alert's information. 

  • The Bookmarks Tab- By clicking on it, you can view all the bookmarks associated with an incident. Search textbox can easily search any bookmark. The Create Time, Name, Created By, and Tags fields can seen for each bookmark. There is context-sensitive menu on the far right side on each listing with Remove from incident option which will ask for your confirmation to remove any bookmark.

  • The Entities Tab- It can show all the entities associated with an incident. Search textbox can search any entity whereas the ENTITIES filter helps you to select one or more Select All, Account, Host, IP, and/or URL. However, Select All is selected by default. ASSOCIATED ALERTS can help you to determine the total number of other alerts with the same entity.

  • The Comments Tab- This one will show all the comments related with an incident along with the total number of comments. You also add new comments while performing your investigation to remember your steps which can also help the others who want to look at the same incident or investigate one that is similar.     







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