https://community.splunk.com/t5/Getting-Data-In/Too-many-Events-generated-for-Windows-Security-EventCode-4662/m-p/155262#M31539 <P>The splunk service user seems to be reading the Active Directory's "Deleted Object Container" as frequent as 60 times per second. </P> <P>Every time this container is accessed, it generates Windows Security audit logs; thus increasing the volume and frequency of Windows Security logs that the Universal Forwarder has to forward for indexing. We suspect this is the cause of the issue to spiral. Also, because of the increased log volume, the Security logs now rolls every 5 hours, instead of a few also we see high resource utaliation due to </P> Tue, 09 Dec 2014 23:53:48 GMT sat94541 2014-12-09T23:53:48Z https://community.splunk.com/t5/Getting-Data-In/Too-many-Events-generated-for-Windows-Security-EventCode-4662/m-p/155262#M31539 <P>The splunk service user seems to be reading the Active Directory's "Deleted Object Container" as frequent as 60 times per second. </P> <P>Every time this container is accessed, it generates Windows Security audit logs; thus increasing the volume and frequency of Windows Security logs that the Universal Forwarder has to forward for indexing. We suspect this is the cause of the issue to spiral. Also, because of the increased log volume, the Security logs now rolls every 5 hours, instead of a few also we see high resource utaliation due to </P> Tue, 09 Dec 2014 23:53:48 GMT https://community.splunk.com/t5/Getting-Data-In/Too-many-Events-generated-for-Windows-Security-EventCode-4662/m-p/155262#M31539 sat94541 2014-12-09T23:53:48Z https://community.splunk.com/t5/Getting-Data-In/Too-many-Events-generated-for-Windows-Security-EventCode-4662/m-p/155263#M31540 <OL> <LI>At some point, unknown root cause, the service account that the SplunkForwarder runs under began accessing the Directory Service object: CN=Deleted Objects,DC=DomainDnsZones,DC=global,DC=scj,DC=loc <OL> <LI>This object does not exist.</LI> <LI>DS Access auditing was enabled on the domain controllers.</LI> <LI>This caused the object access to record a 4662 event in the event log.</LI> <LI>The service account was reading this object dozens of times per second according to the event log.</LI> <LI>The security event log on the DC was configured to roll over at 4GB size which at its shortest only held 5.5 hours of data in the 4GB of size.</LI> <LI>Hence, the events in Splunk were no newer than 5.5 hours because the security log was filling faster than the forwarder could send and index the events.</LI> <LI>Since Splunk instance is set to dump event 4662 to a null queue so it was not indexed.</LI> <LI>DS Access object auditing was disabled and event 4662 stopped being logged.</LI> <LI>Within 12 hours the forwarder caught up to the event log.</LI> <LI>DS Access object auditing was enabled again. NO 4662 events are occurring. Somewhere along the way the forwarder decided to stop attempting to access that object.</LI> </OL></LI> </OL> Tue, 09 Dec 2014 23:56:15 GMT https://community.splunk.com/t5/Getting-Data-In/Too-many-Events-generated-for-Windows-Security-EventCode-4662/m-p/155263#M31540 rbal_splunk 2014-12-09T23:56:15Z