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

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