From 8a80105c071cc5ed6109e1d4f0213d0fa581c542 Mon Sep 17 00:00:00 2001 From: Angel Date: Thu, 19 Dec 2024 17:00:43 -0500 Subject: [PATCH] Apply suggestions from code review Co-authored-by: lena-larionova <54370747+lena-larionova@users.noreply.github.com> --- app/_hub/kong-inc/injection-protection/overview/_index.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/app/_hub/kong-inc/injection-protection/overview/_index.md b/app/_hub/kong-inc/injection-protection/overview/_index.md index 951f86096c5..cb83870a69f 100644 --- a/app/_hub/kong-inc/injection-protection/overview/_index.md +++ b/app/_hub/kong-inc/injection-protection/overview/_index.md @@ -81,12 +81,16 @@ Logs are automatically collected when you enable the Injection Protection plugin * [UDP Log](/hub/kong-inc/udp-log/) * [{{site.konnect_short_name}} Advanced Analytics](/konnect/analytics/) -The following is an example of the information that is logged by the Injection Protection plugin: +Here's a sample log entry created by the Injection Protection plugin. ``` threat detected: 'sql', action taken: log_only, found in path_and_query, query param value: foo: insert into test ``` - +Where: +* The plugin detected a SQL injection threat +* It created a log entry but took no other actions +* The threat was found in the request path or query +* The inserted snippet is `foo: insert into test` ## Get started with the Injection Protection plugin * [Configuration reference](/hub/kong-inc/injection-protection/configuration/)