Re: [Prelude Hybrid IDS] #216: mod_security cleanup, and compatibility with version 2.0

"Prelude Hybrid IDS" <[email protected]> Tue, 12 Aug 2008 10:53:03 -0000
Newsgroups gmane.comp.security.ids.prelude.devel
Message-ID <[email protected]>
#216: mod_security cleanup, and compatibility with version 2.0
-------------------------+--------------------------------------------------
 Reporter:  gegomez      |        Owner:  Peter Vrabec <[email protected]>
     Type:  defect       |       Status:  assigned                         
 Priority:  normal       |    Milestone:  Prelude-LML 0.9.13               
Component:  prelude-lml  |      Version:  0.9                              
 Severity:  normal       |   Resolution:                                   
 Keywords:               |  
-------------------------+--------------------------------------------------

Comment(by yoann):

 Replying to [comment:13 dkopecek@…]:
 > Replying to [comment:12 yoann]:
 > > Replying to [comment:11 [email protected]]:
 > > > Replying to [comment:10 yoann]:
 > > > > Replying to [comment:7 [email protected]]:
 > > > > This is used for regression testing and reviewing generated
 alerts:
 > > > > {{{
 > > > >   cd prelude-lml/tests
 > > > >   ./loggrep.py ../plugins/pcre/ruleset/<name of your
 ruleset>.rules | ../src/prelude-lml --dry-run --metadata=nowrite,head
 --batch-mode --no-resolve --pcre --dump-unmatched --config ./prelude-
 lml.conf --text-output
 > > > > }}}
 >
 >  I get this warning if I run your test: "WARNING: No alert emited for
 log entry" (for all LOG: entries). But I'm sure that this ruleset
 generates alerts, because I tested it in "normal" mode and it worked for
 each LOG: entry. So, what can be wrong?

 After looking at the issue, it only happen when the mod_security ruleset
 is used along with others ruleset: the problem is that the ModSecurity
 rules ID conflict with other ruleset ID. If running the mod_security
 ruleset by itself:

 {{{
 12 Aug 12:49:07 (process:30577) WARNING: 7 line processed in 0.02 seconds
 (358.42 EPS), 7 alert emited.
 }}}

 So the mod_security rules ID need to be given an unique range (You can use
 the old assigned range: 31XX).

-- 
Ticket URL: <https://trac.prelude-ids.org/ticket/216#comment:14>
Prelude Hybrid IDS <http://www.prelude-ids.org>
The Prelude Hybrid Intrusion Detection System suite
_______________________________________________
Prelude-devel site list
[email protected]
http://lists.prelude-ids.org/mailman/listinfo/prelude-devel