anchor.diff:  
   #
   # Set the following policy settings here and they will be propagated to the 30 rules
  -# file (modsecurity_crs_30_http_policy.conf) by using macro expansion.
  +# file (modsecurity_crs_30_http_policy.conf) by using macro expansion.  
   # If you run into false positves, you can adjust the settings here.
   #
   SecAction \
  
positive.code: # operators.  If you have an earlier version, edit the 49/59 files directly to
  # set the appropriate anomaly score levels.
  #
  # You should set the score to the proper threshold you would prefer. If set to "5"
  # 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 "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.
  #
  SecAction \
    "id:'900002', \
    phase:1, \
    t:none, \
    setvar:tx.inbound_anomaly_score_level=<%= @inbound_anomaly_threshold -%>, \
    nolog, \
    pass"
  
  
  SecAction \
    "id:'900003', \
    phase:1, \
    t:none, \
    setvar:tx.outbound_anomaly_score_level=<%= @outbound_anomaly_threshold -%>, \
    nolog, \
    pass"
  
  
  #
  # -- [[ Collaborative Detection Blocking ]] -----------------------------------------------
  #
  # This is a collaborative detection mode where each rule will increment an overall
  
negative.code: 
  
  #
  # -- [[ Collaborative Detection Scoring Initialization and Threshold Levels ]] ------------------------------
  #
  # These variables are used in macro expansion in the 49 inbound blocking and 59
  # outbound blocking files.
  