I will add it to my todo list to update the rule ID documentation file. I
think this makes lots of sense :)

On 3/6/16, 2:27 PM,
"owasp-modsecurity-core-rule-set-boun...@lists.owasp.org on behalf of Noël
Zindel" <owasp-modsecurity-core-rule-set-boun...@lists.owasp.org on behalf
of m...@noelzindel.org> wrote:

>Hi Franziska,
>
>thanks for bringing this up. I absolutely agree with you, and the others.
>
>Since there has been no opposition so far, I will implement the ID
>assignment into our wiki documentation tomorrow.
>If there should come up any argumentation against it, it¹s a quick change.
>
>Cheers,
>Noël
>
>> On 06 Mar 2016, at 09:57, Franziska Buehler
>><franziska.buehler.schmoc...@gmail.com> wrote:
>>
>> Hello,
>>
>> We already have some stricter siblings for existing rules.
>> But we don¹t have a numbering scheme for these new rules yet.
>> My suggestion would be as follows:
>>
>> The RuleIDs in CRS 3.0.0 count up in steps of 10. An obvious
>> possibility is to use the last digit.
>> Subsequent stricter clones of a main rule will be assigned the id of
>> the main rule plus the last digit incremented.
>>
>> For example, we produce a stricter sibling of the rule 920270. The new
>> stricter clone gets the id 920271. If we produce an even stricter
>> sibling, this rule will get the rule id 920272 and so on.
>>
>> We will not produce more than 5 different clones, because we defined
>> the paranoia levels from 0 to 4. So we have enough space.
>>
>> What are your thougts about this proposal?
>>
>> Regards,
>> Franziska
>> _______________________________________________
>> Owasp-modsecurity-core-rule-set mailing list
>> Owasp-modsecurity-core-rule-set@lists.owasp.org
>>
>>http://scanmail.trustwave.com/?c=4062&d=_Inc1hn7VdCEOQEjBDkdbbfAqmS8_XRmR
>>4XmpGaEqA&s=5&u=https%3a%2f%2flists%2eowasp%2eorg%2fmailman%2flistinfo%2f
>>owasp-modsecurity-core-rule-set
>


________________________________

This transmission may contain information that is privileged, confidential, 
and/or exempt from disclosure under applicable law. If you are not the intended 
recipient, you are hereby notified that any disclosure, copying, distribution, 
or use of the information contained herein (including any reliance thereon) is 
strictly prohibited. If you received this transmission in error, please 
immediately contact the sender and destroy the material in its entirety, 
whether in electronic or hard copy format.
_______________________________________________
Owasp-modsecurity-core-rule-set mailing list
Owasp-modsecurity-core-rule-set@lists.owasp.org
https://lists.owasp.org/mailman/listinfo/owasp-modsecurity-core-rule-set

Reply via email to