ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. It has a robust event-based programming language which provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring, logging and real-time analysis.
IIS threads sleeps from time to time, waking up once a request is received. Once started, the thread loads ModSecurity and consequently print these message on the event logs once more, flooding the event logs.
Those events should be treated in a clever way, not changing the default behavior of ModSecurity (which is platform independent) but also not flooding the event log.
I would also consider adding a single event when ModSecurity for IIS is actually enabled in config. I would log the config file (with full path) used for ModSecurity in this event.
It seems like ModSecurity for IIS is logging its startup messages way too much, flooding the logs with messages similar to the one bellow:
IIS threads sleeps from time to time, waking up once a request is received. Once started, the thread loads ModSecurity and consequently print these message on the event logs once more, flooding the event logs.
Those events should be treated in a clever way, not changing the default behavior of ModSecurity (which is platform independent) but also not flooding the event log.