Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

HOWTO: How do I adjust the lag time for retrieving log files via OPSEC LEA?

Expand / Collapse


This article applies to:

  • Security Reporting Center 2.0c
  • Security Reporting Center 2.1

Question:

How do I adjust the lag time for retrieving log files via OPSEC LEA?

Procedure:

There are two configurable options for the LEA service that control the lag time when retrieving log files via OPSEC LEA.

The first value you can modify is the lag time from when the initial connection is created to when the application starts to retrieve log data.  The default value for this option is 50 minutes.  To modify this setting, please follow the instructions below:

  1. Stop the NetiQ – Lea Service.
  2. Open the lea_service.ini file located in the following directory:

    .\modules\leaservice

  3. Find the following line within the file: 

    LagWindowSec=

  4. At the end of the line add the amount of seconds you would like to wait before the LEA log data is collected.  For example:

    LagWindowSec=3000

    1. Minimum value is 30 seconds.
    2. Maximum value is 86400 seconds.

  5. Save and close the file.

  6. Start the NetiQ – Lea Service.


The second value you can modify is the lag time between LEA sessions that update the log file with any new information.  The default value for this option is 5 minutes.  If you would like to modify this setting, please follow the instructions below:

  1. Stop the NetiQ – Lea Service.

  2. Open the lea_service.ini file located in the following directory:

    .\modules\leaservice

  3. Find the following line:

    SessionSuspendTimeSec=

  4. At the end of the line add the amount of seconds you would like to wait before the new lea log data is collected.  For example: 

    SessionSuspendTimeSec=300

    1. Minimum value is 30 seconds.
    2. Maximum value is 86400 seconds.

  5. Save and close the file.

  6. Start the NetiQ – Lea Service.

Notes:

Marshal does NOT recommend changing the LagWindowSec value to anything lower than 50 minutes (3000 seconds) as this setting was implemented to prevent records for recently opened connections from being downloaded. Check Point records do not contain bandwidth statistics for individual connections until the connections are closed, so the higher this value is set, the more likely the bandwidth statistics will be complete for each connection.

For more information on how the OPSEC LEA service works please see the following knowledge base article:

:10552 How does OPSEC LEA work?

This article was previously published as:
NETIQKB37513

To contact LevelBlue about this article or to request support:


Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.