Deploy the Microsoft Defender for Endpoint Environment (part 2)

By Ashwin Venugopal -

To read part 1 please click here

 Configure device groups

In this one, a set of devices are grouped together based on a set of attributes such as their domains, computer names, or designated tags. In the Microsoft Defender for Endpoint, you can create device groups and use them to:

  • Limit access to the related alerts and data to the specific Azure AD user groups with the assigned RBAC roles.
  • Configure different auto-remediation settings for different sets of devices.
  • Assign specific remediation levels to apply during automated investigations. 
  • In an investigation, filter the devices list to just specific device groups by using the Group filter. 

As a part of the process of creating a device group you will:
  • Set the automated remediation level for that group.
  • Specify the matching rule that determines which device group belongs to the group based on the device name, domain, tags, and OS platform.
  • Select the Azure AD user group that should have access to the device group.
  • Rank the device group relative to the other groups after it is created. 

Create a device group

To create a device group:
  1. In the navigation pane, select Settings > Device groups.
  2. Select Add device group.
  3. Enter the group name as well as automation settings and specify the matching rule that determines which devices belongs to the group. 
  4. Preview several devices that will be matched by this rule. 
  5. Assign the user groups that can access the device group you created. 
  6. Select Close and the configuration changes are applied. 

Configure environment advanced features

The Advanced Features area in the General settings area provides many on/off switches for the features within the product. The following are the settings that are environment focused:

Show user details

This feature can be turned on to see the user's details stored in the Azure AD including a user's picture, name, title, and department information when investigating user account entities. You can find user account information in the following views-

  • Security operations dashboard
  • Alert queue
  • Device details page

Skype for business integration

By enabling the skype for the business integration you can have the ability to communicate with the users using skype for business, email, or phone which can be very helpful when you need to communicate with the users and mitigate risks.

Microsoft Defender for Identity integration

The integration with the Microsoft Defender for identity allows you to pivot directly into another Microsoft Identity security product and by enabling this feature, you'll enrich the device-based investigation capability by pivoting across the network from an identity point of view. 

Microsoft Secure Score

It forwards Defender for Endpoint signals to Microsoft Secure Score in the Microsoft 365 security center and by turning on this feature gives Microsoft Secure Score visibility into the devices security posture while the forwarded data is stored and processed in the same location as your Microsoft Secure Score data.

Office 365 Threat Intelligence connection

When you turn on this feature, you can incorporate data from Office 365 Advanced Threat Protection into the Microsoft Defender Security Center to conduct a comprehensive security investigation across Office 365 mailboxes and Windows devices. 

Microsoft Cloud App Security

Enabling this setting forwards Defender for Endpoint signals to Microsoft Cloud App Security to provide deeper visibility to cloud application usage. 

Azure Information Protection

Turning on this setting allows signals to be forwarded to the Azure Information Protection. It gives data owners and administrators the visibility into the protected data on onboarded devices and device risk ratings.

Microsoft Intune Connection

When you turn on this feature, you can share Defender for Endpoint device information with Intune, enhancing policy enforcement and you will need to enable the integration on both the Intune as well as Defender for Endpoint to use this feature.

Conditional Access Policy

When you enable Intune integration, it will automatically create a classic Conditional Access (CA) policy which is a prerequisite for setting up status reports to Intune. It should not be deleted.

Preview features

You can learn about the new features in the Defender for Endpoint preview release and be among the first to try the upcoming features by turning on the preview experience. You can also have the access to the upcoming features, for which you can provide feedback on to help improve the overall experience before the features are generally available. 

 

To read part 1 please click here

   













Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more