Securing Your Enterprise with Microsoft Defender for Identity
+ Full Webinar Transcript
Microsoft Defender for Identity: How to Protect Active Directory and Hybrid Environments
Moderator: Good afternoon and thanks for joining us today. We’re here to discuss securing your enterprise with Microsoft Defender for Identity.
Today’s presenters are Tom Garren, CTO, and Brad Cheney, Modern Work Practice Manager. I’m Subz, Marketing Director here at 2W Tech, and I’ll be moderating today’s conversation.
2W Tech is a technology solutions provider and managed service provider with expertise across Microsoft, cybersecurity, Epicor ERP, cloud infrastructure, and manufacturing technology.
I’ll now turn it over to Tom to get us started.
Why Is Identity Security Important?
Tom: Today, we’re going to explore Microsoft Defender for Identity and how it can help organizations protect their users and identity infrastructure in today’s evolving cybersecurity threat landscape.
Brad, why don’t you start by talking about why identity security is such an important part of the larger cybersecurity picture?
Brad: Protecting business information starts with knowing that the person accessing it is actually who they claim to be.
That’s especially important in organizations with hybrid environments where employees may be accessing Microsoft 365 and cloud applications while the business still relies on traditional on-premises Active Directory for manufacturing systems, ERP applications, CAD tools, file servers, and other resources.
Identity becomes one of the most important security layers because compromised credentials can give attackers an opportunity to access additional systems, elevate privileges, move throughout the environment, steal information, or deploy malware and ransomware.
Why Is On-Premises Active Directory a Cybersecurity Risk?
Brad: Microsoft Entra ID and modern cloud environments provide capabilities such as Conditional Access, multifactor authentication, risk signals, and other identity protections.
But many organizations still have on-premises Active Directory environments supporting important business applications.
Those environments can accumulate security issues over time, including dormant accounts, excessive administrative permissions, outdated configurations, shared or service accounts, and other identity-related risks.
If an attacker gains access to a compromised account, weaknesses in identity configuration can make it easier to escalate privileges or move laterally to additional systems.
Tom: That’s especially relevant for manufacturers.
A manufacturing company may not be able to eliminate on-premises Active Directory simply because it has moved email and collaboration into Microsoft 365.
Machine tools, ERP systems, engineering applications, CAD software, production systems, and other resources may still rely on Active Directory authentication.
What Is Microsoft Defender for Identity?
Brad: Microsoft Defender for Identity is an identity threat detection and response solution designed to help organizations identify suspicious activity and advanced threats involving identities.
Defender for Identity collects identity signals from supported infrastructure and analyzes those signals to help detect suspicious behaviors such as compromised credentials, privilege escalation, reconnaissance, and lateral movement.
It integrates into the broader Microsoft Defender security environment, giving security teams additional context about identities alongside signals from endpoints, email, cloud applications, and other security sources.
How Does Microsoft Defender for Identity Work?
Brad: Defender for Identity uses sensors on supported identity infrastructure to collect identity-related signals.
This can include domain controllers and other supported identity infrastructure such as Active Directory Federation Services, Active Directory Certificate Services, and Microsoft Entra Connect servers.
Those identity signals are analyzed using Microsoft’s security intelligence and behavioral analytics to identify activity that may indicate an identity-based cyberattack.
Alerts and incidents can then surface through the Microsoft Defender portal, where security administrators can investigate suspicious users, devices, activity, and related events.
Tom: That’s an important distinction.
You’re adding deeper visibility into the identity infrastructure itself and then correlating that information with other security signals available through the broader Microsoft security stack.
What Types of Identity Attacks Can Defender for Identity Detect?
Brad: Defender for Identity is designed to help organizations identify several types of suspicious identity activity and attack techniques.
That can include unusual authentication patterns, directory reconnaissance, attempted privilege escalation, brute-force activity, lateral movement, and credential theft or replay techniques.
Pass-the-Hash: An attacker may attempt to use a captured password hash to authenticate to other systems without knowing the user’s actual password.
Pass-the-Ticket: Attackers may attempt to steal and reuse Kerberos tickets to impersonate users or access additional resources.
Kerberoasting: Attackers can request Kerberos service tickets associated with service accounts and attempt to recover account credentials offline.
Defender for Identity can help surface suspicious activity associated with these techniques so security teams can investigate before the intrusion progresses further.
How Does Behavioral Analytics Improve Identity Security?
Tom: One of the important differences between modern identity security and traditional log review is behavioral analysis.
Instead of requiring an administrator to manually review enormous amounts of security logs, modern security tools can look for behaviors that differ from what is normally expected.
For example, perhaps a user suddenly begins accessing systems or resources they don’t normally touch. Maybe there’s unusual authentication activity, suspicious reconnaissance, or access patterns inconsistent with that user’s normal behavior.
Those individual signals can then be combined with other security information to provide more context around the potential threat.
How Does Defender for Identity Work with Microsoft Defender XDR?
Brad: One of the strengths of Defender for Identity is that it doesn’t have to operate as an isolated security product.
Identity alerts can be correlated with additional signals from the Microsoft Defender environment, helping security teams understand the broader attack story.
For example, an incident might involve a suspicious email, an affected endpoint, unusual authentication activity, and later movement into other resources.
Bringing those signals together can make it easier to understand whether you’re looking at separate events or different stages of the same cybersecurity incident.
How Does Defender for Identity Support Zero Trust Security?
Brad: Defender for Identity also supports a Zero Trust security strategy.
Zero Trust is based on the idea that access shouldn’t automatically be trusted simply because a user or device is already inside the network.
Identity, device state, behavior, permissions, risk, and other signals can all be considered when deciding whether activity should be trusted.
The core mindset is: never trust, always verify.
By continuously monitoring identity-related activity, organizations can become better equipped to identify situations where an authenticated account may no longer represent a trustworthy user.
What Are the Business Benefits of Defender for Identity?
Brad: One of the biggest benefits is faster detection and incident response.
When suspicious identity activity is identified quickly, the security team has an opportunity to investigate and contain the threat before the attacker has additional time to move throughout the environment.
Another benefit is improved security visibility.
Instead of relying solely on manual Active Directory log review, security administrators can work from incidents, alerts, identity profiles, timelines, and other correlated information.
The resulting security information can also support compliance and audit activities by giving organizations stronger evidence around how identity activity is monitored and investigated.
How Does Defender for Identity Help Investigate a Compromised User?
Brad: Let’s look at an example.
Imagine a user receives a malicious message and their account becomes involved in suspicious activity.
In the Microsoft Defender portal, the security team can review the incident timeline and see alerts associated with the user, their identity, affected devices, and other related security signals.
Instead of treating each alert as an unrelated event, the investigation can begin to tell the story of what happened.
Maybe the user encountered a malicious attachment. Then their account performed suspicious authentication activity. Then the identity began querying information or attempting to access additional resources.
That timeline can help security teams understand the sequence of events and determine how far the attacker may have progressed.
What Should You Do When an Identity Is Compromised?
Tom: Containment comes first.
If an account is believed to be compromised, one of the first actions may be restricting or disabling the identity to stop additional authentication activity.
Depending on the incident and the tools involved, incident response can also include revoking sessions or credentials, resetting passwords, investigating affected endpoints, and reviewing recent account activity.
Then use the incident timeline and audit information to determine what happened before the account was contained.
Which resources were accessed? Were files opened or modified? Were emails sent? Did the attacker attempt to move to another account or system? Did they elevate privileges?
The answers determine the next phase of response and whether additional systems, employees, customers, or third parties need to be involved.
Can Defender for Identity Automate Threat Response?
Microsoft Defender technologies can support automated investigation and response workflows, allowing organizations to accelerate containment and remediation when suspicious activity is confirmed.
The appropriate automation depends on the organization’s security policies, licensing, environment, and tolerance for automated response.
Some organizations may prefer highly automated containment, while others may require human approval before disabling an account or taking another consequential action.
How Do You Deploy Microsoft Defender for Identity?
Brad: Organizations should start by assessing their identity environment.
Identify the domain controllers and other supported identity infrastructure that need coverage, review Microsoft’s prerequisites, and then deploy the appropriate Defender for Identity sensors.
After deployment, validate signal quality, auditing, identity visibility, security recommendations, alerts, and integration with your broader Microsoft security environment.
The important thing is to build appropriate coverage across the identity infrastructure rather than assuming one monitored server represents the entire Active Directory environment.
What Microsoft Licensing Includes Defender for Identity?
Microsoft Defender for Identity is available through eligible Microsoft security and enterprise licensing offerings.
Because Microsoft’s licensing packages change over time, organizations should verify their current Microsoft 365, Enterprise Mobility + Security, frontline, or standalone security entitlements before deployment.
If you’re already investing in Microsoft security licensing, it’s worth checking whether Defender for Identity is a capability you already own but haven’t fully deployed.
Microsoft Defender for Identity: Webinar Q&A
What Happens After Defender for Identity Detects a Compromised User?
Tom: First, contain the account and stop potentially malicious authentication activity.
Then review the security timeline to determine what the user or attacker did before containment.
Depending on the findings, the response may include password resets, session revocation, additional endpoint investigation, access reviews, malware investigation, and examination of any resources the account accessed.
You should also communicate with the employee so they understand what happened and can provide additional context about suspicious emails, links, downloads, login prompts, or other activity.
Finally, use the incident as an opportunity to identify whether additional security controls or employee cybersecurity training could reduce the likelihood of recurrence.
Does Security Awareness Training Still Matter When You Have Defender for Identity?
Absolutely.
Defender for Identity can help detect identity threats, but technology doesn’t eliminate the human side of cybersecurity.
Employees still need training around phishing, suspicious authentication prompts, passwords, multifactor authentication, social engineering, and how to report unusual activity.
Technology helps detect and contain attacks. Training helps employees avoid creating the opportunity in the first place.
How Is Defender for Identity Different from Basic Active Directory Logging?
Tom: Traditional Active Directory can generate a significant amount of security and authentication logging.
The problem is scale.
Those logs can become enormous, and manually reviewing them for subtle attack patterns isn’t realistic for most organizations.
Defender for Identity adds cloud-based analysis, behavioral context, identity intelligence, threat detections, and correlation with other Microsoft security signals.
Instead of asking an administrator to manually recognize suspicious patterns across thousands or millions of individual events, the security platform can help identify activity that rises to the level of an alert or incident.
How Is Defender for Identity Different from a SIEM?
A SIEM and Defender for Identity can complement one another, but they serve different functions.
A SIEM such as Microsoft Sentinel collects, correlates, searches, and analyzes security information from many systems across the organization.
Defender for Identity is purpose-built around identities and identity infrastructure, providing identity-specific detections, context, posture information, and attack insights.
Together with Microsoft Defender XDR and Microsoft Sentinel, organizations can combine deeper identity visibility with endpoint, email, cloud, network, and broader security telemetry.
Why Is Defender for Identity Especially Relevant to Manufacturers?
Many manufacturers operate hybrid technology environments.
Microsoft 365 and other applications may be in the cloud while ERP systems, CAD applications, file servers, manufacturing systems, and other resources still rely on Active Directory.
That means moving toward cloud services doesn’t automatically eliminate the need to protect traditional identity infrastructure.
Defender for Identity can help close that visibility gap by monitoring supported identity infrastructure while integrating those signals into the organization’s broader Microsoft security environment.
Final Takeaway: Identity Is a Critical Cybersecurity Layer
An attacker who compromises an identity may not need to attack every system individually.
The identity itself can become the pathway to additional applications, servers, data, and privileges.
That’s why organizations need more than passwords and traditional authentication logs.
A modern identity security strategy should combine strong authentication, least-privilege access, secure configuration, identity monitoring, behavioral detection, incident response, and employee cybersecurity awareness.
For organizations that still rely on Active Directory, Microsoft Defender for Identity can provide an additional layer of visibility into identity-based cyber threats while connecting those signals to the broader Microsoft security ecosystem.
Moderator: Thanks, everybody, for joining us today.