Feature/Auto-update OWASP CRS on container start (ModSecurity WAF)

[Divyateja2709]

Hi @adrianwinckles , this is my new PR .this adds an optional way to keep the OWASP Core Rule Set (CRS) up-to-date in the ModSecurity Apache WAF honeypot container.

Changes Made

-Dockerfile: installs necessary packages, and copies a new CRS updater script into the image and makes it executable.
-crs_update.sh (new): a script that will install/download the requested (or default latest) version of CRS in the target rules directory used by the container.
-modsec_entry.sh: this entry script will first call the CRS updater (with an environment flag), and then proceeds with the normal WAF start.

Why

Up-to-date CRS would mean improved coverage/log data. A user doesn't want to have to rebuild the image every time CRS has a new release.

How to Use

At container run time, set an environment variable, such as CRSUPDATE=true, and optionally the desired version using CRSVERSION=, then launch the container as usual.

could you please review this PR and confirm whether this CRS auto-update approach (Dockerfile + crs_update.sh + modsec_entry.sh changes) is a good direction to pursue for the project?

[adrianwinckles]

I like that approach its makes sense

[Divyateja2709]

I like that approach its makes sense

Hi @adrianwinckles , i have worked on chameleon persona system mainly . the first 7 prs were inclined towards the crs auto update side and the main focus was on developing websites mimicing cve s of drupal and wordpress
i m planning to add sharepoint next .