The modseclogc is a ModSecurity audit log file manipulation and analysis tool, command-line or python module based.
Project
Installation
$ pip install modseclogc
Examples
View a request by unique ID:
$ modseclogc --match-id VtU2o38AAQEAAEV6AuwAAAAE modsec.log
--fc565b0b-A--
[01/Mar/2016:06:28:51 +0000] VtU2o38AAQEAAEV6AuwAAAAE 127.0.0.1 34882 127.0.0.1 80
[...snip...]
--fc565b0b-Z--
Display request IDs that match a path glob:
$ modseclogc --match-path /path/to/resource/** --show-id modsec.log
VtU2o38AAQEAAEV6Au0AAAAE
VtU2o38AAQEAAEV6AuwAAAAE
VtU2o38AAQEAAEV5BIgAAAAK
Display the request line and the request payload (modsec audit part “C”) of each audit record:
$ modseclogc --show-request-line --show-parts C modsec.log
OPTIONS /path/to/resource HTTP/1.1
GET /path/to/resource HTTP/1.1
POST /path/to/resource HTTP/1.1
--40382b65-C--
query=foo+bar&page=1
GET /path/to/resource HTTP/1.1
Generate a copy of the audit excluding the payloads (modsec audit part “C”) for a specific path glob, and compress the output:
$ zcat modsec_audit.log.gz \
| modseclogc \
--match-path /path/to/resource/** --hide-parts C \
--unmatched keep \
| gzip -9 > clean-modsec_audit.log.gz
Details
By default, all input records are matched. This is modified via the --match-* and --inverse arguments.
By default, all unmatched records are dropped. This is modified via the --unmatched argument.
Output operations (show, hide, etc) only apply to matched records (note that the --inverse argument inverts the matching algorithm, not this rule).
The audit log must be in Native format (see the SecAuditLogFormat modsec option).
Metadata
Release files for modseclogc 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| modseclogc-0.1.0.tar.gz | 23.8 kB | Without provenance | Details |
Release files / modseclogc-0.1.0.tar.gz
| Download URL | modseclogc-0.1.0.tar.gz |
|---|---|
| Size | 23.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6548cd9fd651f952f524e1b7079fe67bc6b213a4492a48c8162edcba080625ac
|
|
BLAKE2b-256 checksum How to use checksums |
9837d4855f4ebe348563c96e1f36c07fed7f6d3973edf4bea38864f5aa74081d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for modseclogc 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.