mcpField
I
implementing-web-application-logging-with-modsecurity

implementing-web-application-logging-with-modsecurity

github.com/mukul975Security35.2k135 installsUpdated 8w ago
Repository

About implementing-web-application-logging-with-modsecurity

A deployment and tuning guide for web application logging with ModSecurity, aimed at teams configuring web-server security controls. It covers OWASP CRS rule deployment, audit logging, false-positive tuning, and forwarding events to a SIEM.

Key features

  1. 01Configure ModSecurity detection and blocking
  2. 02Deploy OWASP CRS rules
  3. 03Set relevant-only audit logging
  4. 04Tune false positives and exclusions
  5. 05Forward audit logs to a SIEM

Use cases

  1. 01Establishing web application logging
  2. 02Aligning controls with compliance requirements
  3. 03Correlating WAF events in a SIEM

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill implementing-web-application-logging-with-modsecurity

After installing, type/implementing-web-application-logging-with-modsecurityin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

LICENSE
references/
api-reference.md
scripts/
agent.py

Details

From the project README

Implementing Web Application Logging with ModSecurity

Overview

ModSecurity is an open-source WAF engine that works with Apache, Nginx, and IIS. The OWASP Core Rule Set (CRS) provides generic attack detection rules covering SQL injection, XSS, RCE, LFI, and other OWASP Top 10 attacks. ModSecurity logs full request/response data in audit logs for forensic analysis and generates alerts that feed into SIEM platforms.

When to Use

  • When deploying or configuring implementing web application logging with modsecurity capabilities in your environment
  • When establishing security controls aligned to compliance requirements
  • When building or improving security architecture for this domain
  • When conducting security assessments that require this implementation

Prerequisites

  • Web server (Apache 2.4+ or Nginx) with ModSecurity v3 module
  • OWASP CRS v4.x installed
  • Log aggregation infrastructure (ELK, Splunk, or Wazuh)

Steps

  1. Install ModSecurity and configure SecRuleEngine in DetectionOnly mode
  2. Deploy OWASP CRS v4 and set paranoia level (PL1-PL4)
  3. Configure SecAuditEngine for relevant-only logging
  4. Tune false positives with SecRuleRemoveById and rule exclusions
  5. Switch to blocking mode (SecRuleEngine On) after tuning period
  6. Forward audit logs to SIEM for correlation and alerting

Expected Output

ModSecurity: Warning. Pattern match "(?:union\s+select)" [file "/etc/modsecurity/crs/rules/REQUEST-942-APPLICATION-ATTACK-SQLI.conf"] [line "45"] [id "942100"] [msg "SQL Injection Attack Detected via libinjection"] [severity "CRITICAL"]

Comments

Markdown supported