Perform Device Investigations (part 1)

By Ashwin Venugopal -

 



To read part 2 please click here


The Device Inventory List

The device inventory page shows a list of the devices in your network where alerts were generated. By default, the queue displays the devices with alerts seen in the last 30 days and the device page can also be accessed from the various investigation pages like Incidents and Alerts. At a glance, you will see the information such as domain, risk level, OS platform, and the other details for easy identification of the devices mostly at risk. 

Risk Level

The risk level reflects the overall risk assessment of the device based on a combination of the factors, including the types and severity of the active alerts on the device and by resolving the active alerts, approving remediation activities, and suppressing the subsequent alerts can lower the risk level.

Exposure Level

The exposure level reflects the current exposure of the device based on the cumulative impact of its pending security recommendations and if the exposure level says, "No data available", there are a few reasons why this may be the case:
  • The device stopped reporting for more than 30 days- in that case, it is considered inactive, an the exposure isn't computed
  • The device OS is not supported- see minimum requirements for the Microsoft Defender for Endpoint
  • The device has a stale agent (very unlikely) 

 Health State

The following device health states:
  • Active- devices that are actively reporting sensor data to the service
  • Inactive- devices that have stopped sending signals for more than seven days
  • Misconfigured- devices that impaired communications with service or are unable to send sensor data. These devices can be further classified to no sensor data and impaired communications.  

Antivirus Status

The antivirus status for Windows 10 devices only:
  • Disabled- Virus and threat protection is turned off
  • Not reporting- Virus and threat protection not reporting
  • Not updated- Virus and threat protection is not up to date 

Investigate the device

You should investigate the details of an alert raised on a specific device to identify the other behaviors or events that might be related to the alert or the potential scope of the breach. Affected devices are identified in the following cases:
  • Devices list
  • Alerts queue 
  • Security operations dashboard
  • Any individual alert
  • Any individual file details view
  • Any IP address or domain details view
Whenever you investigate a specific device. you will see:
  • Device details
  • Response actions
  • Tabs (overview, alerts, timeline, security recommendations, software inventory, discovered vulnerabilities, missing KBs)
  • Cards (active alerts, logged on users, security assessment)



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