Diving Deeper Into Windows Event logs for Security Operation Center (SOC) – Guide

Cyber Security operations center is protecting organizations and the sensitive business data of customers.

It ensures active monitoring of valuable assets of the business with visibility, alerting and investigating threats, and a holistic approach to managing risk.

Analytics service can be an in-house or managed security service. Collecting event logs and analyzing logs with real-world attacks is the heart of the security operation center.

Events – The security operations center

Events are generated by systems that are error codes, devices generate events with success or failure to their normal function.

so event logging plays an important role to detect threats. In the organization, there are multiple numbers and flavors of  Windows, Linux, firewalls, IDS, IPS, Proxy, Netflow, ODBC, AWS, Vmware, etc.

These devices usually track attackers’ footprints as logs and forward them to SIEM tools for analysis. In this article, will see how events are pushed to the log collector. To know more about Windows events or event ids .

Log Collector

It’s a centralized server to receive logs from any device. Here I have deployed Snare Agent on Windows 10 machine.

So we will collect Windows event logs and Detect attacks on Windows 10 machines attacks using Snare Agent.

The snare is SIEM(SECURITY INCIDENT AND EVENT MANAGEMENT) Solution for log collector and event analyzer in various operating systems Windows, Linux, OSX Apple, and supports database agent MSSQL events generated by Microsoft SQL Server. It supports both Enterprise and Opensource Agents.

Snare Installation

• For Demo purposes, I have been using no credentials but it is always recommended to use strong passwords to protect logs without a leak.

Snare Web interface:-

• By default, the snare will run at Port 6161.

• A random port can also be chosen with TCP or UDP or TLS/SSL Protocols.
• Snare will ask for credentials to log in. Here I have given no authentication.
• The below figure shows the snare agent install success and provides additional details on screen.

Network & File Destination Configuration

• Our Windows 10 is started sending event logs to the Snare console.
• The snare console is running at localhost and collecting logs from a Windows machine.

NOTE: Logs can be sent to a centralized server, and then the centralized server pushes logs to the SIEM (this method reduces the load in the SIEM), or snare logs can be sent directly to the SIEM (if your SIEM is capable of good storage for long—and short-term log retention, this method can be deployed). It is recommended to configure your SIEM with port details of the snare, and the test connection should be the successor to collect logs.

• So you can change the network destination IP to SIEM IP or LOG COLLECTOR IP.

• The above figure shows destination is configured with localhost to collect and store event logs in various formats SNARE, SYSLOG, CEF (Common Event Format), or LEEF (Log Event Extended Format)
• By default, it will be collecting logs and saving files with snare format & logs are forwarded to SIEM.

Access Configuration

• Web server port, authentication for console access, and Web server Protocol can be easily defined according to your environment.

• The above figure shows a configuration with Web server port 6161, Snare agent port 6262, and HTTP as web server protocol for demo purposes, It is recommended to install a certificate for secure connection to forward logs.

Objective Configuration

• The objective includes events with different categories which can be Windows Log on/Log off, access to file or directory, security policy change, system restart, and shutdown.
• Modify or delete specific events to assign a priority(Critical, High, Low & Information)

Audit Service Statistics

• Audit Service ensures snare is connected and sends logs to SIEM.
• It shows daily average bytes of events transmitted to SIEM.

• In case of network failures, Soc Administrator can check the status of the service.

Security Certification – The security operations center

• To make connection encrypted and generate a self-signed certificate to WEB-UI, snare agent, and network destination certificate validation to establish a secure way of forwarding logs to SIEM.

Restart-Service

• If SIEM is not collecting Event logs from the Snare agent for a while, then it’s time to troubleshoot and retrieve logs from the Snare server.

• The above figure shows Snare services are restarted successfully.

Events – The security operations center

• Windows 10 is forwarding event logs to your deployed SIEM or events can be viewed in the snare console.
• Every time you cannot open and lookup for intrusions to your environment with snare, for this reason, we are forwarding logs to SIEM for Intelligence to detect attacks.
• SIEM will be Intelligent to trap attackers by building an effective correlation rule.

• Above pictures with Event Ids 4625 which is failed password attempt to Windows 10 machine followed by Successful 4689 Event.
• List of Windows Event Ids Here

Correlation Rule & Incidents

• It’s an engine designed to write a defensive rule to detect offensive guys, Each rule will be a unique incident.
• Example: Assume that you’re writing a rule for a brute-force attempt, Brute-force attempts will have continuous threads with a different passphrase to the server.
• As per NOTE: failed attempts followed by a successful login.

Correlation Rule : failed password attempts + Followed by successful Login = Brute-force (Incident)

Now your customer environment is ready for a Known use case(Brute-force detected), you can also build or write your own use case and deploy it in your SIEM to detect sophisticated cyber-attacks !!!