Incident Management (part 3)

By Ashwin Venugopal -

 




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




Investigating an Incident

An incident investigation can be done in Microsoft Sentinel via the graphical investigation page, which is a graphical interface to show the incident in question as well as find the related information. There is an Investigate button at the bottom of the incident details page and by simply clicking on it you can start the graphical investigation but if it is grayed out, then, that means there are no entities associated with the incident as it requires at least one entity for the graphical investigation to work. 

Clicking on the button will take you to a page divided into different sections where the header bar provides the general information related to the incident (like title, severity, status, owner, and last update time); there are two columns buttons on the right side of the screen and the column on the left is consists of screen control buttons in which the top button can zoom in or out while on the far right of the page are the buttons related to the incident itself described below:

  • The Timeline Button- As the name suggests, it helps you to view the timeline of all the incidents present on the screen and if there are a lot of alerts shown, then the timeline can show a history of when the alerts occurred. However, if a single incident is selected, then only the related entities will be highlighted in the view while others will be grayed out which makes it easier to navigate through the timeline and see what entities are related to which incidents.

  • The Info Button- Here, you can view the related information of your selected entity. It can either ADDRESS, HOST NAME, or ACCOUNT NAME for IP, host, and account according to the type you have selected. But, if a URL is selected, then Microsoft Sentinel will perform URL detonation on all URL entity types which means that the URL against a list of known bad addresses will be checked and a screenshot of the website at the time of the alert firing is grabbed. DENOTATIONVERDICT is either BAD or GOOD whereas DETONATIONFINALURL is the final destination after all the URL redirects occur. DETONATIONSCREENSHOT is a screenshot of the site at the time of an alert firing.

  • The Entities Button- It will show a list of all the Entities, Alerts, and Bookmarks along with the information of all the related alerts. If the mouse hover over any of the listed items, the User Interface (UI) will simply highlight the entities related to the item.

  • The Help Button- As the name suggests, it can offer general help on the screen. Its page shows the entities and how they are related to each other. Its screen is a fully interactive one and you can move around the objects for a better view while zooming in and out.   







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