Agentless User ID - Server Log Monitor Frequency

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Agentless User ID - Server Log Monitor Frequency

L2 Linker

After configuring Agentless User ID, the default value for Server Log Monitor Frequency of 2 seconds caused CPU usage on the Domain Controller to be higher than desired.  Changing this value to 10 seconds brought CPU usage on the Domain Controller to an acceptable level.  What are the ramifications of having this longer Server Log Monitor Frequency?

1 accepted solution

Accepted Solutions

Cyber Elite
Cyber Elite

The longer the time between log reads, the longer a user may potentially be blocked from accessing resources

 

If a user logs on to his device the second after a log read ocurred, UserID will not be aware of this account for another 9 seconds. Any security policy requiring a UserID will not be available for the next 9 seconds. For the average user activity this will probably not have big consequences, as a user tends to boot up and launch 'slower' applications first. Any startup scripts launched at startup may be blocked by policyhowever as they trigger the moment a user is logged in

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

View solution in original post

3 REPLIES 3

L2 Linker

In our testing the user-ID agent running on windows box will reduce CPU usage .

We sow only 3% increase using user-ID agent .

 

Also see this refferece; here   (Page 13) . 

 

 

Cyber Elite
Cyber Elite

The longer the time between log reads, the longer a user may potentially be blocked from accessing resources

 

If a user logs on to his device the second after a log read ocurred, UserID will not be aware of this account for another 9 seconds. Any security policy requiring a UserID will not be available for the next 9 seconds. For the average user activity this will probably not have big consequences, as a user tends to boot up and launch 'slower' applications first. Any startup scripts launched at startup may be blocked by policyhowever as they trigger the moment a user is logged in

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

Thanks reaper.  I suspected that was the case but wanted someone to verify that I wasn't crazy.

  • 1 accepted solution
  • 3884 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!