-
-
-
-
DNS Query Monitoring
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
DNS Query Monitoring
uberAgent ESA monitors outgoing DNS queries and their responses. This includes all DNS queries that are processed by the operating system.
Functionality
The implementation and functionality of DNS query monitoring differ between operating systems.
Windows
uberAgent uses the local DNS machine’s DNS resolver as the data source. uberAgent sees all DNS requests that are handled by the OS, including requests via encrypted DNS (DoT or DoH). uberAgent doesn’t see requests that bypass the OS resolver, e.g., requests from tools such as nslookup.
uberAgent cannot differentiate between requests that go over the wire and requests that can be answered from the local DNS cache. Both types of requests are collected by uberAgent.
macOS
uberAgent monitors network traffic at the packet level. uberAgent sees any and all DNS requests, but it cannot process encrypted DNS (DoT or DoH). uberAgent only collects requests that go over the wire, it doesn’t process requests that can be answered from the local DNS cache.
Configuration
uberAgent ESA DNS query monitoring is enabled or disabled through the timer metric DnsMonitoring. For Windows clients, this feature requires Windows 8.1 or newer versions of Windows since the data source for this event is not available in previous Windows versions, such as Windows 7. Enabling the metric on unsupported Windows versions has no effect. For macOS, all versions are supported.
Metadata
Sourcetype
DNS query monitoring events are sent with the sourcetype uberAgentESA:Process:DnsQuery (documentation). This feature may significantly increase the data volume and can be limited using event data filtering. uberAgent’s configuration includes a comprehensive set of rules to exclude known and harmless DNS requests.
Threat Detection
DNS monitoring events are also available via uberAgent’s Threat Detection engine. This allows the creation of rules to report specific DNS events (e.g., malicious events or threat detection).
Visualization
DNS query monitoring events are visualized in the DNS Exfiltration and Tunneling dashboard, which is part of the uberAgent_ESA Splunk searchhead app.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.