Repository navigation
add crs observation and dashboard monitoring - #74
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enable OWASP CRS observation explicitly with installer v1.65
--update --enable-crs. Existing high-confidence AppSec rules keep blocking; CRS runs out of band and retains native observation alerts while suppressing CRS scenario events. Install only the CRS rule package, preserve Hub-managed files and ordinary-update choices, and reject custom acquisition layouts that need operator review.The existing CrowdSec WAF tab separates installer configuration from observed CRS matches, reports attack-pattern rule hits with readable families, and distinguishes disabled, unverified, unavailable, stale and in-band states. Exclude CRS diagnostic counters from observation totals and avoid duplicating CRS observations in the other-rules list. Match counts are neither unique requests nor bans.
Security scope:
setup-npmplus.shadds the policy and bumps the atomic safe-update wrapper to v6 so the bouncer config is snapshotted and restored with CrowdSec state. Backend CrowdSec configuration/metrics helpers expose only non-secret values; the existing admin gate, fixed metrics URL and response limits remain. No dependency or database migration is added. README, operations guidance and changelog describe opt-in and upstream compatibility checks.Validation: 214 backend tests, schema validation, 23 frontend tests, TypeScript, production build and strict per-package Biome; Linux recovery/key-migration/CRS/upstream-sync contracts and ShellCheck; negative verification of observation separation, stale status, configuration, scenario suppression, reconfiguration preservation and rollback pins. Isolated systemd/Docker probes confirm benign 200,
.env403, SQLi/XSS/RCE observation alerts and no IP ban after repeated XSS probes, including a test with the upstream behavioral-ban scenario installed. Real-browser fixture and actual Docker UI checks cover desktop and phones. All PR checks pass, including final-image scanning, browser security, both installer variants and Debian restore. Actual failed-update rollback, backup/restore and controlled restart preserve CRS and existing enforcement.