Now that you have your Elasticsearch Stack setup on multiple servers or a single server it’s time to start sending some data over.
- Winlogbeat – Download here (64-bit)
- Windows hosts – Your system in which we will be collecting the logs from.
Step 1: Download and extract winlogbeat.zip to c:\program files\ (Should look like the image below)
Step 2: Open the winlogbeat.yml and edit with notepad:
We will add the following under winlogbeat.event_logs:
- name: Security
- name: Application
- name: "Microsoft-Windows-TaskScheduler/Operational"
- name: System
- name: "Microsoft-Windows-Application-Experience/Program-Inventory"
- name: "Microsoft-Windows-Sysmon/Operational"
- name: "Microsoft-Windows-TerminalServices-RDPClient/Operational,Microsoft-Windows-TerminalServices-LocalSessionManager/Admin,Microsoft-Windows-TerminalServices-LocalSessionManager/Operational"
- name: "Microsoft-Windows-Windows Firewall With Advanced Security/ConnectionSecurity,Microsoft-Windows-Windows Firewall With Advanced Security/ConnectionSecurityVerbose,Microsoft-Windows-Windows Firewall With Advanced Security/Firewall,Microsoft-Windows-Windows Firewall With Advanced Security/FirewallVerbose,Microsoft-Windows-Windows Firewall With Advanced Security/Network Isolation Operational"
- name: "Microsoft-Windows-WindowsUpdateClient/Operational"
(Note: I’m monitoring various aspects of the windows host including Sysmon which we will install later, at the end of this article you may see a table with a list of Event ID’s along with a description of what they are).
Next, scroll down until you get to output.logstash: here you will add your logstash server information
# The Logstash hosts
Save the winlogbeat.yml and exit.
Step 3: Install Winlogbeat as a service
Launch Powershell (Run as Administrator) – and enter the following:
cd "C:\Program Files\Winlogbeat"
powershell.exe -ExecutionPolicy UnRestricted -File .\install-service-winlogbeat.ps1
Verify that the service is running.
Done! Next tutorial will focus on Kibana so you may start visualizing the data.
Below is a list of Event IDs along with a description. I have a longer list saved; however, these are the ones I believe should be monitored.
|4756||A member was added to a security-enabled universal group||Security|
|4740||A User account was Locked out||Security|
|4735||A security-enabled local group was changed||Security|
|4732||A member was added to a security-enabled local group||Security|
|4728||A member was added to a security-enabled global group||Security|
|4724||An attempt was made to reset an accounts password||Security|
|4648||A logon was attempted using explicit credentials||Security|
|4625||An account failed to log on||Security|
|1102||The Audit Log was cleared||System|
|4624||An accout was successfully logged on||Security|
|4634||An account was logged off||Security|
|5038||Detected an invalid image hash of a file||Security|
|6281||Detected an invalid page hash of an image file||Security|
|1002||Application Hang- Crash||Application|
|1001||Application Error – Fault Bucket||Application|
|104||Event Log Cleared||System|
|1102||The Audit Log was cleared||System|
|4719||System Audit Policy was changed||System|
|6005||Event log Service Stopped||System|
|7022-7026,7031,7032,7034||Windows Services Fails or crashes||System|
|7045||A service was installed in the system||System|
|4697||A service was installed in the system||System|
|104||Event log was cleared||System|
|6||New Kernel Filter Driver||System|
|2005||A Rule has been modified in the WindowS firewall Exception List||Firewall||Microsoft-Windows-Windows Firewall With Advanced Security/Firewall|
|2004||Firewall Rule Add|
|2006, 2033||Firewall Rules Deleted|
|23||Session Logoff Scceeded||TerminalServices-LocalSessionManager||Microsoft-Windows-TerminalServices-LocalSessionManager/Operational|
|24||Session has been disconnected||TerminalServices-LocalSessionManager||Microsoft-Windows-TerminalServices-LocalSessionManager/Operational|
|25||Session Reconnection Succeded||TerminalServices-LocalSessionManager|
|1102||Client has initiated a multi-transport connection||TerminalServices-ClientActiveXCor||Microsoft-Windows-TerminalServices-RDPClient/Operational|
Update 8-10-2017: Microsoft has an article pertaining their suggested Events to monitor which is very useful, it can be accessed here