Coreruleset: Discussion about what to add in the official CRS Docker Image

[CRS-migration-bot]

_Issue originally created by user franbuehler on date 2019-01-24 09:56:47.
Link to original issue: https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/1290._

Chaim and I discussed about opening a PR for the Docker Image. And then discussing the changes in that PR.
But now I thought it would be easier to think first about what we want to have in the official Docker Image and then open a PR.

I am sure you have already looked at it, but here again what I have done:

docker-entrypoint.sh:

• Extended Python Code with if statements and added more CRS variables to docker-entrypoint.sh: https://github.com/franbuehler/modsecurity-crs-rp/blob/v3.1/docker-entrypoint.sh

Reverse Proxy Config:

• Added Apache Reverse Proxy httpd.conf (taken from Christian Folini's tutorials): https://github.com/franbuehler/modsecurity-crs-rp/blob/v3.1/Dockerfile#L10
  and https://github.com/franbuehler/modsecurity-crs-rp/blob/v3.1/httpd.conf

Pretty 403.html:

• Added custom 403.html with pretty CRS logo :-) and appropriate config to httpd.conf: https://github.com/franbuehler/modsecurity-crs-rp/blob/v3.1/Dockerfile#L11-L12 and https://github.com/franbuehler/modsecurity-crs-rp/blob/v3.1/httpd.conf#L226-L255

Dockerfile:

• Change to user www-data: https://github.com/franbuehler/modsecurity-crs-rp/blob/v3.1/Dockerfile#L21

• mkdir and change ownership: https://github.com/franbuehler/modsecurity-crs-rp/blob/v3.1/Dockerfile#L15-L16

Which parts would you see in the official image?

docker-compose
I have also added a sample or prepared docker-compose.yaml file:

• https://github.com/franbuehler/modsecurity-crs-rp/blob/v3.1/docker-compose.yaml

With prepared exclusion files:
https://github.com/franbuehler/modsecurity-crs-rp/blob/v3.1/REQUEST-900-EXCLUSION-RULES-BEFORE-CRS.conf and
https://github.com/franbuehler/modsecurity-crs-rp/blob/v3.1/RESPONSE-999-EXCLUSION-RULES-AFTER-CRS.conf

Let's discuss about that...

[CRS-migration-bot]

_User nicosmaris commented on date 2019-02-10 12:54:22:_

Are you considering only a single flavor of a docker image? Then which is the purpose of CRS on maintaining a docker image?

1. CI?
2. Easy installation of a CRS-enabled modsecurity and reverse proxy for demo
3. Easy installation of a CRS-enabled modsecurity and reverse proxy for production

Personally, I am more familiar with docker and testing than with anything related to security (modsecurity, crs, etc) so I prefer images that are for production use and maintained. That way, I don't need crontabs, I just use the following to pick the new image whenever it is pushed:

https://github.com/v2tec/watchtower

franbuehler you have done a nice job for CI. If a docker-compose.yml can be provided for production use in a simple set-it-and-forget-it way of installation (letting me as an extra step to do just the SSL), it will help.

[CRS-migration-bot]

_User danehrlich1 commented on date 2019-02-10 14:41:35:_

1. Can this proxy be set to allow SSL?

2. this will generate a self-signed cert on this server if placed in the Dockerfile: RUN openssl req -x509 -newkey rsa:4096 -keyout /etc/ssl/private/selfsigned.key.pem -out /etc/ssl/certs/selfsigned.cert.pem -days 1065 -nodes -subj "/C=xx/ST=x/L=x/O=x/OU=x/CN=localhost"

3. Then configure httpd.conf to listen for SSL. Something like the following will work and just needs to be slightly adjusted to however you want:

# Rewrites all HTTP requests to HTTPS
<VirtualHost *:80>
        RewriteEngine On
        RewriteCond %{HTTPS} off
        RewriteRule (.*) https://%{HTTP_HOST}/$1 [R,L]
</VirtualHost>


<VirtualHost _default_:443>
        #   SSL Engine Switch:
        #   Enable/Disable SSL for this virtual host.
        SSLEngine on

        SSLCipherSuite "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 \
                       EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 \
                       EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS"
        SSLProtocol -ALL +TLSv1.2
        SSLCertificateFile      /etc/ssl/certs/selfsigned.cert.pem
        SSLCertificateKeyFile /etc/ssl/private/selfsigned.key.pem
</VirtualHost>

[CRS-migration-bot]

_User spartantri commented on date 2019-02-11 18:35:12:_

Hi franbuehler , I think TLS support is a must have (with A+ from ssllabs) but use ACME or mod_md to get a valid cert from let's encrypt or provide it with the conf, and let self-signed certs as bad non-default option.
Also proxyprotocol support would be nice so that it can be behind an HAproxy and keep original client ip on the logs or at least remoteip support :)

[CRS-migration-bot]

_User nicosmaris commented on date 2019-02-17 00:17:08:_

As a demo of my previous comment you can look at the following which is work in progress.

https://github.com/nicosmaris/auro-update-crs

My question is whether it makes sense to pull updates of this repository (for example once every month). If yes, then an official image that stays up to date would help.

[CRS-migration-bot]

_User dune73 commented on date 2019-02-18 13:42:54:_

Reasonable thoughts, nicosmaris.

[CRS-migration-bot]

_User franbuehler commented on date 2019-02-20 15:32:11:_

csanders-git and I are working on these Docker images for modsecurity and modsecurity-crs.
The work is "in progress"...

[CRS-migration-bot]

_User danehrlich1 commented on date 2019-02-20 20:42:04:_

Franziska, do you need help on anything?

I’m an expert on Docker and Kubernetes, much more so than ModSecurity sadly, so maybe this is something I can actually help with.

On Feb 20, 2019, at 7:32 AM, Franziska Bühler wrote:

csanders-git and I are working on these Docker images for modsecurity and modsecurity-crs.
The work is "in progress"...

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[CRS-migration-bot]

_User franbuehler commented on date 2019-02-21 06:37:10:_

Many thanks, danehrlich1! I will contact you on Slack.

[CRS-migration-bot]

_User danehrlich1 commented on date 2019-03-14 05:19:21:_

Worked on this today. See https://github.com/danehrlich1/modsecurity-docker
and this issue where I basically just echo what franbuehler says above.

[CRS-migration-bot]

_User bittner commented on date 2019-04-10 14:06:38:_

Configuration files for loading the security2_module are missing, IIUC. This should go after the INSTALL instructions and into files placed in /etc/apache2/mods-available/:

# FILE: /etc/apache2/mods-available/security2.conf
<IfModule security2_module>
    Include modsecurity.d/owasp-crs/crs-setup.conf
    Include modsecurity.d/owasp-crs/rules/*.conf
</IfModule>

# FILE: /etc/apache2/mods-available/security2.load
LoadModule security2_module /usr/lib/apache2/modules/mod_security2.so

... and enabled via a2enmod security2 in the Dockerfile, probably.

[CRS-migration-bot]

_User franbuehler commented on date 2019-04-10 15:56:09:_

bittner: which Docker image are you talking about?

[CRS-migration-bot]

_User bittner commented on date 2019-04-10 17:09:30:_

franbuehler: The official CRS Docker image v3.1 from Docker Hub.

In the meantime we've noticed that the configuration I mentioned above is already included:

• modsecurity.d/include.conf -> contains the Include directives
• mods-available/modsecurity.load -> contains the LoadModule directive
• mods-available/modsecurity.conf -> loads the modsecurity.d/include.conf file

... and modsecurity is already symlinked in mods-enabled/.

Sorry for the noise! :expressionless:

[CRS-migration-bot]

_User franbuehler commented on date 2019-04-10 21:05:19:_

Great! No problem 😊

[CRS-migration-bot]

_User github-actions[bot] commented on date 2019-11-18 00:05:27:_

This issue has been open 120 days with no activity. Remove the stale label or comment, or this will be closed in 14 days

[CRS-migration-bot]

_User bittner commented on date 2019-11-18 15:38:43:_

This may be addressed in the long run by #1600.