-
Notifications
You must be signed in to change notification settings - Fork 439
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
appsec: missing SQLi and LFI RC capabilities #2851
Conversation
BenchmarksBenchmark execution time: 2024-09-09 16:30:45 Comparing candidate commit 4eae623 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 59 metrics, 0 unstable metrics. |
@@ -409,7 +410,14 @@ func (a *appsec) enableRASP() { | |||
if err := remoteconfig.RegisterCapability(remoteconfig.ASMRASPSSRF); err != nil { | |||
log.Debug("appsec: Remote config: couldn't register RASP SSRF: %v", err) | |||
} | |||
// TODO: register other RASP capabilities when supported | |||
if err := remoteconfig.RegisterCapability(remoteconfig.ASMRASPSQLI); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WDYT of moving the calls to RegisterCapability
into the WAF listener's instantiations, like setting the SQLi capability when the SQL listener is being setup?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question asked
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all good, implem details discussed over standup: RC capabilities must be sent regardless of the actual app capabilities.
Signed-off-by: Eliott Bouhana <[email protected]>
4eae623
to
b252a99
Compare
What does this PR do?
Reviewer's Checklist
Unsure? Have a question? Request a review!