Device | Details |
---|---|
Vendor | Wing FTP Software |
Device Type | FTP Server |
Connection Type | Syslog |
Data Source Name | wing-ftp-server |
Data Source ID | 1887 |
You can choose to enable Admin Log, Server Log, Domain Log, or all three logs.
Click OK to save your changes.
If not done already, download nxlog.conf, and then place it in the conf
directory of your NXLog installation. Depending on which version you use, the directory can be C:\Program Files (x86)\nxlog\conf for the 32-bit version or C:\Program Files\nxlog\conf for the 64-bit version.
Note: This step overwrites the default nxlog.conf
file. You may want to back up the original copy before placing the one provided by AT&T Cybersecurity.
nxlog.conf
file in a text editor.
Update the root path of your NXLog installation.
Locate the following lines:
#define ROOT C:\Program Files\nxlog #define ROOT C:\Program Files (x86)\nxlog
Enter the Sheriff CSM Sensor (Deputy) IP address.
Locate the following line:
define OUTPUT_DESTINATION_ADDRESS <Sheriff-CSM-Sensor-IP>
<Sheriff-CSM-Sensor-IP>
with the IP address of the Sheriff CSM All-in-One or Sheriff CSM Sensor that will receive the Windows events.
Uncomment the section between WINGFTP-NXLOG
and /WINGFTP-NXLOG.
Important: Only remove the first # symbol in each line when uncommenting the sections. The remaining # symbol indicates that the line is either a comment or optional.
You need to enable all three sections, <Input in_wingftp_admin>
, <Input in_wingftp_server>
, and <Input in_wingftp_domain>
, even if you do not collect all three logs.
In the following line, replace <EDIT THIS WITH YOUR DOMAIN NAME!>
with the domain name defined in your Wing FTP Server:
define WING_DOMAIN <EDIT THIS WITH YOUR DOMAIN NAME!>
For example, if your domain is called "my-FTP-domain", this line should look like:
define WING_DOMAIN my-FTP-domain
Save the file.