Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

About the Device

Domain Name System (DNS) is the name resolution protocol for TCP/IP networks, such as the Internet. Domain Name System (DNS) is a system for naming computers and network services that is organized into a hierarchy of domains.

Device Information

Entity

Particulars

Vendor Name

Microsoft

Product Name

Windows DNS 

Type of Device

Hosted 

Collection Method

 Log Type

Ingestion label

Preferred Logging Protocol - Format

Log collection method

 Windows DNS

WINDOWS_DNS

 Syslog

 CyberHub

Port Requirements

Source

Destination

Port

Microsoft Windows DNS

CyberHub

10014 (TLS)

To facilitate secure communication and align with our best practice, we strongly encourage the use of Transport Layer Security (TLS) between your security devices and our Adaptive MxDR platform for event forwarding.

While we understand that TLS support may not be available on all devices, if your devices do support TLS communication, we recommend utilizing port 10014 for seamless integration.

In some cases, the upgraded version of the device might incorporate TLS support without prior notice. If you come across such a scenario or for further assistance in configuring TLS, we kindly ask you to reach out to your dedicated Adaptive MxDR Service Delivery Lead.

Device Configuration

Chronicle supports the Regional [English United States] M/d/yyyy h:mm:ss date format which is recommended format by Windows. This change won't impact on the device timezone , it is just a date format change. So, make sure device date format is set to [English United States] M/d/yyyy h:mm:ss before configuring device for log collection.

Enable DNS Logging: From Microsoft Server 2012 & 2012 R2:

  1. Click StartAdministrative ToolsDNS

  2. Right click on DNS server and select properties.

image-20240321-071454.png
  1. Click Debug Logging.

    image-20240321-071644.png
  2. Select Log Packets for debugging.

  3. In the Log file, type the file path and name, and the Maximum size.

  4. Click Apply and OK.

Log Forwarding:

To configure Windows NxLog Agent for TLS TCP Log flow on port 10014:

  1. Download and Install NxLog agent from location NxLog Agent.

  2. Go to services.msc and stop the nxlog service.

  3. For TLS, need to create certificate file for communication. On CyberHub ,Go to support user mode and choose option 11 to view Certificate to export for FTPS and TCP.

  4. Copy paste the certificate to new file and save this file into DNS server at desired location.

  5. Go to folder "C:\Program Files (x86)\nxlog\data" and delete "configcache.dat".

  6. For Windows Agent , go to installed location “C:\Program Files (x86)\nxlog\conf” and rename the attached nxlog_windows.conf(TLS) to "nxlog.conf" and copy into this folder.

  7. Replace “LCP_IP_Address” with “CyberHub IP address” in nxlog.conf.

  8. DNS Log location (access.log) needs to be mentioned on line 31 against "File".

  9. Add CAFile location at position 44

  10. Now start the nxlog service from services.msc.

  11. NxLog agent logs will be available at location "C:\Program Files (x86)\nxlog\data\nxlog.log".

Integration Parameters

Parameters required from customer for Integration.

Property

Default Value

Description

IP Address

Microsoft Windows DNS interface IP address

Hostname or IP address of the device which forwards logs to the CyberHub.

  • No labels