ModSecurity With The OWASP Core Rule Set, Pinned

ModSecurity from EPEL in httpd with the OWASP Core Rule Set 4.30, its tarball pinned by the SHA-256 of a signature-checked copy: anomaly scoring at paranoia 1, each change checked in a copy of the httpd tree first, loopback until you open it. The live test sends a SQL injection, a script tag, a scanner and a traversal; each is refused by its own rule. Original role, live-tested on Rocky Linux 10.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

ansibleMulti-cloud & platform-agnosticSecurity & Identityv1.0.0live-tested

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Scheduled Lynis Audit That Fails On A Low Score A Suricata IDS With ET Open And A Canary Rule AIDE, A Baseline And A Timer That Notices A Change An LDAP Directory That Refuses Anonymous Reads An MIT Kerberos KDC With An ACL And A Lockout Authelia SSO Portal, Secrets Kept Out Of The Config, Proven By A Login Bandit, A shell=True Call Found At High Severity Boundary, Run To The Controller's Door Twice

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_modsecurity_crs" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-modsecurity-crs/any"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.