owasp-modsecurity / owasp-modsecurity/ModSecurity
[Idea] Add variable support for SecAuditLog
Open
Nobody has claimed this yet.
new feature
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
I would like to provide a log file separately for each user and their website. Is there a chance to do this using variables SecAuditLog?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the SecAuditLog directive documentation and tracing how audit-log paths and variables are currently handled; the issue names no files or tests. Done means an agreed approach for variable support, implementation coverage, and validation of separate per-user and per-site log paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100