| 1 |
On 12/18/2020 07:51 PM, Jigme Datse wrote: |
| 2 |
> On Fri, 18 Dec 2020 18:20:44 -0700 |
| 3 |
> thelma@×××××××××××.com wrote: |
| 4 |
> |
| 5 |
>> ModSecurity is installed: |
| 6 |
>> APACHE2_OPTS="-D DEFAULT_VHOST -D INFO -D SSL -D SSL_DEFAULT_VHOST -D |
| 7 |
>> LANGUAGE -D PHP -D SECURITY" |
| 8 |
>> |
| 9 |
>> In which file I have to enable "SecStatusEngine On" ? |
| 10 |
>> |
| 11 |
>> |
| 12 |
> |
| 13 |
> Not worked with Apache for a bit, but I think this is needed in your |
| 14 |
> Apache configuration. Though I'm not sure if it's per virtual server |
| 15 |
> or if it's a global option. |
| 16 |
> |
| 17 |
> If this isn't helpful, I'm just sitting here waiting for stuff to |
| 18 |
> happen, and saw your message, and just thought I'd look to see if I can |
| 19 |
> maybe help. |
| 20 |
> |
| 21 |
|
| 22 |
Looking at FAQ in: |
| 23 |
https://github.com/SpiderLabs/ModSecurity/wiki/ModSecurity-Frequently-Asked-Questions-(FAQ) |
| 24 |
|
| 25 |
Should I initially set the SecRuleEngine to On? |
| 26 |
|
| 27 |
No. Every Ruleset can have false positive in new environments and any |
| 28 |
new installation should initially use the log only Ruleset version or if |
| 29 |
no such version is available, set ModSecurity to Detection only using |
| 30 |
the SecRuleEngine DetectionOnly command. After running ModSecurity in a |
| 31 |
detection only mode for a while review the evens generated and decide if |
| 32 |
any modification to the rule set should be made before moving to |
| 33 |
protection mode. |
Archives