DETECTION OVERVIEW
Risk Factors
LLMNR is an older and vulnerable protocol that is typically disabled, so the likelihood of an attack is low. However, if an attacker impersonates a proxy or harvests user credentials, they can ultimately gain privileged information or unauthorized access to assets on your network.
The system might change the risk score for this detection.
Category

When a DNS request for a hostname cannot be resolved or no DNS server is available (1), some clients will broadcast a query to all local devices over LLMNR (2). If an attacker is listening, they can respond and impersonate the requested host (3). If the host is an authenticated resource, that client might send user credentials to the attacker.
Quarantine the attacking and victim devices if they are compromised
If LLMNR is not required for your Windows environment, disable LLMNR in local security settings or by group policy
Ensure secure password policies are applied to your network devices to offset potential damage in the aftermath of an attack
Network analysis and visibility solutions remain underrepresented in enterprises. Find out why in this preview of a new Wave report.
ExtraHop® Named a Leader in First-Ever Gartner® Magic Quadrant™ for Network Detection and Response
Visit this resource for more information.
This analysis exposes the critical link between an organization's lack of internal visibility and the escalating cost of compromise, demanding an urgent re-evaluation of how core business assets are protected.
Learn why you need to be wary of the claims certain network detection and response providers make about their coverage against the MITRE ATT&CK framework.
Learn how NDR from RevealX helps security teams detect and investigate more adversary TTPs in the MITRE ATT&CK framework than rule-based tools.
