top of page

Proof of Concept Steps 01

  • Writer: Pavan Raja
    Pavan Raja
  • Apr 9, 2025
  • 2 min read

Summary:

This document is a "Tip & Trick" guide for exporting and importing events in a Proof of Concept (POC) related to Event Management System (ESM) and Logger. Emrah Alpa, the author or user here, needed to retrieve information about Windows account creations, including who created the account, what account was created, and when these actions occurred. To solve this challenge: 1. Utilize Logger's fast search capabilities to identify events categorized as "Authentication / Add." 2. Use an Active Channel in ESM to filter events within a specified time range. 3. Export filtered events as CSV files from the Console. 4. Convert these CSV files into an .events file using the "csvconvert" syntax. 5. Install a test replay Connector on a laptop and register it with the ESM environment. 6. Adjust agent properties to preserve event timestamps during the replay process. 7. Replay the events, maintaining original timestamps, to retrieve desired information without showing blank reports. This method involves several steps: identifying relevant events using Logger, exporting as CSV files, converting into an .events file for import, and replaying through a test Connector in ESM. The guide provides practical steps on managing event data collection and retrieval within a POC framework.

Details:

The document is a "Tip & Trick" guide for exporting and importing events in a Proof of Concept (POC) related to ESM (Event Management System) and Logger. Emrah Alpa, presumably the author or user mentioned here, faced an issue where they needed to retrieve specific information about Windows account creations, including who created the account, what account was created, and when these actions occurred. To address this challenge, Alpa utilized the fast search capabilities of Logger to identify events categorized as "Authentication / Add." They then used an Active Channel in ESM to filter events within a specified time range. The events were exported from the Console as CSV files, which were subsequently converted into an .events file using the "csvconvert" syntax. Next, Alpa installed a test replay Connector on their laptop and registered it with their ESM environment. They adjusted agent properties to ensure event timestamps were preserved during the replay process. The events were successfully replayed, maintaining original timestamps, which allowed Emrah to retrieve the desired information without showing blank reports. This method involved several steps: identifying relevant events using Logger, exporting filtered events as CSV files, converting these into an .events file for import, and finally replaying the events through a test Connector in ESM. The document serves as a practical guide on how to efficiently manage event data collection and retrieval within a POC framework.

Disclaimer:
The content in this post is for informational and educational purposes only. It may reference technologies, configurations, or products that are outdated or no longer supported. If there are any comments or feedback, kindly leave a message and will be responded.

Recent Posts

See All
Zeus Bot Use Case

Summary: "Zeus Bot Version 5.0" is a document detailing ArcSight's enhancements to its Zeus botnet detection capabilities within the...

 
 
 
Windows Unified Connector

Summary: The document "iServe_Demo_System_Usage_for_HP_ESP_Canada_Solution_Architects_v1.1" outlines specific deployment guidelines for...

 
 
 

Comments


@2021 Copyrights reserved.

bottom of page