-
Notifications
You must be signed in to change notification settings - Fork 412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(asm): improve rasp call mechanism #9954
chore(asm): improve rasp call mechanism #9954
Conversation
|
…PPSEC-54272_improve_rasp_call_mechanism
Datadog ReportBranch report: ✅ 0 Failed, 109880 Passed, 3927 Skipped, 6m 11.25s Total duration (3m 21.04s time saved) |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9954 +/- ##
===========================================
- Coverage 73.94% 10.56% -63.38%
===========================================
Files 1402 1367 -35
Lines 130460 127989 -2471
===========================================
- Hits 96465 13520 -82945
- Misses 33995 114469 +80474 ☔ View full report in Codecov by Sentry. |
BenchmarksBenchmark execution time: 2024-07-26 13:41:01 Comparing candidate commit 13ccfe4 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 214 metrics, 2 unstable metrics. |
Unless explicitly disabled by an environment variable, the WAF is used for each supported exploit prevention endpoint. This PR enhances this behaviour by leveraging the WAF's "known addresses" feature, which, as of version 1.19.0, skips disabled rules, to prevent calling the WAF if unnecessary.
Now, calls to the WAF will only occur if at least one specific rule for that endpoint has been enabled via remote configuration.
Also:
APPSEC-54272
Checklist
Reviewer Checklist