Gecko [ georgetownmover.com ]

Name	Size	Permission	Date
REQUEST-900-EXCLUSION-RULES-BEFORE-CRS.conf	7.48 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-901-INITIALIZATION.conf	13.58 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-903.9001-DRUPAL-EXCLUSION-RULES.conf	13.31 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-903.9002-WORDPRESS-EXCLUSION-RULES.conf	25.28 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-903.9003-NEXTCLOUD-EXCLUSION-RULES.conf	10.46 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-903.9004-DOKUWIKI-EXCLUSION-RULES.conf	7.71 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-903.9005-CPANEL-EXCLUSION-RULES.conf	1.9 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-903.9006-XENFORO-EXCLUSION-RULES.conf	17.97 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-905-COMMON-EXCEPTIONS.conf	1.59 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-910-IP-REPUTATION.conf	10.16 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-911-METHOD-ENFORCEMENT.conf	2.62 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-912-DOS-PROTECTION.conf	10.42 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-913-SCANNER-DETECTION.conf	6.97 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-920-PROTOCOL-ENFORCEMENT.conf	53.07 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-921-PROTOCOL-ATTACK.conf	16.41 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-922-MULTIPART-ATTACK.conf	4.38 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-930-APPLICATION-ATTACK-LFI.conf	5.89 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-931-APPLICATION-ATTACK-RFI.conf	5.62 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-932-APPLICATION-ATTACK-RCE.conf	53.59 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-933-APPLICATION-ATTACK-PHP.conf	31.93 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-934-APPLICATION-ATTACK-NODEJS.conf	3.9 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-941-APPLICATION-ATTACK-XSS.conf	39.52 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-942-APPLICATION-ATTACK-SQLI.conf	68.87 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-943-APPLICATION-ATTACK-SESSION-FIXATION.conf	5.16 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-944-APPLICATION-ATTACK-JAVA.conf	15 KB	-rw-r--r--	2023-08-02 10:15
REQUEST-949-BLOCKING-EVALUATION.conf	4.07 KB	-rw-r--r--	2023-08-02 10:15
RESPONSE-950-DATA-LEAKAGES.conf	4.67 KB	-rw-r--r--	2023-08-02 10:15
RESPONSE-951-DATA-LEAKAGES-SQL.conf	17.55 KB	-rw-r--r--	2023-08-02 10:15
RESPONSE-952-DATA-LEAKAGES-JAVA.conf	3.5 KB	-rw-r--r--	2023-08-02 10:15
RESPONSE-953-DATA-LEAKAGES-PHP.conf	4.91 KB	-rw-r--r--	2023-08-02 10:15
RESPONSE-954-DATA-LEAKAGES-IIS.conf	5.7 KB	-rw-r--r--	2023-08-02 10:15
RESPONSE-959-BLOCKING-EVALUATION.conf	4.18 KB	-rw-r--r--	2023-08-02 10:15
RESPONSE-980-CORRELATION.conf	6.71 KB	-rw-r--r--	2023-08-02 10:15
RESPONSE-999-EXCLUSION-RULES-AFTER-CRS.conf	3 KB	-rw-r--r--	2023-08-02 10:15
crawlers-user-agents.data	786 B	-rw-r--r--	2023-08-02 10:15
iis-errors.data	551 B	-rw-r--r--	2023-08-02 10:15
java-classes.data	933 B	-rw-r--r--	2023-08-02 10:15
java-code-leakages.data	264 B	-rw-r--r--	2023-08-02 10:15
java-errors.data	240 B	-rw-r--r--	2023-08-02 10:15
lfi-os-files.data	30.48 KB	-rw-r--r--	2023-08-02 10:15
php-config-directives.data	5.28 KB	-rw-r--r--	2023-08-02 10:15
php-errors.data	8.99 KB	-rw-r--r--	2023-08-02 10:15
php-function-names-933150.data	683 B	-rw-r--r--	2023-08-02 10:15
php-function-names-933151.data	20.78 KB	-rw-r--r--	2023-08-02 10:15
php-variables.data	224 B	-rw-r--r--	2023-08-02 10:15
restricted-files.data	2 KB	-rw-r--r--	2023-08-02 10:15
restricted-upload.data	390 B	-rw-r--r--	2023-08-02 10:15
scanners-headers.data	216 B	-rw-r--r--	2023-08-02 10:15
scanners-urls.data	418 B	-rw-r--r--	2023-08-02 10:15
scanners-user-agents.data	4.75 KB	-rw-r--r--	2023-08-02 10:15
scripting-user-agents.data	717 B	-rw-r--r--	2023-08-02 10:15
sql-errors.data	1.85 KB	-rw-r--r--	2023-08-02 10:15
unix-shell.data	1.35 KB	-rw-r--r--	2023-08-02 10:15
windows-powershell-commands.data	3.83 KB	-rw-r--r--	2023-08-02 10:15

Rename

# ------------------------------------------------------------------------
# OWASP ModSecurity Core Rule Set ver.3.3.5
# Copyright (c) 2006-2020 Trustwave and contributors. All rights reserved.
# Copyright (c) 2021-2023 Core Rule Set project. All rights reserved.
#
# The OWASP ModSecurity Core Rule Set is distributed under
# Apache Software License (ASL) version 2
# Please see the enclosed LICENSE file for full details.
# ------------------------------------------------------------------------

# You should set the score to the proper threshold you would prefer. If kept at "@gt 0"
# it will work similarly to previous Mod CRS rules and will create an event in the error_log
# file if there are any rules that match.  If you would like to lessen the number of events
# generated in the error_log file, you should increase the anomaly score threshold to
# something like "@gt 20".  This would only generate an event in the error_log file if
# there are multiple lower severity rule matches or if any 1 higher severity item matches.
#
# You should also set the desired disruptive action (deny, redirect, etc...).
#

#
# -= Paranoia Level 0 (empty) =- (apply unconditionally)
#

# Summing up the anomaly score.

# NOTE: tx.anomaly_score should not be set initially, but masking would lead to difficult bugs.
# So we add to it.
SecRule TX:PARANOIA_LEVEL "@ge 1" \
    "id:959060,\
    phase:4,\
    pass,\
    t:none,\
    nolog,\
    setvar:'tx.outbound_anomaly_score=+%{tx.outbound_anomaly_score_pl1}'"

SecRule TX:PARANOIA_LEVEL "@ge 2" \
    "id:959061,\
    phase:4,\
    pass,\
    t:none,\
    nolog,\
    setvar:'tx.outbound_anomaly_score=+%{tx.outbound_anomaly_score_pl2}'"

SecRule TX:PARANOIA_LEVEL "@ge 3" \
    "id:959062,\
    phase:4,\
    pass,\
    t:none,\
    nolog,\
    setvar:'tx.outbound_anomaly_score=+%{tx.outbound_anomaly_score_pl3}'"

SecRule TX:PARANOIA_LEVEL "@ge 4" \
    "id:959063,\
    phase:4,\
    pass,\
    t:none,\
    nolog,\
    setvar:'tx.outbound_anomaly_score=+%{tx.outbound_anomaly_score_pl4}'"

# Alert and Block on High Anomaly Scores - this would block outbound data leakages
#
# Note: This rule also sets the 'tx.anomaly_score' variable.
# That variable name was formerly used in CRS, but not any longer.
# However, Jwall AuditConsole depends on this exact variable name.
# Without setting it, the 'Outbound Score' in the AuditConsole GUI would always be 0.

SecRule TX:OUTBOUND_ANOMALY_SCORE "@ge %{tx.outbound_anomaly_score_threshold}" \
    "id:959100,\
    phase:4,\
    deny,\
    t:none,\
    msg:'Outbound Anomaly Score Exceeded (Total Score: %{TX.OUTBOUND_ANOMALY_SCORE})',\
    tag:'anomaly-evaluation',\
    ver:'OWASP_CRS/3.3.5',\
    setvar:'tx.anomaly_score=+%{tx.outbound_anomaly_score}'"

SecRule TX:EXECUTING_PARANOIA_LEVEL "@lt 1" "id:959011,phase:3,pass,nolog,skipAfter:END-RESPONSE-959-BLOCKING-EVALUATION"
SecRule TX:EXECUTING_PARANOIA_LEVEL "@lt 1" "id:959012,phase:4,pass,nolog,skipAfter:END-RESPONSE-959-BLOCKING-EVALUATION"
#
# -= Paranoia Level 1 (default) =- (apply only when tx.executing_paranoia_level is sufficiently high: 1 or higher)
#

SecRule TX:EXECUTING_PARANOIA_LEVEL "@lt 2" "id:959013,phase:3,pass,nolog,skipAfter:END-RESPONSE-959-BLOCKING-EVALUATION"
SecRule TX:EXECUTING_PARANOIA_LEVEL "@lt 2" "id:959014,phase:4,pass,nolog,skipAfter:END-RESPONSE-959-BLOCKING-EVALUATION"
#
# -= Paranoia Level 2 =- (apply only when tx.executing_paranoia_level is sufficiently high: 2 or higher)
#

SecRule TX:EXECUTING_PARANOIA_LEVEL "@lt 3" "id:959015,phase:3,pass,nolog,skipAfter:END-RESPONSE-959-BLOCKING-EVALUATION"
SecRule TX:EXECUTING_PARANOIA_LEVEL "@lt 3" "id:959016,phase:4,pass,nolog,skipAfter:END-RESPONSE-959-BLOCKING-EVALUATION"
#
# -= Paranoia Level 3 =- (apply only when tx.executing_paranoia_level is sufficiently high: 3 or higher)
#

SecRule TX:EXECUTING_PARANOIA_LEVEL "@lt 4" "id:959017,phase:3,pass,nolog,skipAfter:END-RESPONSE-959-BLOCKING-EVALUATION"
SecRule TX:EXECUTING_PARANOIA_LEVEL "@lt 4" "id:959018,phase:4,pass,nolog,skipAfter:END-RESPONSE-959-BLOCKING-EVALUATION"
#
# -= Paranoia Level 4 =- (apply only when tx.executing_paranoia_level is sufficiently high: 4 or higher)
#

#
# -= Paranoia Levels Finished =-
#
SecMarker "END-RESPONSE-959-BLOCKING-EVALUATION"