blog: add CRS migration series part 4 — anomaly scoring and reporting#499
Merged
blog: add CRS migration series part 4 — anomaly scoring and reporting#499
Conversation
Covers the anomaly scoring refactor, the new tx.reporting_level model replacing 980xxx rules, tx.early_blocking, and the impact of paranoia level redistribution on anomaly score baselines. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sets refLinksErrorLevel=WARNING so cross-post ref links don't break the build when sibling posts don't yet exist on the same branch. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The author is already shown from the front matter. Adds the related-pages shortcode to cross-link migration series posts. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Deploying website with
|
| Latest commit: |
c2ae1b5
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4839c252.website-1u6.pages.dev |
| Branch Preview URL: | https://blog-crs-migration-part-4.website-1u6.pages.dev |
theseion
requested changes
Apr 19, 2026
Co-authored-by: Max Leske <250711+theseion@users.noreply.github.com>
- Clarify that per-severity and threshold variables are unchanged from CRS 3 - List the actual CRS 4 accumulator variables (per-PL, per-direction, and combined inbound+outbound aggregates) so the custom-rule advice below has concrete names to reference - Correct the PL redistribution claim for PL2+ baselines: rules shifted up do not add coverage at levels that already included them - Link "Reporting Model" reference to the section anchor - Describe the new reporting flow as a restructure within the 980xxx range, with a single phase 5 action covering both directions
Member
Author
|
@theseion Ok, just doing a |
theseion
requested changes
Apr 19, 2026
Co-authored-by: Max Leske <250711+theseion@users.noreply.github.com>
theseion
approved these changes
Apr 20, 2026
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
2 participants
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.
what
Add Part 4 of the CRS 3.3 → 4.25 LTS migration blog series covering anomaly scoring, the new reporting model, early blocking, and paranoia level redistribution.
why
Continues the migration guide series to help CRS users understand the scoring and reporting changes between CRS 3 and CRS 4, which are among the most impactful areas
during migration.