You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The chat is going to happen on https://owasp.slack.com in the channel #coreruleset on the first Monday of the month (usually), at 20:30 CET (CEST during summer in the Northern Hemisphere). Please note that we have a CRS calendar (maintained by @fzipi).
Archived previous meetings and their decision are here.
What happened in the meantime since the chat last month
Re-visiting this discussion: How does CRS want to approach modsecurity.conf-recommended in the future? The situation is clearly different, now, in 2025.
In the past, there was friction with the engine's previous owner (e.g. CRS advocated for enabling rule 200006 (allow JSON subtypes) by default, but we were told 'no'.)
We previously discussed the idea that one day CRS could handle everything from modsecurity.conf-recommended directly within CRS, so that all config would be in one place and CRS could control which "default" rules to enable/disable.
There is also now the potential to work with team ModSecurity to come up with a solution (e.g. keep modsecurity.conf-recommended but change the defaults to be more sensible/CRS-friendly).
Why re-open this discussion now? It follows on from issue 9EA-241022. We removed several default allowed content types (including some "+json" subtypes). The open question remaining was: do we want to enable 'recommended' rule 200006 by default and retire rule 200001? And, more broadly, how do we want to work with/around modsecurity.conf-recommended going forwards?
How does CRS want to approach modsecurity.conf-recommended in the future?
🔵 As a first step: Xanadu will open two issues in ModSecurity, one for "default rules" and one for "error handling"
CRS Community Call
🔵 It's time to launch a social media campaign with as many personal / individual posts as possible
Uh oh!
There was an error while loading. Please reload this page.
This is the Agenda for the Monthly CRS Chat.
The chat is going to happen on https://owasp.slack.com in the channel #coreruleset on the first Monday of the month (usually), at 20:30 CET (CEST during summer in the Northern Hemisphere). Please note that we have a CRS calendar (maintained by @fzipi).
Archived previous meetings and their decision are here.
What happened in the meantime since the chat last month
Outside development
Inside development
Rules
CRS Sandbox
Security
Plugins
Documentation and Public Relations
Project Administration and Sponsor relationships
Tools
Containers
Read-only Root Filesystem
(only for nginx based images for now).Project discussions and decisions
modsecurity.conf-recommended
in the future? The situation is clearly different, now, in 2025.modsecurity.conf-recommended
directly within CRS, so that all config would be in one place and CRS could control which "default" rules to enable/disable.modsecurity.conf-recommended
but change the defaults to be more sensible/CRS-friendly).modsecurity.conf-recommended
going forwards?Rules development, key project numbers
PRs that have been merged since the last meeting
RootAndLeafOpenCamera.jpg
(933150 PL-1, 933160 PL-1) #4016We merged 19 PRs since the last monthly project chat.
Open PRs
Open PRs marked DRAFT or work in progress or needs action
at
to PL-2 (932370 PL-1, 932371 PL-2) #4015How to get to our slack and join the meeting?
If you are not yet on the OWASP Slack, here is your invite: https://owasp.org/slack/invite .
Everybody is welcome to join our community chat.
The text was updated successfully, but these errors were encountered: