To collect log information from a stand alone Windows (Vista in this case) workstation, download and install the Splunk Universal Forwarder
splunk-4.3-115073-x86-release.msi
Follow the install configuration and select the WindowsEventLog : Security and whatever performance monitoring is required. Enter the IP address of the Splunk indexer/search head and the host IP address as directed. If the default port (9997) was selected ensure that the indexer firewall is set to allow connections from the forwarder on this port.
In addition to the standard windows event logs:
- Application log (tracks events that occur in a registered application)
- Security log (tracks security changes and possible breaches in security)
- System log (tracks system events)
[default]
host = acer-expire
[script://$SPLUNK_HOME\bin\scripts\splunk-perfmon.path]
disabled = 0
[monitor://$WINDIR\WindowsUpdate.log]
sourcetype = WindowsUpdateLog
disabled = 0
[monitor:C:\Windows\System32\LogFiles\Firewall\pfirewall.log]
sourcetype = WindowsFirewallLog
disabled = 0
Note enable windows firewall logging as follows:
- Click Start, All Programs, and search for Administrative Tools.
- Select Windows Firewall with Advanced Security.
- Right click Windows Firewall with advanced security on local computer.
- Select Properties and Profile tabs. customise logging.
- Select log dropped packets and log successful connections.
- Click OK.
Start Windows Task Manager and restart SplunkForwarder service.
NB The Splunk Universal Forwarder for windows must run as local admin, in order to forward the above logs. Linux/Solaris forwarders do not need to and should not run as root, but log group permissions may need to change to forward some logs.
NB The Splunk Universal Forwarder for windows must run as local admin, in order to forward the above logs. Linux/Solaris forwarders do not need to and should not run as root, but log group permissions may need to change to forward some logs.
Comments